University of Gondar

College of natural and computational science

Department of computer science
Industrial project
Web-based online student registration for university of Gondar fasil
campus
Developed by:
Name ID

1. Abeba Fekadu----------------------------1076/05
2. Aberu Mamo------------------------------1083/05
3. Ambaw Mulat-----------------------------1099/05
4. Belachew Gebrie--------------------------1117/05
5. Hemen Teklie------------------------------1194/05
6. Shegaw Tassew----------------------------1285/05

Project advisor Anteneh Mekuryaw

Jan 15/01/ 2016

 I

Certificate
This is to certify that this BSc industrial project report entitled web-based online student
registration for University of Gondar Fasil Campus by:

1. Abeba Fekadu
2. Aberu Mamo
3. Ambaw Mulat
4. Belachew Gebrie
5. Hemen Teklie
6. Shegaw Tassew

is approved by me for submission. I certify further that, to the best of my knowledge, the report
represents work carried out by the students.

___________________________ ____________________________________
Date Name and Signature of Supervisor

Department of computer science

 II

Declaration
This is to declare that the project work is done under the supervision of Mr. Anteneh Mekuriaw
and having the title web-based online student registration system for University Gondar Ate Fasil
campus is the sole contribution of:
Abeba Fekadu
Aberu Mamo
Ambaw Mulat
Belachew Gebrie
Hemen teklie
Shegaw Tassew
No part of the project work has been reproduced illegally which can be considered as Plagiarism.
All referenced parts have been used to argue the idea and cited properly. We will be responsible
and liable for any consequence if violation of this declaration occurs.

Date: Jan 2016

Group members:

Full Name: Signature

Abeba Fekadu ________________________________

Aberu Mamo _________________________________

Ambaw Mulat _________________________________

Belachew Gebrie _________________________________

Hemen Teklie _________________________________

Shegaw Tassew __________________________________

Department of computer science

 III

Acknowledgement
Above all, we would like to thank the almighty GOD for guiding us throughout the project.
Then, we would like to thank all those who contributed throughout the completion of the project
and helped us with value able suggestions for the improvement of the system.
We are extremely grateful for our advisor Instructor ANTENEH MEKURIAW for guiding us
throughout the completion of the project. We would like to thank Instructor Yosef the
department head for helping us having a computer usage in the lab.

Department of computer science

 IV

Abstract
The main objective of this project is to develop web-based student registrar system for university
of Gondar Ate Fasil campus. This web-based application helps the college to serve students in
optimized way and used to facilitate the efficiency of the registrar system for storing and
retrieving any student information to and from the database. This document holds the main
activities done towards the success of the project. It contains the introduction and background of
the organization, the problem statement, the objective and significance of the project in chapter
one. In chapter two it contains the requirement analysis activities such as current system
description and proposed system analysis such as scenario; use case diagram, use case
description, activity diagram, sequence diagram, class modeling, and user interface. I chapter
three we describe system design activities such as current software architecture, proposed
software architecture, subsystem decomposition, hardware/software mapping, persistent data
management strategy, access control and security, subsystem service, detailed class diagram
,and packages.

Department of computer science

 V

Table of content

Contents
Certificate...................................................................................................................................................... 1
Declaration .................................................................................................................................................... 2
Acknowledgement ........................................................................................................................................ 3
Abstract ......................................................................................................................................................... 4
Table of content ............................................................................................................................................ 5
List of figures ................................................................................................................................................ 8
list if table ................................................................................................................................................... 12
Definitions................................................................................................................................................... 13
Chapter one ................................................................................................................................................... 1
1. Project proposal .................................................................................................................................... 1
1.1. Introduction ................................................................................................................................... 1
1.2. Statement of the Problem .............................................................................................................. 2
1.3. Objective of the project ................................................................................................................. 3
1.3.1. General objectives of the project........................................................................................... 3
1.3.2. Specific objective of the project............................................................................................ 3
1.4. Scope and limitation of the project ............................................................................................... 4
1.4.1. Scope of the project............................................................................................................... 4
1.4.2. Limitation of the project: ...................................................................................................... 5
1.5. System development methodology ............................................................................................... 5
1.6. Investigation (fact-finding) methods ............................................................................................. 5
1.6.1. Direct observation ................................................................................................................. 5
1.6.2. Interview ............................................................................................................................... 6
1.6.3. Inspect form slips .................................................................................................................. 6
1.7. System development tools ............................................................................................................ 6
1.7.1. Software tools ....................................................................................................................... 6
1.7.2. Hardware tools ...................................................................................................................... 7
1.8. Significance of the project ............................................................................................................ 7
1.9. Beneficiaries ................................................................................................................................. 7
1.10. Time scheduling ........................................................................................................................ 9

Department of computer science

 VI

Chapter two ................................................................................................................................................. 10

2. Requirement analysis .......................................................................................................................... 10
2.1. Introduction ................................................................................................................................. 10
2.2. Current system ............................................................................................................................ 10
2.2.1. Major function of the current system/ current system description ...................................... 10
2.2.2. Problem of the existing system ........................................................................................... 10
2.3. Requirement gathering ................................................................................................................ 11
2.3.1. Requirement gathering methodologies ............................................................................... 11
2.3.2. Results found ...................................................................................................................... 11
2.4. Proposed system.......................................................................................................................... 11
2.4.1. Overview ............................................................................................................................. 12
2.4.2. Functional requirements...................................................................................................... 12
2.4.3. Non-functional requirements .............................................................................................. 13
2.5. System model .............................................................................................................................. 15
2.5.1. Scenario............................................................................................................................... 15
2.5.2. Use case model.................................................................................................................... 23
2.5.3. Object model ....................................................................................................................... 74
Chapter three ............................................................................................................................................. 112
3. System design ................................................................................................................................... 112
3.1. Introduction ............................................................................................................................... 112
3.2. Current software architecture .................................................................................................... 112
3.3. Proposed software architecture ................................................................................................. 112
3.3.1. Overview ........................................................................................................................... 112
3.3.2. Subsystem decomposition ................................................................................................. 113
3.3.3. Hardware/software mapping ............................................................................................. 115
3.3.4. Persistent data management strategy ................................................................................ 115
3.3.5. Access control and security............................................................................................... 116
3.3.6. Subsystem service ............................................................................................................. 119
3.4. Detailed class diagram .............................................................................................................. 122
3.5. Packages .................................................................................................................................... 126
4. Implementation ................................................................................................................................. 127
4.1. Mapping model to code................................................................................................................. 127
4.2. Screen images ............................................................................................................................... 136

Department of computer science

 VII

5. Conclusion ........................................................................................................................................ 137

Recommendation ...................................................................................................................................... 137
6. Bibliography ..................................................................................................................................... 138
7. Glossary ............................................................................................................................................ 139
References ................................................................................................................................................. 140

Department of computer science

 VIII

List of figures
Figure 1 use case diagram ............................................................................................................. 24
Figure 2 use case diagram cont… ................................................................................................. 25
Figure 3 use case diagram cont… ..................................................Error! Bookmark not defined.
Figure 4 activity diagram for create account ................................................................................ 51
Figure 5 activitydiagram for view account ................................................................................... 52
Figure 6 Activity diagram for update account .............................................................................. 52
Figure 7 Activity diagram for delete account ............................................................................... 53
Figure 8 Activity diagram for add student information ................................................................ 53
Figure 9 Activity diagram for view student information .............................................................. 54
Figure 10 Activity diagram for update student information ......................................................... 54
Figure 11 Activity diagram for delete student information .......................................................... 55
Figure 12 Activity diagram for add instructor information .......................................................... 55
Figure 13 Activity diagram for view instructor information ........................................................ 56
Figure 14 Activity diagram for update instructor information ..................................................... 56
Figure 15 Activity diagram for delete instructor information ...................................................... 57
Figure 16 Activity diagram for add course information ............................................................... 57
Figure 17 Activity diagram for view course information ............................................................. 58
Figure 18 Activity diagram for update course information .......................................................... 58
Figure 19 Activity diagram for delete course information ........................................................... 59
Figure 20 Activity diagram for add department information........................................................ 59
Figure 21 Activity diagram for view department information...................................................... 60
Figure 22 Activity diagram for update department information ................................................... 60
Figure 23 Activity diagram for delete department information .................................................... 61
Figure 24 Activity diagram for add enrollment information ........................................................ 61
Figure 25 Activity diagram for view enrollment information ...................................................... 62
Figure 26 Activity diagram for update enrollment information ................................................... 62
Figure 27 Activity diagram for delete enrollment information .................................................... 63
Figure 28 Activity diagram for add employee information .......................................................... 63
Figure 29 Activity diagram for view employee information ........................................................ 64
Figure 30 Activity diagram for update employee information ..................................................... 64

Department of computer science

 IX

Figure 31 Activity diagram for delete employee information ...................................................... 65

Figure 32 Activity diagram for generate report information ........................................................ 65
Figure 33 Activity diagram for add cost-sharing information ...................................................... 66
Figure 34 Activity diagram for view cost-sharing information .................................................... 66
Figure 35 Activity diagram for update cost-sharing information ................................................. 67
Figure 36 Activity diagram for delete cost-sharing information .................................................. 67
Figure 37 Activity diagram for add cost-sharing amount ............................................................. 68
Figure 38 Activity diagram for view cost-sharing amount ........................................................... 68
Figure 39 Activity diagram for update cost-sharing amount ........................................................ 69
Figure 40 Activity diagram for delete cost-sharing amount ......................................................... 69
Figure 41 Activity diagram for post message ............................................................................... 70
Figure 42 Activity diagram for view posted message information............................................... 70
Figure 43 Activity diagram for update posted message................................................................ 71
Figure 44 Activity diagram for delete posted message ................................................................. 71
Figure 45 Activity diagram for add admission code ..................................................................... 72
Figure 46 Activity diagram for view admission code ................................................................... 72
Figure 47 Activity diagram for update admission code ................................................................ 73
Figure 48 Activity diagram for delete admission code ................................................................. 73
Figure 49 Class diagram ............................................................................................................... 77
Figure 50 Sequence diagram for add student information ............................................................ 78
Figure 51 Sequence diagram for view student information .......................................................... 79
Figure 52 Sequence diagram for update student information. ...................................................... 79
Figure 53 Sequence diagram for delete student information ........................................................ 80
Figure 54 Sequence diagram for add instructor information ........................................................ 81
Figure 55 Sequence diagram for view instructor information ...................................................... 82
Figure 56 Sequence diagram for update instructor information ................................................... 82
Figure 57 Sequence diagram for delete instructor information .................................................... 83
Figure 58 Sequence diagram for add course information ............................................................. 84
Figure 59 Sequence diagram for view course information ........................................................... 85
Figure 60 Sequence diagram for update course information ........................................................ 85
Figure 61 Sequence diagram for delete course information ......................................................... 86

Department of computer science

 X

Figure 62 Sequence diagram for add department information ..................................................... 87

Figure 63 Sequence diagram for view department information ................................................... 88
Figure 64 Sequence diagram for update department information ................................................ 88
Figure 65 Sequence diagram for delete department information.................................................. 89
Figure 66 Sequence diagram for add enrollment information ...................................................... 90
Figure 67 Sequence diagram for view enrollment information .................................................... 91
Figure 68 Sequence diagram for update enrollment information ................................................. 91
Figure 69 Sequence diagram for delete enrollment information .................................................. 92
Figure 70 Sequence diagram for add employee information ........................................................ 93
Figure 71 Sequence diagram for view employee information ...................................................... 94
Figure 72 Sequence diagram for update employee information ................................................... 94
Figure 73 Sequence diagram for delete employee information .................................................... 95
Figure 74 Sequence diagram for view generated report information ........................................... 95
Figure 75 Sequence diagram for add cost-sharing information .................................................... 96
Figure 76 Sequence diagram for view cost-sharing information .................................................. 97
Figure 77 Sequence diagram for update cost-sharing information ............................................... 97
Figure 78 Sequence diagram for delete cost-sharing information ................................................ 98
Figure 79 Sequence diagram for add cost sharing amount ........................................................... 99
Figure 80 Sequence diagram for view cost-sharing amount ....................................................... 100
Figure 81 Sequence diagram for update cost-sharing amount information ................................ 100
Figure 82 Sequence diagram for delete cost-sharing amount information ................................. 101
Figure 83 Sequence diagram for posting messages .................................................................... 102
Figure 84 Sequence diagram for view posted message .............................................................. 103
Figure 85 Sequence diagram for update Posted message ........................................................... 103
Figure 86 Sequence diagram for deleting posted message ......................................................... 104
Figure 87 Sequence diagram for add admission code ................................................................ 105
Figure 88 Sequence diagram for view admission code .............................................................. 106
Figure 89 Sequence diagram for update admission code............................................................ 106
Figure 90 Sequence diagram for delete admission code ............................................................. 107
Figure 91 Sequence diagram for add account ............................................................................. 108
Figure 92 Sequence diagram for view account .......................................................................... 109

Department of computer science

 XI

Figure 93 Sequence diagram for update account ........................................................................ 109

Figure 94 Sequence diagram for delete account ......................................................................... 110
Figure 95 Sequence diagram for user interface .......................................................................... 111
Figure 96 Sequence diagram for user interface cont… .............................................................. 111
Figure 97 proposed software architecture ................................................................................... 113
Figure 98 Decomposing the system into subsystem (using component diagram) ...................... 114
Figure 99 Deployment diagram for hardware/software mapping ............................................... 115
Figure 100 Object diagram for the major persistent object ........................................................ 116
Figure 101 Subsystem managed on different interface using component diagram .................... 120
Figure 102 Services implemented on different interface ............................................................ 120
Figure 103 Services implemented on different interface continued from above ........................ 121
Figure 104 Services implemented on different interface cont… ................................................ 121
Figure 105 Detailed class diagram .............................................................................................. 123
Figure 106 Invariants on exist on class student .......................................................................... 124
Figure 107 Invariants exist on Admin class ................................................................................ 124
Figure 108 Invariants exist on cost-sharing class ....................................................................... 125
Figure 109 Package diagram ....................................................................................................... 126

Department of computer science

 XII

list if table
Table 1 Data dictionary…………………………………………………………………………………73
Table 2 Access control and security…………………….……………………………………………..116

Department of computer science

 XIII

Definitions
Class Diagram: it is a type of static structure diagram that describe the structure of a system by
showing system classes, their attribute, operation and the relationship among the class.
Component Diagram: is UML diagram depicts how components are wired together to form
larger components and or software system.
Deployment Diagram: is a UML diagram that models the physical deployment of artifact of
nodes.
Functional requirement: a requirement that specifies a function a component or system must
perform.
Hardware: is computer equipment including all the components use to make the computer.
Information: the meaning of data as it is intended to be interpreted by people.
Non-functional requirement: are requirements which specify criteria that can be used to judge
the operation of a system, rather than specific behaviors.
Package Diagram: UML diagram that depicts the dependency between the packages that make
up a model.
Process: is a sequence of instructions to perform some task.
Scenario: is an instance of use case explaining concerned major set of actions.
Sequence Diagram: is a king of interaction diagram that show how process operate with one
another and in what order.
Software: computer programs, instructions that make hardware work.
System: any collection of component element that work together to collect task.
Use case diagram: Graphical Representation of mark full of step wise activity and action with
support for choice, iteration and concurrency.
User interface: the combination of menus, screen design, keyboard command, command
language and help, which creates the way a user interact with computers.
User: any user of the system including database administrator, librarian, member, system
administrator.
Access Control and security: Model is system resource protection that depict who use the
system with what protection.

Department of computer science

 UOG Ate fasil campus online student registration

Chapter one
1. Project proposal
1.1. Introduction
In rapidly emerging world of technological advancements and innovation computer has become
a way of life and a driving force of modern industry and business. This becomes one of the most
significant tools for more productive operation and accurate result. The web technology is going
through major changes as a basis of development web based applications; web technology is
being matured over the past few years.

Web development is a broad term for the work involved in developing a website for internet,
intranet or private network. This can include web design, client side or server side. This includes
from developing a single static single page of plain text to the most complex web-based internet
applications, or social network services. Many organization and institution increase their
investment in web technology and online system. The scope of web based application has grown
enormously and has moved to a plat form that can support all facets of organizational work. But
evidently the majority of the institution still does not adopt with in involving world of
technology example the institution in university of Gondar does not have web based registration.
What is registration?
Registration is a process to determine which student will be taking courses within the university,
and for the administrator to keep its record up-to-date. Registration is ways that give students the
necessary authorized membership of the university.

Gondar University (serving the community since 1954 E.C with a total of five campuses), the
process of registering all students as a members of the institution is conducted in a short period
of time. Until now registration at university of Gondar is done manually when student came to a
single place registrar and department office with in the university. From these campuses our
target area concerned with fasil campus web based online student registration. At fasil campus,
the registration period occupies at most three days at the start of each academic year semester.
Thus with this short period of time it is hard to serve the alarming growth rate of students.

In response to this problem, now we hope to develop web-based online student registration that
will minimize all paper works and manual record keeping, therefore allowing administration and

Department of computer science Page 1

 UOG Ate fasil campus online student registration

staff ease in keeping track of students, and reducing the waiting time of the students to process
all the registration process. Thus the system will increase the number of client served. The
system is expected to be fully automated, time effective, and practical. The aim is to enable
students to achieve the full potential of the students in terms of academic competencies by
focusing on the emotional, social, and educational needs of each student.
1.2. Statement of the Problem
The web based registration for UOG fasil campus seeks to provide solution to the following
problems. The registration resulting to unorganized record-keeping and gathering information is
insufficient for student information processing. the current system have no any form of
authentication mechanism and the document of one student can be seen and exposed to other
users. The students are taking too much time of long processing of registration for validation.
The record was kept into document which cannot accommodate the growing number of the
student. Calculating correct grade and the corresponding GPA for student is difficult. Whenever
there is incorrect grade and GPA student is confused to know whether their result is missed in
the instructor, department or in the registrar office. Admin deliver messages for the responsible
person through a printed paper notice and those persons have to read the notice on message
boards. Making agreement for cost-sharing is time consuming process and/or done manually.
Getting report of students for the required purpose is time consuming and may not be consistent
for the given student. Students must have a photo for registration and/ or require a camera man
for their hard copy of their photo. Most students have eaten more than their menu in the café.
The other major problem that student do is just go outside the campus and do irrelevant actions.
Such as have a bed outside the campus because they expect that any one of their family don’t
know them and they think that we can do what we want. Until now, most web application
display data in the form of text only that is tedious for long line of text.
Ate FASIL campus online registration system to be developed aims at changing the current
system of registering students manually into web based application. This system is able to
register students who are sitting from anywhere and allow them to enroll a course. It also allows
generating report of students for the taken courses and student status.
In general in response to the above mentioned problems this web based registrar system that we
are going to develop, solve those problems by storing and retrieving student information, course
information, enrollment information that result when someone takes a course and derived

Department of computer science Page 2

 UOG Ate fasil campus online student registration

attributes, the department information, and cost sharing information in the well-organized web
and database server. It also supports online messages to be delivered for the responsible person
and accessed. The system also helps students to snap a photo and use it as profile picture. The
system is able to speak for the whole body as a student is going to eat beyond their menu. And
able to tell for the admin how a student is going to eat and able to generate reports related to
which student have eaten their menu properly, which of the students is eat beyond the limit, and
which of the student have not eat. The system generates report related to this case. The system is
able to tell whether a given student is inside the campus or outside the campus. And is also able
to tell how much time spent outside the campus for a particular student. The system also
provides a means that family of student control their child placement that means checks whether
their student is inside or outside of the campus. And is also check whether their child eat
properly their menu or not. The system displays or tells most of the necessary information in the
form of voice i.e tells as normal person talks with us.
1.3. Objective of the project
1.3.1. General objectives of the project
The general objective of the system is to develop web based online student registration system
for FASIL campus.
1.3.2. Specific objective of the project
 Interview: we ask from the registrar office about how student is registered and their
enrollment information is managed.
 Inspect the current condition how student is being registered
 Inspect how student made agreement for the services that they are going to use in the
campus.
 Inspect form that student fills at the time of registration
 Discussion among group members about the project every two days and take
responsibility of its own part.
 Inspect the document holding the students information in the registrar office
 Asking and gain information about the registrar system from anyone who have the idea
about the registrar system.
 Dividing the work among the group members for the seek of managing each part
individually.

Department of computer science Page 3

 UOG Ate fasil campus online student registration

 Collect those work done by individually and discuss among the team
 Having contact with the advisor continuously
 Correct those faults we have made and commented by the advisor.
 Refer documents related to the registrar system online on the internet.

1.4. Scope and limitation of the project

1.4.1. Scope of the project
The study was focused on web-based student registration system development for university of
Gondar Ate fasil campus. We formulate the scope and limitation of this project to identify the
boundaries of the study.
1. The system is able to register students online sitting from anywhere and able to tell time
period for students that tell when to come to the university and take their identification
card for freshman student and time period to renew their identification card for senior
students.
2. The system will store and retrieve the cost sharing history of student regarding to their
agreement to use service of the campus.
3. Provide the best solution for student in waiting their turn at the time of registration and
save their time, no need to go to the department staff, and registrar office for registration.
4. The system will display the course taken by student with the corresponding GPA.
5. Student is able to see their information such as available courses, grade and GPA sitting
from anywhere.
6. The system uses username and password for authentication and user will retrieve the
necessary information according to their authentication mechanism.
7. The system will register students who are in active state for senor student and whose
admission code is officially stored by the admin in the system for freshman students.
8. The system shall be able to deliver admin messages for the directed person.
9. It is also able to generate reports regarding to students such as grade report, GPA, and
their status.
10. The system is able to snap profile photo for students.

Department of computer science Page 4

 UOG Ate fasil campus online student registration

11. The system is able to determine placement of the given student in the form of normal
talk for the admin and main gate employees.
12. The system is able to tell placement of student for their family and whether they eat their
menu in the café properly or illegally.
13. The system is able to generate reports related to student eat and their placement for the
admin based on their option as a normal text or in the form of normal talk with net
English language.
14. Whenever the user selects voice the system also able to provide option for the speaker
person either in the form of male voice or female voice.
1.4.2. Limitation of the project:
 The system does not support payment for students who have been registered after the
registration date deadline.
 The system does not convert the data obtained from the server to excel format or in the
form of csv file.
 The system does not prepare (print) student identification card.
1.5. System development methodology
We use an object oriented approach to develop the system. Object-oriented analysis and
design is a popular technical approach for analyzing, designing an application and system by
applying the object-oriented paradigm and visual modeling throughout the development life
cycles to foster better stakeholder communication and product quality.

This methodology shall be done using water fall process model which is used in software
development process in which flowing steadily downwards like water fall through the phases of
conception, initiation, analysis, design, and implementation.
1.6. Investigation (fact-finding) methods
In our system we use three different fact-finding methods:
1.6.1. Direct observation
We observe student is registered to the university when they came to the area. The admin post
notices in a printed paper format on message boards. Whenever a student is dismissed or
removed from the university, they use the services of the campus illegally since the notices are
not available for a responsible person in a short period of time.

Department of computer science Page 5

 UOG Ate fasil campus online student registration

1.6.2. Interview
We gather information from Fasil campus registrar system employees: As there is a problem of
grade calculation so that course result of a student is not valid. Cost sharing information
manipulation problem. In general there is no good way of retrieving or accessing and storing
data.
1.6.3. Inspect form slips
From form slips we get registration requirement information such as Student information,
Adopter information, services requirement
1.7. System development tools
System model is abstract description of systems whose requirements are being analyzed.

1.7.1. Software tools

The mathematical tools and techniques that we are going to use in the system development
include HTML, PHP, JAVASCRIPT, JQUERY, AJAX, and bootstrap.
 HTML: Hypertext Markup Language, a standardized system for tagging text files to
achieve font, color, graphic, and hyperlink effects on World Wide Web pages.
 PHP: PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open
source general-purpose scripting language that is especially suited for web development
and can be embedded into HTML.
 JAVASCRIPT: an object-oriented computer programming language commonly used to
create interactive effects within web browsers.
 JQERY: JQUERY is a fast, small, and feature-rich JavaScript library. It makes things like
HTML document traversal and manipulation, event handling, animation, and Ajax much
simpler with an easy-to-use API that works across a multitude of browsers.
 AJAX: Ajax is a client-side script that communicates to and from a server/database
without the need for a post back or a complete page refresh.
Ajax is the method of exchanging data with a server, and updating parts of a web page -
without reloading the entire page.
 Bootstrap is the most popular HTML, CSS, and JavaScript framework for developing
responsive, mobile-first web sites.
 Note pad++ : it is an editor for the code

Department of computer science Page 6

 UOG Ate fasil campus online student registration

 Microsoft word for the preparation of the documentation set

 WAMP server for running the software.
 Edrawmax for drawing all available diagrams
 Microsoft project 2013 for time scheduling.
1.7.2. Hardware tools
 Personal computer: it is a mandatory device which is used to organize the project
documentation and implementation.
 Printer: it a device that is used to print the document.
 Flash disk: It a device which is used to hold the document.
 Compact Disk (CD): It a device which is used to hold the document.
1.8. Significance of the project
Security of the website is one of the main importance’s to be improved as the registration is
moving from traditional to online based system. The reason is because user will send their
confidential data to the system. Some user might use the same login ID or password, and without
proper security, the data might be accessed by third party, or the user session is hijacked while
sending the data. The security improvement will also provide log to the administrator in case
there are some abnormality in the system after some user log in. As the security improved, we
are giving the user a better understanding why they should trust our system.

The other core importance of the project is to change the current manual work system to easily
manageable web based online student registrar system. The system provides easy way for storage
and access or retrieval of data to and from the database. The system is used to remove the
mismatch of student grade and corresponding GPA for all courses that a student has already
enrolled. The system is also used to store and retrieve cost sharing information that a student
made agreement to use the services of the college. The system is also used to deliver admin
notices for the responsible person and accessed by them according to their authentication
mechanism.
1.9. Beneficiaries
This project will be implemented and expected to provide good effect and beneficial to the
following:

Department of computer science Page 7

 UOG Ate fasil campus online student registration

 UOG fasil campus: the college will be benefited a lot because through this system they
are more capable to provide better service for the students.
 For the student: the students can be registered sitting from anywhere, so they can save
their time and energy at the time of registration. Student can access or retrieve their grade
and cost sharing information easily.
 Students do not further require hard copy of their photo. System provides means to snap
their photo and use it as their profile.
 Admin: admin can deliver messages easily for the responsible person (can post online
messages and notices).
 Students, clinical employee, proctor, and librarians access or retrieve the necessary
information and notices from the admin in the appropriate time and able to do what is
required from them.
 Dean: deans shall be able to retrieve all the necessary student information from the
system quickly and easily.

Department of computer science Page 8

 UOG Ate fasil campus online student registration

1.10. Time scheduling

Time scheduling describes the start and deadline and/or plan of the system development. In this
schedule we describe the duration of each task with the start and finish time. It also includes
main resources such as the use of computer and human power to develop the system. a dark blue
color along with resource shows tasks already executed.

Figure 1 Time scheduling

Department of computer science Page 9

 UOG Ate fasil campus online student registration

Chapter two
2. Requirement analysis
2.1. Introduction
The purpose of this requirement analysis document is to describe and documents how we specify
functional and non-functional requirement of the system and how we describe the functional
requirement using use case diagram, activity diagram, sequence diagram, and class modeling.
The use case description associated with each functional requirement and/or use case and the
interface of the system is also documented in this requirement analysis document.

2.2. Current system

2.2.1. Major function of the current system/ current system description
The major function of the current system includes the following elements:
Register student by providing form to them and instruct them to fill those forms. The form to be
filled includes personal detail, cost sharing information, the course that a student is going to take.
Keeping track of the cost sharing and store them in the document. Calculate the student’s course
result such as student grade and the corresponding GPA. Assigning instructors to course and
every instructor must announce the result of the course to the students. Assigning a student to a
particular department, providing services for the students according to their cost agreement are
the major functions of the current system.
2.2.2. Problem of the existing system
It is difficult for storing and retrieval of data as well as updating the sored information and
deleting information when necessary. The delivery of information for the directed person is
difficult and can be done in a printed paper format and the directed person must read the message
from message boards. Generating correct grade report and the corresponding GPA is difficult
and keeping track of cost sharing information is hard to manipulate. Reading normal text data is
tedious and boring. Knowing which of the students have eaten according to their menu or not is
difficult since referring the menu document is so tedious. Knowing which student is in the
campus or not is difficult. The family of student is not able to know whether their child behave
properly or not.

Department of computer science Page 10

 UOG Ate fasil campus online student registration

2.3. Requirement gathering

2.3.1. Requirement gathering methodologies
In our system we use the following requirement gathering methodologies:
Direct observation: We observe, a student is registered to the university when he or she comes to
this campus. The administrator posts notices in a printed paper format. Whenever a student is
dismissed or removed from the university they use services of the university illegally because the
notice is not available for a responsible person in a short period of time.
Interview: We gather information from FASIL campus registrar system employees:
As there is a problem of grade calculation so that course result of a student may not be correct.
Cost sharing information manipulation problem. In general there is no good way of retrieving or
accessing and storing data.
Form slips: from form slips we get registration requirement information such as Student
Information, Adopter information, services that student demand and use in the campus. In
general from slip forms we get all attribute that belong to students.

2.3.2. Results found

By observing the environment in this campus we obtain the result described below.
There are sophisticated work environment in the registrar system due large set of documents.
The storage and retrieval of information is difficult. Generating the correct grade report and the
corresponding GPA for student is the difficult task. Messages and notices posted by the
administrator are not delivered for the directed person on the appropriate time. Student who is
already dismissed from the system use the services of the university illegally. In general there is
wastage of resources such as time, money, and needs more man power to administer the system.
2.4. Proposed system
In response to the trivial aspects of the current system we are going to replace the present work
environment by online registrar system that are easy to store and retrieve data to and from the
system, deliver administrative notices and information for the responsible person that have
privilege to access in the appropriate time. Generating correct grade report and the corresponding
GPA as well as calculating cost sharing of the student will be done without ambiguity.

Department of computer science Page 11

 UOG Ate fasil campus online student registration

2.4.1. Overview
Ate FASIL campus online student registration system should be able to register students with
information such as student full name, student birth date, student age, student sex, student region,
zone, town, adopter’s information such as adopter’s full name, region, zone, town, house
number, phone number, P.O.BOX, department information such as department name, department
location, course information such as course name, course code, credit hour, points, administrator
posts such as news for students, librarians, clinic employees, café employees, proctors, Instructor
information, and cost sharing information.
2.4.2. Functional requirements
The system to be developed is going to support the following functionality:
1. The system shall allow students to be registered by their full name, sex, age, Address such as
region, zone, town, Adopter’s information such as address, full name, house number, phone
number, P.O.BOX, University information they joined such as university name, faculty,
department, year of entrance and their batch, Cost sharing agreement, School information
that they complete the preparatory program, date that they complete the preparatory program
2. The system shall allow students to enroll a course
3. The system shall allow storing department information such as department name, department
location
4. The system shall allow storing course information such as course name, course code,
course’s credit hour, points,
5. The system shall allow storing and delivering administrator notices and/or messages.
6. The system shall allow storing enrollment information such as student id, course code, grade
result, semester in which the course taken, the year in which the course is taken, grade and
GPA.
7. The system shall allow students to store cost sharing information.
8. The system shall allow the administrator store instructor information
9. The system shall allow instructors to calculate grade from exam result of student.
10. The system shall allow instructor to submit student course result to the administrator.
11. The system shall allow students to view registration information and update their information
12. The system shall allow administrator messages and notices to be delivered and seen by
students, librarians, clinic employees, proctors, café employees

Department of computer science Page 12

 UOG Ate fasil campus online student registration

13. The system shall allow students to view their course result such as grade and GPA.
14. The system shall allow deans to generate and view report of the students
15. The system shall allow students to snap or capture a photo for their profile.
16. The system shall allow family of students to know their child placement (inside the campus
nor not) and how much time they spent outside the campus.
17. The system shall allow family of students to know about their child activity in the café i.e eat
their menu properly or go beyond.
18. The system shall allow the admin to know how many of the student is inside the campus and
how many of them are outside the campus in the form of pie chart.
19. The system shall allow most of the response to be displayed in the form of voice as normal
talk with the person.
20. The system shall allow main gate and café employee (ticker) to determine whether the
students have eaten their menu or not in the form of voice or normal talk with a person.
2.4.3. Non-functional requirements
2.4.3.1. User interface and human factor
The system supports many users such as students, administrators, clinical employees, librarians,
clinical employees, proctors, instructors and deans to use it at a time. There should be help menu
included that helps to achieve common tasks for users. There should also be error messages that
help the user to recover from those errors. The specified user is able to read and able to enter the
necessary information in the appropriate interface and therefore no need of extended period of
time for user to learn the system usage.

2.4.3.2. Documentation
The user documentation is an excellent guide for the user. In addition of the user documentation
maintainers can use the documentation that is provided with the source code in the form of
comment. That means the comment part of the source code provides help the purpose of each
code so that maintainers can use it to maintain the system.
2.4.3.3. Hardware consideration
The system is hardware compatible. It can run on windows operating system. It is also
compatible for mobile device. The component of the system can released and compressed
according to the hardware it is running. On smaller device the content is collapsed in to the

Department of computer science Page 13

 UOG Ate fasil campus online student registration

buttons, panels and hidden and when it run on large device the hidden part is stretched and
becomes visible. The optimized memory size and storage space is required for running the
application and data on systems will be posted to the server.
2.4.3.4. Performance characteristics
This system should give response to user actions within seconds. Database processing time
should not more than 100ms. The system must perform a minimum of one transaction per
second. The system reacts to its environment with in microsecond of seconds. The system is
available for users when requested by end users according to their authentication mechanism.
2.4.3.5. Error handling and extreme condition
The system has validation for incorrect inputs. Actions that are not able to undo should ask
confirmation and user must be sure with this confirmation question because it is extreme and
never be restored. Whenever there is incorrect input the system should respond for user as
incorrect input. Example if user fill for student name only one letter, the system must inform for
user a single letter cannot be name of student please enter correct value. The system should no
longer operate if security attacks have become obvious. The violated system shall not permit any
further operation unless the operator guard is in place. An authorized user shall not edit any
functionality. To see from the perspective of safety requirement, this web based application will
not affect data stored outside of its servers nor will it affect any other applications installed on
the user’s machine. It cannot cause any damage to the machine or its internal components.

2.4.3.6. Quality issues

Robustness: The system must restart after failure within seconds.
Availability: The system shall be able to work about 24 hours a day and acceptable down time
may be half hour for some cases. The system is portable and able to move to different hardware
platforms. It is able to run on windows operating system and smart phones in general. The
system shall be able to trap faults.
2.4.3.7. System modification
The university administrator can work for the addition of new feature to the system by inviting
those persons who have programming knowledge in PHP and scripting language such as
JAVASCRIPT, JQUERY, and AJAX, and bootstrap, and database management ability. Such

Department of computer science Page 14

 UOG Ate fasil campus online student registration

addition of new feature may require temporarily disabling the system and further compilation of
the system is needed.
2.4.3.8. Physical environment
The web based student registration should be implemented with html, CSS, bootstrap for
interface, PHP for server side scripting, JavaScript and JQUERY for validation and MYSQL for
database management.
The system will be available for all users after it is hosted into internet service providers (ISP) or
any other domains. Whether condition may interrupt the system because whether have impacts
on the power and related to this broadband connection may interfere.
2.4.3.9. Security issues
The students, librarians, café employees, proctors, clinic employees, admin and deans have their
own authentication mechanism to access the necessary information in the system. The
administrator has the authentication mechanism to post news for the responsible person. In
general the access permission of the systems data can only be changed by the owner of the
account.
2.4.3.10. Resource issues
The system work is backed up to the central database as soon as every user works with it. The
system administrator plays the role of system installation (host) and system maintenance by
inviting those people having knowledge of the above system development tools.
2.5. System model
2.5.1. Scenario
A scenario is a specific sequence of actions and interactions between actors and system under
discussion. As system requirements may be updated during the development process, reusable
coding and documentation is a must for each of the scenarios composing the system. A scenario
may be Insert student information, view student information, Update cost sharing information,
and Delete student information. Scenario which is generated for each domain or either be a more
complex one affecting more than one domains of the system. In general the combined part of
systems scenarios is described in the use case model.
Scenario name: view student information, Participating actor: aster and she is a student then,
Aster selects student information option and the view option. System displays list of options on

Department of computer science Page 15

 UOG Ate fasil campus online student registration

how to view her information. Aster selects from the given option to view System checks against
the database value. If the system determines that aster exists, it displays her information.

Scenario name: view student information. Participating actor: Abebe: admin, aster: student.
Abebe select student information option and select the view option. System displays list of
options on how to view aster’s information. Abebe selects from the given option to view then
System checks whether the aster exists there If the system determines the aster exists in the
database, it displays her information such as her id, first name ,middle name ,last name age, sex,
region ,woreda ,zone ,Keble ,preparatory school of coming.

Scenario name: Add student information. Participating actor: student: Samuel

Samuel includes login use case first then; Samuel selects the student information option. Samuel
selects insert option. System displays a form to him. Samuel enters the information such as first
name ,middle name ,last name id, age, sex , year ,region ,WOREDA ,zone ,Keble, preparatory
school ,address he or she comes, in their appropriate place provided by select each of alternative
form fields. He select save changes option. Then System informs to him as he is added to the
system.

Scenario name: Update student information. Participating actor: student: Shegaw

First shegaw must login to the system. Then Shegaw selects student information option Shegaw
selects the update option then, Shegaw fills the new information to be updated, and Shegaw
selects the save change option. System asks confirmation question and shegaw accepts the
confirmation and System informs to shegaw as he update his information

Scenario name: Delete student information. Participating actor: admin: Elisa

First Elisa selects student information option. Elisa selects delete option and deliver
confirmation to her Elisa accepts the confirmation, System informs her success for her work.

Scenario name: insert instructor information. Participating actor: admin: Abebe

Abebe selects the instructor information option and Abebe selects add instructor option System
displays form to abebe. Abebe fill form. System validate for the filled information. And he select
save changes option and system deliver success message for abebe.

Scenario name: view instructor information. Participating actor: Ermias: Admin

Department of computer science Page 16

 UOG Ate fasil campus online student registration

Ermias selects instructor information option and he selects the view option. System displays list
of options on how to view instructor’s information. Ermias selects from the given option to view.
System checks query against the database value and display instructor information to abebe.

Scenario name: Update instructor information. Participating actor: Admin: Jemal

First jemal must login to the system then he select instructor information option. Jemal selects
update option. Jemal fills the new information of instructor to be updated System validates the
input information and jemal select the save change option. System confirms the update. Jemal
allow confirmation. System informs jemal as he finishes his work.

Scenario name: Delete instructor information. Participating actor: Admin: Ayele

First ayele must login to the system. Ayele select instructor information option and Ayele select
delete option. System confirms the delete operation. Ayele accept the confirmation operation
System informs success message.

Scenario name: insert course information: Participating actor: Admin: kebede

First kebede must login to the system. Then Kebede selects course information option. System
displays list of options such as update, insert, delete. Kebede selects insert option. System
display form to kebede. Kebede enters course information such as course name, course code,
credit hour, in their appropriate place provided and press save change option System displays as
course is added.

Scenario name: View course information: Participating actor: student: Mulu

First mulu must login to the system and select course information option, then Mulu selects the
view option, System displays list of options on how to view course data. Mulu selects from the
given option to view. System checks the query against the database value. The system displays
the requested value to mulu.

Scenario name: Update course information. Participating actor: Admin: Daniel

First Daniel must login to the system Daniel selects student information option. Daniel selects
update option. System display form to Daniel and Daniel fills the new information to be updated
such as course name, points, course credit hour. He press the save change option. System asks
confirmation question like do you want to update? He accepts confirmation. System deliver
success message.

Department of computer science Page 17

 UOG Ate fasil campus online student registration

Scenario name: Delete course information. Participating actor: Admin: Belew

First Belew must login to the system. Belew selects course information option Belew select
delete option, System requests the confirmation. Belew accepts the confirmation. He select save
changes option. System displays course is deleted from the system.

Scenario name: insert department information. Participating actor: Admin: Natty

First Natty must login to the system. Natty selects department information option. The he selects
add department option. System provides form for filling department information such as
department name, department location; Natty enters department information such as department
name, department location in their appropriate place provided. System validates information.
Natty select save changes option. System displays as department information is saved.

Scenario name: View department information. Participating actor: Student: Meron

First Meron must login to the system. Meron selects department information option. Meron
selects the view option. System displays list of options on how to view department information.
Meron selects from the given option to view. System checks whether the value exist in the
database. System displays department information such as department name, and location. If
department is not exist no content can be displayed for Meron rather than error message

Scenario name: Update department information. Participating actor: Admin: Aman

First Aman must login to the system. Aman selects the department information option. Aman
selects update option, System displays the form to execute the update, and he fills the form.
System validates the input value, He select save change option. System displays confirmation.
He accepts the confirmation. System deliver success message to Aman.

Scenario name: Delete department information: Participating actor: Admin: Sara

First sara must login to the system. Sara selects department information option. Sara select delete
option. System provides confirmation. Sara accepts confirmation. System deliver success
message for Sara.

Scenario name: Insert enrollment information: Participating actor: Admin: Mikias

First Mikivas must login to the system. Mikias selects enrollment information option, and then
he selects insert option. System displays form for input the enrollment information. Mikias enters
enrollment information such as student first name, middle name, last name course code, grade,

Department of computer science Page 18

 UOG Ate fasil campus online student registration

year, semester, point, GPA in their appropriate place provided Employee select insert option.
System validates input data. Mikias select save change option. System displays as enrollment
information is inserted.

Scenario name: update enrollment information: Participating actor: Admin: Tadese

First Tadese includes login use case and then he selects enrollment information option

Tadese selects the update option. System displays form for input the enrollment information. he
fills the form. System validates the input information. He selects the save changes option.
System displays confirmation. System displays as content is updated

Scenario name: View enrollment information: Participating actor: Student: mekedes

First Mekedes includes login use case. Then Mekedes select enrollment information option.
Mekedes selects the view option. System displays list of options on how to view enrollment
information. Mekedes selects from the given option to view. System checks whether the
enrollment information exists. If the system determines the enrollment for her exists, it displays
enrollment information

Scenario name: Delete enrollment information: Participating actor: Admin: Fikadu

First Fikadu must login to the system, and then Fikadu selects enrollment information option.
Fikadu select delete option, System confirms the delete operation. Fikadu accepts the
confirmation. System displays as enrollment information is removed from the system.

Scenario name: Add employee information: Participating actor: Admin: Selam

First Selam must login to the system, and then Selam selects the employee information option.
Selam selects employee insert option. Selam enters employee information. Selam select insert
option. He select save changes option. System displays as employee is added to the system

Scenario name: View employee information: Participating actor: Admin: Yared, Employee:
abrham
First Yared must login to the system .Yared selects view employee information option. Yared
selects the view option. System displays list of options on how to view Abrham’s information.
Yared selects from the given option to view. System checks whether Abrham exists there and
display his information.

Department of computer science Page 19

 UOG Ate fasil campus online student registration

Scenario name: Update employee information: Participating actor: Admin: Selomon

First Solomon must login to the system, and then Selomon selects employee information option
Selomon selects update option. Selomon fills the new information to be updated. System asks
confirmation question as do you want to update? He accepts the confirmation. System displays
as employee information is updated

Scenario name: Delete employee information: Participating actor: Admin: Matiwos

First Matiows must login to the system, and then Matiwos select employee information option.
Matiwos select delete option. System asks as are you sure you want to delete? The accept
confirmation. System deletes the employee.

Scenario name: Generate report: Participating actor: Dean: Assefa

First Assefa must login to the system, and then Assefa select generate report option. Assefa
selects the view option. System displays list of options on how to view report data. Assefa selects
from the given option to view. System checks whether the report exists. And display report if
available.

Scenario name: insert cost sharing information: Participating actor: Student: Tesfay
First Tesfay must login to the system, and then he select cost sharing information option Tesfay
select add option. System displays the form. Tesfay insert information such as his id, first name,
middle name, last name, batch, semester, year, food expense, boarding expense, tuition expense,
and total. He select save change option. System informs as cost sharing information is stored to
the system

Scenario name: View cost sharing information: Participating actor: Admin: Bekele, student:
Lema
First Bekele must login to the system, and then Bekele selects student information option. Bekele
selects the view option. System displays list of options on how to view lema’s information.
Bekele selects from the given option to view. System checks whether the cost information exists
If the system determines his information exists, it displays the information such as his id, first
name, middle name, last name, age, sex, batch, semester, year, food expense, boarding expense,
tuition expense

Scenario name: Update cost sharing information: Participating actor: admin: Alias

Department of computer science Page 20

 UOG Ate fasil campus online student registration

Alias must be login to the system, and then Alias select cost sharing information option. Alias
selects update option. He fills the new information to be updated such as his id, first name,
middle name, last name, batch, semester, year, food expense, boarding expense, tuition expense,
and total. Alias select the save change option. System asks confirmation question as do you want
to update? He accepts confirmation. System updates the cost sharing.

Scenario name: Delete cost sharing information: Participating actor: admin: Kirubel
First Kirubel must include login use case. Kirubel select cost sharing information option. Kirubel
select delete option. System asks confirmation as are you sure you want to delete. Kirubel
accepts the confirmation. System informs as information is deleted

Scenario name: insert cost sharing amount: Participating actor: admin: Berket
First berket must login to the system, and then Berket select cost sharing amount option. Berket
select add option. System displays the form. Berket inserts information such as food expense,
boarding expense, and tuition expense, total. Berket select save change option. System display
success message.

Scenario name: View cost sharing amount: Participating actor: admin: Bezawit
Bezawit must login to the system, and then she select cost sharing amount option. Bezawite
selects the view option. System displays list of options on how to view data. She selects from the
given option to view. System checks whether the cost information exists. If the system
determines the information exists, it displays the information such as food expense, boarding
expense, and tuition expense, total.

Scenario name: Update cost sharing amount: Participating actor: admin: Yonase
Yonase first must login to the system, and then he select cost sharing amount option. Yonase
selects update option. Yonase fills the new information to be updated such as food expense,
boarding expense, and tuition expense, total. Yonase select the save change option. System asks
confirmation question as do you want to update? Yonase confirms the update. System displays
as cost information is updated.

Scenario name: Delete cost sharing amount: Participating actor: admin: Mesfen

Department of computer science Page 21

 UOG Ate fasil campus online student registration

First Mesfen must login to the system, and then Mesfen select cost sharing amount option.
Mesfen select delete option, System asks as are you sure you want to delete? He accepts the
confirmation, System displays as cost amount is deleted from the system.

Scenario name: post message: Participating actor: admin: Ananya

Ananya first must login to the system, and then he selects post message option. Ananya select
post option. System displays the form, Ananya fill form such as message id, message title, and
message body. Ananya select save change option and Message is stored to the system.

Scenario name: View message information: Participating actor: User: Berhanu

First Berhanu must login to the system, Berhanu selects message option. Berhanu selects the
view option. System displays list of options on how to view data. Berhanu selects from the
given option to view, System checks whether the message exists in the database. If the system
determines the message exists, it displays the information such as message id, name, and body of
message.

Scenario name: Update message information: Participating actor: Admin: Derege

First Derege must login to the system, and then he selects post message option. Derege selects
update option. Derege fills the new information to be updated such as message id, message title,
and message body. He select the save change option. System asks confirmation question as do
you want to update? He confirms the update. System displays as message information is updated.

Scenario name: Delete message information: Participating actor: Admin: Betty

First Betty must login tot the system. Betty selects message option, Betty select delete option.
System delivers confirmation. Betty accepts the delete confirmation. System displays as message
deleted from the system

Scenario name: insert first year admission code: Participating actor: Admin: Tesema
First Tesema must login to the system, and then he selects admission code option. System
displays form. Tessema fill form, System validates the entered information. He select save
change option. System deliver success message.

Scenario name: view first year admission code: Participating actor: Admin: Belay

Department of computer science Page 22

 UOG Ate fasil campus online student registration

First Belay must be login to the system, and then he selects view admission code option. System
displays different option to view. If admission code not found system displays is not exist
message

Scenario name: update first year admission code: Participating actor: Admin: Yeshi
First Yeshi must be login to the system, Yeshi select update admission code option. System
displays the form. She fills the form. System validates the entered data. She select save option.
System displays confirmation. She accepts the confirmation. System displays success message

Scenario name: delete first year admission code: Participating actor: Admin: Ali
First Ali must login to the system. Ali select delete admission code option, System displays
confirmation. Ali accepts confirmation. System deletes admission code

Scenario name: create account: Participating actor: Admin: Meron

First Meron must login to the system. Meron select create admission code option. System
displays the form. She fills the form System validates the input data. She select save change
option. System displays success message.
Scenario name: view account: Participating actor: Admin: Alem
First alem must be login to the system. Alem select admission code option. Alem select view
option. Alem select view option. System displays account

Scenario name: delete account: Participating actor: Admin: Negus

First Negus must be login to the system. Negus selects admission code option. Negus select
delete option. System displays confirmation. Negus accepts confirmation. System tells as student
account is deleted.

2.5.2. Use case model

2.5.2.1. Use case diagram
A scenario is an instance of a use case; that is, a use case specifies all possible scenarios for a
given piece of functionality. A use case is initiated by an actor. After its initiation, a use case
may interact with other actors, as well.

Department of computer science Page 23

 UOG Ate fasil campus online student registration

Figure 2 use case diagram

Department of computer science Page 24

 UOG Ate fasil campus online student registration

Figure 3 use case diagram cont…

Department of computer science Page 25

 UOG Ate fasil campus online student registration

2.5.2.2. Use case description

Describing a use case entails specifying and describing the entry and exit conditions of a use case
enables to understand the conditions under which a use case is invoked and the impact of the use
case on the state of the environment and of the system.
Use case name: Login system
Summary: User login into the system
Actor: Student, café employee, librarian, clinic employee, proctor, admin
Precondition: System is idle displaying welcome message
Main sequence:
1. User selects login option
2. Login interface is produced.
3. user enters username and password
4. System validates input against system database.
5. System accepts user type.
6. The privileged user interface is produced
Alternative sequence:
3: If the system determines that user name and password incorrect, it displays password and
username incorrect.

Use case name: Logout

Summary: System returns to home page of the system.
Actor: Student, employee, admin, dean, instructor.
Precondition: User must be logged into the system
Main sequence: Student click logout option and system displays the home page of the system.
Use case name: Add student information
Summary: Student registered to the system.
Actor: Student, employee
Dependency: Includes login use case
Precondition: Student must not be in the system before
Main sequence:

Department of computer science Page 26

 UOG Ate fasil campus online student registration

1. First it includes login use case

2. User selects student information option
3. User selects add student information option
4. System displays a form to the User
5. User enters student information such as full name, id, age, birth date, region, zone,
WOREDA, KEBELE in their appropriate place provided by select each of alternative
form fields.
6. Student select save changes option
7. System displays as student is added.
Alternative sequence:
5: If the employee fills invalid information then, the system displays error and
announce as error information entered
Post condition: Student is added to the system
Use case name: View student information
Summary: user sees the content of the his or her information
Actor: Student, admin
Dependency: Include login use case
Precondition: Student is already registered
Main sequence:
1. User includes login use case
2. User select student information option
3. User selects the view option
4. System displays list of options on how to view student data.
5. User selects from the given option to view
6. System checks whether the user exists
7. System displays student information.

Alternative sequence:

6: if the system determines that the student not exist it send request error.
Post condition: the content of the student is displayed.
Use case name: Update student information

Department of computer science Page 27

 UOG Ate fasil campus online student registration

Summary: User updates the content of the student data.

Actor: Student, Admin
Dependency: Includes login use case
Precondition: Student is already registered
Main sequence:
1. Includes the login use case
2. User select Student information option
3. User selects update option
4. User fills the new information to be updated
5. User select the update option
6. System asks confirmation question as do you want to update?
7. User confirms.
8. System displays success message.
Alternative sequence:
4: If the student inserts invalid data the system displays error message
5: If User denies confirmation system cancels operation
Post condition: System updates student information
Use case name: Delete student information
Summary: Remove student from the system
Actor: Admin
Dependency: Include login use case
Precondition: Student must already be registered before
Main sequence:
1. Includes login use case
2. Admin select student information option
3. Admin select delete option
4. System confirms the operation
5. Admin accepts the confirmation
6. System informs as student is deleted
Alternative sequence:
5: If Admin denies the confirmation it cancels the operation

Department of computer science Page 28

 UOG Ate fasil campus online student registration

Post condition: Student is deleted from the system

Use case description for instructor information
Use case name: Insert instructor information
Summary: An instructor is added to the system
Actor: Admin
Dependency: Include login use case
Precondition: Instructor must not be in the system before
Main sequence:
1. Employee includes login use case
2. Employee selects the instructor information option
3. Employee selects add instructor option
4. System displays form
5. Employee fill forms
6. System validate inputs
7. Employee select save changes
8. System displays as instructor is added
Alternative sequence:
5. If employee fills invalid information system displays error messages
Post condition: Employee is added to the system
Use case name: View instructor information
Summary: User sees the content of the instructor information
Actor: Employee, instructor
Dependency: Includes login use case
Main sequence:
1. Include login use case
2. User select instructor information option
3. User select the view option
4. System displays different options to view
5. User select from those option to view
6. System displays the instructor information
Alternative sequence:

Department of computer science Page 29

 UOG Ate fasil campus online student registration

5. If instructor is not available, then system informs the user as not content is available
Post condition: The content of the instructor is displayed
Use case name: Update instructor information
Summary: Employee updates instructor data
Actor: Employee
Dependency: Includes login use case
Precondition: Instructor is already registered
Main sequence:
1. Includes the login use case
2. Employee select instructor information option
3. Employee selects update option
4. Employee fills the new information of instructor to be updated
5. System validates the input information
6. Employee select the update option
7. System confirms the update.
8. Employee allow confirmation
9. System informs as instructor information is updated
Alternative sequence:
4: If the employee inserts invalid information the system displays error message
8: if employee denies the confirmation, system aborts the operation
Post condition: System updates instructor information
Use case name: Delete instructor information
Summary: Remove instructor from the system
Actor: Employee
Dependency: Include login use case
Precondition: Instructor must already be registered before
Main sequence:
1. Includes login use case
2. Employee select instructor information option
3. Employee select delete option
4. System confirms the delete operation

Department of computer science Page 30

 UOG Ate fasil campus online student registration

5. Employee accepts the operation

6. System informs as student is deleted
Alternative sequence:
5: If employees deny confirmation, it cancels the operation
Post condition: instructor is deleted from the system

Use case description for course information

Use case name: Insert course information

Summary: course is added to the system
Actor: admin
Dependency: Include login use case
Precondition: System is idle displaying welcome message.
Main sequence:
1. First it includes login use case
2. Admin selects course information option
3. System displays list of options such as update ,insert ,delete
4. Admin selects add option
5. Admin enters course information
6. Admin select save change option
7. System displays success message.
Alternative sequence:
5: If the Admin fills invalid information then, error message.
Post condition: Course is added to the system
Use case name: View course data
Summary: user sees the content of the course information
Actor: admin, Student, instructor
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. User select course information option
2. User selects the view option

Department of computer science Page 31

 UOG Ate fasil campus online student registration

3. System displays list of options on how to view course data.

4. User selects from the given option to view
5. System checks the course against the database
6. System display the course
Alternative sequence:
5: if the course value does not exist in the database it displays request error.
Post condition: the content of the course is displayed
Use case name: Update course information
Summary: admin updates course
Actor: admin
Dependency: Include login use case
Precondition: Course is already added before.
Main sequence:
1. First includes login use case
2. user select course information option
3. user selects update option
4. User fills the new information of student to be updated such as course name, points,
course credit hour.
5. user press the save changes
6. System asks confirmation
7. User accept confirmation
8. System displays success message
Alternative sequence:
4: If the user inserts invalid data the system displays error message
6: If employees deny the confirmation system cancels the operation
Post condition: System updates course information
Use case name: Delete course information
Summary: Remove course from the system
Actor: Admin
Precondition: System is idle displaying welcome message
Main sequence:

Department of computer science Page 32

 UOG Ate fasil campus online student registration

1. user select course information option

2. user select delete option
3. System requests the confirmation
4. Employee accept the confirmation
5. System informs as student is deleted
Alternative sequence:
4: If user denies the confirmation, system cancels the operation
Post condition: Course is removed from the system
Use case description for department information
Use case name: Insert department information
Summary: Admin add department information to the system.
Actor: Admin
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. First include login use case
2. user selects department information option
3. user selects add department option
4. System provides form for filling department information such as department name,
department location,
5. User enters department information such as department name, department location in
their appropriate place provided
6. System validates information
7. User select save changes option
8. System displays as department information is saved.
Alternative sequence:
4: If the employee fills invalid information then, the system displays validation message
Post condition: Department information is added to the system
Use case name: View department data
Summary: user sees the content of the department information
Actor: Admin

Department of computer science Page 33

 UOG Ate fasil campus online student registration

Precondition: System is idle displaying welcome message

Main sequence:
1. First includes login use case
2. User select department information option
3. User selects the view option
4. System displays list of options on how to view department information.
5. User selects from the given option to view
6. System checks the request against the database value
7. System displays department information such as department name, and location
Alternative sequence:
6. If department is not exist no content can be displayed.
Post condition: The content of department information is displayed
Use case name: Update department information
Summary: Admin updates the content of department information
Actor: Admin
Dependency: includes login use case
Precondition: system is idle displaying welcome message.
Main sequence:
1. First includes login use case
2. User selects the department information option
3. User selects update option
4. System displays the form to execute the update
5. User fills the form
6. System validates the input
7. User select save change option
8. System displays confirmation
9. User accepts the confirmation
10. System displays as student data is updated
Alternative sequence:
5. If employee enters invalid data system displays error messages
8. If employees deny the confirmation system aborts the operation

Department of computer science Page 34

 UOG Ate fasil campus online student registration

Post condition: The content of department information is updated

Use case name: Delete department information
Summary: Remove department from the system
Actor: admin
Dependency: include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. First includes login use case
2. User select department information option
3. User select delete option
4. System provides confirmation
5. User accepts confirmation
6. System informs as department is deleted
Alternative sequence:
4: if employee denies the confirmation system cancels the operation
Post condition: Department is removed from the system
Use case description for enrollment information

Use case name: Add enrollment information

Summary: User adds enrollment information to the system.
Actor: admin, instructor
Precondition: includes login use case
Main sequence:
1. User first includes login use case
2. User selects enrollment information option
3. User selects add option
4. System displays form for input the enrollment information
5. User fills enrollment information such as student name, course code, grade, year,
semester, point, mark in their appropriate place provided Employee select insert
option
6. System validates input data

Department of computer science Page 35

 UOG Ate fasil campus online student registration

7. User select save change option

8. System displays as enrollment information is added.
Alternative sequence:
5: If the employee fills invalid information then, the system displays as error information
entered
Post condition: Enrollment information is added to the system
Use case name: Update enrollment information
Summary: Enrollment information is updated
Actor: admin, instructor
Dependency: includes login use case
Precondition: information to be updated must be registered before
Main sequence:
1. User Includes login use case
2. User selects enrollment information option
3. User selects the update option
4. System displays form for input the new enrollment information
5. User fills the form
6. System validates the input information
7. User selects the save changes option
8. System displays confirmation
9. System inform the update
Alternative sequence:
5. If user enters invalid data system displays error message
8. If user denies confirmation system aborts the operation
Post condition: enrollment information is updated
Use case name: View enrollment information
Summary: User sees the content of the enrollment information
Actor: admin, instructor, student
Dependency: include login use case
Precondition: System is idle displaying welcome message
Main sequence:

Department of computer science Page 36

 UOG Ate fasil campus online student registration

1. First includes login use case

2. User select enrollment information option
3. User selects the view option
4. System displays list of options on how to view enrollment information.
5. User selects from the given option to view
6. System checks the enrollment information against the database value
7. System displays enrollment information
Alternative sequence:
6: if enrollment information does not exist, system display request error
Post condition: the content of the enrollment information is displayed
Use case name: Delete enrollment information
Summary: Remove enrollment information from the system
Actor: admin, instructor
Precondition: include login use case
Main sequence:
1. User first includes login use case
2. user select enrollment information option
3. user select delete option
4. System confirms the delete operation
5. User accepts the confirmation
6. system informs as enrollment information is deleted
Alternative sequence:
3: if user denies the confirmation, it cancels the operation
Post condition: enrollment information is removed from the system
Use case description for employee information
Use case name: Add employee information
Summary: Admin adds employee information to the system.
Actor: Admin
Dependency: Includes login use case
Precondition: Employee must not be in the system before
Main sequence:

Department of computer science Page 37

 UOG Ate fasil campus online student registration

1. First it includes login use case

2. Admin selects Employee information option
3. Admin selects employee add option
4. System display form
5. Admin enters employee information
6. Admin select save change option
7. System displays as employee is added.
Alternative sequence:
5: If the admin fills invalid information then, the system displays error and announce as error
information entered
Post condition: Employee is added to the system
Use case name: View employee information
Summary: Employee sees the content of the his or her information
Actor: Employee, admin
Dependency: Include login use case
Precondition: Employee is already registered
Main sequence:
1. User includes login use case
2. User select Employee information option
3. User selects the view option
4. System displays list of options on how to view employee data.
5. User selects from the given option to view
6. System checks employee information against the database value
7. System display employee information
Alternative sequence:
6: If the system determines the requested data does not exist, it display request error.
Post condition: the content of the employee is displayed
Use case name: Update employee information
Summary: user updates employee data
Actor: admin
Dependency: Includes login use case

Department of computer science Page 38

 UOG Ate fasil campus online student registration

Precondition: User is already registered

Main sequence:
1. Includes the login use case
2. User select employee information option
3. User selects update option
4. User fills the new information to be updated
5. User select the save changes option
6. System asks confirmation question
7. User confirms.
8. System displays employee information is updated
Alternative sequence:
4: If the user inserts invalid data the system displays error message
5: If user denies confirmation, system cancels operation
Post condition: System updates employee information
Use case name: Delete employee information
Summary: Remove employee from the system
Actor: Admin
Dependency: Include login use case
Precondition: employee must already be registered before
Main sequence:
1. Includes login use case
2. User select employee information option
3. User select delete option
4. System send confirmation
5. User accepts the confirmation
6. System informs as employee is deleted
Alternative sequence:
5: If User denies the confirmation it cancels the operation
Post condition: employee is deleted from the system
Use case description for generate report
Use case name: Generate report

Department of computer science Page 39

 UOG Ate fasil campus online student registration

Summary: User sees the content the report

Actor: Admin, Dean
Dependency: Include login use case
Main sequence:
1. User includes login use case
2. User select generate report option
3. User selects the view option
4. System displays list of options on how to view report data.
5. User selects from the given option to view
6. System checks request against the database value
7. System displays the requested report
Alternative sequence:
6: if the requested report does not exist system displays request error
Post condition: the content of the report is displayed
Use case description for cost sharing information
Use case name: Insert cost sharing information
Summary: Students cost sharing information is added
Actor: Student,admin
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. Include login use case
2. User select cost sharing information option
3. User select add cost sharing information option
4. System displays form
5. User insert information such as student id, student first name, middle name, last name,
batch, semester, year, food expense, boarding expense, tuition expense, total, paid.
6. Student select save change option.
Alternative sequence:
5. If user fills wrong information system displays error messages.
Post condition: Cost sharing information is stored to the system

Department of computer science Page 40

 UOG Ate fasil campus online student registration

Use case name: View cost sharing information

Summary: user sees the content of cost sharing information
Actor: Admin, Student
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. User includes login use case
2. User select cost sharing information option
3. User selects the view option
4. System displays list of options on how to view data.
5. User selects from the given option to view
6. System checks the requested data against the database value.
7. System display cost sharing information.
Alternative sequence:
6: If the system does not get the requested value in the database it sends request error
Post condition: The content of the cost sharing is displayed
Use case name: Update cost sharing information
Summary: user updates cost sharing information
Actor: Student, Admin
Dependency: Includes login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. Includes the login use case
2. User select cost sharing information option
3. User selects update option
4. User fills the new information to be updated such as id, first name, middle name, last
name, batch, semester, year, food expense, boarding expense, tuition expense, and total.
5. User select the save change option
6. System asks confirmation question
7. User confirms.
8. System displays as cost information is updated

Department of computer science Page 41

 UOG Ate fasil campus online student registration

Alternative sequence:
4: If the user inserts invalid data the system displays error message
5: If user selects no option system cancels operation
Post condition: User updates cost information
Use case name: Delete cost sharing information
Summary: Remove cost sharing information from the system
Actor: Admin
Dependency: Include login use case
Precondition: cost of student must be available before in the database.
Main sequence:
1. Includes login use case
2. Admin select cost sharing information option
3. Admin select delete option
4. System asks confirmation
5. Admin accepts the confirmation
6. System informs as information is deleted
Alternative sequence:
4: If Admin denies the confirmation it cancels the operation
Post condition: cost sharing is deleted from the system
Use case description for cost sharing amount
Use case name: Insert cost sharing amount
Summary: Admin insert cost sharing information
Actor: Admin
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. Include login use case
2. Admin select cost sharing amount option
3. Admin select add option
4. System displays form
5. Admin insert information

Department of computer science Page 42

 UOG Ate fasil campus online student registration

6. Admin select save change option.

Alternative sequence:
5: If Admin enter invalid information system sends validation error
Post condition: cost sharing amount is stored to the system
Use case name: View cost sharing amount
Summary: user sees the content of the his or her cost sharing amount
Actor: Admin, student
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. User includes login use case
2. User select cost sharing amount option
3. User selects the view option
4. System displays list of options on how to view data.
5. User selects from the given option to view
6. System checks the requested data against the database value.
7. System display the cost amount
Alternative sequence:
6: If the system does not get the values it sends request error
Post condition: the content of the cost sharing amount is displayed
Use case name: Update cost sharing amount
Summary: Admin updates cost sharing information
Actor: Admin
Dependency: Includes login use case and view use case
Precondition: System is idle displaying welcome message
Main sequence:
1. Includes the login use case
2. User select cost sharing amount option
3. User selects update option
4. User fills the new information to be updated
5. User select the save change option

Department of computer science Page 43

 UOG Ate fasil campus online student registration

6. System asks confirmation question

7. Admin confirms.
8. System displays as cost information is updated
Alternative sequence:
4: If the user inserts invalid data the system displays error message
5: If user selects no option system cancels operation
Post condition: System updates cost amount
Use case name: Delete cost sharing amount
Summary: Remove cost sharing amount from the system
Actor: Admin
Dependency: Include login use case
Precondition: cost amount must already be added to the system.
Main sequence:
1. Includes login use case
2. Admin select cost sharing amount option
3. Admin select delete cost sharing option
4. System asks confirmation
5. Admin accepts the confirmation
6. System informs as information is deleted
Alternative sequence:
5: If Admin denies the confirmation it cancels the operation
Post condition: Admin delete cost amount from the system
Use case description for post messages
Use case name: post message
Summary: Admin post messages
Actor: Admin
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. Include login use case
2. Admin select post message option

Department of computer science Page 44

 UOG Ate fasil campus online student registration

3. Admin select add option

4. System displays form
5. Admin insert information such as message id, message title, and message body.
6. Admin select save change option.
Alternative sequence:
5: If Admin enter invalid information, system displays error.
Post condition: Message is stored to the system
Use case name: View message
Summary: user sees message
Actor: Admin, student, employee
Dependency: Include login use case
Precondition: System is idle displaying welcome message
Main sequence:
1. User includes login use case
2. User select message option
3. User selects the view option
4. System displays list of options on how to view data.
5. User selects from the given option to view
6. System checks whether the message exists against the database value.
7. System display messages
Alternative sequence:
6: If the system does not get the message, it sends request error
Post condition: the content of the message is displayed
Use case name: Update message
Summary: Admin updates messages
Actor: Admin
Dependency: Includes login use case
Precondition: system is idle displaying welcome message
Main sequence:
1. Includes the login use case
2. User select message option

Department of computer science Page 45

 UOG Ate fasil campus online student registration

3. User selects update option

4. User fills the new information to be updated such as message id, message title, and
message body.
5. User select the save change option
6. System asks confirmation question
7. Admin confirms.
8. System displays as cost information is updated
Alternative sequence:
4: If the user inserts invalid data the system displays error message
5: If user selects no option system cancels operation
Post condition: System updates message
Use case name: Delete message
Summary: Remove message from the system
Actor: Admin
Dependency: Include login use case
Precondition: Message must already be posted before to the database
Main sequence:
1. Includes login use case
2. Admin select message option
3. Admin select delete option
4. System request confirmation
5. Admin accepts the confirmation
6. System informs as information is deleted
Alternative sequence:
4: If Admin denies the confirmation it cancels the operation
Post condition: Admin delete message from the system

Use case description for first year admission code

Use case name: insert admission code
Summary: admin inserts first year admission code
Actor: admin
Dependency: includes login use case

Department of computer science Page 46

 UOG Ate fasil campus online student registration

Precondition: system is idle displaying welcome message

Main sequence:
1. Includes login use case
2. Admin select admission code option
3. System displays form
4. Admin fill form
5. System validates
6. Admin select save option
7. System displays success message
Alternative sequence:
4: if invalid information enter system displays error message
Post condition: admission code is added to the system
Use case name: view admission code
Summary: admin view first year admission code
Actor: admin
Dependency: includes login use case
Precondition: system is idle displaying welcome message
Main sequence:
1. Includes login use case
2. Admin select view admission code option
3. System display view mechanism to view
4. Admin select view mechanism
5. System displays admission code
Alternative sequence:
4: if admission code not found system displays request error
Post condition: admission code is displayed
Use case name: update admission code
Summary: admin updates first year admission code
Actor: admin
Dependency: includes login use case
Precondition: system is idle displaying welcome message

Department of computer science Page 47

 UOG Ate fasil campus online student registration

Main sequence:
1. Includes login use case
2. Admin select update admission code option
3. System displays form
4. Admin fill form
5. System validates
6. Admin select save option
7. System displays confirmation
8. Admin accepts confirmation
9. System displays success message for updating
Alternative sequence:
4: if invalid information enter system displays error message
7: admin deny confirmation system exits.
Post condition: admission code is updated in the system
Use case name: delete admission code
Summary: admin delete first year admission code
Actor: admin
Dependency: includes login use case
Precondition: system is idle displaying welcome message
Main sequence:
1. Includes login use case
2. Admin select delete admission code option
3. System displays confirmation
4. Admin accept confirmation
5. System deletes admission code
Alternative sequence:
3: if admin deny confirmation it cancels the operation
Post condition: admission code is deleted from the system

Use case description for create account

Use case name: create account
Summary: user create their own account

Department of computer science Page 48

 UOG Ate fasil campus online student registration

Actor: admin, student, employee, dean, instructor

Dependency: includes login use case
Precondition: system is idle displaying welcome message
Main sequence:
1. Includes login use case
2. User select create account option
3. System displays form
4. User fill form
5. System validates
6. User select save option
7. System displays success message
Alternative sequence:
4: if invalid information enters system displays error message
Post condition: account is created
Use case name: update account
Summary: user updates their account
Actor: admin, student, employee, dean, instructor
Dependency: includes login use case
Precondition: system is idle displaying welcome message
Main sequence:
1. Includes login use case
2. User select update admission code option
3. System displays form
4. User fill form
5. System validates the entered information
6. User select save option
7. System displays confirmation
8. Admin accepts the confirmation
9. System displays success message
Alternative sequence:
4: if admin enters invalid information, system displays error message

Department of computer science Page 49

 UOG Ate fasil campus online student registration

7: if user denies confirmation, system exits.

Post condition: account is updated
Use case name: view account
Summary: user view their own account
Actor: admin, student, employee, dean, instructor
Dependency: includes login use case
Precondition: system is idle displaying welcome message
Main sequence:
1. Includes login use case
2. User select admission code option
3. System display view options
4. User select from those view option
5. System displays account
Post condition: account is displayed
Use case name: delete account
Summary: Users delete their own account
Actor: admin, student, employee, dean, instructor
Dependency: includes login use case
Precondition: system is idle displaying welcome message
Main sequence:
1. Includes login use case
2. User select admission code option
3. User select delete option
4. System displays confirmation
5. User accept confirmation
Alternative sequence:
4: if users deny confirmation it cancels operation
Post condition: account is deleted

Department of computer science Page 50

 UOG Ate fasil campus online student registration

2.5.2.3. Activity diagram

Activity diagrams are typically used for business process modeling, for modeling the logic
captured by a single use case or usage scenario, or for modeling the detailed logic of a business
rule.

Figure 4 activity diagram for create account

Department of computer science Page 51

 UOG Ate fasil campus online student registration

Figure 5 activity diagram for view account

Figure 6 Activity diagram for update account

Department of computer science Page 52

 UOG Ate fasil campus online student registration

Figure 7 Activity diagram for delete account

Figure 8 Activity diagram for add student information

Department of computer science Page 53

 UOG Ate fasil campus online student registration

Figure 9 Activity diagram for view student information

Figure 10 Activity diagram for update student information

Department of computer science Page 54

 UOG Ate fasil campus online student registration

Figure 11 Activity diagram for delete student information

Figure 12 Activity diagram for add instructor information

Department of computer science Page 55

 UOG Ate fasil campus online student registration

Figure 13 Activity diagram for view instructor information

Figure 14 Activity diagram for update instructor information

Department of computer science Page 56

 UOG Ate fasil campus online student registration

Figure 15 Activity diagram for delete instructor information

Figure 16 Activity diagram for add course information

Department of computer science Page 57

 UOG Ate fasil campus online student registration

Figure 17 Activity diagram for view course information

Figure 18 Activity diagram for update course information

Department of computer science Page 58

 UOG Ate fasil campus online student registration

Figure 19 Activity diagram for delete course information

Figure 20 Activity diagram for add department information

Department of computer science Page 59

 UOG Ate fasil campus online student registration

Figure 21 Activity diagram for view department information

Figure 22 Activity diagram for update department information

Department of computer science Page 60

 UOG Ate fasil campus online student registration

Figure 23 Activity diagram for delete department information

Figure 24 Activity diagram for add enrollment information

Department of computer science Page 61

 UOG Ate fasil campus online student registration

Figure 25 Activity diagram for view enrollment information

Figure 26 Activity diagram for update enrollment information

Department of computer science Page 62

 UOG Ate fasil campus online student registration

Figure 27 Activity diagram for delete enrollment information

Figure 28 Activity diagram for add employee information

Department of computer science Page 63

 UOG Ate fasil campus online student registration

Figure 29 Activity diagram for view employee information

Figure 30 Activity diagram for update employee information

Department of computer science Page 64

 UOG Ate fasil campus online student registration

Figure 31 Activity diagram for delete employee information

Figure 32 Activity diagram for generate report information

Department of computer science Page 65

 UOG Ate fasil campus online student registration

Figure 33 Activity diagram for add cost-sharing information

Figure 34 Activity diagram for view cost-sharing information

Department of computer science Page 66

 UOG Ate fasil campus online student registration

Figure 35 Activity diagram for update cost-sharing information

Figure 36 Activity diagram for delete cost-sharing information

Department of computer science Page 67

 UOG Ate fasil campus online student registration

Figure 37 Activity diagram for add cost-sharing amount

Figure 38 Activity diagram for view cost-sharing amount

Department of computer science Page 68

 UOG Ate fasil campus online student registration

Figure 39 Activity diagram for update cost-sharing amount

Figure 40 Activity diagram for delete cost-sharing amount

Department of computer science Page 69

 UOG Ate fasil campus online student registration

Figure 41 Activity diagram for post message

Figure 42 Activity diagram for view posted message information

Department of computer science Page 70

 UOG Ate fasil campus online student registration

Figure 43 Activity diagram for update posted message

Figure 44 Activity diagram for delete posted message

Department of computer science Page 71

 UOG Ate fasil campus online student registration

Figure 45 Activity diagram for add admission code

Figure 46 Activity diagram for view admission code

Department of computer science Page 72

 UOG Ate fasil campus online student registration

Figure 47 Activity diagram for update admission code

Figure 48 Activity diagram for delete admission code

Department of computer science Page 73

 UOG Ate fasil campus online student registration

2.5.3. Object model

2.5.3.1. Data dictionary
Data dictionary is the textual description of data objects and their attributes.

Student data A data that contains student name, student id,

student address, student age, birth date, status,
region, zone, woreda, kebele, name of school that a
student finishes preparatory program, date of
completion, university join information such as
faculty, department, and batch of student is called
student data. The word data can be used
interchangeability with information.
Course information Information that contains course code, course
name, course’s credit hour, and points is called
course information.
Enrollment information Information that contains student id, course code,
and score of a course such as mid, final, total,
grade, GPA, semester and year is referred to as
enrollment information.
Department information Information that contains department name,
department location is referred to as department
information. In general data have exactly the same
meaning as information

Adopter’s information Information’s that contain adopter’s address, full

name, house number, phone number, P.O.BOX.

Instructor information Information’s that contain instructor id, first name,

last name, sex, age, phone number.

Department of computer science Page 74

 UOG Ate fasil campus online student registration

Cost sharing information Information’s that contain student id, student first
name, middle name, last name, batch, semester,
year, food expense, boarding expense, tuition
expense, total.

Post messages Information’s that contain message id, message

title, message body.

Employee Employees are those persons which include

librarians, proctors, clinic employee to perform
student registration

Semester Semester is the half period of one academic year

Year Year is time in which a given student takes a given
course
Course data Course data is the same as course information and
can be used interchangeably.
User Account User Account is An established relationship
between a user and a computer. User accounts are
assigned a username and Passwords are mandatory
for registrations.
IP IP is like a primary key that uniquely identifies
each row when there are many primary key in the
table
Cost sharing amount Holds available cost amounts that students will
made agreement. It includes tuition expense, food
expense, and boarding expense.
Admission code Admission code is the code that freshman student
take example for passing to university program.
report Report is the information generated from student
enrollment information may be student status, GPA
of student.

Department of computer science Page 75

 UOG Ate fasil campus online student registration

Table 1 data dictionary

2.5.3.2. Class modeling

Class Diagram: it is a type of static structure diagram that describe the structure of a system by
showing system classes, their attribute, operation and the relationship among the class.

Department of computer science Page 76

 UOG Ate fasil campus online student registration

Figure 49 Class diagram

2.5.3.3. Dynamic modeling using sequence diagram

Sequence Diagram is a kind of interaction diagram that show how processes operate with one
another and in what order based on time.

Department of computer science Page 77

 UOG Ate fasil campus online student registration

Figure 50 Sequence diagram for add student information

Department of computer science Page 78

 UOG Ate fasil campus online student registration

Figure 51 Sequence diagram for view student information

Figure 52 Sequence diagram for update student information.

Department of computer science Page 79

 UOG Ate fasil campus online student registration

Figure 53 Sequence diagram for delete student information

Department of computer science Page 80

 UOG Ate fasil campus online student registration

Figure 54 Sequence diagram for add instructor information

Department of computer science Page 81

 UOG Ate fasil campus online student registration

Figure 55 Sequence diagram for view instructor information

Figure 56 Sequence diagram for update instructor information

Department of computer science Page 82

 UOG Ate fasil campus online student registration

Figure 57 Sequence diagram for delete instructor information

Department of computer science Page 83

 UOG Ate fasil campus online student registration

Figure 58 Sequence diagram for add course information

Department of computer science Page 84

 UOG Ate fasil campus online student registration

Figure 59 Sequence diagram for view course information

Figure 60 Sequence diagram for update course information

Department of computer science Page 85

 UOG Ate fasil campus online student registration

Figure 61 Sequence diagram for delete course information

Department of computer science Page 86

 UOG Ate fasil campus online student registration

Figure 62 Sequence diagram for add department information

Department of computer science Page 87

 UOG Ate fasil campus online student registration

Figure 63 Sequence diagram for view department information

Figure 64 Sequence diagram for update department information

Department of computer science Page 88

 UOG Ate fasil campus online student registration

Figure 65 Sequence diagram for delete department information

Department of computer science Page 89

 UOG Ate fasil campus online student registration

Figure 66 Sequence diagram for add enrollment information

Department of computer science Page 90

 UOG Ate fasil campus online student registration

Figure 67 Sequence diagram for view enrollment information

Figure 68 Sequence diagram for update enrollment information

Department of computer science Page 91

 UOG Ate fasil campus online student registration

Figure 69 Sequence diagram for delete enrollment information

Department of computer science Page 92

 UOG Ate fasil campus online student registration

Figure 70 Sequence diagram for add employee information

Department of computer science Page 93

 UOG Ate fasil campus online student registration

Figure 71 Sequence diagram for view employee information

Figure 72 Sequence diagram for update employee information

Department of computer science Page 94

 UOG Ate fasil campus online student registration

Figure 73 Sequence diagram for delete employee information

Figure 74 Sequence diagram for view generated report information

Department of computer science Page 95

 UOG Ate fasil campus online student registration

Figure 75 Sequence diagram for add cost-sharing information

Department of computer science Page 96

 UOG Ate fasil campus online student registration

Figure 76 Sequence diagram for view cost-sharing information

Figure 77 Sequence diagram for update cost-sharing information

Department of computer science Page 97

 UOG Ate fasil campus online student registration

Figure 78 Sequence diagram for delete cost-sharing information

Department of computer science Page 98

 UOG Ate fasil campus online student registration

Figure 79 Sequence diagram for add cost sharing amount

Department of computer science Page 99

 UOG Ate fasil campus online student registration

Figure 80 Sequence diagram for view cost-sharing amount

Figure 81 Sequence diagram for update cost-sharing amount information

Department of computer science Page 100

 UOG Ate fasil campus online student registration

Figure 82 Sequence diagram for delete cost-sharing amount information

Department of computer science Page 101

 UOG Ate fasil campus online student registration

Figure 83 Sequence diagram for posting messages

Department of computer science Page 102

 UOG Ate fasil campus online student registration

Figure 84 Sequence diagram for view posted message

Figure 85 Sequence diagram for update Posted message

Department of computer science Page 103

 UOG Ate fasil campus online student registration

Figure 86 Sequence diagram for deleting posted message

Department of computer science Page 104

 UOG Ate fasil campus online student registration

Figure 87 Sequence diagram for add admission code

Department of computer science Page 105

 UOG Ate fasil campus online student registration

Figure 88 Sequence diagram for view admission code

Figure 89 Sequence diagram for update admission code

Department of computer science Page 106

 UOG Ate fasil campus online student registration

Figure 90 Sequence diagram for delete admission code

Department of computer science Page 107

 UOG Ate fasil campus online student registration

Figure 91 Sequence diagram for add account

Department of computer science Page 108

 UOG Ate fasil campus online student registration

Figure 92 Sequence diagram for view account

Figure 93 Sequence diagram for update account

Department of computer science Page 109

 UOG Ate fasil campus online student registration

Figure 94 Sequence diagram for delete account

Department of computer science Page 110

 UOG Ate fasil campus online student registration

2.5.3.4. User interface

Figure 95 user interface diaggram

Figure 96 user interface diagram cont…

Department of computer science Page 111

 UOG Ate fasil campus online student registration

Chapter three
3. System design
3.1. Introduction
System design activities of the system is all about decomposing the system into manageable parts
that can be realized by individual teams as student information management, course information
management, enrollment information management, department information management, cost
sharing information management, message management, generate report management. We
identify the design goals of the system that are traceable to the nonfunctional requirement that
have acquired during requirement elicitation and analysis.
3.2. Current software architecture
The current software architecture represents the architecture that we are going to replace with the
new system. Now the system is manual and keeps all available student information in paper-
based documents and sometimes in Microsoft excel products.
3.3. Proposed software architecture
3.3.1. Overview
In response to the manual system we are going to develop the three tier architecture for
university of Gondar (UOG) FASIL campus online registrar system.
3.3.1.1. Three tier client-server architecture
In client-server architecture the functionality of the system is organized into services, with each
service delivered from server. Clients are the users of the services and access servers to make use
of them. We will use this three tier architecture because when data in a shared database has to be
accessed from a range of locations.

Data tier: the data tier maintains the application data such as user’s data, department data,
courses data, and enrollment data.

Middle tier: the middle tier (web / application server) implements the controller logic and
presentation logic to control the interaction between the application client and data.

Client tier: the client tier is the application user interface connecting entry forms and client side
applications. It displays data to the user. The user interacts to the application through the user

Department of computer science Page 112

 UOG Ate fasil campus online student registration

interface. The client tier interacts with the web /application server to make request and to retrieve
data from the database. It then displays the user data retrieved from the database.

3.3.1.2. Why three tier architecture?

As more users access the system three tier solutions is more scalable than the other solutions
because you can add as many middle tier as needed to insure good performance. Security is also
best in the three tier architecture because the middle layer protects the database tier.

Figure 97 Proposed software architeture

3.3.2. Subsystem decomposition
The system is decomposed into the following component: student information subsystem, cost
sharing information subsystem, generate report subsystem, course information subsystem,
department information subsystem, enrollment information subsystem, and message information
subsystem.

Student information subsystem is the personal detail of the student. Cost sharing component is
for storing and retrieving the cost sharing of the student with regard to the services that a student
uses in the campus. Department component is about available department and its location.
Message component is about notices that are delivered for the responsible person from the admin
district. Course component holds information about available courses and the credit hour about
that course. Enrollment component is all about the derived attribute that exist when a student
enroll a course.

Department of computer science Page 113

 UOG Ate fasil campus online student registration

Figure 98 decomposing the system into subsystem (using component diagram)

Department of computer science Page 114

 UOG Ate fasil campus online student registration

3.3.3. Hardware/software mapping

The protocol used by two nodes to communicate can be indicated with a stereotype on the
communication path. The Web browser on pc and macs are access web server that provides
information from the database.

Figure 99 Deployment diagram showing hardware/software mapping

3.3.4. Persistent data management strategy
Persistent data outlive a single execution of the system. To do so we use object-oriented
database: An object-oriented database provides services similar to a relational database. Unlike a
relational database, it stores data as objects and associations. In addition to providing a higher
level of abstraction (and thus reducing the need to translate between objects and storage entities),
object-oriented databases provide developers with inheritance and abstract data types. Object-
oriented databases significantly reduce the time for the initial development of the storage
subsystem.
3.3.4.1. Identifying persistent object
The most important persistent objects of the system are described below.
The first is created and accessed during student information management to manage student.

Department of computer science Page 115

 UOG Ate fasil campus online student registration

The second is created and accessed during the management of the course information to manage
course.
The third is created and accessed during the management of department information to manage
department.
The fourth is created and accessed during the management of enrollment information to manage
enrollment.
The fifth is created and accessed during the management of cost sharing information to manage
cost sharing.
The sixth is created and accessed during the management of message to manage available
messages.

Figure 100 Object diagram for the major persistent object

3.3.5. Access control and security

In multi-user systems, different actors have access to different functionality and data. For
example, an everyday actor may only access the data it creates, whereas a system administrator

Department of computer science Page 116

 UOG Ate fasil campus online student registration

actor may have unlimited access to system data and to other users’ data. During analysis, we
modeled these distinctions by associating different use cases to different actors. During system
design, we model access by determining which objects are shared among actors, and by defining
how actors can control access. Depending on the security requirements of the system, we also
define how actors are authenticated and authorized to the system
Object /actor system

Login()
Insert student information()
Delete student information()
Update student information()
View student information()
Insert course information()
admin Delete course information()
Update course information()
View course information()
Insert department information()
Update department information()
View department information()
Delete department information()
Insert enrollment information()
Update enrollment information()
View enrollment information()
Delete enrollment information()
Update cost sharing amount()
Delete cost sharing amount()
View cost sharing amount()
Insert employee information()
Update employee information()
Delete employee information()

Department of computer science Page 117

 UOG Ate fasil campus online student registration

Insert instructor information()

Update instructor information()
Delete instructor information()
Post messages()
Update messages()
Delete messages()
View messages()
View cost sharing information()
Delete cost sharing information(0
student Insert student information()
Update student information()
View student information()
Insert cost sharing information()
Update cost sharing information()
View cost sharing information()
View course information()
View department information()
View enrollment information()
Login()
Instructor Insert enrollment information()
Update enrollment information()
View enrollment information()
View instructor information()
Login()
View department information()
View course information()
employee View admin messages()
Use user name and password to login()
Check id from system()
Password()

Department of computer science Page 118

 UOG Ate fasil campus online student registration

dean View report()

Login()
Table 2 Access control and security

3.3.6. Subsystem service

In the above section, we have examined the key system design decisions that impact the
subsystem decomposition. We have now identified the main subsystems and we have a rough
idea of how to allocate responsibilities to each subsystem. In this activity, we refine the
subsystem decomposition by identifying the services provided by each subsystem. We review
each dependency between subsystems and define an interface for each service we identified as
follows.

Department of computer science Page 119

 UOG Ate fasil campus online student registration

Figure 101 Subsystem managed on different interface using component diagram

Figure 102 Services implemented on different interface using component diagram

Department of computer science Page 120

 UOG Ate fasil campus online student registration

Figure 103 Services implemented on different interface continued from above

Figure 104 Services implemented on different interface cont…

Department of computer science Page 121

 UOG Ate fasil campus online student registration

3.4. Detailed class diagram

Detailed class diagram is used to identify missing attributes and operations that are needed to
realize the subsystem services. This is also used to specify the visibility and signature of each
operation that determines which operation is visible to other objects and subsystems. It is also
used to specify contracts that must be true before and after the operation is invoked.

Department of computer science Page 122

 UOG Ate fasil campus online student registration

Figure 105 Detailed class diagram

Department of computer science Page 123

 UOG Ate fasil campus online student registration

Figure 106 Invariants on exist on class student

Figure 107 Invariants exist on Admin class

Department of computer science Page 124

 UOG Ate fasil campus online student registration

Figure 108 Invariants exist on cost-sharing class

Department of computer science Page 125

 UOG Ate fasil campus online student registration

3.5. Packages
Package: a general purpose mechanism for organizing model elements & diagrams into groups.
A package merge is a directed relationship between two packages that indicates that the contents
of the two packages are to be combined.

Figure 109 Package diagram

Department of computer science Page 126

 UOG Ate fasil campus online student registration

Chapter four
4. Implementation

4.1. Mapping model to code

Associations are UML concepts that denote collections of bidirectional links between two or
more objects. Object-oriented programming languages, however, do not provide the concept of
association. Instead, they provide references, in which one object stores a handle to another
object, and collections, in which references to several objects can be stored and possibly
ordered. References are unidirectional and take place between two objects. During object
design, we realize associations in terms of references, taking into account the multiplicity of the
associations and their direction.

For enrollment add information index page

<script type="text/javascript">
function viewenrollment(){
$.ajax({
type: "GET",
url: "getenrollment.php",
dataType: "html"
}).done(function( msg ) {
$( "#viewdata" ).html( msg );
}).fail(function( jqXHR, textStatus ) {
alert( "Request failed: " + textStatus );
});
}
$('#save').click(function(){
var ip=$('#ip').val();
var id=$('#id').val();
var cocode = $('#cocode').val();
var point = $('#point').val();
var dept = $('#dept').val();

Department of computer science Page 127

 UOG Ate fasil campus online student registration

var section = $('#section').val();

var batch = $('#batch').val();
var semester = $('#semester').val();
var year=$('#year').val();
var mid1 = $('#mid1').val();
var mid2 = $('#mid2').val();
var ap = $('#ap').val();
var fina = $('#fina').val();
vardatas=
"ip="+ip+"&id="+id+"&cocode="+cocode+"&point="+point+"&dept="+dept+"&section="+sec
tion+"&batch="+batch+"&semester="+semester+"&year="+year+"&mid1="+mid1+"&mid2="+
mid2+"&ap="+ap+"&fina="+fina;
$.ajax({
type: "POST",
url: "addenrollment.php",
data: datas,
dataType: "html"
}).done(function( msg ) {
alert( msg );
viewenrollment();
}).fail(function() {
alert( "error" );
}).always(function() {
alert( "finished" );
});
});
</script>
Add enrollment php page
<?php
include "db_connection.php";
$id = $_POST['id'];

Department of computer science Page 128

 UOG Ate fasil campus online student registration

$cocode = $_POST['cocode'];
$point=$_POST['point'];
$dept =$_POST['dept'];
$section = $_POST['section'];
$batch =$_POST['batch'];
$semester = $_POST['semester'];
$year = $_POST['year'];
$mid1 = $_POST['mid1'];
$mid2 =$_POST['mid2'];
$ap = $_POST['ap'];
$fina =$_POST['fina'];
if(isset($id) && isset($cocode)&& isset($point) && isset($dept) && isset($section) &&
isset($batch) && isset($semester) && isset($year) && isset($mid1) && isset($mid2) &&
isset($ap) && isset($fina)){
$s="INSERT INTO adminenrollment (id,
cocode,pointt,dept,section,batch,semester,year,mid1,mid2,ap,f) VALUES ('$id',
'$cocode',$point,'$dept','$section','$batch','$semester','$year','$mid1','$mid2','$ap','$fina')";

$run=mysqli_query($dbcon,$s);
if($run){
echo "Success Post Data";
} else{
echo "duplicate entry";
}
} else{
echo "Error Post Data";
}
//grade calculating
code=================================================================
==================//
$res =("SELECT * FROM enrollment where id='$id' && cocode='$cocode'");
$run_res=mysqli_query($dbcon,$res);

Department of computer science Page 129

 UOG Ate fasil campus online student registration

$tot=0;
$grade='';
while($ro=mysqli_fetch_array($run_res)){
$m1=(double)$ro['mid1'];
$m2=(double)$ro['mid2'];
$a=(double)$ro['ap'];
$f=(double)$ro['f'];
$tot=$m1+$m2+$a+$f;
if($tot >=90){
$grade='A+';
}
else if($tot>=85){
$grade='A';
}
else if($tot>=80){
$grade='A-';
}else if($tot>=75){
$grade='B+';
}
else if($tot>=70){
$grade='B';
}
else if($tot>=65){
$grade='B-';
}
else if($tot>=60){
$grade='C+';
}
else if($tot>=55){
$grade='C';
}

Department of computer science Page 130

 UOG Ate fasil campus online student registration

else if($tot>=50){
$grade='C-';
}
else if($tot>=45){
$grade='D';
}
else if($tot>=40){
$grade='FX';
}
else {
$grade='F';
}
$s="UPDATE enrollment SET total='$tot', grade='$grade' where id='$id' &&
cocode='$cocode'";
$run=mysqli_query($dbcon,$s);
}
/*gpa calculating
code=================================================================
=====*/
$r =("SELECT * FROM enrollment where id='$id' && cocode='$cocode'");
$run_res=mysqli_query($dbcon,$r);
$psa=0.0;
$psam=0.0;
$psbp=0.0;
$psb=0.0;
$psbm=0.0;
$pscp=0.0;
$psc=0.0;
$pscm=0.0;
$psd=0.0;
$gpa=0.0;

Department of computer science Page 131

 UOG Ate fasil campus online student registration

$pointsum=0.0;
$psg=0.0;
$point=0;
while($ro=mysqli_fetch_array($run_res)){
$point=(double)$ro['pointt'];
$pointsum=$pointsum+$point;
$grade=$ro['grade'];
if($grade=='A'||$grade=='A+'){
$psa=4.0*$point;
}
if($grade=='A-'){
$psam=3.75*$point;
}
if($grade=='B+'){

$psbp=3.5*$point;
}

if($grade=='B'){
$psb=3.0*$point;
}
if($grade=='B-'){
$psbm=2.75*$point;
}
if($grade=='C+'){
$pscp=2.5*$point;
}
if($grade=='C'){
$psc=2.0*$point;
}
if($grade=='C-'){
$pscm=1.75*$point;

Department of computer science Page 132

 UOG Ate fasil campus online student registration

}
if($grade=='D'){
$psd=1.5*$point;
}
$psg=$psa+$psam+$psbp+$psb+$psbm+$pscp+$psc+$pscm+$psd;
$s="UPDATE enrollment SET pointsum='$psg' where id='$id' && cocode='$cocode'";
$run=mysqli_query($dbcon,$s);
}
$r =("SELECT * FROM enrollment where id='$id' AND semester='$semester'");
$run_res=mysqli_query($dbcon,$r);
$totf=0.0;
$p=0.0;
while($ro=mysqli_fetch_array($run_res)){
$totf=$totf+(double)$ro['pointsum'];
$p=$p+(double)$ro['pointt'];
$gpa=$totf/$p;
$s="UPDATE enrollment SET sesum='$totf' where id='$id' AND semester='$semester' AND
batch='$batch' AND cocode='$cocode'";
$run=mysqli_query($dbcon,$s);
}
$r =("SELECT * FROM enrollment where id='$id'");
$run_res=mysqli_query($dbcon,$r);
$totf=0.0;
$p=0.0;
while($ro=mysqli_fetch_array($run_res)){
$totf=$totf+(double)$ro['pointsum'];
$p=$p+(double)$ro['pointt'];
$gpa=$totf/$p;
$s="UPDATE enrollment SET gpa='$gpa' where id='$id' AND cocode='$cocode'";
$run=mysqli_query($dbcon,$s);
}

Department of computer science Page 133

 UOG Ate fasil campus online student registration

?>
The get enrollment.php file to load data from the server
<table class="table table-responsive table-condensed table-bordered table-hover table-striped">
<tr>
<th>ID</th>
<th>course code</th>
<th>point</th>
<th>department</th>
<th>section</th>
<th>batch</th>
<th>semester</th>
<th>year</th>
<th>mid1</th>
<th>mid2</th>
<th>A and project</th>
<th>final</th>
<th>total</th>
<th>grade</th>
<th>pointsum</th>
<th>semester sum</th>
<th>gpa</th>
</tr>
<?php
include "db_connection.php";
$res =("SELECT * FROM adminenrollment");
$run=mysqli_query($dbcon,$res);
while($row = mysqli_fetch_array($run)):
?>
<tr>
<td><?php echo $row['id']; ?></td>
<td><?php echo $row['cocode']; ?></td>

Department of computer science Page 134

 UOG Ate fasil campus online student registration

<td><?php echo $row['pointt']; ?></td>

<td><?php echo $row['dept']; ?></td>
<td><?php echo $row['section']; ?></td>
<td><?php echo $row['batch'];?></td>
<td><?php echo $row['semester'];?></td>
<td><?php echo $row['year']; ?></td>
<td><?php echo $row['mid1']; ?></td>
<td><?php echo $row['mid2']; ?></td>
<td><?php echo $row['ap']; ?></td>
<td><?php echo $row['f']; ?></td>
<td><?php echo $row['total'];?></td>
<td><?php echo $row['grade'];?></td>
<td><?php echo $row['pointsum'];?></td>
<td><?php echo $row['sesum'];?></td>
<td><?php echo $row['gpa'];?></td>
</tr>
<?php
endwhile;
?>

Department of computer science Page 135

 UOG Ate fasil campus online student registration

4.2. Screen images

Figure 110 screen images

Department of computer science Page 136

 UOG Ate fasil campus online student registration

5. Conclusion and recommendation

Conclusion

The objective of this project is to change the current manual system of registrar system into web-
based online student registration in partial fulfillment of the degree of BSc in computer science.
When the project is completed it helps the college to serve the large number of students within a
short period of time at the time of registration for each new semester. It also helps every
authenticated person to store and retrieve the required information within a short period of time.
To achieve this functionality we use interview, direct observation, and inspecting form slips as
data gathering methodologies. Based on the result of this requirement gathering methodology we
design the functionality of the system and design the system. finally, we develop web-based
online student registration system that are easy for storing and accessing information in such a
way that it supports different users according to their authentication mechanism.

Recommendation
As a developer of this web-based online student registration system, we recommend the
following to be done and executed in the future

 Expand the system to support for all campus of the university.

 When the addition of new feature is needed the campus administrator should invite those
persons having programming knowledge described in the system development tools.
 Use finger print password system for authentication mechanism.
 To remove distraction of session whenever the student capture a photo.
 To extend student placement and café control system for staff to know how much time
they spent in their office and check whether they enter to their office or not every day.
 Extend the system to tell a specific place that a student is placed whenever they are
outside the campus.
 Expand the system to tell or inform for student family whatever a student has scored in
the university such as student grade, gpa and other information.
 To be able to have direct contact between student’s family and university administrator to
talk about the student.

Department of computer science Page 137

 UOG Ate fasil campus online student registration

6. Bibliography

[Abbott, 1983] R. Abbott, “Program design by informal

English descriptions,”
Communications of the ACM, Vol. 26, No. 11,
1983

[Adams, 2000] D. N. Adams, Mostly Harmless, Ballantine

Books, 2000.
[Baker et al., 2008] P. Baker, Z. R. Dai, & R. Grabowski, Model-
Driven Testing: Using the UML
Testing Profile, Springer, Berlin, 2008.
[Fisher et al., 1991] R. Fisher, W. Ury, & B. Patton, Getting to Yes:
Negotiating Agreement
Without Giving In, 2nd ed., Penguin Books,
1991
[IEEE Std. 610.12-1990] Institute of Electrical and Electronics
Engineers, IEEE Standard Computer
Dictionary: A Compilation of IEEE Standard
Computer Glossaries, New
York, NY, 1990.
[Paulk et al., 1995] M. C. Paulk, C. V. Weber, & B. Curtis (eds.),
The Capability Maturity Model:
Guidelines for Improving the Software
Process, Addison-Wesley, Reading,
MA, 1995.

Department of computer science Page 138

 UOG Ate fasil campus online student registration

7. Glossary

Class Diagram: it is a type of static structure diagram that describe the structure of a system by
showing system classes, their attribute, operation and the relationship among the class.
Component Diagram: is UML diagram depicts how components are wired together to form
larger components and or software system.
Deployment Diagram: is a UML diagram that models the physical deployment of artifact of
nodes.
Functional requirement: a requirement that specifies a function a component or system must
perform.
Hardware: is computer equipment including all the components use to make the computer.
Information: the meaning of data as it is intended to be interpreted by people.
Non-functional requirement: are requirements which specify criteria that can be used to judge
the operation of a system, rather than specific behaviors.
Package Diagram: UML diagram that depicts the dependency between the packages that make
up a model.
Process: is a sequence of instructions to perform some task.
Scenario: is an instance of use case explaining concerned major set of actions.
Sequence Diagram: is a king of interaction diagram that show how process operate with one
another and in what order.
Software: computer programs, instructions that make hardware work.
System: any collection of component element that work together to collect task.
Use case diagram: Graphical Representation of mark full of step wise activity and action with
support for choice, iteration and concurrency.
User interface: the combination of menus, screen design, keyboard command, command
language and help, which creates the way a user interact with computers.
User: any user of the system including database administrator, librarian, member, system
administrator.
Access Control and security: Model is system resource protection that depict who use the
system with what protection.

Department of computer science Page 139

 UOG Ate fasil campus online student registration

References
[1] Berned Bruegge & Allen H.Dotoit, object-oriented software engineering Using UML,
patterns, and Java, 3rd edition. Germany: Technical University of munchi, 2012.
[2] Hassan Gomaa, software modeling and design using UML, use cases, patterns, and software
architectures, NY: Cambridge University press, 2011.

Department of computer science Page 140