ARBA MINCH UNIVERSITY

ARBA MINCH INSTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY
Course Title: Object-oriented system analysis and design
First year, IT MSc. Students
PROJECT TITLE: -Exam Scheduling Management System for
Arba Minch University, AMIT.

Group members:
1. Amare Abraham ID: - PRAMIT/-------/2015
2. Tizita Belihu ID: - PRAMIT/-------/2015
3. Wubet Mada ID: - PRAMIT/-------/2015

Submitted to: Dr. Mohammed. A

Dec 18, 2022

Arba Minch, Ethiopia.

 Team Profile

Project Title:-Exam Scheduling Management System (ESMS).

No
Name Individual Qualifications Responsibility

1. Amare Abraham Programming, Presentation Facilitator

2. Tizita Belihu Management and Organization System Manager

3. Wubet Mada Design, Documentation System Designer

Table 1:-Team Profile

Proposed Project Description

The manual system of preparing time table for exam schedule is time consuming and usually
ends up with various Rooms clashing either at same room or with same teacher having more than
one room or one exam at the same time. It is becoming a continuing problem in higher education
due to bulky nature of the tasks for schedule preparation. Even the most advanced higher
education institutes in Ethiopia haven’t succeeded in automating the task of scheduling. To
overcome all these problems, we propose an automated system that accepts various inputs like
teacher name, course name, course code, credit hour, target group and room. By using the above
inputs it will make a possible exam schedule by making optimal utilization of resources. So, we
will gather requirement, identify the problem, find the solution, design the system, implement the
system and test its functionality. To reduce Tedious, Time consumption, Redundancy and
Irresponsiveness of existing system we will develop this system.

This project hopes to contribute automated exam scheduling management system to higher
educations in general and Arbaminch institute of Technology in Particular.

A Typical customer for our proposed system includes Students, Lectures, department head, and
institute.
 The Functional Features of the system
✓ Develop Exam schedule.
✓ Record the information about room, Lecture, Student Target group and Course information.
✓ Develop Update or edit Exam schedule.
✓ View and print updated time table.

Plan of Work and Product Ownership

The project team members discussed on it to work hardly and also estimate project to be
completed on time without any delay. For organization replacing current systems with automated
one is advisable for better performance. To replace the current system developers (we) should
make the whole plan before starting to develop a computerized system.

Our plan of work should go parallel with the Schedule feasibility, making sure whether potential
time frames and completion data can be meeting or not. In order to develop this project we have
planned all the necessary tasks.

No Tasks Team Members and Months(2015 E.C)

their Involvements.
December January February

1. Title Selection. All Group Members ✓

2. Project Proposal All Group Members ✓

3. Requirement Analysis All Group Members ✓

Document (RAD)

4. System Design Document All Group Members ✓

(SDD)

5. Test Plan Document All Group Members ✓

(TPD)

6. System User Manual All Group Members ✓

Document (UMD)

Table 2:-Tasks and Team contribution.

Functionality:
The new system has basic features to perform system functionality. The functional features of
this project are make exam schedule, update exam schedule, print and view exam schedule, and
add course, department and room in the database.
Qualitative Property
Qualitative property deals with the qualities of the application system needed to be
developed from different evaluation point of view like the response time of the application to a
given user queries, the user friend lines of the application and this requirements do not directly
affect the performance of the system. Qualitative property of the system can be viewed as
follows

Performance
 Speed: - the system should perform at optimum speed at normal circumstances (i.e., when
networks and nodes are ok).
 Robustness: - The system should be tolerant of errors and produce error reports that are
simple to be understood by the users.
 Reliability: - The system should be reliable in generating schedule without any conflict.

User Interface
Since there are potentially many users of this system, it will have different types of user
interface. It will include the necessary features for each user so the application will have a user
friendly interface for low knowledge of computer users, and simple and interactive user interface
components should be part of the system.

Security and Access permission

The system should be protected with different security features (techniques) on both the
software and hardware part.

✓ On software part: - on this part the admin who wants to login to the system must be enter
correct user name and password. This protects the system from any unauthorized access.
Without scheduler other users can’t edit, insert, delete any data, but they can view/see only
the data exist.
✓ On hardware part: - the server is expected to be placed in a secured room.

Backup and Recovery

To recover a data we will have a copy of the original data in another place. Like CD, DVD, flash
desk, email etc.