HARAMAYA UNIVERSITY

COLLEGE OF COMPUTING AND INFORMATICS

DEPARTMENT OF COMPUTER SCIENCE

HARAMAYA UNIVERSITY COLLEGE OF

COMPUTING
AND
INFORMATICS STUDENT ONLINE
REGISTRATION
SYSTEM
Group Members Id.No.
Adisu Dinkisa
Bayana Fanta
Ketema Deresa 459/08
Miliyon Berhanu 467/08
Nugusa Amsalu

A PROJECT SUBMITTED TO THE COLLEGE OF

COMPUTING AND INFORMATICS DEPARTMENT OF
COMPUTER SCIENCE OF HARAMAYA
UNIVERSITY

1
DEPARTMENT OF COMPUTER SCIENCE
 6/18/2018

2
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

Acknowledgement
Abstract
The Project is web based system of Haramaya University College of Computing and Informatics.
The system is mainly developed to replace the manual system of the office to make it
computerized, with the ability of Keep records of Facility, Department, Course, Instructor,
Student and cost share or students loans information and allows Update and Delete as needed by
respected user. This also helps the office from wastage of time, money, man power as well as
workload, In addition the system maintains three levels of users the Administrator, the student
and the registrar. The administrator is the college staff who manage students of our college it
might be the college dean or department head if we management of students as a department.
The student in this system should be able to register using their university Id number and they
should have placed under the University of HU if they are new for the university. The Registrar
manage users of the system by checking users who want to register is university member or not
and registrar should manage the university database by checking active and inactive users in the
university. The users should be registered for cost sharing after login to the system. The System
will show the overall activities that is done in the system to the system administrator by using
History Log function, The Administrator of the system can post announcement to all system
users and the all system users can give comment for each notifications. finally the system
provide Backup mechanism, that the administrator of the system can take a backup of the
systems database, and the system will save the backup in specified folder with backup taking day
and time.

i
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

List of Figures……………………………………………………………………….…………VI

List of Tables…………………………………………………………………………………...VII

List of Acronyms ……….…………………………………………………….. …………...…VIII

Table of Contents
page
Chapter One 1
1 Introduction 1-2
1.1 Background of the Project 2
1.2 Literature Review 2
1.3 Statement of the Problem 2
1.4 Objective 2
1.4.1 General Objectives 2
1.4.2 Specific Objectives 3
1.5 Methodology 3
1.5.1 Data Collection Methodology 3
1.5.1.1 Interview 3
1.5.1.2 Observation……… 3
1.5.2 System Development Methodology 4-6
1.5.3 System Development Tool 6-7
1.6 Scope and Limitation 7
1.6.1 Scope 7-8
1.6.2 Limitation 8
1.7 Significance of the work 8
1.8 Work Breakdown 8-9
Chapter Two 10
2. System Requirements and Specifications 10
2.1 Existing system 10

ii
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

2.2 Proposed System 10-11

2.2.1 Overview 11-13
2.2.2 Functional Requirement 13
2.2.2.1 Functional Requirement 1.1 13-14
2.2.2.2 Functional Requirement 1.2 14
2.2.2.1.1 Child Functional Requirement 1 14
2.2.2.1.2 Child Functional Requirement 2 15
2.2.2.3 Functional Requirement 1.3 15
2.2.2.4 Functional Requirement 1.4 15
2.2.2.5 Functional Requirement 1.5 16
2.2.2.6 Functional Requirement 1.6 16
2.2.2.7 Functional Requirement 1.7 16-17
2.2.2.7.1Child Functional Requirement 1 17
2.2.2.7.2 Child Functional Requirement 2 17
2.2.2.7.3 Child Functional Requirement 3 17
2.2.2.8 Functional Requirement 1.8 18
2.2.2.9 Functional Requirement 1.9 18
2.2.2.10 Functional Requirement 1.10 19
2.2.2.11 Functional Requirement 1.11 19
2.2.3 Non-Functional Requirement 19
2.2.3.1 Non Functional Requirement 1-Consistent Uptime 19
2.2.3.2 Non Functional Requirement 2-Load and Concurrency 19
2.2.3.3 Non Functional Requirement 3-Familiar Interface 20
2.2.3.4 Non Functional Requirement 4-RealTime Feedback 20
2.2.3.5 Non Functional Requirement 5-Focused Layout 20
2.2.3.6 Non Functional Requirement 6-Web Accessibility 20
2.2.3.7 Non Functional Requirement 7-Dealing with large quantities of data
20
2.2.3.8 Non Functional Requirement 8-Effective Recovery 20
2.3 Feasibility 20
2.3.1 Economical Feasibility 21

iii
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

2.3.2 Technical Feasibility 21

2.3.3 Operational Feasibility 22
Chapter Three23
3. System Design 23
3.1 System Model 23
3.1.1 Use Case Model 23
3.1.1.1 User Registration 24
3.1.1.2 User Login 25
3.1.1.3 View Course Details 26
3.1.1.4 User Profile Page 27
3.1.1.5 View Cost Sharing Details 27-28
3.1.1.6 New Information for students 29
3.1.1.7 Records Staff Interface 29-30
3.1.1.8 Manage Users 30
3.1.1.9 Manage Registration 31
3.1.1.10 Manage University Database 31
3.1.1.11 User Logout 32
3.1.2 Class and Object Diagram 32
3.1.2.1 Class Diagram 32-33
3.1.2.2 Object Diagram 33-34
3.1.3 Dynamic Model 34
3.1.3.1.Sequence Diagram 34-37
3.1.3.2 Activity Diagram 37-40
3.1.3.1 State chart diagram 40-42
3.2 Data Dictionary 42-46
3.3 User Interface 46-48
Chapter Four 49
4. System Design 49
4.1 Introduction 49

iv
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

4.1.1 Overview of System Design 49

4.1.2 Design Goal of the system 49-50
4.2 Deployment Diagram 50-51
4.3 Current system Architecture 51
4.4 Proposed Software Architecture 51-52
4.5 Hardware/Software Mapping 52-53
4.6 Persistent Data Management 53-54
4.7 Access control and security 54
4.8 Global Control Flow 54-55
4.9 Boundary Condition 55-56

v
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

List of Figures
Figure Name Page
Fig 1 diagram of prototype model
Fig 2 Work breakdown structure
Fig 3 Use Case Diagram for Student Online Registration System
Fig 4 Class diagram of Student Online Registration System
Fig 5 object diagram of Student Online Registration System
Fig 6 sequence diagram for SORS registration
Fig 7 Sequence Diagram for login Information
Fig 8 Sequence Diagram To new information
Fig 9 Activity Diagram for Registration
Fig 10 Activity Diagram for Login
Fig 11 Activity Diagram for post Information
Fig 12 State chart diagram for registration
Fig 13 statechart diagram login page 42
Fig 14 Haramaya University User Interface Home Page
Fig 15 HU CCI Registration user interface department choose
Fig 16 HU CCI first Year Registration Home page
Fig 17 HU CCI SORS Login Page 48
Fig 18 Deployment diagram of the system 51
Fig 19 Proposed system architectural system diagram 52
Fig 20 persistent Data modelling 54
Fig 21 Boundary condition for HU CCI SORS 56

vi
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

List of Tables

Table 1. Registration use case Description..............................................................................24

Table 2. User Login Use Case Description..............................................................................25
Table 3. View Course Details Use case Description................................................................26
Table 4. View User profile Use case Description....................................................................27
Table 5. View Cost Sharing Use case Description.............................................................27-28
Table 6. New Information for Students Use case Description.................................................29
Table 7. Records Staff Interface Use case Description ......................................................29-30
Table 8. Manage Users Use case Description..........................................................................30
Table 9. Manage Registration Use case Description................................................................31
Table 10. Manage University Database Use case Description.................................................31
Table 11. Users Log out Use case Description........................................................................32
Table 12. Data Dictionary tables........................................................................................42-46

vii
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

List of Acronyms

Abbreviation Expanded form

UML Unified Modelling Language
SORS Student Online Registration System
HU Haramaya University
CCI College of Computing and Informatics
BCA Basic Course of Action
DBMS Database Management System
GUI Graphical User Interface
DESC Description
RAT Rational
DEP Dependency
DB Database

viii
DEPARTMENT OF COMPUTER SCIENCE
HARAMAYA UNIVERSITY COLLEGE OF COMPUTING AND INFORMATICS STUDENT ONLINE REGISTRATION SYSTE

ix
DEPARTMENT OF COMPUTER SCIENCE
 Chapter One
1. Introduction
The project title is Haramaya University College of Computing and Informatics Student Online
Registration System. Student Online Registration System is web-based System which enable you
to register students who placed under College of Computing and Informatics (CCI) in Haramaya
University. In this document we see deeply the purpose, scope, objective of the system, problems
of the existing system, functional requirements, non-functional requirements, system design and
so on. The major aim of this system is to register College of Computing and Informatics students
online and give an in-depth insight of the complete student online registration system (SORS) by
defining the problem statement in detail. Nevertheless, it also concentrates on the capabilities
required by stakeholders and their needs while defining high-level product features. The detailed
requirements of the student online registration system (SORS) are provided in this document.

1.1 Background of the project

Haramaya University Student Online Registration System is a web based application for the
students to register online. It is the process where by students directly get registration services,
without an intermediary service over the network.

This system consists of three set of users Students, Staff, Registrar. Students have to register in
the system by admin side and login to access the system resources. Once logged in, the students
have the privilege to view their profile and Edit their profile. The students have the privilege to
get any new information posted by universities or by College of Computing and Informatics. The
students can view details of course which available for them in each semester even they can view
details of their course without any limitation of year in each department. Students can also view
their cost sharing account details. At the last student can logout from the system.

Staff have to register first before logged in if it’s a new user. Staffs are members of College of
Computing and Informatics who can change registration order of students after he can logged in.
Staff have the privilege to post new information in college. And also Staff have the privilege to
manage instructor in College. Staff can modify and view its own profile page and he can view
course details in each semester for each batch from first year students up to fourth year students.
At the last staff can logout from the system.

1
DEPARTMENT OF COMPUTER SCIENCE
Registrar have the privilege to manage registration date that is registrar can begin registration
and also he can close registration day based on the given registration deadline. Registrar have to
post new information during registration day to this system to announce registration day.
Registrar have the privilege to manage users, registrar can delete users and also can add users
such as students. Generally Registrar manages University database.

1.2 Review of the Literature

In order to develop Student Online Registration system for HU CCI our group uses other related
topics from google to know necessary requirements before going to ask CCI as a manual for this
system but when we ask our college they support us by giving requirements to develop SORS
and also they list the problems found under our college. Therefore, this developed from scratch.

1.3 Statement Of The problem

College of Computing and Informatics had no existing system to register students but they
register students manually as a traditional way. In our process to develop this system we see
some problems that our college had such as:-

 Staff register students in a manual way.

 Students must have available in the same area with staff member
 Students and staff waste their time during registration
 Sometimes disagreement between staff and students
 Costs of paper is very high, so this wasting money
 Student must pay penalty if not available by the time
 University pay penalty for staff during registration if system is manual.

1.4 Objective

1.4.1 General Objective

The General Objective of our system is an online registration of students In College of

Computing and Informatics.

1.4.2 Specific Objective

2
DEPARTMENT OF COMPUTER SCIENCE
  To register students online
 To register students for a course online
 To access resources online form college
 To view grade report for students online
 To make cost sharing agreement online.
 To authenticate students and staff login.
 To post new information in a simple way for all at the same time

1.5 Methodology

During our research, we will use the following methodologies as a way of finding hidden data,
public interests in order to achieve the above mentioned objectives.

1.5.1 Data Collection Methodology

This is the process of acquiring, finding and gathering information from different sources which
is needed for study to be carried out. This process will involve the use questionnaires, interviews
and observations through which we shall study the existing systems.
1.5.1.1 Interview
Interview guides will be designed for in-depth interviews. These will majorly involve the
coordinator at HU CCI who deal with our field of study. For more and clear detailed information,
we shall design questionnaires to issue out to the users of the system. With this information, we
will be able to understand the performance of the current system (we can say manual system),
the challenges and expectations of the user from the new system. (Student Online Registration
System).
1.5.1.2 Observation
As researchers, we will have to look out for the related systems that are already in use therefore
study their performance. In the same way will study the different behavior that currently exist in
the areas where the system is to operate i.e. security, privacy and internet connection network.

1.5.2 System Development Methodology

3
DEPARTMENT OF COMPUTER SCIENCE
In order to develop SORS we used notations, process and tools that support us to fill our
stakeholder’s requirement. In this process of developing our system we used notation called
Unified Modelling Language (UML). The Unified Modelling Language is one of the most
exciting and useful tools in the world of system development. Why? The UML is a visual
Modelling Language that enables us to create blueprints that capture our visions in a standard,
easy to understand way, and provides a mechanism to effectively share and communicate these
visions with others. UML has many goals such as:-

o Provide users with a ready to use, expressive visual modelling language so we can
develop and exchange meaningful models.
o Provide extensibility and specialization mechanisms to extend core concepts.
o Be independent of particular programming language and development processes.
o Provide a formal basis for understanding modelling language.

As we described earlier we used process of software process modelling to develop SORS.

Software Process Modelling as many types of processing model but we used prototyping
software process model.

What is Prototype model?

The basic idea here is that instead of freezing the requirements before a design or coding can
proceed, a throwaway prototype is built to understand the requirements. This prototype is
developed based on the currently known requirements. By using this prototype, the client can get
an “actual feel” of the system, since the interactions with prototype can enable the client to better
understand the requirements of the desired system. Prototyping is an attractive idea for
complicated and large systems for which there is no manual process or existing system to help
determining the requirements. The prototype are usually not complete systems and many of the
details are not built in the prototype. The goal is to provide a system with overall functionality.

4
DEPARTMENT OF COMPUTER SCIENCE
 Diagram of Prototype model:

Figure 1: diagram of prototype model

Why we chose Prototype model:

 Users are actively involved in the development

 Since in this methodology a working model of the system is provided, the users get a
better understanding of the system being developed.
 Errors can be detected much earlier.
 Quicker user feedback is available leading to better solutions.
 Missing functionality can be identified easily
 Confusing or difficult functions can be identified
Requirements validation, Quick implementation of, incomplete, but
functional, application.

When to use Prototype model:

5
DEPARTMENT OF COMPUTER SCIENCE
  Prototype model should be used when the desired system needs to have a lot of
interaction with the end users.
 Typically, online systems, web interfaces have a very high amount of interaction with
end users, are best suited for Prototype model. It might take a while for a system to be
built that allows ease of use and needs minimal training for the end user.
 Prototyping ensures that the end users constantly work with the system and provide a
feedback which is incorporated in the prototype to result in a useable system. They are
excellent for designing good human computer interface systems.

1.5.3 System Development Tool

A number of useful and appropriate technologies will be used during the process in order to
come up with a well-functioning and running system, these will include following system
development tools are used:

o PHP: is an open source, interpreted and object-oriented scripting language i.e. executed
at server side. It is used to develop web applications (an application i.e. executed at server
side and generates dynamic page).
o HTML: is an acronym which stands for Hyper Text Markup Language that used to
create web pages.
o CSS: is an acronym stands for Cascading Style Sheets. It is a style sheet language which
is used to describe the look and formatting of a document written in markup language. It
provides an additional feature to HTML. It is generally used with HTML to change the
style of web pages and user interfaces. It can also be used with any kind of XML
documents including plain XML, SVG and XUL.
o JAVASCRIPT: is used to create interactive websites. It is mainly used for:

 Client-side validation.
 Dynamic drop-down menus.
 Displaying data and time.
 Displaying popup windows and dialog boxes (like alert dialog box, confirm
dialog box and prompt dialog box).
 Displaying clocks etc.

6
DEPARTMENT OF COMPUTER SCIENCE
 o MYSQL: is a relational database management system. It is open-source and free.

Our MySQL tutorial includes all topics of MySQL database such as insert record, update
record, delete record, select record, create table, drop table etc. There are also given
MySQL interview questions to help you better understand the MySQL database.

MYSQL supports many operating systems with many languages like PHP, PERL, C, C+
+, JAVA, etc.

o Wamp Server is a local server that we used to develop SORS.

o Microsoft VISIO2007: for designing UML diagrams associated with the project.
o Microsoft office 2007: for documenting the corresponding deliverables associated with
the project.
o Sublime Text 3: for designing web interfaces

In in order to develop SORS we shall decide since the system is set to run on different platforms
such as, windows XP, window 7/8/8.1/10.
For developing the system we are going to use an MVC technology with PHP.
MVC is a framework for building web applications using a MVC (Model View
Controller) design:
 The Model represents the application core (for instance a list of database
records). The Model is the part of the application that handles the logic for the
application data. Often model objects retrieve data (and store data) from a
database.
 The View displays the data (the database records). The View is the parts of
the application that handles the display of the data. Most often the views are
created from the model data.
 The Controller handles the input (to the database records). The Controller
is the part of the application that handles user interaction. Typically controllers
read data from a view, control user input, and send input data to the model.

The MVC separation helps you manage complex applications, because you can focus on one
aspect a time. For example, you can focus on the view without depending on the business logic.

7
DEPARTMENT OF COMPUTER SCIENCE
It also makes it easier to test an application. The MVC separation also simplifies group
development. Different developers can work on the view, the controller logic, and the business
logic in parallel.

1.6 Scope and Limitation

This study was conducted for the use of Haramaya University College of Computing and
Informatics provided in the registrar office which is works on Student Online Registration
System.

1.6.1 Scope

The main aim of SORS (Student Online Registration System) is registering students of
Haramaya University who placed under College of Computing and Informatics. In this system
every students can register online in everywhere during available registration time.

Therefore, the scope of this project is limited to only the details listed below.

o Register students online using their Id number.

o SORS is only for Regular student of Haramaya University CCI
o Student Online Registration System register students using their university Id Number
o The system will assign Course, Instructor and Room for year and section (student).
o It have the fester that shows classroom, instructors and course information to the user.
o The system will accepts and store Facility, Department, Building, Room, Year section
(students), Instructors and Course information.
o Managing an authorized access to the system by using user name and password.
o The system will provide backup mechanism in case of failure.
1.6.2 Limitation

The Project does not include:

o Online Video tutorial for student.

o Online penalty payment.
o Normal tutorial class (make up class).
o Add and Drop Students.
o Weekend classes and extensions.

8
DEPARTMENT OF COMPUTER SCIENCE
 1.7 Significance of the work

After this project is finished and properly used it gives incredible benefits to the staff, students
and other users.

The Propose system has the following significance:-

o Users (staff and students) are able to register online in anywhere during registration day.
o Students, Instructors and other users are able to search the information and see their
results online in anywhere, any time without geographical and organizational affiliation.
o Since it is Online it will speedy up the staff work and put them in the line of technology
o The system provide all the information need for registration (viewing, Saving and
printing for the users and storing, updating, and deleting footer for the Administrator.
o The administrator can add users, edit user information and delete user if it is needed.
o The system can Store, Update, and Retrieve the course details in safe and in reliable
manner
o For security reason the system use user name and password for staff, student and other
user.

1.8 Work Breakdown

In order to develop the Haramaya University College of Computing and Informatics Student
Online Registration system, work break down structure is very important to solve simply and
quickly the available problems in our college.

Work Breakdown Structure: Is a deliverable oriented decomposition of a project into smaller

components. It defines and groups a project's discrete work elements in a way that helps organize
and define the total work scope of the project.

Whatever tasks which are operated by responsible person require time, So to manage and process
each and every task, the time should be divided for specific task.

9
DEPARTMENT OF COMPUTER SCIENCE
Scheduling the project tasks is an important project planning activity. It involves deciding which tasks
would be taken up when. In order to schedule the project activities, a software project manager needs
to do the following:
 Identify all the tasks needed to complete the project.
 Break down large tasks into small activities.
 Determine the dependencies among different activities.
 Establish the most likely estimates for the time durations necessary to complete the
activities.
 Plan the starting and ending dates for various activities.
 Determine the critical path, A critical path is the chain of activities that determines
the duration of the project.

Figure 2 work Break down structure diagram

10
DEPARTMENT OF COMPUTER SCIENCE
 Chapter Two

2. System Requirements and Specification

2.1 Existing System

College of Computing and Informatics is one of the colleges in Haramaya University. Under this
college there are five Departments such as: Computer Science, Information System, Information
Technology, Software Engineering and Information Science. When we study about College of
Computing and Informatics gives different services for students like registering students
(Registration system), learning and teaching, examination service, grading service and etc.in a
manual way. From this service we focused on registration system. Student registration system is
one of major function done by CCI. Also our team studying how the manual system register
students and we need to develop additional new system for our College that register students
online. So, we focused only on manual Student Registration System in college of computing and
informatics for developing new system that we called Student Online Registration System. As
we study about registration system in CCI they register students if students are only available by
body in the same area with staff to be registered on time. But this is wasting time for both
students and staffs to finish their process and also registration process may take high cost of
paper to register students. Therefore after we studied about this manual system we thought to
change the manual system to online Registration system because the manual system has many
problems such as:

 CCI register students manually.

 Students and staff must be available in the same area at the same time to register
students.
 Students waste their time to be registered and staff waste their time to register students
 Costs of paper is high even they give registration paper up to four pages for one student
so this is wasting money.
11
DEPARTMENT OF COMPUTER SCIENCE
  Student who cannot available because of some reason must pay penalty for University.
 Payment for staff is high when College arrange them to registration.

2.2 Proposed System

In order to solve the above problem of existing system, the team proposed to developed web-
based application to enhance or improve the Student Registration system, list of proposed
solutions is:

 Developed Student online registration system for CCI.

 Automating service given by the system to increase performance of the system
 Developed more security data.
 Make the system back up file to prevent loss of data.
 Make the system user friendly.
 The system must be able to serve up to one thousand users concurrently without crashing.
 The developed system will have to deal with large quantities of data and a large number
of users accessing the data at once.

2.2.1 Overview

To reduce the work overload and increase quality, the new system distributes the functions to
different sections based on the relevance they have to the job. Such work division highly relieves
the registrar from doing redundant and tiresome jobs daily. It should also have the accuracy of
information, timelines (both in being up-to-date and available when required), easy of processing
documents, easy of taking out/insert data/information from/to database (for Registered users),
easy of searching and viewing the search result that can be printed or saved for any system user
and providing good service for all. Hence to create such system we need to make the new
system to be Online System.

The proposed system controls the Online Registration system in Haramaya University College of
Computing and Informatics in a computerized way. This system stores information about
students from the existing registrar system if they are students of Haramaya University or not
and also store information about room, cost share registration details, instructors, Faculty and
Course Information. Additionally the system General overview is described below:

12
DEPARTMENT OF COMPUTER SCIENCE
  The system is developed for online registration system for regular students in HU CCI
only.
 The system contains three levels of users: Administrator, Users and Registrar.
 The system needs a system Administrator who control the system
 The system has staff who arrange status orders of registered students.
 The system has registered User (department Heads) who manages colleges database.
The system provides the following Facilities
1. Faculty, Department, Building, Room, Course, Instructor, Student information
registration

2. Prepare Schedule by effectively assigning :

1. Student - The users who register regularly to study their field
2. Course - The course that is taken by students in each semester.
3. Cost share account – The agreement between students and university which
paid after few years.
4. Instructors - The one who teaches the student
5. Room - The place where the student grasp the knowledge
3. Keeping records of Faculty, Department, Building, Room, Course, Instructor, Student
information and allows Update and Delete as needed by respected user.

4. Search for users:

 Students: to know is students are registered or not? And is student is fill the
required form during registration or not.

 Staff: To know is the staff is University employee or not. If not to delete it

otherwise the system can update the database.

5. The Administrator of the system can post announcement to anonymous system users
and the system users can give comment for each announcement.

6. The System will show the overall activities that is done in the system to the Admin by
using History Log function.

13
DEPARTMENT OF COMPUTER SCIENCE
 7. The system able to create account for the system users by providing all the required
information and update this information when it is needed, and this capability is given
to the Administrator of the system.

8. The system provide Backup mechanism, the administrator of the system can take a
backup of the systems database, and the system will save the backup in specified
folder with backup taking day and time.

9. The system should have to take feedback from users and also must improve from the
users comment.

Goals of the proposed system

The goal of the proposed system is to provide the following:

1. Giving new information in Student Online Registration System of Haramaya University
College of Computing and Informatics by making the system available at any time and
accessible from any ware since it’s online.
2. Change the manual system with the efficient and speedy new Online Registration system
to decrease staff members during registration time, since the system is developed with the
aim to overcome the drawbacks of manual system.
3. Prepare user friendly Student Online Registration System, since the retrieval and storing
of data is easy and fast and the system maintain the data efficiently, moreover the
graphical user interface is more attractive and easy to the user to deal with the system.
4. Prepare easy reports generating mechanism; the system should provide various reports in
accordance with requested information i.e. (about students, Course, and staff.
5. No or minimize use of paper work, the proposed system either does not require paper
work or very few paper works is required. All the data is feted into the computer
immediately and various reports can be generated through computers. Since all the data is
kept in a database no data of the campus can be destroyed. More over work becomes very
easy because there is no need to keep data on papers.
6. Computer operator control, since the system is computerized there will be effective,
efficient and onetime work.
7. Moreover storing and retrieving of information is easy.

14
DEPARTMENT OF COMPUTER SCIENCE
 2.2.2 Functional Requirement

Functional requirements capture the intended behavior of the system. This behavior may be
expressed as Services, tasks or functions the system is required to perform. Some the functional
requirements are the following.
The Student Online Registration System can be accessed by three users such as student,
Administrator and registrar.

2.2.2.1 Functional Requirement 1.1

ID: FR1

TITLE: User Registration-Student Online Registration System

DESC: A students/Staffs of Haramaya University who under College of Computing and

Informatics should be able to register to use SORS in everywhere at any time. In this system who
does not register cannot access the resources that used for education. The system should be
available 24/7.

RAT: In order for a students to register online.

DEP: None.

2.2.2.2 Functional Requirement 1.2

ID: FR2.

TITLE: User Single Sign-on - Student Online Registration System

DESC: The system checks if the entered student Id Number is valid.

Input: User enters student Id Number

Processing: The system checks if the student is valid and the Id Number is correct. The system
authorizes the student to access their record information and an staff to look up registration
orders if they entered valid student Id Number.

Output:

 System returns the user to the log in page if the student Id Number is invalid.
15
DEPARTMENT OF COMPUTER SCIENCE
  System provides user with options to access different records and perform different tasks
with the system if the student Id Number is correct.

2.2.2.2.1 Child Functional Requirement 1

Title: Identified staff login
When an employee is identified logging in, the system should take them to the Records
management screen.
2.2.2.2.2 Child Functional Requirement 2
Title: Identified Student login
When a Student is identified to have logged on to the system, it should take them to the welcome
page which has their name and timetable information for the current session.

RAT: In order for users to login to the main page.

DEP: FR1.

2.2.2.3 Functional Requirement 1.3

ID: FR3.

TITLE: View course Details

DESC: The new system will provide a report that clearly shows what courses the student has
completed and what courses they still need to take. This functionality will be important in saving
students time from looking at the whole timetable of their course.

Input: Student wants a report on the state of their degree

Output:-Shows the courses completed, the prerequisites and courses that are needed to complete
their degree.

RAT: In order for users to view course details.

DEP: FR1, FR2.

2.2.2.4 Functional Requirement 1.4

16
DEPARTMENT OF COMPUTER SCIENCE
ID: FR4.

TITLE: Users Profile Page- Student Online Registration System

DESC: A user should be able to access their own profile page. The system should be free for
users while they modify and view their profile page without any error. System should be able to
support users while they upload their profile picture.

RAT: In order for users to view and modify their profile page.

DEP: FR1, FR2.

2.2.2.5 Functional Requirement 1.5

ID: FR5.

TITLE: Student Cost Sharing Registration details

DESC: The system will display the student’s cost sharing account details. Student should be able
to register for cost sharing. The student should be able to view their cost sharing account from
their profile page. The system should not verify students who did not register for cost sharing.

Input: Student checks their cost sharing account details.

Output:-The system will output the student’s current cost sharing balance. Indicate that the
amount owed until payment is fulfilled and will provide detailed breakdown of all fees charged
by the University.

RAT: In order for a students to register for cost sharing

DEP: FR1, FR2, FR4.

2.2.2.6 Functional Requirement 1.6

ID: FR6.

TITLE: Posting New Information for students

DESC: The Administrator should be able to post new information during Registration date and
any other day about their college. An Administrator should be able to get the day of registration
from Registrar system to post on SORS.

17
DEPARTMENT OF COMPUTER SCIENCE
RAT: In order for a student’s post new Information for students like registration day.

DEP: FR1, FR2.

2.2.2.7 Functional Requirement 1.7

ID: FR7.

TITLE: Records Staff Interface

DESC: The system will allow the Records staffs to view registration orders submitted by the
students, and change the order’s status.

Input: Records staff changes the status of an order

Processing: The system will store the new status of the order and automatically send out an e-
mail to inform the student that the status of their order has changed with the name of the records
staff who changed the status.

Output:-An e-mail will notify the student that their order’s status has changed.

2.2.2.7.1 Child Functional Requirement 1

Title: Changing Order Status
To change an order’s status, the record’s staff needs to have selected that order by checking the
Tick box of the appropriate order.
2.2.2.7.2 Child Functional Requirement 2
Title: Order Information
For an order to be made it must have the appropriate information which is:-
 Student name
 Student Id
 Student’s e-mail
 Date
2.2.2.7.3 Child Functional Requirements 3
Title: Order Statuses
There are three possible status states for an order. These states are:-
 New
18
DEPARTMENT OF COMPUTER SCIENCE
  In-progress
 Complete
An order must have one of these statuses to be legal.

RAT: In order to change the order of registered students based on the given criteria above.

DEP: RF1, RF2.

2.2.2.8 Functional Requirement 1.8

ID: RF8.

TITLE: Manage Users

DESC: The system should be able to users such as deleting users, if users are graduated from
college, the system can delete that users from the Universities database or if users are Instructor
and that Instructor is not working in HU CCI the system can delete that instructor. The system
should also can add and modify users database.

Input: The checks users by their username if they are available in the college or not.

Processing: The system checks the user who is finished and who is not working for HU CCI
from staff, after that the system can delete the user who not working for CCI and students who
are graduated and also who fail the year exam.

Output: the system modify the database.

RAT: In order to delete users from the college.

DEP: None.

2.2.2.9 Functional Requirement 1.9

ID: FR9.

TITLE: Manage Registration

DESC: The Registrar should be able to manage the Registration Date. The Registration Date
after managed by the Registrar the system should be able open and close registration date for

19
DEPARTMENT OF COMPUTER SCIENCE
Users of Haramaya University College of Computing and Informatics Student Online
Registration System.

RAT: In order for the system to manage Registration Date

DEP: None.

2.2.2.10 Functional Requirement 1.10

ID: FR10.

TITLE: Manage University Database

DESC: The system should be able to manage database of the university by checking system
users and also in this system the Registrar may modify or add another course for students. The
system should have to give course description for college based on the given curriculum about
new courses and the Registrar should give all list of college students in order to register regular
students.

RAT: In order for the Registrar to manage University Database.

DEP: None.

2.2.2.11 Functional Requirement 1.11

ID: FR11.

TITLE: Users Logout

DESC: A user can be log out from the SORS after he/she finished their job. The system should
be able logout, if a user want to logout.

RAT: In order for user to be able log out from the system.

DEP: FR1, FR2.

2.2.3 Non Functional Requirement

2.2.3.1 Non-Functional Requirement 1 – Consistent Uptime

20
DEPARTMENT OF COMPUTER SCIENCE
The new system will be able to stay up and running at least 99% of the time. Any downtime
would be due to maintenance or upgrades.

2.2.3.2 Non-Functional Requirement 2 – Load and Concurrency

The system must be able to serve up to one thousand users concurrently without crashing.

2.2.3.3 Non- Functional Requirement 3 – Familiar Interface

They have no existing but students of CCI may become familiar with our system because they
are students of technology.

2.2.3.4 Non-Functional Requirement 4 –Real-time Feedback

The new registration system should display the student’s timetable and show the changes made
to it in real-time as the student adds and drops courses.

2.2.3.5 Non-Functional Requirement 5-Focused Layout

The new system will reduce the potential for confusion by having a focused layout. This means
that it will display information that is relevant to the current task and conversely, leave out
irrelevant information.

2.2.3.6 Non-Functional Requirement 6 – Web Accessibility

The new system will be compatible with screen readers to assist the visually impaired. This
means that screen readers should interpret the displayed text into speech and should not output
anything that does not correspond to displayed text.

2.2.3.7 Non-Functional Requirement 7 – Dealing with large quantities

of data

The developed system will have to deal with large quantities of data and a large number of users
accessing the data at once.

2.2.3.8 Non-Functional Requirement 8 – Effective Recovery

21
DEPARTMENT OF COMPUTER SCIENCE
The system must effectively recover from a crash within ten minutes. Effective recovery means
that the data is still in a consistent state when the system returns.

2.3 Feasibility Study

The aim of feasibility study activity is to determine whether it would be financially and
technically feasible to develop the system or not. A feasibility study is comes out form following
different aspects:-

2.3.1 Economical Feasibility

The purpose of assessing economic feasibility is to identify the financial benefit and cost
association with the development project, economic feasibility is referred to us cost benefit
analysis. The costs and benefits associated with the proposed system compared and the
project is economically feasible only if tangible or intangible benefits outweigh costs.

Tangible benefits
Our system trim down any costs for paper and for other different writing materials.

Intangible benefits

The proposed system encompass many intangible benefits that revolve around mental
satisfaction of users. These are:

 Satisfies the student and the college staff workers in the way that they trust the system is
secure and accurate on giving service.

 Knowledge gain by project developer.

 Increasing the competitiveness of the developers
 Improving the morale of our team.

2.3.2 Technical Feasibility

Technical feasibility can arise two questions:

 Do we have skilled man power to develop the project,

 Do we have enough technology
22
DEPARTMENT OF COMPUTER SCIENCE
In designing the project we already have qualified individuals and enough technologies so, this
project is technically feasible.

2.3.3 Operational Feasibility

The purpose of Operational feasibility can ask, is the system solving the problem after the
proposed system is implemented for the user? YES, because, the system is allow for
Administrator to notice Registration Information and other new information about our college in
automated manner rather than manual way. So, this project is operationally feasible.

Chapter Three

3. System Design

3.1 System Model

3.1.1 Use Case Model for SORS

23
DEPARTMENT OF COMPUTER SCIENCE
Figure 3: Use Case Diagram for Student Online Registration System

Manage Registration use case detail

This use case describes the components of manage users which enables the registrar to open and close registration
date for the proposed system.

24
DEPARTMENT OF COMPUTER SCIENCE
Manage Users use case detail

This use case describes the components of manage users which enables the registrar to add, update, and delete
users for the proposed system.

25
DEPARTMENT OF COMPUTER SCIENCE
Manage University Database Use Case detail

This use case describes the components of manage users which enables the registrar to add, update, and delete
university based on different category for the proposed system.

26
DEPARTMENT OF COMPUTER SCIENCE
 3.1.1.1 User Registration

Use Case Name Registration

Use Case ID FR1
Brief description The user who have the unique University ID Number can register to
the system as a student or as staff if he/she is member of CCI
Actor Administrator (Staff) and Student
Pre-condition The Users should have Id Number that placed him/her under CCI.

Post Condition If the users registered to the system he/she should be able to login to
the system (SORS).
Basic Course Of Action (BCA)
This use case starts when the User accesses the system feature that enables him/her to create an
account by entering information that is saved in the User’s account.
1. The system displays user Account Form.
2. User enters the required user account information on the form.
3. The system verifies values entered are valid or not.
4. System saves the new account in the database after User Click the save button.
5. The system notifies success message.
The use case is end when User clicks the ok button.
Alternate Flows
Title Description
User inserts Invalid User 1. The system prompts invalid user account
Account Information 2. system prompts user to reenter valid account
3. use case continues with BCA 2
user inserts existed account 1. system prompts error message
2. System display message that the account is already exist.
3. use case ends
Table 1: Registration Use case for SORS

27
DEPARTMENT OF COMPUTER SCIENCE
 3.1.1.2 User Login

Use Case Name Login to system

Use Case ID FR2
Brief description User who have privilege to access the system’s functionalities should
be able to login each time he/she wants to use the system
Actor Administrator and Student
Pre-condition The user must to be registered to user Account.
Post Condition If the system is authenticated the User logged into the system and the
system displays all features available for the role associated to the
user.
Basic Course Of Action (BCA)
This use case starts when the User accesses the login in feature of the system by selecting his
privilege.
1. The system displays a login form
2. The user enters his/her username and password
3. The user clicks login button
4. The system validates the entered information.
5. The system takes the user to his/her interface.
6. The use case ends.
Alternate Flows
Title Description
4.1 User forgot password 1. system display invalid password
2. The system ask the user to enter user name.
3. system ask the user to answer his security question
4. System displays his password if his answer is correct.
5. use case continues with BCA 2
4.2User fills invalid 1. The system Displays error message.
username and/or password 2. The system prompts the user to reenter the valid information.
3. Use case continues with BCA 2.
Table 2: User Login Use case for SORS

28
DEPARTMENT OF COMPUTER SCIENCE
 3.1.1.3 View Course Details

Use Case Name View Course Details

Use Case ID FR3
Brief description Student who have privilege to access the system’s functionalities
should be able to view Course description each time he/she wants to
use the system.
Actor Student
Pre-condition The Student must to be login first to the user Account.
Post Condition Student should be able to get resources about the course he/she wanted
to study or lecture if user is Instructor.
Basic Course Of Action (BCA)
This use case starts when the student login to the system
1. The system displays a login form
2. The user enters his/her user and password
3. The user clicks login button
4. The system validates the entered information.
5. The system takes the user to his/her interface.
6. The user view course details.
7. The use case ends.
Alternate Flows
Title Description
student search error course The system display error message for student course not available
to the system The system display course details if student insert valid course
otherwise the system continues to display error message
use case continues with BCA 2
Table 3: View Course Details Use case Description

29
DEPARTMENT OF COMPUTER SCIENCE
 3.1.1.4 User Profile Page

Use Case Name Profile

Use Case ID FR4
Brief description Any users who authenticated to the system can manage its own profile
page for example the user can edit his/her profile page and also he can
view his/her own profile page.
Actor Student and Staff (Administrator)

Pre-condition The User must to be login first to the system.

Post Condition Users should be able to get available features from the student online
registration system and they can modify their profile picture.
Basic Course Of Action (BCA)
This use case starts when the user wants to use their profile
1. The system displays home page after login
2. The user’s clicks on profile page link to view his/her profile.
3. The system takes the user to the profile page
4. The user can modify his/her profile page.
5. The use case ends.
Alternate Flows
Title Description
The user modify his/her The system display error message for user.
profile with invalid The system display invalid or valid messages to users to correct and
information. edit his/her profile
use case continues with BCA 2
Table 4: View User profile Use case Description

3.1.1.5 View Cost Sharing Details

Use Case Name View Cost Sharing Details

Use Case ID FR5
Brief description Student who have privilege to access the system’s functionalities

30
DEPARTMENT OF COMPUTER SCIENCE
 should be able to view Cost sharing details each time he/she wants to
use the system. In this system the student must to be registered for cost
sharing before going to access any other features from the system
otherwise he/she may not registered on the university database.
Actor Student
Pre-condition The Student must to be login first to the user Account and going to
profile page.
Post Condition Student should be able to see the successfully message from the
interface after cost sharing registration.
Basic Course Of Action (BCA)
This use case starts when the student login to the system
1. The system displays home page after login
2. The student clicks on profile page link to register for cost sharing details from his/her
profile.
3. The system takes the student to the cost sharing page
4. The system validates the entered information for cost sharing registration.
5. The system gives successful message for student for valid information.
6. The use case ends.
Alternate Flows
Title Description
Student enters invalid The system display error message for student entered information is
information to the system incorrect
for cost sharing during The system display cost sharing details if student insert valid
registration. information
use case continues with BCA 2
Table 5: View Cost Sharing Use case Description

31
DEPARTMENT OF COMPUTER SCIENCE
 3.1.1.6 New Information for Students

Use Case Name New Information for Students

Use Case ID FR6
Brief description The Administrator should be able to post new information during
Registration date and any other day about their college. An
Administrator should be able to get the day of registration from
Registrar system to post on SORS.
Actor Administrator
Pre-condition Administrator should be able login to the system to post information.

Post Condition Information should be accessed by all users.

Basic Course Of Action (BCA)
This use case starts when the Administrator login to the system
1. The system displays home page after login
2. The Administrator clicks news page to post new information for college.
3. The system takes the Administrator to the news page
4. The Administrator posts the information like registration date and deadline.
5. The system successful message for posted information for Administrator.
6. The use case ends.
Table 6: New Information for Students Use case Description

3.1.1.7 Records Staff Interface

Use Case Name Records Staff Interface

Use Case ID FR7
Brief description The system will allow the Records staffs to view registration orders
submitted by the students, and change the order’s status.
Actor Administrator or staff
Pre-condition The Administrator must to be login to the system first

32
DEPARTMENT OF COMPUTER SCIENCE
 Post Condition The administrator should be able to change order of status and should
tell to registered students who change the orders.
Basic Course Of Action (BCA)
This use case starts when the Administrator login to the system
1. The system displays home page after login
2. The Administrator clicks on change registration status link to order the registered
students.
3. The system takes the Administrator to the change registration status page
4. The Administrator changes and informs students who change their orders through their
email.
5. The system gives successful message for Administrator the status is changed.
6. The use case ends.
Table 7: Records Staff Interface Use case Description

3.1.1.8 Manage Users

Use Case Name Manage Users

Use Case ID FR8
Brief description The system should be able to users such as deleting users, if users are
graduated from college, the system can delete that users from the
Universities database or if users are Instructor and that Instructor is not
working in HU CCI the system can delete that instructor. The system
should also can add and modify user’s database.
Actor Registrar
Pre-condition None.
Post Condition The Registrar should have to add, delete, and modify users.
Table 8: Manage Users Use case Description

33
DEPARTMENT OF COMPUTER SCIENCE
 3.1.1.9 Manage Registration

Use Case Name Manage Registration

Use Case ID FR9
Brief description The Registrar should be able to manage the Registration Date. The
Registration Date after managed by the Registrar the system should be
able open and close registration date for Users of Haramaya
University College of Computing and Informatics Student Online
Registration System.

Actor Registrar
Pre-condition None.
Post Condition The Registrar should have to open and close registration date.
Table 9: Manage Registration Use case Description

3.1.1.10 Manage University Database

Use Case Name Manage University Database.

Use Case ID FR10
Brief description The system should be able to manage database of the university by
checking system users and also in this system the Registrar may
modify or add another course for students. The system should have to
give course description for college based on the given curriculum
about new courses and the Registrar should give all list of college
students in order to register regular students.

Actor Registrar
Pre-condition None.
Post Condition The Registrar should have to manage university database.
Table 10: Manage University Database Use case Description

34
DEPARTMENT OF COMPUTER SCIENCE
 3.1.1.11 Users Log out

Use Case Name Users Log out

Use Case ID FR11
Brief description A user can be log out from the SORS after he/she finished their job.
The system should be able logout, if a user want to logout.

Actor Registrar
Pre-condition User must be logged in to the system.

Post Condition The system should be free to enter any user who had login passwords
and username again.

Table 11: Users Log out Use case Description

3.1.2 Class and Object Diagram

3.1.2.1 Class Diagram

o Class diagram is a component of unified modeling language that shows level of

association among classes and objects. It also shows multiplicity associations; how many
objects participate on the association. Class diagram shows the role of objects or classes
and aggregations. Mostly generalization specialization can be shown in class diagram.
Generalization specialization means a relationship between a general class and one or
more specialized classes.
o In design, we model classes to represent the static structure of how the system will be
built. Class model in design is that focus on the solution domain. I have done all the
necessary modification that will cover the way toward the implementation of the system.
o The Class Diagram of the proposed system of Student Online registration system for
Haramaya University College of Computing and Informatics is shown below.

35
DEPARTMENT OF COMPUTER SCIENCE
 Figure 4 Class diagram of Student Online Registration System
3.1.2.2 Object Diagram

An object diagram may be considered a special case of a class diagram. Object diagrams use a
subset of the elements of a class diagram in order to emphasize the relationship between
instances of classes at some point in time. They are useful in understanding class diagrams. They
don’t show anything architecturally different to class diagrams, but reflect multiplicity and roles.
The following diagram shows the differences in appearance between a class element and an
object element. Note that the class element consists of three parts, being divided into name,
attribute and operation compartments; by default, object elements don’t have compartments. The
display of names is also different: object names are underlined and may show the name of the
classifier from which the object is instantiated.

36
DEPARTMENT OF COMPUTER SCIENCE
 Figure 5 Object Diagram for Student Online Registration System

3.1.3 Dynamic Model

The dynamic model of our project is described as the following one.

3.1.3.1 Sequence Diagram

37
DEPARTMENT OF COMPUTER SCIENCE
Sequence diagrams are used to model the logic of usage scenarios or the description of the
potential way the system used. Sequence diagrams are a great way to validate and flesh out the
logic of use case scenarios and to document the design of the system.

Haramaya University College of Computing and Informatics Student Online Registration System
has the following sequence diagrams

3.1.3.1.1 Sequence Diagram for Registration

Registration sequence diagram shows a sequence of activities that happen when user is going to
register to the system.

Figure 6 Sequence Diagram for Registration in SORS.

38
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.1.2 Sequence Diagram for Login

Login sequence diagram shows a sequence of activities that happen when user login in to the
system.

Figure 7 Sequence Diagram for Login in SORS

39
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.1.3 Sequence Diagram for New Information in SORS

Figure 8 Sequence Diagram for New Information in SORS

40
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.1.4 Sequence Diagram for Viewing Course Details

Figure 9 Sequence Diagram for Viewing Course Details in SORS

41
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.1.5 Sequence Diagram for Viewing Cost Share Details

Figure 10 Sequence Diagram for Viewing Cost sharing Account Details in SORS

42
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.1.6 Sequence Diagram for Records Staff Interface

Figure 11 Sequence Diagram for Records Staff Interface in SORS

43
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.1.6 Sequence Diagram for Manage Users

Figure 12 Sequence Diagram for Manage Users in SORS

3.1.3.2 Activity Diagram

Activity diagram is used to document the logic of a single operation/method, a single use case or
the flow of logic of a business process. It is equivalent to flowchart and data flow diagram from s
structured development.

44
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.2.1 Registration Activity Diagram

Figure 13 Registration Activity Diagram for SORS

45
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.2.2 Login Activity Diagram

Figure 14 Login Activity Diagram

46
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.2.3 New Information Activity Diagram

Figure 15 Post New Information for students Activity Diagram

47
DEPARTMENT OF COMPUTER SCIENCE
Figure 16 Viewing Course Details Activity Diagram

3.1.3.3 State Chart Diagram

State chart diagram is used for modeling the dynamic aspects of systems if focuses on
identifying the behavior within our system, behavior specified to the instances of a single class.

It is similar to activity diagram. Both activity and state chart diagrams are useful in modeling the
lifetime of an object. However, activity diagram shows flow of control from activity to activity;
whereas state chart diagram shows flow of control from state to state.

48
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.3.1 State chart Diagram for Registration in SORS

Figure 12 State chart Diagram for Registration in SORS

49
DEPARTMENT OF COMPUTER SCIENCE
 3.1.3.3.2 State chart Diagram for login in SORS

Figure 13 state chart login diagram

3.2 Data Dictionary

Class Name Attribute and return method Description

Description

User Name String

College String

50
DEPARTMENT OF COMPUTER SCIENCE
 Department String

Date String

Age int

Sex String

Nationality String

Region String

Zone String

Username String

Password String

Register() Allow users to be

registered

View() Allow users to

view features of
the system

Search() Allow users to

search course

Modify() Allow users to

modify their
profile and other
things.

Student Id int

Class_year String

Semester String

51
DEPARTMENT OF COMPUTER SCIENCE
 Advisor_name String

View_cost_share() Allows students to

view their cost
share account
details

View_profile() Allows students to

view their profile
page

View_course() Allows students to

views their course
details in each
time he/she
entered to the
system

Administrator/staff Ssn int

Qualification String

Major_course String

postInfo() Allows staff to

announce new
information from
college using
online

Changestatus() Allows
administrator to
change order of
registered students
and tell them who

52
DEPARTMENT OF COMPUTER SCIENCE
 change the order
through email

Managestaff() Allows
staff/administrator
to manage college
employees

Registrar Manage_users() Allow the registrar

to manage users

Manage_uni_db() Allow the registrar

to manage the
database of the
Haramaya
University as a
whole

Manage_registration( Allows the

) registrar to
manage opening
and closing of
registration date

Course Course_Code String

Course_title String

Course_crhr String

Course_ECTS String

Course_Instructor String

Add_course() Allows the users

53
DEPARTMENT OF COMPUTER SCIENCE
 to add a course

Search_course() Allows a users to

search a course
he/she wanted to
study

View_course() Allows users to

view the course
details

Table 12 data dictionary

3.3 User Interface Design

User interface is the part of application or system software that enable user of the system to
interact with it. It may contain input boxes, message boxes and different controls. It also contains
some help page that supports the user to simply interact with the system. The system that we
proposed to submit has different forms. These are mentioned as follows:

The home page user interface, this home page form is visible to any user of the system.

54
DEPARTMENT OF COMPUTER SCIENCE
Figure 14 Haramaya University CCI Student Online Registration System Home page

55
DEPARTMENT OF COMPUTER SCIENCE
Figure 15 HU CCI Student Online Registration System Departments Home Page

Figure 16 HU CCI SORS First Year computer science Registration page

56
DEPARTMENT OF COMPUTER SCIENCE
Figure 17 HU CCI users Login Page

57
DEPARTMENT OF COMPUTER SCIENCE
 Chapter Four

4. System Design

4.1 Introduction

In the chapter one we have seen statement of the problem, objective of the system,
methodologies for Student HU CCI student online registration system. Next in chapter
two we have seen, proposed system, feasibility study, functional requirements and non-
functional requirements and In chapter three we have seen about system Models deeply
with UML diagram, data dictionary and user interface of our system. In this chapter we
are going to describe overview of the system design, goal of the system, deployment
diagrams, persistent data management, access control and security, global control flow
and boundary condition.

4.1.1 Overview of system Design

The Student Online Registration system of Haramaya University College of Computing and
Informatics is going to replace the manual way which our college had before we develop the
computerized system. This system stores information about students from the existing registrar
system if they are students of Haramaya University or not and also store information about room,
cost share registration details, instructors, Faculty and Course Information. In this system
students should have Valid Id Number from the university to be registered. In this proposed
system students who want to ask question, can ask every day in each time he/she entered to the
system. In addition our system has help page for new students up to they familiar with our
system.

4.1.2 Design Goal of the system

Design goals describe the qualities of the system that developers should optimize. Such goals are
normally derived from the non-functional requirements of the system.
Design goals are grouped into 8 categories. These are
Consistent Uptime

58
DEPARTMENT OF COMPUTER SCIENCE
The new system will be able to stay up and running at least 99% of the time. Any downtime
would be due to maintenance or upgrades.

Load and Concurrency

The system must be able to serve up to one thousand users concurrently without crashing.

Familiar Interface

They have no existing but students of CCI may become familiar with our system because they
are students of technology.

Real-time Feedback

The new registration system should display the student’s timetable and show the changes made
to it in real-time as the student adds and drops courses.

Focused Layout

The new system will reduce the potential for confusion by having a focused layout. This means
that it will display information that is relevant to the current task and conversely, leave out
irrelevant information.

Web Accessibility

The new system will be compatible with screen readers to assist the visually impaired. This
means that screen readers should interpret the displayed text into speech and should not output
anything that does not correspond to displayed text.

Dealing with large quantities of data

The developed system will have to deal with large quantities of data and a large number of users
accessing the data at once.

Effective Recovery

The system must effectively recover from a crash within ten minutes. Effective recovery means
that the data is still in a consistent state when the system returns.

4.2 Deployment Diagram

59
DEPARTMENT OF COMPUTER SCIENCE
 A UML deployment diagram depicts a static view of the run time configuration of processing
nodes and component that run on those nodes. Deployment diagram show how the software
components process and objects are deployed into physical architecture of the system. It shows
the configuration of the hardware units or communication device and how this software
components and objects redistributed across the unit and also the middle ware used to connect
the desperate machine one another. The deployment diagram of the system describes as follows.

Figure 18 Deployment Diagram for Our system

4.3 Current Software Architecture

Haramaya university uses manually Student Registration from the establishment of the
organization till know. All this registration is done by the Staff. College of computing and
Informatics managing Instructors and register students are done in Microsoft access it uses this
application in order to use the table, then after printing all the document he/she distributed for
each department, and stored in a documented catalog form in order to keep all these college
document files.

4.4 Proposed Software Architecture

60
DEPARTMENT OF COMPUTER SCIENCE
The proposed system controls the Online Registration system in Haramaya University College of
Computing and Informatics in a computerized way. This system stores information about
students from the existing registrar system if they are students of Haramaya University or not
and also store information about room, cost share registration details, instructors, Faculty and
Course Information.

The system is a web based application. The website will be hosted on a web server, where users
are able to access it from a PC/laptop using a browser. This allows for the system to be
accessible from different operating system and devices but it will also easily manageable. It will
also decrease the staff effort when registering students in each semester by allowing students
online to register in each semester and fill the other information, and then the system add the
confirm when the students press register button.

Figure 19 Proposed System Architecture Diagram

4.5 Hardware/Software Mapping

61
DEPARTMENT OF COMPUTER SCIENCE
Hardware/software mapping raise the questions, what is the hardware configuration of the
system, which services are realized using existing software components and how are these
components encapsulated. Addressing hardware/software mapping issues often leads to the
definition of additional subsystems dedicated to moving data from one node to another, dealing
with concurrency, and reliability issues. Off-the-shelf components enable developers to realize
complex services more economically. User interface packages and database management
systems are prime examples of off-the-shelf components. Components, however, should be
encapsulated to minimize dependencies on a particular component: A competing vendor may
come up with a better component.

4.6 Persistent Data Management

Persistent data management deals with how the persistent data (file, database, etc) are stored and
managed and it outlives a single execution of the system. Information related to programs basic
information, and the registered students and other related information are persistent data and
hence stored on a database management system. This allows all the programs that operate on the
registration system data to do consistently. Moreover, storing data in a database enables the
system to perform complex queries on a large data set .The Universities register programs every
year in thousands per year level. For complex queries over attributes and large dataset Microsoft
SQL Server is implemented, which is a Relational Database Management System.

62
DEPARTMENT OF COMPUTER SCIENCE
Figure 20 Persistent Data Modelling
4.7 Access Control and Security

While entering data or in requesting the performance of certain functions error may occur which
could result in improper use of the system.
Access Controls provide ways to:-
Insure that only the authorized user access the system.
Validate the data for accuracy.
Guarantee that transactions are acceptable.
Determine that weather any necessary data have been omitted.
4.8 Global Flow Control

To make the system standardize the proposed system includes procedural driven and event
driven control policy.

A. Procedural driven control policy: in this control policy the user makes a request to the
system and waits for the system response. For instance, the user wants login to the
system; the user clicks the login link and waits the system to display the login form. After

63
DEPARTMENT OF COMPUTER SCIENCE
 this also the user inserts the username and password and waits the system response (error
message or successful).
B. Event driven Control Policy: in this control flow it shows what is going on happen to
the system if we apply an external event. The control flow waits for external events, after
the events occurs the system transmitted to the appropriate object based on the associated
information. For instance, by the user request the system displays the login page. After
this the system waits for an event the user will apply. After some delay the user click on
login button (in this case the click_on_button event is happened), so the system
dispatched to account object.
4.9 Boundary Condition

There are three conditions happens on the system.

Start HU CCI SORS – In the System Actors (student, department or administrator) will start up
the system/ use case.

Exit HU CCI SORS – after an actor (s) initiate (s) the system and doing his/her activity saving
use case will be the Exit HU CCI SORS use case.

Failure – system error (internal error like database connectivity) & external error like power
supply

64
DEPARTMENT OF COMPUTER SCIENCE
Figure 21 Boundary Condition Diagram

65
DEPARTMENT OF COMPUTER SCIENCE