CS Department

Project ID: CS-452-P1-M18

Year/month:2024/1

Automation of Academic department

activities

Dept. of computer science

Faculty of Computer and Information Systems

Umm Al-Qura University, KSA

This project report is submitted to the Department of computer science at Umm Al-Qura University in
partial fulfillment of the requirements for the degree of Bachelor of Science in Computer Science.

Author(s):
Abdulrahman Mohsen Alabdali

Laith Abdulaziz Alzahrani

Marwan abduallah alramadani

Abdulmajed hamed althaqfi

University supervisor(s):
Mohamed nour
Computer scientist department

i
Intellectual Property Right Declaration

This is to declare that the work under the supervision of Mohamed Nour having title “ Automation of
Academic department activities” carried out in partial fulfillment of the requirements of Bachelor of
Science in is the sole property of the Umm Al Qura University and the respective supervisor and is
protected under the intellectual property right laws and conventions. It can only be considered/ used for
purposes like extension for further enhancement, product development, adoption for
commercial/organizational usage, etc., with the permission of the University and respective supervisor.

This above statement applies to all students and faculty members.

Date: 2/1/2024

Author(s):

Name: Abdulrahman Alabdali Signature: 441009351

Name: Abdulmajed hamed althaqfi Signature: 442002677

Name: Marwan abduallah alrmadani Signature: 441003415

Name: Laith Abdulaziz Alzahrani Signature: 442008648

Supervisor(s):

Name: Mohamed Nour Signature:

Anti-Plagiarism Declaration

ii
This is to declare that the above publication produced under the supervision of Mohamed Nour having
title “Automation of Academic department activities” is the sole contribution of the author(s) and no part
hereof has been reproduced illegally (cut and paste) which can be considered as Plagiarism. All referenced
parts have been used to argue the idea and have been cited properly. I/We will be responsible and liable
for any consequence if violation of this declaration is proven.

Date: 2/1/2024

Author(s):

Name: Abdulrahman Alabdali Signature: 441009351

Name: Abdulmajed hamed althaqfi Signature: 442002677

Name: Marwan abduallah alrmadani Signature: 441003415

Name: Laith Abdulaziz Alzahrani Signature: 442008648

ABSTRACT

This project aims to automate and organize the curricula of an academic

college department by implementing a database system. The system will

iii
 allow the department to enter or select pre-defined templates, and the
system will automatically populate the templates with the required
curriculum information. The system will also provide flexibility for
modifying and changing the curricula as needed, while ensuring access
control restrictions to authorized personnel.

Table of Contents
CHAPTER 1 - introduction
1.1 Introduction………………………………………………………….……..3
1.2 Problem domain ……………………………………………………………
3
1.3 Problem statement…………………………………………………………
3
1.4 Existing System ……………………………………………………………3
1.4.1 Existing system description ……………………………………………3
1.4.2 Problems in the existing system ………………………………………4

iv
Chapter 2 – System Analysis

2.1 overall Description ……………………………………..………………………

5
2.1.1 product elements…………………………………..…………………...……
5
2.1.2 product elements data ………………………………..……………..………
5

2.2 Functional requirements ……………………………………..…………………

7

2.3 Non-functional requirements ……………………………………..……………8

2.3.1 product elements…………………………………..…………………...……
8
2.3.2 product elements…………………………………..…………………...……
8
2.3.3 product elements…………………………………..…………………...……
8
2.3.4 product elements…………………………………..…………………...……
8

2.4 Structural design …………………………………………………..……………

9
2.4.1 Use case diagram…………………………………..…………………...……
9
2.4.1.1 Use case descriptions………..………………..…………………...……10
2.4.2 Class diagram…………………………….………..…………………...…12
2.4.3 ERD diagram …………………………….………..………………...……13

2.5 Proposed system ………………………………………..…………..…………15

2.5.1 Aims and objectives……………………………..…………………...…….15
2.5.2 Proposed system features……………………………………………...
…..15

Chapter 3 – Design Considerations

v
3.1 Design Constraints………………………………………..………..…………17
3.1.1 Hardware and software environment……………………………..……17
3.1.1.1 Hardware Environment …………………………………..…………17
3.1.1.2 Software Environment ………………………………………..………17

3.2 Architectural Strategies ………………………………………..………………

18
3.2.1 Project Methodology ……………………………..…………………...…18
3.2.1.1 Agile Project Methodology……………………………………………18
3.2.2 Architectural pattern……………………………..…………………...…19

Chapter 4 - System Design

4.1 System Architecture………………………………………………..…………21
4.1.1 Major Modules……………………………..………………...………...…21
4.1.2 System Architecture Design…………………………………………...…..22

Chapter 5 - System Implementation & Validation

5.1 Introduction ………………………………………...………..………………24

5.2 Snapshots of main execution screens of the website……………..…………24

5.2.1 Home Page………………………………..………..…………………...…24
5.2.2 The Courses Plan page………………………………………………...…28
5.2.3 The Program Equivalency Module page……………………………...…31
5.2.4 The Word Document Table Extractor page………………………...……33

Chapter 6 - Conclusion & Future Work

6.1 Conclusion…………………………………………...………..………………40

6.2 Project Achievements………………………..……...………..………………40

6.3 Restrictions………………………..……..……..…...………..………………41

6.4 Future Work……………………………………...………..………..…………41

6.5 REFRENCES………………………………………...……….………………42

vi
 List of Figures

Figure 1: Use Case Diagram ……………................................................................................................. 9

Figure2. 1: class diagram. ........................................................................................................................

12

Figure2. 2: ERD diagram. ........................................................................................................................

13

Figure 3: Agile methodology................................................................................................................. 18

Figure 4: System Architecture Design...................................................................................................

22

Figure 5.1: UI for Home Page..................................................................................................................

25

Figure 5.2: UI for the Courses Plan page..............................................................................................

28

Figure 5.3: UI for Home Page..................................................................................................................

31

Figure 5.4.1: Word Document Table Extractor page..........................................................................

33

Figure 5.4.2: Word Document Table Extractor page..........................................................................

34

Figure 5.4.3: Word Document Table Extractor page..........................................................................

34

Figure 5.4.4: Word Document Table Extractor page..........................................................................

35

Figure 5.4.5: Word Document Table Extractor page..........................................................................

35

Figure 5.4.6: Word Document Table Extractor page..........................................................................

36

Figure 5.4.7: Word Document Table Extractor page..........................................................................

36

vii
viii
 List of Tables

Table 1: Compare services and features between other applications and our application .......
3

Table 2.1: Use case Description for Evaluate and manage program equivalencies...................
10

Table 2.2: Use case Description for validating and verifying the validity of program
equivalencies....10

Table 2.3: Use case Description for Auto Generate Report.............................................................

10

Table 2.4: Use case Description for Program and Course Information Management..............
11

Table 2.5: Use case Description for Manage Information................................................................

11

ix
 CHAPTER 1
INTRODUCTION

1
1.1 Introduction
In recent decades, the university education sector has undergone a radical shift towards relying
on technology to improve teaching and learning processes. With the rapid advancement in
technologies, it has become imperative to implement digital solutions and automation operations
to enhance the experience of Academic department activities.

1.2 Problem domain

The problem domain addressed by this project revolves around the challenges faced by
computer science academic departments in efficiently managing and adapting to the
complexities of curricula. Currently, many institutions rely on manual methods or disparate
systems, leading to inefficiencies and potential errors in keeping up with evolving educational
standards.
1.3 Problem statement
The manual management of curricula in computer science academic departments lacks efficiency,
introduces potential errors, and hinders collaboration. Existing systems do not adequately address
template-based curricula management, program equivalency. Faculty members face challenges in
data entry, modification, and access control also . This project aims to develop a customized
database system to automate and organize curricula, improving efficiency, collaboration, and
accessibility while addressing these knowledge gaps.

1.4 Existing System

We searched for some related ideas, and we did not find many systems or applications that related
to our idea, most of the systems are the same in Saudi universities.

1.4.1 Existing system description

Curriculum management system of computer science department at Umm Al-Qura University : It is a

system responsible for managing curricula, updating them, updating programs, and anything related to
managing curricula and program.

2
1.4.2 Problems in the existing system
The current knowledge gap lies in the absence of a comprehensive, automated system specifically
designed to address the complexities of managing curricula within computer science and
computer engineering departments. Manual methods and disparate systems lead to inefficiencies
and potential errors, hindering the adaptability to changing educational standards.

Curriculum Automation of
management system Academic department
of computer science activities project
department
program Equivalency Module

Auto Reporting and Export

User Authentication and Access

Control

User Interface for Curricula

Management

Table 1: Compare services and features between other applications and our
application.

3
CHAPTER 2
System Analysis

4
2.1 overall Description
Our project talks about curriculars and program . Before that, we need to understand what the
curriculum is, what the program is, what they contain, and how they approved and where it
comes from.

2.1.1 product elements

In Saudi universities, the process of approving and continually refining programs and courses is
meticulously overseen by the Education Evaluative commission, operating within defined roles
and responsibilities. At the core of this process lies the comprehensive documentation
encapsulated in Program Specifications for programs and Course Specifications for individual
courses. These documents serve as foundational blueprints, encompassing essential elements
such as Program Identification, articulation of program goals, intricate details concerning
Program Structure, and an array of other pertinent information critical to the academic
framework.

Within the Program Specifications, a meticulous examination of the program's overarching

objectives is conducted, delineating the intended outcomes and desired educational
achievements. This encompasses a thorough exploration of the curriculum's scope and sequence,
ensuring alignment with institutional standards and broader educational objectives. Additionally,
it entails a comprehensive overview of the resources and infrastructure required to support the
successful delivery of the program.

Similarly, the Course Specifications provide a granular examination of individual courses within
the program, outlining their unique identifiers, explicit Course Learning Outcomes, and requisite
materials and resources. These specifications serve as a roadmap for instructors, offering
guidance on the design, delivery, and assessment of course content.

Adherence to these meticulously crafted guidelines is paramount, as it ensures the attainment of

educational excellence and the fulfillment of institutional objectives.

2.1.2 product elements data

A university curriculum is a unit of teaching typically lasting one semester or term, offered by a
specific department within a college or school. It focuses on a particular subject area and aims to
achieve specific learning outcomes in students.

5
Here is some information that included in each curriculum:

• Credit Hours: Each course carries a designated number of credit hours reflecting the
workload and expected student effort.
• Course Type: Courses can be departmental (offered by a specific department) or
university-wide, and they can be mandatory (required) or elective (optional).
• Level/Year: Courses are offered at different levels or years of study based on the program
structure (e.g., undergraduate, graduate).
• Prerequisites & Co-requisites: Some courses may require successful completion of other
courses (prerequisites) or need to be taken simultaneously with other courses
(corequisites).
• Delivery Format: Courses can be delivered in different modes, such as face-to-face
lectures, online formats, blended approaches, or combinations of these.
• Learning Outcomes: Each course has clearly defined learning outcomes, specifying the
knowledge, skills, and values students should gain by the end.

A university program refers to a defined pathway of courses and experiences leading to a

particular academic qualification (e.g., bachelor's degree, master's degree).

Program Identification:

• Program Title and Code: Official name and unique identifier for the program.
• Total Credit Hours: Number of credits required to complete the program.
• Award Granted: Degree, diploma, or certificate awarded upon successful completion.
• Major Tracks/Pathways or Specializations: Any sub-categories or focus areas within the
program (if applicable).
• Intermediate Exit Points and Awards: Options for early program completion with
recognized credentials (if available).
• Type of Program: Undergraduate, graduate, professional, etc.
• Program Chair or Coordinator: Name of the individual responsible for the program

6
2.2 Functional requirement:

• User Authentication and Access Control:

The system should provide secure user authentication mechanisms to ensure that only authorized
personnel can access and modify curricula data.
Different user roles should be defined, such as administrators, faculty members, and department
heads, with varying levels of access and permissions.

• Template-Based Curriculum Display:

The system should support the creation and management of multiple curriculum templates.
Users should be able to select a template to display the curriculum information in a predefined
format, catering to different stakeholders' needs.
The system should dynamically populate the template with the corresponding curriculum data.

• Curriculum Versioning and History:

The system should maintain a history of changes made to curricula, including the ability to track
modifications, additions, and deletions.
administrators should be able to view and revert to previous versions of a curriculum if needed.

• Search and Retrieval:

The system should provide search capabilities to allow users to find curricula based on specific
criteria, such as program names, course codes, or keywords.
Users should be able to retrieve and view the details of a specific curriculum in a user-friendly
manner.

• Reporting and Export:

The system should include reporting capabilities to generate predefined and custom reports on
curricula.
Users should be able to export reports in common formats.
• Program Equivalency Module:

Inclusion of a dedicated module for program equivalency evaluations, providing a streamlined

process for assessing and managing program equivalencies.
Users should be able for users to enter the program into the Program Equivalency Module to be
completed with high accuracy.

2.3 Non-functional requirement:

7
quality attributes or quality of service requirements, define the overall attributes or qualities that a
system or product should possess, in our project we will focus on Usability, Performance,
Security.

2.3.1 Usability requirement:

The system should have an intuitive and user-friendly interface, allowing users to easily navigate,
enter data, and perform tasks without extensive training.
The system should provide clear instructions, tooltips, and error messages to guide users in using
the system effectively.

2.3.2 Performance requirement:

The system should be highly responsive, providing quick response times for data entry, retrieval,
and modification operations or reporting operations.

2.3.3 Security requirement:

The system should incorporate robust security measures to protect the confidentiality, integrity,
and availability of curricula data.
Access controls should be implemented to ensure that only authorized users can access and
modify the system.

2.3.4 Compatibility requirement:

The system should be compatible with different operating systems, web browsers, and devices
commonly used by faculty members and administrators.

2.4 Structural design

8
 In the Structural Design phase, we delve into the architectural components of the system,
focusing on how various elements interact to fulfill the requirements. providing a structural
blueprint that guides the subsequent development stages.

2.4.1 Use case diagram

Figure1: Use Case Diagram.

2.4.1.1 Use case descriptions

9
 Use case for Evaluate and manage program equivalencies
Actor Curriculum managers
Description This functionality assists Curriculum managers in efficiently determining
course equivalencies between different programs offered by the academic
institution.
Data Course ID
Pre-condition The Curriculum manager is logged into the database system.
The database system has access to the necessary data regarding courses and
programs.
Output A list of equivalent courses from other programs offered by the institution,
automatically evaluated by the system.
Table 2.1: Use case Description for Evaluate and manage program equivalencies.

Use case for validate and verify the validity of program equivalencies
Actor Curriculum managers
Description The system reviews the program equivalencies and compares them with
program requirements to verify their correctness and alignment with
institutional policies.
Data Program Equivalencies, Program Requirements
Pre-condition The Curriculum manager is logged into the database system. The database
system has access to the program equivalencies and program requirements
data.
Output The system generates a report of invalid or questionable program
equivalencies for the Curriculum manager to review.
The Curriculum manager can take appropriate actions to rectify or update
the program equivalencies based on the report.
Table 2.2: Use case Description for validating and verifying the validity of program equivalencies.

Use case for Auto Generate Report

Actor Lecturer
Description Lecturer generates reports automatically through the system.
Data Date range, specific courses.
Pre-condition Lecturer is logged into the system.
Output Auto-generated report presented for review and download.
Table 2.3: Use case Description for Auto Generate Report.

Use case for Program and Course Information Management

Actor Lecturer, Commission, Curriculum Managers
Description Lecturers, Commission, and Curriculum Managers manage program and

10
 course information.
Data New courses, program details, faculty assignments.
Pre-condition Actors (Lecturer, Commission, Curriculum Managers) are logged into the
system.
Output Program and course information updated as per the performed actions.
Table 2.4: Use case Description for Program and Course Information Management.

Use case for Manage Information

Actor Curriculum Managers
Description Curriculum Managers manage various types of information within the
system.
Data Program and course information.
Pre-condition Curriculum Manager is logged into the system.
Output Successful management of program and course information, contributing to
overall information management within the system.
Table 2.5: Use case Description for Manage Information.

2.4.2 Class diagram

the class diagram provides a basic overview of the classes involved in managing academic
programs and their curriculums. However, it would be helpful to have more information about
the relationships between the classes in order to fully understand the system.

11
 Figure2.1: class diagram.

The class diagram shows the relationships between the classes Program, Course, Curriculum, and
several other classes related to curriculum management.

2.4.3 ERD diagram

The ERD depicts a database for the system. It shows the entities involved and how they relate to
each other.

12
 Figure2.2: ERD diagram.

Here's a breakdown of the entities and their relationships:

Entities:

• Program: Represents the academic programs offered.

13
 • Course: Represents the courses offered within each program.
• Institution: Represents the institutions offering the programs.
• Department: Represents the academic departments within the institution.
• College: Represents the colleges within the institution.
• Learning Resources Facilities: Represents the resources available for student learning.
• Teaching And Assessment: Represents the methods used for teaching and assessing
students in the program.
• Course Quality Evaluation: Represents the process of evaluating the quality of courses
offered.
• Student Academic Counseling: Represents the process of academic advising and guidance
provided to students.

Relationships:

• A Program consists of many Courses.

• A Course is offered by Department.
• A Department belongs to one College.
• A College belongs to one Institution.
• A Faculty member teaches Courses in one or more Course Sections.
• Courses are assessed using teaching and Assessment Methods.
• Courses have specific Learning Outcomes.
• Learning Resources Facilities are required by Courses.
• Counseling sessions might address specific courses.

2.5 Proposed system

Simplify curriculum management with advanced features.

2.5.1 Aims and objectives

Project aims to bridge the gap in inefficient curriculum management by developing a
sophisticated database system. This system will introduce advanced features to:

14
 • Boost efficiency: Streamline processes for creating, updating, and sharing curriculum
information, saving faculty and staff valuable time.
• Improve accessibility and collaboration: Provide authorized users with a user-friendly
interface for easy access and sharing of curriculum data.
• Increase flexibility and adaptability: Facilitate easy curriculum modification based on
program changes or evolving needs.

2.5.2 Proposed system features

To achieve these aims, the system will offer:

• User-friendly interfaces: Tailored interfaces for different user roles (administrators,

faculty) with intuitive navigation and data entry processes.
• Robust user access controls: Granular permission settings to ensure data security and
restrict access based on user roles and responsibilities.
• Auto-filling templates: Pre-defined templates for various course types with automated
population using existing data or user selections, minimizing manual effort.
• Course equivalency evaluation module: Evaluate equivalency between courses within or
across programs, simplifying course selection and transfer processes.
• Reporting and analytics: Generate reports on curriculum usage, faculty activity, and other
relevant data for informed decision-making.

15
 Chapter 3
Design Considerations

3.1 Design Constraints

Design constraints are factors that limit the options available to the system designers. These
constraints may arise from technical limitations, organizational policies, budgetary constraints, or
other external factors.

3.1.1 Hardware and software environment

Environment can be hardware environment or software environment.

16
3.1.1.1 Hardware Environment
The hardware requirements for the web application are minimal, as it is designed to be versatile
and platform independent.
The application can run on standard computers or laptops, providing flexibility and accessibility
for users. Given that the application is developed using ASP.NET Core, it ensures compatibility
across various platforms, allowing users to access the system from a diverse range of devices
without significant hardware constraints.

3.1.1.2 Software Environment

Programming language: The web application is developed using the C# programming language,
which is well-suited for building robust and scalable web applications on the .NET platform.

Database: The web application uses a SQL Server database for storing and managing data.

Version control: Git is used as the version control system for managing the source code of the
web application.

Operating systems: The ASP.NET Core framework supports deployment on a wide range of
operating systems, including Windows, Linux, and macOS. This allows the web application to be
deployed on various server environments.

3.2 Architectural Strategies

In the process of designing and developing a software system, Architectural Strategies play a
pivotal role in shaping its fundamental structure

3.2.1 Project Methodology

The complexities of curriculum management demand innovative solutions. That's where the
Agile methodology steps in, offering a flexible and collaborative approach to navigate
development and adaptation.

17
3.2.1.1 Agile Project Methodology

Figure3: Agile methodology

Agile is an iterative and incremental project management approach that prioritizes continuous
learning and adaptation.

Benefits of Agile for our Project:

• Flexibility and adaptability: Respond effectively to changing needs and requirements .

• Enhanced collaboration: Foster continuous communication and feedback between
stakeholders (faculty, administrators).
• Faster time to value: Deliver working features quickly and incrementally.
• Improved quality: Continuously identify and address issues, leading to a more refined
final product.

18
3.2.2 Architectural pattern
The Model-View-Controller (MVC) architectural pattern is a widely adopted design paradigm for
building modern web applications. In the context of ASP.NET Core, MVC serves as the
foundational framework for structuring and organizing web applications, providing a systematic
approach to separating concerns, enhancing maintainability, and promoting code reusability.

MVC divides an application into three interconnected components:

Model: The Model represents the application's data and business logic. It encapsulates the data
model, including entities, relationships, and data access operations. The Model component is
responsible for managing the application's state and enforcing business rules.

View: The View represents the presentation layer of the application. It is responsible for
rendering user interface elements and displaying data to the user. Views are typically HTML
templates that incorporate dynamic content using data provided by the Model.

Controller: The Controller serves as the intermediary between the Model and the View. It handles
user input, processes requests, and orchestrates interactions between the Model and the View.
Controllers are responsible for executing business logic, invoking appropriate operations on the
Model, and selecting the appropriate View to render the response.

19
 Chapter 4
System Design

4.1 System Architecture

A system architecture is essentially the blueprint of a system, outlining its structure

4.1.1 Major Modules

The system architecture consists of the following major modules:

1. Program Equivalency Module

20
 o Responsible for determining the equivalency of programs based on user
input.
o Compares programs to determine equivalency.
2. Login Form Module

o Allows users to log in to the system. o Takes username and password as

input.
o Verifies credentials against a database of authorized users.
3. Reporting and Export Module

o Allows users to generate reports and export data.

o Likely allows users to specify the type of report or data desired.
4. Search and Retrieval Module

o Allows users to search for information within the system. o Takes user
queries as input. o Returns a list of relevant results.

21
4.1.2 System Architecture Design

Figure4: System Architecture Design.

22
 Chapter 5
System Implementation & Validation

23
5.1 Introduction
This chapter provides an overview of application interfaces and the implementation phases.
First, we describe these phases and show their related snapshots. Secondly, we present the
programs used in these implementation phases works. Third, we finalize this chapter by
providing a description of the testing and verification phase to check if the expected results
match the actual results.

5.2 Snapshots of main execution screens of the website

5.2.1 Home Page

The home page of the UQU Collaboration Website is designed to provide users with essential
functions and features aimed at facilitating collaboration and access to educational resources.

24
Figure5.1: UI for Home Page

25
Key Functions and Features:

 Navigation and Accessibility:

• The header prominently displays the UQU logo and intuitive navigation links
("Home", "courses-plan", "program Equivalency Module"), ensuring easy access
to different sections of the website.

 Welcome Banner:
• Upon loading, users are greeted with a welcoming banner that sets the tone for
collaboration and educational exploration at UQU.

 Academic Majors Overview:

• Immediately visible sections highlight various academic majors offered by UQU.
Each major is presented in a structured card format, featuring relevant images and
concise descriptions to inform prospective students and collaborators.

 Feature Highlights:
• The page emphasizes key features such as comprehensive reporting tools, robust
search capabilities, and interactive program equivalency modules. Each feature is
clearly outlined with descriptive text, showcasing the website's capabilities in
supporting academic collaboration and resource management.

 Responsive Design:
• The layout is responsive and optimized for various devices, ensuring seamless
access and usability across desktops, tablets, and mobile phones.

26
User Interaction:

 Intuitive Elements:
• Interactive elements like navigation links, buttons, and feature boxes are designed
to be user-friendly and accessible, promoting engagement and exploration of the
website's functionalities.

Visual Design:

 Color Scheme and Typography:

• Utilizes a modern color palette with contrasting dark backgrounds and light text,
enhancing readability and visual appeal. Arial and sans-serif fonts maintain a clean
and professional aesthetic.

27
5.2.2 The Courses Plan page
The Courses Plan page of the UQU Collaboration Website is dedicated to detailed planning and
evaluation of academic courses, enhancing transparency and efficiency in curriculum
management.

Figure5.2: UI for the Courses Plan page.

28
Key Functions and Features:

 Navigation and Accessibility:

• The header includes the UQU logo and navigation links ("Home", "Courses Plan",
"Program Equivalency Module"), ensuring easy access to different sections of the
website for administrators and faculty members.

 Course Evaluation Overview:

• The page presents a comprehensive overview of course evaluations, displaying
structured tables with detailed metrics and feedback from students and faculty
members.

 Interactive Controls:
• Users can dynamically add, modify, or delete course evaluation entries through
intuitive input fields and action buttons. This functionality facilitates real-time
updates and data management.

 Visual Representation:
• Utilizes tables with alternating row colors for clarity and ease of reading. Action
buttons are color-coded (e.g., red for deletion, yellow for modification) to
streamline user interactions.

 Data Export:
• Incorporates a feature for exporting course evaluation data into downloadable
formats, enhancing accessibility and sharing capabilities among stakeholders.

User Interaction:
29
  Efficient Data Management:
• Enables administrators and faculty members to efficiently manage course
evaluations, ensuring informed decision-making and continuous improvement in
curriculum offerings.

Visual Design:

 Color Scheme and Typography:

• Maintains consistency with the overall website design, using a professional color
palette and clear typography to enhance readability and visual appeal.

30
5.2.3 The Program Equivalency Module page
The Program Equivalency Module page of the UQU Collaboration Website facilitates seamless
comparison and alignment of academic programs across different educational standards and
institutions.

Key Functions and Features:

 Navigation and Accessibility:

• The header includes the UQU logo and navigation links ("Home", "Courses Plan",
"Program Equivalency Module"), ensuring easy access to various sections of the
website for educational administrators and evaluators.

 Program Comparison Tools:

• Features interactive tools and visual aids for comparing curriculum structures,
learning outcomes, and course equivalencies between academic programs.

 Customizable Filters:
• Users can apply customizable filters to refine program comparisons based on
specific criteria such as course credits, core requirements, and accreditation status.

 Visual Representation:
• Utilizes charts, graphs, and side-by-side comparisons to present complex data in a
visually engaging and comprehensible manner, aiding decision-making and
evaluation processes.

 Collaborative Features:
• Supports collaboration among educational institutions by providing secure sharing
options for program equivalency reports and findings.

31
User Interaction:

 Enhanced Decision Support:

• Empowers educational administrators and evaluators with tools to make informed
decisions regarding program equivalencies and academic partnerships.

Visual Design:

 Color Scheme and Typography:

• Maintains consistency with the website's design language, using colors and
typography that enhance clarity and professionalism while ensuring accessibility
across devices.

32
5.2.4 The Word Document Table Extractor page
The Word Document Table Extractor page is designed to facilitate the extraction and display of
tables from Word documents, making it easier for users to view and analyze structured data
contained within these documents.

Figure5.4.1: Word Document Table Extractor page.

33
Figure5.4.2: Word Document Table Extractor page. Figure5.4.3: Word Document Table Extractor page.

34
Figure5.4.4: Word Document Table Extractor page. Figure5.4.5: Word Document Table Extractor page.

35
Figure5.4.6: Word Document Table Extractor page. Figure5.4.7: Word Document Table Extractor page

36
Key Functions and Features:

 Navigation and Accessibility:

• The header includes the UQU logo and navigation links ("Home", "Courses Plan",
"Program Equivalency Module"), providing easy access to other sections of the
website.

 File Upload:
• Users can upload Word documents (.docx) via an input field. This allows users to
select and process their documents directly from their devices.

 Table Extraction:
• Utilizes the Mammoth.js library to convert Word documents to HTML and extract
tables. This ensures accurate extraction and display of tabular data from the
uploaded documents.

 Loading Indicator:
• A spinner (loading indicator) is displayed while the document is being processed,
providing visual feedback to users that the extraction process is underway.

 Display Extracted Tables:

• Extracted tables are displayed in a clean, readable format within the page. This
allows users to easily view and analyze the data without needing to open the
original Word document.

 Error Handling:
• Provides feedback in case no tables are found or if there's an error during the
extraction process. This ensures users are informed about the outcome of their
actions.

37
User Interaction:

 Upload and Extract:

• Users can upload a Word document and click the "Extract Tables" button to initiate
the extraction process. The system processes the document and displays any tables
found.

Visual Design:

 Dark Theme:
• The page uses a dark background with contrasting light-colored text and elements,
ensuring readability and a modern aesthetic.

 Responsive Design:
• The layout is designed to be responsive, ensuring that the page is accessible and
usable on various devices, including desktops, tablets, and smartphones.

38
 Chapter 6
Conclusion & Future Work

39
6.1 Conclusion
The "Automation of Academic Department Activities" project aims to address the inefficiencies in
managing academic curricula within the Department of Computer Science at Umm Al-Qura
University. By developing a comprehensive database system, we have provided a solution that
enhances the management, modification, and accessibility of academic curricula. The system's
user-friendly interface and robust functionality ensure that department staff can perform their
tasks more efficiently and accurately.

In an era where digital transformation is essential, our project demonstrates the potential to
significantly streamline academic operations. The automated system improves data management,
reduces errors, and facilitates better collaboration among faculty members. We believe that this
project will not only benefit our department but also serve as a model for other academic
institutions looking to modernize their administrative processes.

Throughout the project, we focused on creating a flexible and scalable system capable of adapting
to future needs. Our solution empowers the department to maintain high standards of academic
management, ultimately contributing to the quality of education provided to students.

6.2 Project Achievements

In this project, we developed a system for automating academic department activities, which
offers a unique and efficient approach to managing curricula. The following are our key
achievements:

 We began by investigating the problem domain and identifying inefficiencies in the

existing system (Chapter 1).
 We conducted a thorough analysis of relevant literature and existing systems to ensure our
solution was innovative and effective (Chapter 2).
 We specified the necessary software requirements to meet the department's needs (Chapter
3).
 We designed the system architecture, including detailed diagrams and technical
specifications (Chapter 4).
 We implemented the system using appropriate tools and technologies, completing the
project with a functional and reliable solution (Chapter 5).

40
These accomplishments collectively contribute to a significant improvement in the management
of academic department activities. The project provided us with valuable experience in problem-
solving, teamwork, and the application of new technologies.

6.3 Restrictions
Despite the successes of this project, there are a few limitations:

 The system currently supports only English, which may limit its usability for non-English
speaking staff and students.
 Some advanced features, such as real-time data analytics, were not implemented due to
time constraints.

6.4 Future Work

The project presents several opportunities for further development and enhancement. Some
potential future work includes:

 Adding Multilingual Support: Expanding the system to support multiple languages to cater
to a broader user base in the Middle East and beyond.
 Integrating Real-Time Data Analytics: Implementing advanced analytics features to
provide real-time insights and improve decision-making processes.
 Enhanced Security Measures: Incorporating more robust security protocols to protect
sensitive academic data.
 Mobile Application Development: Developing a mobile version of the system to provide
greater accessibility and convenience for users.
 User Feedback Integration: Continuously improving the system based on user feedback to
ensure it meets evolving needs and expectations.

41
6.5 REFRENCES
[1] the Course Contents we are using is from Umm Al-Qura University https://uqu.edu.sa/ .
[2] We used Visual Studio to develop the website https://code.visualstudio.com/ .

42