Umer Aliyi - S/259/07

DIRE DAWA INSTITUTE OF TECHNOLOGY
DEPARTMENT OF INFORMATION TECHNOLOGY

TITLE: WEB BASED INSTRUCTOR PERFORMANCE EVALUATION
SYSTEM
Name ID
1. UMER ALIYI ----------------------------------S/259/07
2. MUKAR UMER -------------------------------- S/205/07
3. TEMAM MUSTEFA ---------------------------S/244/ 07
4. KUSLUMA SULTEEAN---------------------------S/122/06
5. AFENDI MOHAMMED-----------------------S/036/07
6. KAMAL HUSSIEN------------------------------S/164/07
August 2019
Dire Dawa, Ethiopia
WEB BASED INSTRUCTOR PERFORMANCE EVALUATION SYSTEM
2019
DIRE DAWA INISTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY
TITLE: WEB BASED INSTRUCTOR PERFORMANCE EVALUATION
SYSTEM
PREPARED BY:
Name ID
1. UMER ALIYI---------------------------------------S/259/07
2. MUKTAR UMER----------------------------------S/205/07
3. TEMAM MUSTEFA----------------------------S/244/ 07
4. KUSLUMA -------------------------------------------S/122/06
5. AFANDI MOHAMMED-----------------------S/036/07
6. KAMAL HUSSIEN-----------------------------S/164/07
A Project submitted to Dire Dawa University in partial fulfillment of the

requirement for the Degree of Bachelor of Science in Information Technology
August 2019
Dire Dawa, Ethiopia
1
2019
Table of Contents
Table of Contents ................................................................................................................................... 2
List of tables ........................................................................................................................................... 3
Acronyms ................................................................................................................................................ 4
Chapter One:........................................................................................................................................... 5
Introduction ........................................................................................................................................ 5
1.1 Background of the Organization................................................................................................... 5
1.2 Background of the Project ............................................................. Error! Bookmark not defined.
1.3 Statement of the Problem ............................................................................................................. 5
1.4. Objective of the Project ............................................................................................................... 7
1.4.1 General Objective .................................................................................................................. 7
1.4.2 Specific Objective ................................................................................................................. 7
1.5 Scope of the project ...................................................................................................................... 7
1.6 Limitation of the Project ............................................................................................................. 8
1.7 Significance of the Project.......................................................................................................... 8
1.8 Beneficiaries of the Project .......................................................................................................... 8
1.9 Methodology ................................................................................................................................ 9
1.9.1 Data Gathering Methodology ................................................................................................ 9
1.9.2 System analysis and Design methodology ............................. Error! Bookmark not defined.
1.9.3Development approach ......................................................................................................... 10
1.9.4 Development tool .............................................................................................................. 10
1.10 Testing methodology ................................................................. Error! Bookmark not defined.
1.11 Feasibility Study ....................................................................................................................... 12
1.11.1 Technical Feasibility.......................................................................................................... 12
1.11.2 Operational Feasibility ...................................................................................................... 13
2
2019
1.11.3 Economic Feasibility ......................................................................................................... 13
1.11.4 Schedule Feasibility.............................................................. Error! Bookmark not defined.
1.13. Project Plans ............................................................................................................................ 13
1.13.1. Project Time Schedule ...................................................................................................... 13
1.13.2 Project Cost ....................................................................................................................... 14
1.12.3 Budget Plan ....................................................................................................................... 15
List of tables
Table 1: Hardware tools ....................................................................................................................... 11
Table 2: software tools ......................................................................................................................... 12
Table 3: Time Schedule for Our Project................................................................................................ 14
Table 4: Cost estimation for each phase of the software development. ............................................... 15
Table 5: Budget plan ............................................................................................................................ 15
3
2019
Acronyms
List of Acronyms
DDU: Dire Dawa University
IPES: Instructor Performance evaluation system.
SI: School of Informatics
OOA: Object Oriented Analysis
OOD: Object oriented Design.
DBMS: Database management software.
HTTP: Hypertext Transfer Protocol.
MySQL: My Structured Query Language
RAM: Random Access Memory
PC: Personal computer
MS Word: Microsoft words
PHP: Hyper -text pre-processor
HTMLs: Hypertext markup language.
CSS: Cascading style sheet
BR: Business rule
PIECES framework:-
P: Performance,
I: information,
E: efficiency,
C: Control (security)
E: economic, and
S: service.
UC: use case
Dep’t: department.
UI: user interface
ID: identity card
UML: unified modeling language.
GB: Giga Byte
HOD: Head of Department
GUI: Graphical User interface
4
2019
Chapter One:
Introduction
Education is crucial for development and is one of the most powerful tools in breaking the cycle
of poverty and beginning a progress. Today in Ethiopian higher education reform and quality
assurance ensuring the quality of education deliverance for all citizens and increasing the
educated human labor among the country. Dire Dawa University is one of the leading higher
educational institutions in Ethiopia by being center of excellence in education and research in
areas of administration, policy and cultural value utilization for development.
The ultimate aim of Dire Dawa University is the teaching and learning activity, Producing of
Quality graduate; graduates with the knowledge, skill, Professional Ethics and high competence.
In addition, it is heavily involves in research to solve existing problems and fill knowledge gaps
and community service to Enhance participation in partnership and development service.
Instructors are the key human resource of any educational institution in the delivery of quality
education. Teaching performance evaluation is a necessary step in ensuring good quality and
performance of instruction. Traditionally, teaching performance evaluation used as a tool to
apprise instructors on how they are doing their job. Performance defined as a set of outcomes
produced during a certain period, and does not refer to the traits, personal characteristics or
competencies of the performer.
It is designed to identify teaching strengths and weaknesses of the Instructor just depend up on
some specifically listed related to the course and teaching style, lecture note and exam
preparation,
1.1 Background of the Project

In DDU Instructor performance evaluation system is done manually (paper-based) and very
laborious in terms of consumption of cost and time. So in order to minimize and improve the
quality of learning and teaching method and to produce competent and well skilled instructors,
we believe it is necessary to develop web based Instructor performance evaluation system.
1.2 Statement of the Problem

The existing system is paper-based (manual) system. It must need to develop a system, which
automates all currently seen problems as a school and department level. As it has a risk of
5
2019
mismanagement of data, less security, no proper coordination between head of department and
evaluation committee, also student and Instructor. Therefore, they are not being evaluated
properly with a shortest period before each semester ends. Instructors’ performance evaluation
activity processed manually and it cannot be done with the appropriate time. The following are
list of problems on Instructors’ evaluation system and their justification
Currently, nstructors’ performance evaluation did not be performing with the specific period. To
make this evaluation to be processing within the specific period before each semester ends each
student, school head, vice -president and director of teaching and learning should have to
evaluate Instructors based on specific criteria.
Instructors’ performance evaluation system cannot calculate with the appropriate time and it
cannot inform the appropriate result and comments to the Instructors. Accessing resource
through the web is fast and after this system will implemented, the system will able to calculate
each Instructor’s performance when it will requests.
Calculating performance for each Instructor physically is very error prone. To avoid these errors
and to reduce the time it takes, we will go to develop the system that addresses these problems.
The teachers’ evaluator gives the evaluation paper to the Instructor who is going to be evaluated.
Therefore, students are not willing to give the exact result because they are frightened.
The evaluation system creates work overload to the Instructors as well as the students who
evaluate their teacher for each course who is assigned for them. There must be one teacher to
afford evaluation paper for each student and control each student. However, after the system is
implemented, well there is no any agent between the evaluators and evaluation coordinator.
Simply evaluator will login into the system and evaluates the instructor.
Evaluation processes are not clear. Therefore, students and Instructors are not aware of the
evaluation before. Firstly, before each evaluator evaluates a short description helps them how to
evaluate. Generally, existing Instructor’s performance evaluation is boring and tedious to
perform.
6
2019
1.3. Objective of the Project
1.3.1 General Objective
The general objective of this project is to develop a web-based Instructor performance evaluation
system for school of computing in Dire Dawa University.
1.3.2 Specific Objective

The specific objective of this project:
 Perform a requirement analysis to find out the system functional and non-functional
requirements.
 Design the system using object-oriented models for understanding the system and to
make the implementation easy.
 Design the database for storing student information using MySQL.
 Implement a web application using PHP, CSS, and apache web server.
 To study and analyze the limitation behind current evaluating Instructor’s performance
system.
 To understand both functional and non-functional requirements of school of computing
Instructor’s performance evaluation system.
 To develop automated system that facilitates effective and good efficiency report
generation.
 To design and implement web based Instructor performance evaluation system that
performs tasks in efficient way.
 Deploying the implemented system..
1.4. Scope of the project

This project, which is web based Instructors Performance Evaluation system, overcome the
drawbacks of their (DDU) manual system by replacing it with computerized system and it
provide simple, efficient environment and reduce time consumption. Moreover, at the end of our
project we can give good opportunities for school of computing Instructor’s as well as the staff
members and dean office by enabling the instructors to view new information and their ranks
through the web and it ensuring good file management and database management system. This
system only applicable or developed for Instructors of undergraduate student of school of
computing in Dire Dawa University.
Students are able to evaluate their Instructors for each course and, head, and scientific director
based on criteria set by university.
7
2019
 Instructor can evaluate him/herself based on given criteria
 The system can generate the result of evaluation for the respective user and period (time)
based on their privileges.
 Processing all evaluation information based different criteria.
 Teachers can also see what their inflexibility is and what good performance is there.
 The system will calculate the weight the values filled in the evaluation form.
 The system can determine promotion of instructors based on their efficiency points.
1.5 Limitation of the Project
Our project will limit on the following activities:-
 The project will not include the post graduate class students and instructors.
 The project will do only for undergraduate students’ instructor.
 Lack of IT infrastructure for, specially other school rather than school of computing.
1) Because we will have a limited time to do this project it is difficult to include those all the
above activities Time Constraint.
1.6 Significance of the Project

The new system expected to bring remarkable change in the Instructor performance evaluation
system. This project brings some significance such as
 Multiple users can access the system to get services.
 Provides secured service for all users of the system.
 Able to reduce the workload of Instructor as well as student.
 This system provides full and fast-organized service for the school.
 The system is cost effective because paper and other similar materials not needed.
 This system can be accessed everywhere in the university in the given time.
 Therefore, it minimizes the time and work force.
 The system gives fast delivery evaluation report for schools.
 Accuracy and confidentiality of evaluation data maintained
1.7 Beneficiaries of the Project

The beneficiaries of the project will be:-
8
2019
 Instructor, dean or scientific director, quality assurance and reform, directorate of
learning and teaching all are benefit from this system because it reduces workload,
time, and cost consumption and expense.
 Students also benefited because they can simply evaluate their Instructor, dean, head
and scientific director within a matter of second.
For Head of Department: -
 Reduce workload and time consumption

 Reduce data redundancy and Mishandling of information
 Reduce error occurrence
 Reduce weight calculation time and provides feedback in shorter time
For Instructor: -
 View the result through online

 Able to evaluate him/herself through web based way
 Evaluate another teacher (peer evaluation) through online
 Enable to view their evaluation result and feedback.

The project development team.
 The project has initiated our team to get knowledge of how to develop the required
system application.
 While struggling with some difficulties, the team got a lot of experiences of solving
problems.
1.8 Methodology
1.8.1 Data Gathering Methodology

We will use the following methods to collect relevant data required to our project.
 Interview: - we will gather necessary information about the background of the
clinic, their works activities and the function of their existing system using some
structured (when did the DDIT was established, how does the existing system function,
9
2019
how many patients get services per day, how many employers are there etc.) and
unstructured interview questions from management of the student and workers.
 Observation: We will also arrive to the registrar and observe how workers carrying out
their work activities in a natural setting. Observation will allows us to collect data in real
time where activities are being performed.
 Document analysis: - we will also collect certain relevant information from written
documents in the registrar. Not only that but also we will tried to review other relevant
documents to develop our project.
 Brainstorming:-we will use our previous experience on the developing of other
systems, thinking and reasoning of real world problems.
1.8.2 Development methodology approach
A software development approach helps us to structure, plan and control the process of
developing software. There are several software methodologies that can be used in
developing software.
1. Waterfall model
2. Prototyping model
3. Spiral model
4. Iterative model and others.
By comparing the above methodologies our group selects ‘Iterative model’ because this model
are the following advantage
 Generates working software quickly and early during the software life cycle.
 This model is more flexible – less costly to change scope and requirements.
 It is easier to test and debug during a smaller iteration.
 In this model customer can respond to each built.
 Lowers initial delivery cost.
 Easier to manage risk because risky pieces are identified and handled during it’d
iteration.
1.8.3 Development tool

To develop this project some hardware and software tools will needed.
10
2019
1.9.4.1Hardware
Name of hardware Use
Desktop Computer or To perform any tasks
Laptop with (RAM According to [7] a web server that is capable of serving
4.00GB,Storage space more than 1000 users should have the following
300GB – 500GB , specifications
Processor 2.67GHz)
Printer To print out the end report of the project
CD For backup the data.
Flash disk 16GB and Store and transfer file
Hard disk 1TB
Table1: Hardware tools
1.8.4 Software
To develop our system we will use the following software tools:-
Software Use
Front end Software Programming Language: PHP, Coding purpose Why PHP?
According to [8], there are several
HTML, JS, CSS
types of web programming language
that are used for making a site more
dynamic. But, for this project chooses
PHP scripting language to design this
database. Because
It’s fast and easy
It’s cross platform
It accesses everything
It’s free
Back end Software My SQL Database Store data in an organized form
Why MySQL?
According to [9], there are several
reasons to use MySQL.
It’s quick and powerful
It’s improving all the time
11
2019
It’s free
Handles large database. MySQL with
some database that contains 50,000,000
records and users MySQL with 60,000
tables and about 5,000,000,000 rows.
All columns have default values. You
can use insert a subset of a table’s
columns; those columns that are not
explicitly given values are set to their
default value.
VertrigoServer Package contain PHP and

MYSQL database for storing
data
Windows7, 8.1 and 10 Operating General purpose of computer
System
Microsoft Word Writing the document
Notepad For writing PHP and HTML
code
Browser (Chrome, Mozilla Firefox To running and testing our PHP
43.0 and Internet Explorer) and HTML code
E-draw max and Visio 2013 To draw UML diagrams
Table2: software tools

1.9 Feasibility Study
The feasibility study is the preliminary study that determines whether a proposed system project
is financially, technically and operationally feasible.
1.9.1 Technical Feasibility
The system will be developed by following the object oriented system development technique,
and the team will have the ability to develop this system without any difficulty since the team
have studied the required methodologies and have tools for development, and also we will use
12
2019
currently exist technology’s to perform and to develop the system. So the entire group members
are expected the system will be technically feasible.
1.9.2 Operational Feasibility
Since we will organize friendly user interface any user can easily interact with the system. Also
we will provide a help menu to give direction for users. As the users are almost educated there is
no more complexity to the users.
The system will be secured because of only authorized person can access information due to user
name and password, and also the system will be efficient because to develop this system we will
use object oriented concept due to this we reuse resources.
1.9.3 Economic Feasibility

Economically our project does costly more and also the materials to implement the system will
cost great amount of money, since this project will be computerize the current manual system. So
we will reduce the cost of materials used in manual operation such as paper, pen, human power,
space needed to record, and save data storage & time that we can be induced or bring on during
in the manual system
 Our system is economical feasible because the cost that we generate in order to develop
our system is less than that of we will get from market after produce thissystem.
 Once the system is developed the organization will be beneficiary by reducing theamount
of money they rely on the manual system.
 Minimize the payment for the customer that work in the manual system so
theorganization is economically feasible.
Finally when the organization will need additional functions it is easy to add the needed
functionality because we use incremental development method.
1.10. Project Plans
1.10.1. Project Time Schedule

Within the time duration, we will have identified the activities of the project in order to
accomplish the project objective within their schedule requirement which is on the table below
Time duration
2011/2019 2012/2020
Activities
No
13
2019
Augs Septemb october novembe decembe April May June
Wee Week Week Week Week Week Week

k
1 2 3 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
1 Proposal and
Presentation
2 System Analysis
3 Presentation
4 System design
5 Implementation
and coding
6 Testing
7 Presentation
8 Post
Implementation
Table3: Time Schedule for Our Project
1.10.2 Project Cost

Activity Cost(in birr)
Requirement analysis 550.00
Design 365.00
14
2019
Coding 300.00
Testing 650.00
TOTAL 1,865.00
Table4: Cost estimation for each phase of the software development.
1.10.3 Budget Plan

NO Item Description Quantity Price (Birr)
1 Paper 3 360
2 Internet Access --- 100
3 Mobile card --- 300
4 CD 3 75
5 Photo copy 500 500
6 Pen 6 30
7 Flash Disk (16GB) 2 500
TOTAL COST --- 1,865 ETB
Table5: Budget plan
15
2019
Chapter Two
Requirement Elicitation
2.1 Introduction
This chapter contains description of existing system, business rule, drawback and advantage of
the existing system, proposed and preferred solution, domain modeling with CRC, essential use
case documentation, essential use case diagram and user interface prototype.
2.2 Description of the Existing System

After filling the first part, the students will go to the second part of the student evaluation form.
In this part, the evaluation form contains about thirty two (32) statements divided in to three
parts: Part A Part B and Part C, each containing eighteen statements.
Statements under Part A are focused on the performance of the instructors regarding to the
course and the approaches he /she used, statements under Part B focused on the knowledge of
subject matter and delivery whereas, statements under Part C focused on the relationship
between the instructor and their students. Students are expected to carefully read each of the
statements listed in both parts, and then they will indicate how they evaluate their instructors on
each statement by circling one of the options against each statement. The options are represented
as numbers ranging from 5 down to 1, and N where option “5” represents “Strongly Agree”, “4”
represents “Agree”, “3” represents Neutral, “2’ represents “Disagree”, and “1” represents
“Strongly Disagree” For both parts, the students will select one of the check boxes as an overall
judgment of the instructor
Finally the choices made by a student are added and the average choices are computed for the
student. Then, the total average choice is computed by adding the average choice of each student
and dividing the value by the total number of students. This value is used for decision making
processes. However this manual processing of the student evaluation form is tedious, time
taking, error prone and exhausting since one instructor is evaluated by a large number of
16
2019
students. On the other hand, processing of the student evaluation form can be automated by using
different system analysis techniques which enable to extract information from system software
2.3 Business Rule

Business rule define the rules of the organization that must be followed by the users. In every
organization or institutions there are rules and policy which used to govern all activities in
specified work flow that performed in the working environments.
 BR01: In each semester, students must have registered to his/her own department before
to evaluate his/her instructor.
 BR02: Evaluation process should processed at the end of each semester.
 BR03: At a time, one student can fills students’ fills form for a teacher.
 BR04: Student privileged to evaluate only instructor who teach a course for then.
 BR05: The must evaluated only the course they offer for students.
 BR06: Student can evaluate instructor based on his/her moral.
 BR07: To calculate and generate the evaluation result for some on all the respective
evaluator must evaluate according to the different criteria.
 BR08: The teacher’s evaluation has been conduct before final examination and after
completion of 90% of the course
 BR09: For Head or Dean Performance evaluation, ad-hoc committee selects 50%
randomly from staff members.
 BR10: For Instructors evaluation by peer must be grouped in to either one to three or one
to five group members, grouped by Head of department.
 BR11: every user who registered by system administrator for that system has the full
privilege to participate involves filling the form that it concerns.
2.4 Advantage of the existing system

The main advantages of the current manually student information system gives an opportunity
for students to have a good communication skill. In the existing system the workers only needs
writing and reading skill to handle manual data that doesnot need any knowledge of skill to
register costumer needs and information. It was easy to understand and, had clear and precise
course identification/ code.Students can easily view and record the different information like
schedule by their mobile devices by capturing a photo or writing on paper.On the other hand,
since, the system stored manually on paper, it did not depend on on/off or availability of electric
17
2019
service. In addition it is not must the availability of network service to perform a task searching,
storing, updating data.
2.5 Disadvantage of the existing system

The existing teacher evaluation system performs manually and this leads to security weakness.
Because of the manual system, is time consuming and boring. This is the result of lack of
computerized system or web-based system. When the project team was analyzing the existing
system, the team has tried to study the detailed nature and procedure of the tasks and operations
performed by the instructor evaluation system. The project team analyses the existing system
problem as by using a “PIECES” framework.
2.5.1 Performance Related problem

 Poor performance in terms of time.
 The work procedure is prone to error and tedious.
2.5.2 Information related problem
 Mishandling of information occur.
 Data is difficult to correct and maintain.
 Data is stored redundantly in multiple files.
 Data is not easily accessible.
 Data is not well organized.
 Data is not secure from damage.
2.5.3 Efficiency related problem
 Since the work is performing manually, the efficiency of the working system is poor.
 Since the data is stored in redundant manner, the information generated also is redundant.
2.5.4 Control related problem
 Security is another big issue concerning manual based system.
2.5.5 Economic related problem
 There is many requirement resource of paper; printer, pen and other are very cost
effective.
 Manual handling of data is expansive.
 Cost in terms of time is high.
2.5.6 Service related problem
 The instructor does not get better service and they do not satisfy with service.
18
2019
2.6 The proposed solution
The new system will designed to solve problems affecting the manual system in use. It is design
to be used online thereby relieving both the students, employees and the offices workers from
much stress as experienced in the manual system.
This system will perform the analyzing and storing of information either automatically or
interactively. It will make use of online access to Internet.
The proposed solutions are alternative solution that may help as to solve the disadvantage of the
existing system. The proposed solution is described below:
1. Web Based System: is a system that uses a website as the interface. User access the
application from any computer connected to the internet using standard browser, instead
of using an application that has been installed on their local computer. So any costumer
can access to get information on the website at any time.
2. Networked System: it is a system which works with a local area network for some limited
computer that is connected for that specific network.
3. Stand-alone application: A desktop or laptop computer that is used on its own without
requiring a connection to a local area network (LAN) or wide area network (WAN).
Although it may be connected to a network, it is still a stand-alone PC as long as the
network connection is not mandatory for its general use.
2.7 Preferred solution

Easy to manage and update: web based systems only need to be installed once on the company’s
server rather than separately installed on each of the end users workstations. This makes any
updates to the web based system quick and easy to roll out.The proposed system has many
applications and advantages compared to the existing system. It solves the problems of the
existing system and increase the performance of the evaluation. In our proposed system, we
develop a web based application instructor’s evaluation system that is capable of controlling the
evaluation form. Instructor’s Evaluation system is a web application more reliable and efficient
service. Any operations can have done easily with an easy interaction with the system.
Furthermore, the system especially could evaluate instructors and might calculate the evaluation
result more easily than before the existing system.
19
2019
The applications of proposed system are:
 Replace the manual to automated system.
 The proposed system enables to calculate the evaluation result and store evaluation
information in the database.
 The application composes different forms to store data to the database and retrieve required
information from the database.
 Create accounts for different users.
 It provides better and efficient service to the user.
 Reduce the workload of student, head of department, dean, quality assurance and reform and
staff members.
 Faster retrieval of information.
 Provides facility for proper monitoring, reduce paper-based work & provide data security.
 All details will be available in one click with the matter of second.
2.8 Domain Modeling With Class Responsibility Collaborator (CRC) Card

A Class Responsibility Collaborator (CRC) model is a collection of standard index cards that
have been divided into three sections, class, responsibility and collaborator. A class represents a
collection of similar objects, a responsibility is something that a class knows or does, and a
collaborator is another class that a class interacts with to fulfill its responsibilities.
CRC card
Class
Responsibility Collaborator
What the class knows(Name, ID, Address etc.)
What the class does(class activity).
Table 2.1: CRC card form
Administrator
20
2019
- Name - Head of
- ID Department
- Department
- Gender
- Birth place
- Manage Account-
- Manages users:
- Manage profile:
- Send notice:
Table 2.2: CRC card for administrator
Head of Department
- Name - Administrator
- Manage - Lecturer
profile: -
- Fills form
filled by
Head
department
- Self-
evaluate
- View result
- View
Report
Table 2.3: CRC card for Head of Department
- Lecturer
21
2019
- Name - Administrator
- ID - Head of Department
- Fills form by peer:-
the
- Fills form by staff

members:
- View result:.
- Self-evaluate
- View Report:
- Manage profile:
Table 2.4: CRC card for lecturer
Student
- Name - Administrat
- ID or
- Gender
- Fills form by student:
- Manage profile:
Table 2.5: CRC card for student
2.9 Essential Use Case Diagram

A use case diagram is a dynamic or behavior diagram in UML. Use case diagrams model the
functionality of a system using actors and use cases. Use cases are a set of actions, services, and
functions that the system needs to perform.
Relationships: Illustrate relationships between an actor and a use case with a simple arrow line.
 System administrator: - In this proposed system have a full privilege to access an does a
work related with managing the users, account such as Register user, delete user, and
22
2019
modify users, again create account, delete account, change password and related works
needs a role of system admin.
 Student:-One of the DDU social member who makes are attending the plays a vital role
 Teacher: -Person who teaches a subject or skill
 Head of Department: -An authorized person who manage overall activity which done at
department level.
 Vice-Dean of school: -The deputies in the college who is in charge of particular locations
or functions.
 Dean of school: -are top manager of the college who administrate different department
 Staff member: -the selected group from the different staff member.
 Quality assurance and Reform coordinator: -an authorized person who mainly
involves on academic quality assurance
 Vice-president: - The deputies in the Dire Dawa university who is in charge of particular
locations or functions. Also privileged to evaluate the college dean.
Directorate of teaching and learning: -An officer who control all the quality of teaching
learning methods in the university. In addition, they the right to evaluate the dean and vice dean
of the university
Table 10: List of actors and use cases for proposed system
List of Actors List of Use cases

Student Login
Dir. Of teaching and learning Calculate result
V/president Dean or V/Dean Generate report
Head of department Manage profile(change password, logout)
Manage Users (add users, delete users)
System administrator Department heads fills form
Quality assurance & reform Leaders fills form
Instructor Students fills form
Staff members fills form
Non-appointed fills form
Appointed fills form
View report
View result
Peers fills form
23
2019
Figure 2. 1: Essential use case diagram for Teacher performance evaluation system for DDU
2.10 Essential use case documentation
24
2019
2.11 Essential User Interface Prototype
The notice can prepare for two different categories, the academic and the administrative.
The manual notice looks the following:
25
2019
26
2019
27
2019
28
2019
ACADEMIC STAFF PERFORMANCE EVALUATION FORM 5
Instructor performance Evaluation Result Summary
Instructor’s/Trainer’s Name: __________________
1. Performance rating result summary

Immediate Colleagues Customers Self Total score Rank / status Remark
Supervisor’s / team rating evaluation out of
Rating members (40%) rating 100%
(20%) rating (10%)
(30%)
2. Instructor’s / trainers comment

Your contribution towards achieving better results in some activities
______________________________________________________________________________
______________________________________________________________________________
____________
Activities that have not been performed as per the standard and reasons for low performance
______________________________________________________________________________
______________________________________________________________________________
_____________
3. Immediate supervisor’s comments

Activities that have been performed well and instructor’s / trainer’s contribution towards that end
______________________________________________________________________________
______________________________________________________________________________
_____________
4. Comments agreed upon

Similar comments forwarded by both the instructor/trainer and the immediate supervisor
29
2019
______________________________________________________________________________
______________________________________________________________________________
_____________
Points of disparity between immediate supervisor’s and instructor’s comments
______________________________________________________________________________
______________________________________________________________________________
_____________
Issues upon which consensus has been reached by both parties
______________________________________________________________________________
______________________________________________________________________________
______________
Measures that are agreed upon and should be taken with the view to achieve better performance
results________________________________________________________________________
______________________________________________________________________________
_______________
Instructor’s/ Trainer’s Name: ____________________ Immediate Supervisor’s Name:
______________ Name:_____________________________
Signature:__________________________
Date: _____________________________ Date:
____________________________
Figure 2.2: essential user interface prototype
30
2019
Chapter Three
System Analysis
3.1. Introduction
This chapter deals with analyzing the proposed system. It includes the systems use case
diagrams, the use case descriptions (scenarios), sequence diagrams, class diagrams and activity
diagrams. After identifying the actors and use cases, the use cases are developed and textual
descriptions (scenarios) are stated. The Sequence diagram id depicted based on the use cases,
which are develop for the proposed system. The activity diagrams will represent activities.
3.2. Over view of the project
The new system is going to develop by keeping in mind the existing system as bench mark.
The proposed system has many applications and advantages compared to the existing system. It
solves the problems of the existing system and increase the performance of the evaluation. In our
proposed system, we develop a web based application instructor’s evaluation system that is
capable of controlling the evaluation form. Instructor’s Evaluation system is a web application
more reliable and efficient service. Any operations can have done easily with an easy interaction
with the system. Furthermore, the system especially could evaluate instructors and might
calculate the evaluation result more easily than before the existing system.
The applications of proposed system are:
 Replace the manual to automated system.
 The proposed system enables to calculate the evaluation result and store evaluation
information in the database.
 The application composes different forms to store data to the database and retrieve
required information from the database.
 Create accounts for different users.
 It provides better and efficient service to the user.
 Reduce the workload of student, head of department, dean, quality assurance and reform
and staff members.
 Faster retrieval of information.
 Provides facility for proper monitoring, reduce paper-based work & provide data
security.
 All details will be available in one click with the matter of second.
31
2019
3.3. System requirements
To distinguish the different features and aspects of the newly developed system we have tried to
use two approaches in requirement specification:
 Functional requirement
 Nonfunctional requirement
3.3.1. Functional requirements

The functional requirements generally deal with the different scenarios that depict an
operational System from the perspective of the end users:The functional requirement written in
term of its priority, requirement ID and the user of the system
. The following are some of the system functional requirements
For Administrator: -
 Manage Account- The new system asks user name and password and allows only
authorized users to access the database.
 Manages users: - the newly proposed system allows only the system administrator to add
new users and removes unauthorized users account if necessary.
 Manage profile: - the proposed system allows the users to change their password and
authenticates the users to access database. Also allows the users to logout the system
when performing of particular tasks.
 Send notice: -To notify the evaluation date and other necessary information to other
users.
For Head of Department: -
 Manage profile: -the proposed system allows the users to change their password and
 Fills form filled by Head department:-also, allows only head of department to fill the
form filled by head of department and save that result in database.
 Self-evaluate-Allows the head of department evaluates him/herself through filling a form

filled by appointed teachers.
 View result: -the new system allows the head of department to access his own result and
other teacher belongs to his/her leading.
32
2019
 View Report: - the proposed system allows the head of department to view report based
on some performing tasks regarding evaluation system that generated by high-level users.
For Instructor: -
 Fills form by peer:-the newly proposed system allows the instructors to fill the form
filled by peer and submits that
 Fills form by staff members: -the newly proposed system allows the instructor and
other staff members’ instructor to fill the form filled by staff members for evaluating
appointed teacher.
 View result: -also allow the instructors to view his/her own result in online.
 Self-evaluate- enables to evaluate him/herself through web based way.
 View Report: - the proposed system allows the instructors to view report generated for a
performing tasks before.
 Manage profile: -the proposed system allows the users to change their password and
For student: -
 Fills form by student: - allows the student to fills the form filled by student for every
instructor who takes courses for it again its head and dean.
 Manage profile: - the proposed system allows the users to change their password and
3.3.2. Non-functional requirements
While the non-functional requirement addresses Aspects of the system other than specific
functions it performs.There are many non-functional requirements ranging from user interface
to security issues. Generally non-functional requirements of our system can be viewed as
follows.
User friendly
 The interface should be user friendly.
 The system should support error-handling mechanism that display graphic approach and
the system guide the user what will be the next action.
Hardware consideration
33
2019
 The system may not need additional hardware. It uses desktop computer or laptop at front
end and database server at back end.
Software consideration:-Such as
 Front end:- Macromedia Dream Weaver
 Language:- HTML, CSS
 Database:-MYSQL, PHP web Server
 Server side script:- PHP

Availability: - The system should easily be available at any desired time.
Reliability: - The system is effective and consistent in that integrity of information is maintain
and supplied to the system
Usability The system is user friendly. The developed system provides web application user-
interfaces that are compatible with browsers like Mozilla Firefox, chrome, Baidu-spark.
Portability: -The system is machine independent and software system independent so, it can be
move to different target platforms.
Security Requirement
 The system support user name and password to authentic.
 The system has different privilege to protect intruding.
Performance: the system is responsibly fast in order to access the required information.
 This system is response with a second for requests.
Robustness (Error handling requirement).
Resources: The system is compatible with specified hardware and software environment.
Documentation: - The system contains the well designed, and manner documents needed to
implement the project
3.4. System modeling
The use case model provides detailed information about the behaviors of the system or
application that we are developing. The use case model identifies the requirements of the system
in terms of the functionality that must exist to achieve the goals set out by the user or to solve a
problem identified by the user.
System modeling: is the conceptual model as result of the modeling describes and represent a
system State.
34
2019
A use case defines a goal-oriented set of interactions between external users and the system
under consideration or development. Thus, a Use Case Scenario is a description that illustrates,
systematically, how a user is intending to use a system, essentially capturing the system behavior
from the user's point of view. In order to create relevant use cases for the system; we used the
following actors for the system has identified:
Components of use cases
Actor: is a person, or external system that plays a role in one or more interaction with the
system and represented with:
Use case: describes interaction of actions that provides something of measurable value to an
actor and drawn as a horizontal ellipse.
System boundary: indicates the scope of the system project. Anything within the box,
represent functionalities in side in scope.
Include Relationship: A part of use case, which appears in the same identical form in other
use cases or may be transferred to its own use case and re-integrated universally via an Include
relationship in order to avoid the redundant specification of these identical parts.
– – ‒<<include>> – – ‒>
Extend Relationship: If a part of the tasks transferred from one circumstance to another,
this modelled in its own use case. The arrow given the stereotype "extend". The Extend
relationship points to the use case to extended, and starts from that use case, which describes the
extension's behavior
– – ‒ <<extend>>– – ‒>
3.1.1 Scenarios
Manage user: System administrator login to the system with user name and password. The main
home page is displayed and there is menu of add user and delete user among those menus the
admin can choose what he/she want to perform. When the admin chooses to add user menu, the
system displays the new user’s registration form to the admin and the administrator enter all
valid input and submit it to the system, then the system provides default username and password
with the successful messages. When the admin wants to delete users he/she chooses delete menu
and click on it then the databases displays “would you want to permanently delete?”, alerts if ok
the selected user is deleted from the system and the system display success message.
35
2019
Manage profile: Admin, student, directorate of teaching and learning, quality assurance and
reform, dean or V/dean, V/president, instructor login into the system with user name and
password. Then main home page is displayed and each of the actor can manage their own profile
by changing Username and password and each of they can able to logout their accounts.
Generate report: Quality and reform can login to the system with user name and password. The main
home page is displayed and there is menu choose, among those users click on generate report button.
Then system displays the report to the users.
Change password: All actors clicks on login link at home page. The system displays Login
form, then they enter password and user name and they enter into their main page. Then they
choose change password link among various menus then the system prompts them to enter the
old password and new password; after that they fill and they click change button, then the system
display password is successfully changed message to user.
Fill evaluation form: Admin, student, directorate of Teaching and learning, quality assurance
and reform, dean or V/dean, V/president, instructor login to the system with user name and
password. System displays the main home page for each of them accordingly based on different
criteria, and then they fill all the provided criteria and submit it to the system. Then the system
displays successful message.
View result: Admin, directorate of teaching and learning, dean or V/dean, V/president,
instructor are want to view their result through login into the system and enter their unique id, the
system generates their results successfully.
View report: Admin, directorate of teaching and learning or dean or V/dean, V/president, and
instructor can view the generated report from quality assurance &reform by login into their own
pages.
Actor List
 System administrator: - In this proposed system have a full privilege to access an does a
work related with managing the users, account such as Register user, delete user, and
modify users, again create account, delete account, change password and related works
needs a role of system admin.
 Student:-One of the DDU social member who makes are attending the plays a vital role
 Teacher: -Person who teaches a subject or skill
 Head of Department: -An authorized person who manage overall activity which done at
department level.
36
2019
 Vice-Dean of school: -The deputies in the college who is in charge of particular locations
or functions.
 Dean of school: -are top manager of the college who administrate different department
 Staff member: -the selected group from the different staff member.
 Quality assurance and Reform coordinator: -an authorized person who mainly
involves on academic quality assurance
 Vice-president: - The deputies in the Dire Dawa university who is in charge of particular
locations or functions. Also privileged to evaluate the college dean.
 Directorate of teaching and learning: -An officer who control all the quality of
teaching learning methods in the university. In addition, they the right to evaluate the
dean and vice dean of the university.
Table 10: List of actors and use cases for proposed system
List of Actors List of Use cases

Student Login
Dir. Of teaching and learning Calculate result
V/president Dean or V/Dean Generate report
Head of department Manage profile(change password, logout)
Manage Users (add users, delete users)
System administrator Department heads fills form
Quality assurance & reform Leaders fills form
Instructor Students fills form
Staff members fills form
Non-appointed fills form
Appointed fills form
View report
View result
Peers fills form
37
2019
3.4.1. System use case
A use case diagram is a sequence of actions that provide a measurable value to an actor. It
describes the systems behavior as it responds to a series of related requests from an actor. This
use case perhaps the best way to capture functional requirements of the system. The following
diagram shows our system use case diagram.
Figure 1Use case diagram for Teacher performance evaluation system for DDU
38
2019
3.4.2. System use case documentation
Our system use case documentation provide a document to each activities performed by
scheduling actors on the system. From the above system use case we describe the core
function which is manage system user and schedule (such as add schedule, Edit schedule,
delete schedule and search schedule ), and print/ save schedule documentation about the
system as follows.
Use case Documentation

Use case ID Name
UC100 Login
UC101 Add users
UC102 Peers fills form
UC103 Appointed fills form
UC104 Logout
UC105 Staff members fills form
UC106 Change password
UC107 Leaders fills form
UC108 Students fills form
UC109 Department Heads fills form
UC110 Delete users
UC111 Calculate weight
UC112 Generate report
UC113 View report
UC114 View Results
39
2019
Table 11: Use case descriptions for Login use cases
Use case: Login
ID UC100
Admin, student, Head of department, Dean or V/dean, teacher, vice-president,

Actor
directorate of teaching and learning, and quality and reform coordinator
Description: A users need to login in to the system before performing any action.
Pre-condition: The users must have its own username and password to log in the system.
Post-condition: The users successful logged in to the system.
Main flow of events: 1. The users select login link among the menus list.
2. The system displays the login interface.
3. The users fill username and password, and submit to the system.[A1]
4. The system validates input and accept.[A2]
5. Then the system displays the Main home page for the user
6. Use case end.
If the one of the form lefts empty by the users:-
Alternative flow
Event[A1] 1. the system informs the users to complete the left field
2. Use cases return back, and continues from step main flow event.
If the users complete with wrong username and password:-
Event [A2] 1. The systems display error message and informs the users to try to fill the
correct username and password.
2. Use cases return back, and continues from step 3 main flow event.
40
2019
Table 12: Use case descriptions for Add users use cases
Use case: Add users

ID UC101
Actor: Admin
Description: Allow admin to add new user to the system.
Pre-condition: The system administrator logged in to the system successfully.
The system displays successfully accomplishment of tasks and generate

Post-condition
default username and password for each user.
1. The system admin select add user link.

2. System display user registration form.
Main flow of event: 3. System admin complete the form and submit it. [A1]
4. System validates and creates new account to user.
5. Use case ends.
If the one of the fields left empty by users or filled with incorrect input
Alternate flow of Event 1. System informs the administrator to fill correct input or fill the field lefts
empty with appropriate input.
Table 13: Use case descriptions for peer fills form use cases
Use case: Peers fills form

ID UC102
Actor: Instructors
The system shall allow the instructors able to evaluate each other based on
Description:
specific criteria.
Pre-condition: The instructor must logged in to the system successfully.

Post-condition The system display message for successfully accomplishment of task.
1. The users’ selects peer evaluate link.

2. The system displays the peer evaluation form to user.
Main flow of event: 3. The instructor fills the provided field and submits evaluation form by
clicking on peer evaluation button [A1].
4. The system validates input and store evaluation result to database.
5. The use case ends.
41
2019
If the field lefts empty by users or fill the field with invalid input:-
Alternate flow of
1. The system displays error message; the system informs the users to fill
Event [A1].
the field lefts empty or filled with incorrect input.
Table 14: Use case descriptions for appointed fills form use cases
Use case: Appointed fills form

ID UC103
Actor: Head of department and dean or V/dean
Description: The system shall allow self-evaluation for both head of department and dean
or V/dean through filling forms filled by appointed teacher.
Pre-condition: Users must logged into the system successfully by their own account.
Post-condition Display message about successfully accomplishment of task to users.
1. The users selects appointed self-evaluation links
2. The system displays the appointed self-evaluation form to the users.
3. The users, fills the form provided and submit form. [A1]
Main flow of event:
4. The system validates the input and stores (saves) on a database.
If the field lefts empty by users or fill the field with invalid input:-
Alternate flow of 1. The system displays error message; the system informs the users to
Event [A1].
fill the field lefts empty or filled with incorrect input.
42
2019
Table 15: Use case descriptions for Logout use cases
Use case: Logout
ID UC104
Student, Instructor, Head of department, Dean or V/Dean, Reform and
Actor:
Quality Assurance, V/President, Directorate of teaching and learning, and
System administrator
Description: The system allows those usersto logout or sign out from the page when
he/she wants to back to home page or exit from the system.
Pre-condition: Users must logged in to system successfully first, then finish his currently
performing task if there.
Post-condition The systems log out or must be sign out.
Main flow of event: 1. They want to log out
2. They click the log out button
3. The system responds to the requested action.
4. System returns the users to the home page.
5. Use case Ends
Table 16: Use case descriptions for staff members fills form
Use case: Staff members fills form

ID UC105
Actor: Instructors
The system shall allow the randomly selected staff members, to fill the form
Description:
filled by staff members.
Pre-condition: Instructors must logged into the system successfully.

Post-condition The appointed evaluated successfully.
1. The users select staff members form link
2. The system displays forms filled by staff member to the user.
3. The users fills the form provided and submit form. [A1]
Main flow of event:
43
2019
If the field lefts empty by users or field with invalid input:-
Alternate flow of Event 1. The system displays error message; the system informs the users to
[A1] fill the field lefts empty or filled with incorrect input.
Table 17: Use case descriptions for change password use cases
Use case: Change password

ID UC106
Student, Instructor, Head of department, Dean or V/Dean, Reform and
Actor:
Quality Assurance, V/President, Directorate of teaching and learning, and
System administrator
Description: The system shall allow change password for the new user enter in to the
system for the first time and for other.
Pre-condition: The users must logged in the system and remember the old password
Post-condition The users account password changed successfully and save the current
password in to database.
1. The users selects change password links
2. The system displays the change password form to the users.
3. The users fills the form provided and submit form. [A1]
Main flow of event:
4. The system validates the input and clear the previous from database
stores a current one. [A2]
Alternate flow of Event 1. If the field lefts empty by users or fills incorrect input in the field provided: -
1.1 The system displays error message and, the system informs
For event [A1] 1.2 Use cases return back, and continues from step 3 main flow
again recommended to fill the either the left or invalid input.
For event[A2] 2. If the current password and the previous one is not match: -
2.1 The system, display error message!
44
2019
2.2 Use cases return back, and continues from step 3 main flow
again, recommends the users to input the correct old password.
Table 18: Use case descriptions for leaders fills form use cases
Use case: Leaders fills form

ID UC107
Actor: Dean or V/dean, Dir. Of teaching and learning, V/President,
The system shall allow dean, or V/dean, directorate of teaching and learning,
Description:
and V/president to fill the form filled by leader
Pre-condition: Users must logged into the system successfully by their own account.
Post-condition The system displays a successfully accomplishment of tasks performed.
1. The users selects leaders fills form links
2. The system displays the form filled by academic leader to the users.
3. The users fills the form provided and submit form.[A1]

Main flow of event:
Alternate flow of 1. The system displays error message; the system informs the users to
Event[A1]
fill the field lefts empty or filled with incorrect input.
2. Return back to step 3 main flow event.
Table 19: Use case descriptions for students fills form use cases
45
2019
Use case: Students fills form
ID UC108
Actor: Student
Description: The system shall allow the students to fill the form filled by student.
Pre-condition: The student logged in to the system successfully
Post-condition The system display the successfully message for performed task.
1. The student selects form filled by student link.
2. The system display form filled by student.
3. The student fills the provided field and submits evaluations.[A1]

Main flow of event:
1. The system displays error message; the system informs the users to fill
Alternate flow of Event
the field lefts empty or filled with incorrect input.
2. Use cases return back, and continues from to step 3 main flow event.
Table 20: Use case descriptions for department heads fills form use cases
Use case: Department Heads fills form

ID UC109
Actor: Head of department
Description: The system shall allow the head of department to fill the form filled by head of
department.
Pre-condition: The head of department logged in to the system successfully
Post-condition The system displays successful message for the performed task.
1. The head selects the forms filled by head of department link.
2. The system display the form to the leader of department.
3. The leader fills the provided field and submits evaluation result by clicking
Main flow of event: on submit button.[A1]
Alternate flow o If the field lefts empty by users or field with invalid input:-
f
46
2019
1. The system displays error message; the system informs the
users to fill the field lefts empty or filled with incorrect
Event [A1] input.
2. Use cases return back, and continues from step 3 main
flow event.
Table 21: Use case descriptions for delete users use cases
Use case: Delete user
ID UC110
Actor: Admin
Description: The system shall allow the system administrator to delete users account if needed.
Pre-condition: The system administrator logged in to the system successfully
Post-condition The system display message for successfully accomplishing of task.
1. The system administrator selects remove user account link.

2. The system displays the list all users to system administrator.
Main flow of event: 3. The administrator selects that account who want to remove and submits
delete button.
4. The system pops out the confirmation message to the administrator. [A1]
If the administrator decided right to remove
The system displays successfully accomplishing message.
Alternate flow of Event Else
For event [A1] 1. The system displays the message the removing users account is not finished!
2. Use cases return back to step 3 main flow event, and again
recommends the administrator by displaying another message “do
you want to remove another user”.
Table 22: Use case descriptions for calculate weight use cases
Use case: Calculate weight
47
2019
ID UC111
Actor: Quality assurance and reform
Description: The system shall allow the quality assurance and reform to calculate result
through accessing from the databases
Pre-condition: The Quality assurance and reform logged in to the system successfully
Post-condition The system displays success message for the tasks performed.
1. The reform and quality assurance users request to calculate weight
and click on the link.
2. Then, the system displays calculate weight form to the users.
3. Then users complete the form and submits by clicking on calculate
Main flow of event:
weight button.[A1][A2]
4. Then the system store evaluation result and display successfully
completion of tasks
1. If the field lefts empty by users: -

a. The system pops out error message and informs the users to fill with
[A1].
the correct input
b. Use cases return back, and continues from step 3 main of flow event.
[A2]. 2. If the system did not find from the database or if there is not yet
evaluation form submitted
a. System displays error message for invalid selected teacher form did
not submitted and informs the users try for other teachers.
b. Use case return backs and continues from step 3 of main flow of event.
Table 23: Use case descriptions for generate report use cases
Use case: Generate report( View Result)

ID UC1112
Actor: Quality assurance and Reform
48
2019
Description: The system shall allow the Quality and Reform to generate report
Pre-condition: The users must login in to the system
Post-condition The Quality assurance and Reform has generated report for the whole result.
1. The users’ selects generate report link.

2. The system displays the generate report form.
3. The users select appropriate parameters based on form request and
Main flow of event: click view result Button [A1].
4. The system successfully displays the whole result in a report format
based on selected parameters.
1. If the field lefts empty by users or fill the field with invalid input: -
1.1 The system displays error message, and recommends the user to fill
[A1].
with the correct input or fill the with lefts empty
1.2 Use case return back to step 3 main flow of event.
Table 24: Use case descriptions for view report use cases
Use case: View report

ID UC1113
Actor: Instructor, head of department, dean or V/dean, V/president, directorate of
teaching and education
Description: The system shall allow the users to view the report
Pre-condition: The users must logged in to the system successfully through their own account.
Post-condition The system, displays generated report format successfully to the users.
1. The users’ requests to view report generated for the tasks performed.
2. The users selects view report link from their own main page menus.
3. The system allows the users to choose from different parameters for
types of report to wants to view.
Main flow of event: 4. The users chooses single parameters, and submits by clicking on view
report button [A1].
5. The system displays the generated report through considering the
chosen parameters.
49
2019
Alternate flow of Event 1. If the users did not chooses the field provided as parameters.
[A1].
a. The system displays error message, and recommends
the users to choose parameters.
b. Use case return back, and continues to step 3 main flow of event.
Table 25: Use case descriptions for view results use cases
Use case: View result

ID UC1114
Actor: Instructor, Head of Department, dean or V/dean
The system shall allow the users to access their own result, and considering
Description:
privilege for appointed teacher.
Pre-condition: The users must logged in to the system successfully.
Post-condition The users has viewed his/her own evaluation result securely.
1. The users’ select view result link.
2. The system provides view result form to the users.
Main flow of event: 3. The users select and complete appropriately the pops out field [A1].
4. The system displays the result and again the feedback forwarded
from the evaluation form
Alternate flow of Event If the field lefts empty by users or fill the field with invalid input: -
[A1].
a. The system displays error message, and the system
recommends the users either fill the field left empty before
or fill with field with correct input
b. Use case return back, and continues from step 3 main flow of event.
50
2019
3.4.3. Sequence diagram
The sequence diagram of our system shows the sequences which are taken to perform scheduling
activities and services from use case scenario to system processes. The following are our scheduling
system main sequence diagrams:
Figure 4: Sequence diagram for login form
Figure 5: Sequence diagram for Add new users
51
2019
Figure 6: Sequence diagram for staff members fills form
52
2019
Figure 7: Sequence diagram for peer fills form
53
2019
Figure 8: Sequence diagram for change password
Figure 9: Sequence diagram for heads of department fills form
Figure 10: Sequence diagram for students fills form
54
2019
Figure 11: Sequence diagram for appointed fills form
Figure 12: Sequence diagrams Leaders fills form
55
2019
Figure 13: Sequence diagram for Delete user
56
2019
3.4.4. Activity diagram
The activity diagram of our scheduling system supports to modeling the lifetime of the activities
in the system. The following diagram shows the flow of control from activity to an activity in our
system.
a c t Add us e r
Add Us e r
Click on Add user link
Register new user form will be display ed
Sy stem admin complete the form
Submit F orm
All F ields v alidated?

No
Ye s
Sav e on Database
New user added successfully
Figure 15: Activity diagram for add user
57
2019
a c t De le te Us e r
Click on Delete User link
List of User displyed
Selects user wants to be delete
Click Delete Button
Do you want
Permanently remove? No
Ye s
Remove from Databes
Successfully deletion accomplished!
Figure 16: Activity diagram for Delete user
Figure 17: Activity diagram for leaders fills form
58
2019
a c t Pe e rs fills form
Pe e rs fills form
Click on Peer evaluate link
Peer evaluation form will be displayeed
Instructor complete the form
Submit Form
All Fields No
validated?
Ye s
Save on Database
Evaluation successfully accomplished
Figure 18: Activity diagram for peers fills form
59
2019
a c t Sta ff me mbe rs fills form
Staff me mbe rs
fills form
Click on staff evaluation link
Staff member evaluation form will

be displayeed
Instructor complete the form
Submit Form
All fie ld s No
valid ate d ?
Ye s
Save on Database
Evaluation successfully
accomplished
Figure 20: Activity diagram for staff members fills form
a c t De pa rtme nt he a ds fills form
De partme nt
he ads fills form
Click on ins tructor e valuation link
Evaluation form will be dis playe d
He ad of de partme nt comple te the form
Submit Form
All fields Validated? No
Ye s
Save on Databas e
Evaluation s ucce s s fully accomplis he d
Figure 21: Activity diagram for Department Heads fills form
60
2019
a c t S tude nts fills form
Stude nts fills

form
Click on Te ache rs e valuation link
Evaluation form will be dis playe d
Stude nt comple te the form
Submit Form
All fields validated ?

No
Ye s
Save on Databas e
Evaluation s ucce s s fully accomplis he d
Figure 22: Activity diagram for students fills form
a c t Appointe d fills form
Appointe d
fills form
click on s e lf-e valuate link
Se lf-e valuation inte rface dis plye d
No
Fill the e valuation form
Submit e valuation form
All fields Validated?
Ye s
Save on databas e
Evaluation s ucce s s fuly accomplis he d!
Figure 23: Activity diagram for Appointed fills form
61
2019
3.4.5. Conceptual class diagram
The conceptual class diagram of our scheduling system notifies Classes that are identified from
scheduling system and specify each class by adding the possible methods an attribute. These
Classes during this phase are helping in developing the source code. The class diagram is the
main building block of object oriented modeling. It is used both for general conceptual
modeling of the systematic of the application, and for detailed modeling translating the models
into programming code. The classes of the scheduling system are integrated as follows:
62
2019
Chapter Four
System Design
4.1. Introduction
In the previous chapter we have identified the functional and non-functional requirements of the
system and produced the analysis model. The following are discussed in this chapter: design
goals, system architecture, system decomposition, deployment and database design and interface
design. Systems design is the process of defining the architecture, modules, interfaces, and data
for a system to satisfy specified requirements. Systems design could be seen as the application of
systems theory to product development. There is some overlap with the disciplines of systems
analysis, systems architecture and systems.
4.2. Proposed software architecture

The proposed system is a 3-tier (client, server, and data) where clients use the system software to
access the database server in a local area network using HTTP as a protocol. The data tier
controls the software’s data related to class and exam scheduling system and store or retrieve
these data to/ from a relational database.
LAN
Figure 2architecture for the system
63
2019
4.3. Sub System decomposition
Figure 3subsystem decomposition for the system
64
2019
Figure 4subsystem decomposition for student and instructor
Figure 5subsystem decomposition student, instructor, and dep't head
65
2019
4.4. System class diagram
Figure 6system class diagram for the system
4.5. State chart diagram

The state chart of the scheduling system used to model and identify the behavior with in our
system and behaviors specified to the instances of a single class. The following diagram shows
the flow of control from state to state.
66
2019
Figure 7state diagram for create account
Figure 8state diagram for login
67
2019
Figure 9state diagram for edit user
Figure 10state diagram for delete use
68
2019
Figure 11state diagram for add user
Figure 12state diagram for print or save result
4.6. Collaboration diagram

Collaboration diagram of our system represents a combination of information taken from class,
sequence, and use case diagrams that describes the behavior of a system. And it also shows data
flows between objects
Collaboration diagram represent a combination of information taken from class, sequence, and
use case diagrams describing both static structure and dynamic behavior of a system. And it
also shows some data flows between objects and the interaction caused between them. The
following figures show the Collaboration Modeling of the system.
Figure 13collaboration diagram for login
69
2019
Figure 14collaboration diagram for manage account

1.1.Persistence data management
It is achieved in practices, for storing the states in the system database to store and manage
system data.
70
2019
Figure 15data persistence management system.

1.2. Component diagram
The component diagram of our Performance system shows how the physical components
(system actors) are organized. And which of our physical component modules or objects will
be accessed by whom and what type of security infrastructures it is considering to use.
71
2019
Figure 16component diagram for the system
1.3. Deployment diagram

In the deployment diagram of our scheduling system, it intends to show the hardware of the
system, the software that was installed in the hardware and the middle-ware or the server that
connects the disparate machines to one and another [5].
72
2019
Figure 17deployment diagram for the system
1.4.User interface design
Figure 18user interface for home page
73
2019
Figure 19user interface for login
Figure 20user interface for wronged password
CHAPTER FIVE
2. CONCLUSION AND RECOMMENDATION

2.1. CONCLUSION
Conclusion provides an effective ending to our project and the content should relate to the aim of
the project [2].
This system is DDU class scheduling system for regular students and the proposed system
address add/drop case for students. Our system is networked class ,exam and lab scheduling
system it is a more important system in our university for avoiding many problems such as cl ash
class , room optimizing, add/drop case and assigning a course to un available or inactive
instructor.
74
2019
It is attractive and user friendly interface easy to access for anyone .the objective of this project
is develop functional and conflict free networked class and exam scheduling system for DDU.
The system provides all information needed for class, exam and lab scheduling (view, save and
print for the user and store, update and delete footer for the registrar and department head .and
we use several data collection methodologies by interview and observing the working
environment and use iterative a development approach.
The new system is feasible at different aspects on economical , technical , operational and time
feasibility to given immediate response to the users ,refers to benefit or outcomes we can
divining from the product and compressed to total cost that is economical feasible and it is
measure of how will a proposed system to solve the problem operationally it is feasible .this
system has been developed using PHP as front-end and MYSQL at back end by working those
our system is technical feasible.
The system is have functional and non-functional requirements .the functional requirements
include manage information about the schedule ,validate the data users tray to store , search
retrieve and generate notifications and feedback and the other hand in non-functional
requirements performance ,robustness, reliability, and scalability. We have four actors in our use
case diagram those are registrar, department head, instructor and students. By their collaboration
and sequence activities work the system. Our proposed software architecture is 3 tire (client,
server &data).
We use many diagrams to describe how to work the system such as activity diagram, sequential
diagram, collaboration diagram, system class diagram, etc. they are clearly describing activity
sequence of each actors, their relationship and responsibilities of those by their attributes and
entity of the class or objects.
2.2. RECOMMENDATION
Nowadays, the world is highly becoming a competitive world. Organizations have to divert their
attention on using the recent technology to be on the first line and competitive. This can be real if
they are able to use computerized system to successfully achieve their objective. DDU is the
Government institution that includes many offices in fulfilling its function. As we describe in this
document, almost all activities of the organization is done on manual basis. The project team wants
to recommend some ideas considering the project .This project is developed based on the current
problems of scheduling system of DDU registrar office so we think that this project is the best
75
2019
solution for the problems raised based on the manual system of the office. And help the office to
save time, money and man power whenever the project is small scale.
From the various facts that constitute the project, the following points can be recommended:
 Attention should be given to the existing practice in the design, development and
utilization of the new system.
 Serious consideration should be given for the introduction of the new system.
 Behavioral change of the users of the system to adapt the new system.
 There should be a network infrastructure in order to connect the different computers and
access the system.
 We advise that the site be hosted on a secure server and that the administration of the
website is given to a person or entity that has experience in managing a website.
 We also fell for ease of access an accompanying application is developed for the system
for Smartphone implementing the Android and IOS operating systems.
 We also recommend the new system to be applicable not only for DDU but also for other
universities, High schools and elementary schools by upgrading the boundary.
References
[1] D. D. university, "Dire Dawa university 10th year anniversary," DDU, Dire dawa, Ethiopia,
2009.
[2] A. i. P. C. S. ·. D. 2015, "Automated_Scheduling_System_for_Thesis_and_Project," 11

February 2016. [Online]. Available: https://www.researchgate.net/publication/290014669.
[Accessed 16 march 2017].
[3] D. Thakur, "ecomputer.com/software engineering/feasibility study," 12 05 2015. [Online].

Available: http://www.ecomputer.com/software engineering/feasibility study. [Accessed 17
09 2017].
[4] R. Biddle, "www.mcs.vuw.ac.nt/essential use case." 22 may 2012. [Online]. Available:

http://www.mcs.vuw.ac.nt. [Accessed 16 04 2017].
76
2019
[5] A. Akoko, class time table management system for NCMT college, Asia: www.aaua.edu.ng,
2015.
[6] WIKIPEDIA, "functional requirement, system design, project plan requirement elicitation,
non-functional requirement," 21 12 2013. [Online]. Available: http://en.wikipedia.org.
[Accessed 17 09 2017].
[7] H. POST, "www.huffingtonpost.com/static/business rule," 17 may 2014. [Online].

Available: http://www.huffingpost.com. [Accessed 16 Jan 2017].
4.7.
[8] P. A. Igbekele, "kupdf.com_new-class-scheduling-system," 12 08 2016. [Online]. Available:
http://www.google.com/class-scheduling system pdf. [Accessed 23 04 2017].
1.10. REFERENCE
[1] Zhibing Liu, H. W., HuiZan, Design and implementation of student information management
system. International symposium on intelligence information processing and trusted computing,
2010
[2] Rumbaugh, J., Jacobson, I., &Booch, G., The Unified Modeling Language Reference
Manual: the definitive reference to the UML from the original designers. 2003, Singapore:
Pearson Education Inc.
[7] Williams, J., New Hardware Purchasing Guidelines 2012.
[8] Greenspan, J., Wall, D. and Bulger, B., MySQL/PHP Database Applications. 2004.
[9] Lane, D. A. W., H. E., Web Database Applications with PHP and MySQL. 2004: O'Reilly.
https://en.wikipedia.org/wiki/Enrollment
GRADING SYSTEM
http://www.deped.gov.ph/orders?f%5B0%5D=field_classification%3A226
STUDENT INFORMATION SYSTEM
http://www.techlearning.com/student-information-systems
http://edutechwiki.unige.ch/en/Student_management_system
STUDENT PORTAL
77
2019
http://our.upou.edu.ph/student/
https://myuste.ust.edu.ph/student/
https://www.ue.edu.ph/studentsportal/?nav=ebsco
Joshua Joloc, PUP Student Information System as perceived by PUPSMB Students
https://prezi.com/fuvgiygrh71g/pup-student-information-system/
PhilnaPalongpalong; Virginia Verdun; Yolanda Sayson; Melvin Niñal and Leo Bemudez,
Automated Enrollment System For a State College
http://uc.edu.ph/journals/wp-content/uploads/2016/05/Paper-9-Enroll.pdf
78

Umer Aliyi - S/259/07

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Umer Aliyi - S/259/07

Hochgeladen von

Copyright:

Verfügbare Formate

DIRE DAWA INSTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

DIRE DAWA INISTITUTE OF TECHNOLOGY

A Project submitted to Dire Dawa University in partial fulfillment of the

List of tables ........................................................................................................................................... 3

1.1 Background of the Organization................................................................................................... 5

1.2 Background of the Project ............................................................. Error! Bookmark not defined.

1.3 Statement of the Problem ............................................................................................................. 5

1.4. Objective of the Project ............................................................................................................... 7

1.4.1 General Objective .................................................................................................................. 7

1.4.2 Specific Objective ................................................................................................................. 7

1.5 Scope of the project ...................................................................................................................... 7

1.6 Limitation of the Project ............................................................................................................. 8

1.7 Significance of the Project.......................................................................................................... 8

1.8 Beneficiaries of the Project .......................................................................................................... 8

1.9 Methodology ................................................................................................................................ 9

1.9.1 Data Gathering Methodology ................................................................................................ 9

1.9.3Development approach ......................................................................................................... 10

1.9.4 Development tool .............................................................................................................. 10

1.10 Testing methodology ................................................................. Error! Bookmark not defined.

1.11 Feasibility Study ....................................................................................................................... 12

1.11.1 Technical Feasibility.......................................................................................................... 12

1.11.2 Operational Feasibility ...................................................................................................... 13

1.11.4 Schedule Feasibility.............................................................. Error! Bookmark not defined.

1.13. Project Plans ............................................................................................................................ 13

1.13.1. Project Time Schedule ...................................................................................................... 13

1.13.2 Project Cost ....................................................................................................................... 14

1.12.3 Budget Plan ....................................................................................................................... 15

1.1 Background of the Project

1.2 Statement of the Problem

1.3. Objective of the Project

1.3.1 General Objective

1.3.2 Specific Objective

1.4. Scope of the project

1.6 Significance of the Project

 Provides secured service for all users of the system.

 Able to reduce the workload of Instructor as well as student.

 Therefore, it minimizes the time and work force.

 The system gives fast delivery evaluation report for schools.

 Accuracy and confidentiality of evaluation data maintained

1.7 Beneficiaries of the Project

For Head of Department: -

 Reduce workload and time consumption

 View the result through online

The project development team.

1.8.1 Data Gathering Methodology

1.8.3 Development tool

Table1: Hardware tools

VertrigoServer Package contain PHP and

E-draw max and Visio 2013 To draw UML diagrams

Table2: software tools

1.9.3 Economic Feasibility

1.10. Project Plans

1.10.1. Project Time Schedule

Wee Week Week Week Week Week Week

Table3: Time Schedule for Our Project

1.10.2 Project Cost

Requirement analysis 550.00

Table4: Cost estimation for each phase of the software development.

1.10.3 Budget Plan

Table5: Budget plan

2.2 Description of the Existing System

2.3 Business Rule