Documentation

HARAMBEE UNIVERSITY COLLEGE ONLINE REGISTRATION SYSYTEM
Chapter one
1. Introduction
Online registration system allows student’s, through internet, to register, drop and add courses
within the registration period. The online student registration system will eliminate all the manual
intervention & increase the speed of whole process. System will allow student to fill the form
online, system has inbuilt validation system to validate the entered data. After successful
submission, system will give unique registration number for each student. Student can login into
the system by using username and password. Online student registration system (software) is an
easy way to use, responsive and flexible alternative to manual, paper-based student registration. It
will also allow online submission of student application, retrieving, and recording and update
student’s data. Online student registration system also increases the number of students (users) and
makes managing large amounts of information a snap (without loose of the information).
1.1. Background of the organization
1.2. The College
1.1. Location of the College
The main of Harambee College is found in Oromia Regional State, Adama City Kebele 12. The
college has its branch in Arsi Zone in Abomsa town, which was functional since1997EC.
1.2. Establishment of the College
Harambee College was founded in 2002 G.C. with the aim of enhancing the development of
education sector. The College was primarily founded as center for learning foreign languages
especially English language in Adama on Nur Piazza Building. The institution launched teacher-
training program for primary school in the level of 10+1 and 10+3 in 2003 and 2004 respectively.
However, due to shortage of classrooms and inconveniency of the area of the training, the college
was shifted its location to Kebele 11 to train more number of trainees in 2004. With the transfer of
its location, accompanied by its commitment to quality of education and training, Harambee
College has got great demand and become one of the famous and competent colleges in Adama.
Under this condition, the number of trainees was increased and forced the college to expand it’s to
other areas Dembela in kebele 10 in the year 2005. Besides, the demand for the college was
Page
expanded to Arsi zone Abomsa town which was functional in the same year. Beyond the teacher
education and training, the institute expanded its service to TVET in the fields of accounting, law,
secretarial science and office management, human resource management, ICT and clinical
nursing education. Moreover, the college behind expanding its service to the TVET in the year
2010 due to inconvenience of management and inefficiency of utilization of human and other
resources the two as of the college in Adama were merged into one and shifted its current location
to kebele 12 building.
The Ministry of Education Higher Education Relevance and Quality Agency has accredited the
college in the fields of Management Information Systems, Accounting and B. Administration with
ref 01/7-1/510/05 on 24 October 2012. Moreover, the same agency accredited the College in the
fields of Accounting, Management and Economics in distance mode. Accordingly, in its recently
established in Adama Town, the college accommodates large number of trainees with necessary
educational and training inputs with which it provides education and training for the degree
program in the fields of accounting, management information systems and business
administration in both the regular and extension programs since then.
1.3. Infrastructure of the College
 The college has classrooms, IT laboratories, and demonstration rooms for clinical
nursing and veterinary Science
 The college has water service, electricity, telephone and broad band and wireless
internet
 Services
 The college has library, E-library, office and other facilities.
 The college has a separate and adjacent compound for CDE.
 A 4 tier building under construction
1.4. Statement of Problem

Slow of performance
Less transfer Information
 Input
 Output
Page
Not arrangement of Stored data

Slow registration speed
Lack of economy
The office consumes manpower, time and resources because of manual service of
student registration system
Not efficiency
Give as not active Service
Haven’t Control and Security
Reports are not processed on time
Redundant flow of student information(repetition
1.5. Purpose of the project for organization

 Save time
 Free Online registration
 Secure online registration processing 24/7 hours per day services
 Centralized data management
 Improve event efficiency
 Detailed reporting etc.
For Students (participants)
 Save time
 Improved customer support
 Receive automated confirmation receipt
 Access to discounts
 Enter multiple and team registrations
1.5.1. Objective
1.5.2. General objectives
 The General objective of our project is to change the current manual system in to
computerized one.
1.5.3. Specific objectives
Page
The particular activity that the system will do at the end of its successes full complementation.
The system will do the following-
 Register the student’s information online
 Search the student information
 Update the student information
 delete un necessary information
 View student result or grade
1.6. Feasibility study
A feasibility study is an analysis of how successfully a project can be completed, for factors that
affect it such as economic, technological, legal and scheduling factors. Project managers use
feasibility studies to determine potential positive and negative outcomes of a project before
investing a considerable amount of time and money into it.
1.6.1. Technical feasibility
Technical Feasibility - assessment is centered on the technical resources available to the

organization. It helps organizations asses if the technical resources meet capacity and whether the
technical team is capable of converting the ideas into working systems. Technical feasibility also
involves evaluation of the hardware and the software requirements of the proposed system.
1.6.1. Operational
The workers of Online Student Registration System are somewhat computer literate. This means
once we have trained how to use the software or the system we can easily use it without any doubt.
Since this system is all about entering data and modifying data by following procedure given it is
not as such difficult for computer literate person. And we will provide for them the manual
documentation about the software.
1.6.2. Economic feasibility

Cost benefit analysis: The system which we are going to develop will have economic benefit. That
economic benefit may be tangible or intangible.
Tangible benefit: This means the concrete benefit that can be expressed in terms of dollars or birr.
So the system proposed to develop will decrease a lot of birr that was expensive to buy the hard
Page
copy document material such as paper, pencil, rubber, and so on. Also reduce the loss of data that
means if it reduces the loss of data it also reduces the cost of replacing the lost data. For example
if the university college have 100 employees to handle these amount data there must be many
people to manage the data and a lot of paper, pen ,and pencil will be bought. But after the system
developed the data can be managed with one person and in one computer in very short time.
 Intangible benefit: Those benefits that cannot be expressed in terms of birr or dollar. Intangible
benefit that the system will give is the following:
1. Give more readable, reliable, easily manageable, and database which
contains all employees track.
2. The proper and ordered files of employees which has stability means
which is not easily lost.
Cost of the project: The project we are planning to do needs some software and hard ware. And
also require other material such as paper, pen, pencil that are used when gathering the information,
design our system manually and so on.
We break the needed costs into:
o Recurrent cost: The cost needed after the system is developed for different factors. Such
factors include maintenance, buying computers on which the software is work, the cost
needed to employ the administrator and etc.
 Resource plan
Budget for activity
1. Hardware specification quantity Unit price Total price

2. paper A4 200 0.50 100
3. CD-ROM prince 4 25 100
4. Flash SanDisk 2 120 240
5. PC HP 1 11,00 11,000
6. Data collection 2000 2000
7. Data or system analysis 2500 2500
8. System design 3000 3000
9. Database designing 2000 2000
10. Coding and testing 2000 1000
Page
11. Implementation 1000 1000

12 Contingency 3000
SUM 23,940 birr
Table 1.1 Resource plan
Total budget spent for this project development: =23,940 Birr
1.6.3. Scope and limitation

1.7. Scope of the project
The office of registrar has many duties. Hence dealing with automation of service it provides
doesn’t go with the short time that we have. So we limit ourselves to the following areas.
 To view their grade
 Generating necessary information
 All department heads to Enabling send students mark to registrar
 Delete un necessary Student registration
 Student admission
 Readmission
 Withdrawal/drop out
 Add/drop courses
 Prepare student copy
 Adding, Updating and searching student information
 Enabling students information
Our system does not include the following systems

 Student placement
 Class scheduling
 Exam scheduling
 Payment of fees
 Student admission and readmission
 Withdrawal or drop out
 Prepare student copy and Add/ drop course to pass works another researcher
Page
1.7.1. Limitation of the project

The limitation of the proposed system is:
The system depends on internet connection
If there is no power means our system is not accessible
The system does not cover the computation of student’s grade
Without students control
Not accepting any online payments
customers out of the destination control
The system is limited only to English language and not support local languages.
1.7.2. Significance of the project

For users:-
 To register student within a short period of time.
 To get timely information.
 To save their time and money.
 To access accurate and fast information
 An easy way of registration
 To update the student files automatically
 Minimizing loose of data
 Secured means of storing files
 Improved planning and management
 Minimizing data redundancy
 Supplies timely information for the students
 Accelerating user requirement and benefits
 Enabling all department heads to send students mark to registrar
For HUCR office:-
 To easily retrieve user information.

 To improve management system.
 To solve problem of manual work.
 To save time and money and manpower
Page
1.7.3. Methodology
The methodology is very important to insure that the new system .would give benefits to the school.
Before implementation and design requirement analysis is the first step. So, this data collection
method is a precondition for requirement analysis. Knowing this fact we have collected information
from the existing system and used it for proposed system. There are many methods used to collect
data. Among them we have used three methods:-
 Interview
Interview is a powerful tool for data gathering since it allows the interviewer to probe and
clarify a number of issues face to face interview is used to interact with the registrar and the
users of the proposed system to obtain the required for the database management system.
 Document review
Document review was important data gathering technique because of this method revise resent
documents, sample documents etc
 Observation
This is by observing:-
Written documents and procedural manuals
Registration form
Grade recording mechanism and
Other activities
1.8. Fact finding methodology
Fact finding is process of collection of data and information based on techniques which contain
sampling of existing documents, research, observation, questionnaires, interviews, prototyping and
joint requirements planning.
1.8.1. Software development methodology

Software methodologies are concerned with the process of creating software this includes:-
Page
Re Requirement gathering
& analysis
Sy System design
Iu Implementation
Te Testing
D Deployment of system
Maintenance
Page
Figure 1.1. Software development methodology

1.8.2. Development tools
The resources required for this new project to success is may be categorized into two ways,
hardware specification and software specification.
Page
 Hardware and Software specifications
Page
Processing power  64 bit operating system

 Intel(R) core™i3 CPU [email protected]
Memory & Secondary  RAM: 4GB MB and above

storage  500GB Hard-disk: and swap space (if RAM is
insufficient).
Peripherals  CD-ROM drives

 Network devices
 Printer
Hardware  Keyboard
 Flash or CD-ROM
 Disk/memory
Operating system windows 7
Documentation and  Microsoft office word 2007

PPT  Microsoft office power point 2007
Web browser Mozilla Firefox
Programming languages  My-SQL

and their application  visual studio 10
 PHP
 Enterprise architect
 Microsoft Office Access 2007
Page
Table 1-2: Hardware and Software specifications
 Spiral Development
Software specifications are the programming languages that are used for data base designing,
testing, coding, and implementing the project. The language I will use to test and to implement this
new project may involve the following:-
 MySQL :-for database to create table, query

 visual studio:-visual studio to interface design
 HTML-[Hyper Text Markup Language]
 PHP designer:-program part and connect to MYSQL
 Microsoft Office Access 2007:- program part and connect to DBMS
 Java script:-to design interface and coding or programming
 Redraw-Max:-for use case diagram and activate, deployment, and sequence
 Enterprise architecture:-for use case diagram and activate, deployment, and sequence
1.8.3. Test plan
Test plan: A document describing the scope, approach, resources and schedule of intended test
activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will
do each task, degree of tester independence, the test environment, the test design techniques and
entry and exit criteria to be used, and the rationale for their choice, and any risks requiring
contingency planning.
1.9. Unite test
Unit testing is a level of software testing where individual units/ components of software are
tested. The purpose is to validate that each unit of the software performs as designed.
Acceptance
testing
System testing
Integration testing
Page
Unit testing
Figure 1.2 Unit test
A unit is the smallest testable part of software. It usually has one or a few inputs and usually a single
output. In procedural programming a unit may be an individual program, function, procedure, etc. In
object-oriented programming, the smallest unit is a method, which may belong to a base/ super class,
abstract class or derived/ child class. (Some treat a module of an application as a unit. This is to be
discouraged as there will probably be many individual units within that module)
1.9.1. Integration test
Integration Testing is a level of software testing where individual units are combined and tested as
a group. The purpose of this level of testing is to expose faults in the interaction between integrated
units. Test drivers and test stubs are used to assist in Integration Testing.
1.9.2. Overview of project phase
1.10. Schedule
Table 1-3 schedules
Page
1.10.1. Team composition
The five members of the group will have the following responsibilities:
Project title Name Responsibility Email Phone number
Online Mulu ketema Project Manager/Programmer [email protected] 0923816041
registration Getachewu System designer 0920049386
system Dame
Harambee Zeritu Duguma Data base designer [email protected] 0921389927
University Tuto Olani Data collector 0983272453
college Mestewat Merga Webpage designer [email protected] 0919650091
Table 1-4. Team composition
Page
Chapter Two
2.1. Current system
The existing system or current is manual based system. This means slow performance employee
activities, data redundancy, slow registration speed, not time saved, a lot of resource usage example:-
paper, manpower, money, pen, time etc. Generally this system old works flow of activities.
2.1.1. Major functionality of the current system
This current system functions/worked

 Student manual Registration
 Student admission
 Readmission
 Withdrawal/drop out with manual
 Prepare student copy
 Prepared exam schedule
 Prepare grade report and prepare student slip etc.
2.1.2. User of the current system
The user of current system includes: - all University college students, Teachers (lectures),
admin employees.
2.1.2. Problem of the current system
The current system problems include:-

 Slow Performance
 Data redundancy not sequence data
 Data inconsistent(not constant data or sustainable)
 Wastage of paper
 Destroyed of data or resent data
Page
 Defragmented documented data or not arrangements of documented data

 Wastage of resource
 Redundant flow of student information
2.1.3. Business rule of the current system

The business rules of the current system includes; all students into University college school hold
Id card, timely student’s month payment, give us exam schedule for students, view grade reports
for students, learn finished all course then graduated then gives as full documents each students,
list out total credit hour for students, each students record by registrar, each semester record
students payment. Generally the business rule of the current system students must mandatory
every monthly payment now.
Page
3. Chapter Three
3.1. Proposed system model
The overview of proposed system is registered students computerized system through the
internet. The purpose of this project system shall be called the online admission and registration
system (OARS). And its main purpose will be to allow students registration.
The Online Student Registration System is a web based portal developed in Wamp. It can be used
by educational institutes or colleges to maintain the records of students easily. It also provides a
less time consuming process for viewing, adding, editing and deleting the marks of the students.
Online Registration system will allow online submission of student application, Student
Registration, Perform Computer based quiz or test. Stored test results, modify student profile.
Achieving this objective is difficult using a manual system as the information is scattered, can be
redundant and collecting relevant information may be very time consuming. Online Student
Registration System Project consists of two functional elements: an enhanced Student module for
Registration, Edit Profile, View Test history, Change Password. The project provides facilities like
online registration and profile creation of students thus reducing paperwork and automating the
record generation process in an educational institution. Online forgive, calculate results, store test
results, manage question banks. Student Information system will store all the details of the students
including their background information, educational qualifications, personal details and all the
information related to their resume.
The proposed system is the solution of the above mentioned problems. By using this system an
organization can handle its all kinds of above mentioned works efficiently, accurately, and speedily
with all kinds of security features by involving a few employees. Avoid all these problems and
made the system worked more accurately it needs to be computerized.
Page
After observing and identifying the current (existing) system, it is mandatory to develop proposed
system. This proposed system should solve the problem of the existing system and must be
advanced. So, the key solution to avoid all the problems mentioned previously is to find a unified
way to solve the problems mentioned earlier. The only unified way is by computerization. The
various entities that interact with the system are identified. In addition to this, the work flows,
functional, non-functional requirement, activities performed by man and by machine and procedure
within the system are being examined to understand and visualize the system.
3.2. Functional requirement
This online registration system is directly works:-
These requirements describe the interactions between the system and its environment independent
of its implementation. The environment includes the user and any other external system with which
the system interacts.
This requirement document is prepared with some balance of scope, time, cost and quality
considerations. Operations of the system, which can be realized under the time and resource limits,
are included in the requirements document.
Functional requirements that must be included in the system are listed below:
A. User requirement
The users interface language is English.
Personal Computer with both a standard keyboard and a mouse are required.
The user interface consists of menus and navigations that can be dictated by user’s
responses.
B. Hardware Requirement
The other part of the external interface is hardware interface, this interface describe the hardware
part of the system. So the system needs:-
Computer
Printer
Network cables
Page
Hub (16 port or more)

512 or more MB RAM
Additionally it also needs the use of a computer equipped with a mouse and a standard keyboard.
A monitor with not less than 800 x 600 resolutions and with 256 color capability.
C. Software Requirement
The product requires:-
1) Browsers such as:-
Mozilla fire fox
Google chrome
Opera
Internet explorer and others
2) Operating systems such as:-
Windows 7
Windows 8
Windows 10 etc.
The Functional Requirements Specification is designed to be read by a general audience.

Readers should understand the system, but no particular technical knowledge should be required
to understand the document.
In general functions of the proposed system are:-

Create account and login
Showing student their grade and CGPA
Sending request to registrar for grade and CGPA errors
Filling add, drop and withdrawal forms.
Student registration
Head of departments send grade and grade change request to registrar and
receive CGPA from.
Page
Placement: - enables students to select department and then register.

Report for students, Head of departments and registrar
Operations such as add, delete, edit and search for all users according to
their authority.
3.3. Non-functional requirement

Non-functional requirements are this works indirectly influence projects
Even though these requirements do not directly affect the performance of the system, they are
important. They are concerned with security, performance, usability, maintainability, reliability,
modifiability, efficiency, portability (across operating systems) testability, understandability.
The non functional requirements of the system are presented below:-
A. Security requirements
The system must be secured and protected by only the office of registrar. Every user of the
system is not allowed to access data or modify all files in the database without having correct
username, password and their security key. Each member can manipulate the necessary
operation that allowed for them on the database.
In addition to these, since the system runs on the internet environment, there are a lot of
security treat on the system. Therefore, the system should be secure from the malicious and
hackers by developing security key
B. Performance requirements
The software performs different operations when data types are numeric, text, date and time.
And it also gives an error messages when an authorized person tries to perform some
operation without entering inputs.
C. Maintainability
The system shall be distributed with independent modules or classes for the databases. This
independency bring to easily testability, maintainability, flexibility and easy to use.
Page
In general after the system has been produced, change or improvement may be needed. This
could happen because user need, change of the office plan and need of adding function to the
system.
D. Accuracy
Users need an accurate and correct data from the system that they use for the registration
process.
We can easily imagine the consequences of any decision that made inaccurate and incorrect
data on their basis. We expect to address this major issue through implementing a number of
validity checks such as every fields going to be entered in to the data base of the system.
3.4. System model

The system model is composed of three individual models: -
1) Functional model: represented by use case and Scenario
2) System object model: represented by classes and objects diagrams and
3) Dynamic model: represented by state chart and sequence diagram.
In this section we try to analyze the overall activity of the proposed system by using use
case description, use case diagram, sequences diagrams, activity diagrams, Class diagram
scenarios, deployment diagram and state diagram.
3.4.1. Scenario
A Scenario is a Use Case Instance
3.5. Use case model
A use case is an interaction between users and a system. It captures the goal of the users and the
responsibility the system to its users. It is the functionality of the system or the service provided by
the system. A Use Case Model describes the proposed functionality of a new system. A Use Case
represents a discrete unit of interaction between a user (human or machine) and the system.
3.5.1. Actor identification
Page
An actor in the Unified Modeling Language (UML) specifies a role played by a user or any other
system that interacts with the subject. These systems include some actors such as: - Students,
teachers (lecture), registrar and department head
3.5.2. Use case description and Diagram

Description 1
Use case name Login
Use case description Any user login into the sytem
Participating Actor Department, lecture, Student, registrar,
Precondition They login in to the system they must have username and password
Description 2
Use case name Registered
Use case description To registered active students
Participating Actor Students
precondition Students login to the system
Flow of events  Students click on register button.
 The system displays student registration form.
 Student fills registration data and click on Register button.
Post condition The system displays successfully registered message.
Description 3
Use case name View course information
Use case description To view course information to the user
Participating actor Student , lecture, department officer
Precondition The user into the system
Flow of status 1. The user clicks on the “view course information” link from the ORS
home page.
2. The System displays search options (course code, course name) and
advanced.
Page
3. The user searches the course using course code, course name.
4. The system displays the searched course.
5. The user selects that course.
6. The system displays the full course information
Post condition The user views the course information.
Description 4
Use case name Grade submit
Use case To grade submit for registrar
description
Participate actor Lecture
Precondition Lecture login into the system
Flow of events 1. Lecture clicks Grade submission button.
2. The system displays Grade submission form.
3. Lecture submit Grade and click on submit button
Post condition Student ‘s grade submitted
Description 5
Use case name Prepare slip
Use case To prepare slip to the student
description
Participate actor Registrar
Precondition Registrar login the system from home page of the ORS
Flow of events 1. Record worker clicks on the curriculum button.
2. The System displays curriculum list of each department semester
course
3. Record worker selects the needed department.
4. The system displays the existing courses of the semester.
5. Record worker fill the forms.
post condition The system display successful preparation message.
Description 6
Page
Use case name Modify account

Use case To create new account to the user
description
Participation actor Registrar officer
Recondition Registrar officer login into the system
Flow of events 1. Registrar officer clicks on modify account link from the home page of
the ORS.
2. Registrar officer clicks on search user account button.
3. The System displays search options (by name, by ID).
4. Registrar officer searches using one search method.
5. The system displays the user’s profile.
6. Registrar officer clicks on the update button to modify account.
Post condition The system modify successfully.
Description 7
Use case name Prepare grade report
Use case To prepare student grade report.
description
Participation actor Record worker
Precondition Record worker login into system.
Flow of events 1. Record worker clicks on “prepare grade report” link from the ORS home
page
2. The System displays the grade report form.
3. Record worker fills the form properly and clicks on generate
button
4. The system generates the grade report
Post conditions The system display successful message.
Description 8
Use case name Add/drop course
Use case Students to add/drop courses in to the student database table
Page
description
Participation actor Students
precondition Students login into the system
Flow of events 1. Student clicks on add/drop course link from the ORS home page.
2. The system displays students add/drop course form.
3. Student fills the form properly (to fill total credit text field click on sum
button after fill the credit hours of all courses that are added or dropped or
both).
4. Finally she click on the submit button.
Post condition The system displays successful submit message.
Table 1.5. Use case description
A use case is a list of actions or event steps, typically defining the interactions between a role
(known in the Unified Modeling Language as an actor) and a system, to achieve a goal. The actor
can be a human or other external system.
A use case is an interaction between users and a system. It captures the goal of the users and the
responsibility the system to its users. It is the functionality of the system or the service provided by
the system.
Page
Page
Figure 1.3. Use case diagram

3.6. Object model
An object model is a logical interface, software or system that is modeled through the use of object-
oriented techniques. It enables the creation of an architectural software or system model prior to
development or programming. An object model is part of the object-oriented programming (OOP)
lifecycle.
3.7. Class diagram
A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, operations (or
methods), and the relationships among objects.
The class diagram is the main building block of object-oriented modeling. It is used both for general
conceptual modeling of the systematic of the application, and for detailed modeling translating the
models into programming code. Class diagrams can also be used for data modeling. The classes in a
class diagram represent both the main elements, interactions in the application, and the classes to be
programmed
Page
class Use Case Model
Class
Coerse
{*}
- cdep: char
- cid: char
Department 1 * - cname: char Semister
- creadit houre: int * 1
- did: char - cid: char
- dname: char - did: char
- grade: char
+ location() : void - semister: char
* 1 - sid: char
- year: int
Student
1 1 1 *
- age: int
- birthdate: char
- city: int
- country: char
Admin users - depart: char
- fname: char
- id: char
- gpa: float
- password: char 1 * - lname: int
- uname: char
- mname: char
- usertype: char
- nationality: char
- password: char
- phone: int
- region: char
- sex: char
- sid: char
- username: char
Figure 1.4. Class diagram
3.8. Dynamic Model
A dynamic model represents the behavior of an object over time. It is used where the object’s
behavior is best described as a set of states that occur in a defined sequence.
3.8.1. Sequence Diagram

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.
Page
Figure 1.5. Registrar sequence diagram
Page
sd Use Case Model
Student Register Registeration Form Semister Year Database
Fill()
Select()
Click()
Fill()
Tray again()
Register successful()
print()
Figure 1.6. Student sequence diagram
Page
sd Use Case Model
sequence
Lecture Grade submit Grade submit Form Mark List Data Base
Fill()
Submit()
Click()
Cross check()
Tray again()
Print()
Figure 1.7. Teacher (Lecture) sequence diagram
Page
sd Use Case Model
sequence
Department View course Course Year Data Base

information
Select()
View information()
Click()
Check()
Tray again()
Print()
Figure 1.8. Department sequence diagram

3.9. Activity Diagram
An activity diagram illustrates the dynamic nature of a system by modeling the flow of control
from activity to activity. An activity represents an operation on some class in the system that results
Page
in a change in the state of the system. Typically, activity diagrams are used to model workflow or
business processes and internal operation. Because an activity diagram is a special kind of state
chart diagram, it uses some of the same modeling conventions. Activity diagrams are mainly used
as a flow chart consists of activities performed by the system. But activity diagram are not exactly a
flow chart as they have some additional capabilities.
act Use Case Model
get register
Enter username and passw ord
invalid
Login verifiy
valid
Display the registration form
fill the form
Figure 1.9.Activity diagram for Registered
Page
act Use Case Model
Login
Enter username and passw ord
invalid
Login verifiy
valid
Display the form
Figure 1.10. Activity diagram for Login
3.10. State diagram
Page
Specifically a state diagram describes the behavior of a single object in response to a series of
events in a system. Sometimes it's also known as a Harel state chart or a state machine diagram.
This UML diagram models the dynamic flow of control from state to state of a particular object
within a system
Figure 1.11. State diagram
Page
4. Chapter Four
System design
System design is the process of defining the elements of a system such as the architecture,
modules and components, the different interfaces of those components and the data that goes
through that system. It is meant to satisfy specific needs and requirements of a business or
organization through the engineering of a coherent and well-running system.
Systems design is the process of defining the architecture, components, modules, interfaces, and
data for a system to satisfy specified requirements.
4.1. Overview of system design
It is a process of planning a new business system or replacing an existing system by defining its
components or modules to satisfy the specific requirements. Before planning, you need to
understand the old system thoroughly and determine how computers can best be used in order to
operate efficiently. System Design focuses on how to accomplish the objective of the system.
4.1.1. Purpose of system design
The purpose of the System Design is to supplement the system architecture providing information
and data useful and necessary for implementation of the system elements. Design definition is the
process of developing, expressing, documenting, and communicating the realization of the
architecture of the system through a complete set of design characteristics described in a form
suitable for implementation.
4.1.2. Design Goal
The design goals represent the desired qualities of Student Online Registration System and
provide a consistent set of criteria that must be considered when make design decisions. Based on
the non functional requirements the following design goals will have to be achieved in order to
qualify the system as successful.
Page
1. Dependability criteria:-
 Robustness: The system has to be robust enough to manage any invalid input from the
users.
 Reliability: The system has to perform all operations of the registrar with no errors.
 Security: This is one of the most important nonfunctional requirements for securing all
information and data of the office.
2. Cost Criteria:-
 Deployment cost: The system has to be easy enough to have a cheap training cost.
3. Maintenance Criteria:
 Extensibility: the system must support that new functionalities can be added.
 Modifiability: The system has to be highly modifiable to maintain.
 Readability: The system has to be readable to assure its modifiability.
 Traceability of Requirements: the code should be easy to be mapped to specific
requirements.
4. End User Criteria:
 Utility: The system has been conceived specifically to support the students and
employers.
 Usability: The system will be designed in a user friendly fashion, both for students and
employers of registrar.
4.2. Proposed system architecture
Proposed System architecture is a conceptual model that defines the structure, behavior, and more
views of a system. An architecture description is a formal description and representation of a
system, organized in a way that supports reasoning about the structures and behaviors of the system.
Page
Figure 1.12. Proposed system architecture
4.2.1. System process
The system process is the first process means Harambee University College students mandatory rules
create user name and password then Login after then using online registration system registered.
The student may use the system to register, if the following conditions are fulfilled:
 The registration is done during the registration schedule, drop and add period, as published by
Admission and Registration Deanship;
 The student should have registered all courses as outlined in his/her study plan and should not have
had any exceptions during his/her study period
Page
 The student status is not suspended, prohibited, canceled, or does not have an academic Block from
the Admissions & Registration Deanship;
 The student has an Academic Advisor entered on the mysql System;
 The student has regular financial status;
 The student has no academic warnings.
 The student email is active.
 The advisor or student cannot register completed courses, i.e. courses have already passed. The
advisor may use the mysql System to register such a course.
4.2.2. Subsystem decomposition
During the subsystem decomposition we divide the system into smaller subsystem. Each subsystem
is strongly coherence and loosely coupled.
The system will be decomposed based on the use case and different actors defined in the system.
The decomposition shows the existence of the following subsystems.
 User management subsystem

 Account management subsystem.
 Transaction management subsystem
 Storage subsystem.
 Database subsystem.
The database subsystem will be implemented by the relational database management system
(RDMS) used to store the persistent data. The storage subsystem will encapsulate the database,
providing a common interface to the other three high level subsystems.
The following figure shows relationship between subsystem decomposition.
Page
Figure 1.13. Subsystem Decomposition
4.2.3. Hardware and Software mapping
Student online registration system will be web-based so that students and employers access through
the internet. All functionality will be performed in the main host and will be accessed through
Harambee University college website (www.HUC.edu.et) by all users.
The system will run on windows 7, windows 8, and windows 10, operating system. The web server
will run over wamp web server version 2. 2.
The programming language used to develop this product will be PHP version 5.3.13 and some
scripting language such as hyper text markup language (HTML), Java script (JS) and we have used
MYSQL version 5.0.51b as the database management system.
The following diagram illustrates software and hardware mapping of the system.
Page
Page
Figure 1.14. Software and hardware mapping of the system
Page
4.2.4. Persistent data management
The followings are persistent data objects based on the requirement analysis document.
 Person: this is information about all the system users. It can be system administrator and user.
 Account: It is information about the registration accounts. It includes the account holder’s
information.
 Transaction: Detail information about database transaction when different students registered at the
same time in the same table
This persistent information will be stored in a relational database management subsystem. We have
selected MYSQL as RDBMS due to its versatility, high performance and integration with the other
products that constitute the new platform.
Page
4.2.5. Component Diagram
cmp Use Case Model
component
Student
Online student
registration system
DB
«flow»
Registration
Payment
Registrar member
System search
Fee
Figure 1.15. Component Diagram
4.2.6. Deployment diagram
Deployment diagrams are used to visualize the topology of the physical components of a system,
where the software components are deployed. Deployment diagram is a structure diagram which
shows architecture of the system as deployment (distribution) of software artifacts to deployment
targets.
Deployment diagrams are used to describe the static deployment view of a system. Deployment
diagrams consist of nodes and their relationships.
Page
Figure 1.16. Deployment Diagram
Page
4.2.7. Database design
The overall objective in the development of database technology has been to treat data as an
organizational resource and as an integrated whole. Database Management System allows data to be
protected and organized separately from other resources.
Entity Relation Ship Diagram
Figure 1.17.Database Design
4.2.8. Access control
Page
The access control for the system is implemented through the capabilities list. This representation
comes up to be more compact and efficient for the system. A capability associates a class, operation
paired with an actor. A capability allows an actor access to an object of the class. Denying access is
another word for denying capability.
Registrar Capability List:
Class Operation
Create Account(),
Select Menu update Login(),
Login()
Create Login Menu Create Student Login(),
Create Department Login()
Create Student Login Form Create(), Update(), Login()
Create Department Login Form Create(), Update(), Login()
Create Login Report Show(),Print(),Exit()
Table 1.6. Registration capability list
The above table indicates that Registrar can create account for departments, students and give them
access control.
Students Capability List:
Class Operation
Create Account(),
Select Menu Update Login(),
Login()
Table 1.7. Student’s capability list
The above table indicates that Students can create account with the help of registrar, edit their
account and print information.
Page
Department Head Capability List:
Class Operation
Create Account(),
Select Menu Update Login(),
Login()
Table 1.8. Department Head capability list
The above table indicates that Head of Department can create account with the help of registrar, edit
their account and print information
Page
4.2.9. User interface design

 Home page interface
Figure 1.18. Home page
Page
 Student registration form interface
Figure 1.19. Student registration form
Page
 Students registration for a semester interface
Figure 1.20. Student registration for a semester
Page
5. Chapter five
5.1. Implementation and Coding
Implementation is the carrying out, execution, or practice of a plan, a method, or any design, idea,
model, specification, standard or policy for doing something. As such, implementation is the action
that must follow any preliminary thinking in order for something to actually happen.
5.1.1. Sample Implementation code
 Employee Login code
<?php
require('db.php');
session_start();
// If form submitted, insert values into the database.
if (isset($_POST['username'])){
$username = stripslashes($_REQUEST['username']); // removes backslashes
$username = mysqli_real_escape_string($con,$username); //escapes special characters in a string
$password = stripslashes($_REQUEST['password']);
$password = mysqli_real_escape_string($con,$password);
//Checking is user existing in the database or not
$query = "SELECT * FROM `adminusers` WHERE username='$username' and

password='".md5($password)."'";
$result = mysqli_query($con,$query) or die(mysql_error());
Page
$rows = mysqli_num_rows($result);
if($rows==1){
$_SESSION['username'] = $username;
header("Location: pageadmin.php"); // Redirect user to index.php
}else{ }
}else{
?>
<?php } ?>
 Department code
<!DOCTYPE html>
<?php
include("aauth.php"); ?>
<!DOCTYPE html>
<html>
<head>
<link rel="stylesheet" href="css/style2.css" />
</head>
<body>
<div style="clear:both; width:100%; background-color: #30292F; padding-top:-1%;">
<imgsrc="recource/harambe.png” height="120px” width="1365px"/>
</div>
Page
<ul id="nav">
<li><a href="pageadmin.php">Admin Home</a></li>
<li><a href="logout.php">Logout</a></li>
</ul>
<div style="padding:20px;margin-top:30px;background-color: #CCC;height:1500px;">
<?php
require('db.php');
// If form submitted, insert values into the database.
if (isset($_SESSION['R'])&& $_SESSION['R']=="Y")
echo '<script language="javascript">';
echo 'alert("Department Registerdsuccesfuly")';
echo '</script>';
if (isset($_SESSION['R'])&& $_SESSION['R']=="N")
echo '<script language="javascript">';
echo 'alert("Failed to Register")';
echo '</script>';
$_SESSION['R']="";
if (isset($_POST['register'])){
Page
$did = stripslashes($_REQUEST['did']);
$did = mysqli_real_escape_string($con,$did);
$dname = stripslashes($_REQUEST['dname']);
$dname = mysqli_real_escape_string($con,$dname);
$dl = stripslashes($_REQUEST['dl']);
$dl = mysqli_real_escape_string($con,$dl);
$dp = stripslashes($_REQUEST['dp']);
$dp = mysqli_real_escape_string($con,$dp);
$df = stripslashes($_REQUEST['df']);
$df = mysqli_real_escape_string($con,$df);
$query = "INSERT INTO `department`(`did`, `dname`, `dlocation`, `phone`, `fax`) VALUES

('$did','$dname','$dl','$dp','$df')";
$result = mysqli_query($con,$query);
if($result){
$_SESSION['R']="Y";
header("Location: Departmentreg.php");
else
$_SESSION['R']="N";
header("Location: Departmentreg.php");
Page
}else{
?>
<div class="form">
<h3>DEPARTMENT REGISTRATION FORM</h3>
<div class="r"
<div class="pb">
<form name="registration" action="" method="post" enctype="multipart/form-data">
<p><br>
<input type="text" name="did" placeholder="Department ID" required />
<br>
<input type="text" name="dname" placeholder="Department name" required />
<br>
<input type="text" name="dl" placeholder="Loction: B511" required />
<br>
<input type="text" name="dp" placeholder="phone number" required />
<br>
<input type="date" name="df" placeholder="fax number" />
<br>
</div>
<div class="botomform">
<input type="submit" name="register" value="Register" />
</div>
Page
</form>
<br /><br />
</div>
</div>
<?php } ?>
</body>
</html>
Chapter six
6. Conclusion and Recommendation
6.1. Conclusion
Page
The project online student registration system was proposed

The system has been developer with much care and free of errors and at the same time it is efficient
and less time consuming.
This project has given us great satisfaction in having designed an application which can be
implemented to Harambee University College various kinds of registration by simple modifications.
This project helped us in gaining valuable information and practical knowledge on several topics
like designing web pages using HTML & PHP, usage of responsive templates, designing of web
applications, and management of database using MY_SQL. The entire system is secured. Also the
project helped us understanding about the development phases of a project and software
development life cycle. We learned how to test different features of a project.
The purpose of this project was to develop a web application.
As the scope of this project describes we developed the online registration system Harambee
University College by making it more reliable and efficient. The system will register students,
update student information, view student’s results, search student information, browse student’s
photo and removing unnecessary information. These project system additionally works add new
employee, record course and add new department.
So the software will:
 Minimize the work load

 Make decision process fast
 Minimize the time required to perform task
 Provide sufficient security
 Reduce the number of employee involved
6.2 Recommendation
The project team wants to recommend some ideas considering the project .During the development
of the project the group members faced some problems like rewriting of the documentation part due
to some ideas and comments from the external advisors. Finally the project teams conclude that the
Page
department should give a special consideration for the student during the development of the final
project, during a regular class time also the department should bring advisors who have a special
skill in both coding and documentation and the department should attend the work of the internal
advisors at least two times in a month. We recommend that in future if another researcher picks up
interest in Online Registration system, this project should be a starting point. Future work may
consider all other resources from ORS.
Our recommend the project not include student admission, Readmission, add or drop course and
payments of fee, because of lack of time, not enough of budget. So these project picks up another
researcher or group team include above not include our project.
Reference
Internet
 . http://www.docstoc.com/docs/20179356/BANKING-SYSTEM-SYSTEM-DESIG
DOCUMENT
Page
 http://www.docstoc.com/search/subsystem-decomposition
Books
2. MySQL Cookbook author O'Reilly 1st Edition

3. PHP & MySQL author Vikram Vaswani 2nd Edition
4. Advanced PHP for Web Professionals Christopher Cosentino
5. CSS Pocket Reference author O’Reilly 2nd Edition
Appendix
1. How to student register
2. What you use software
3. How to grade submit instructor to registrar
4. How many registrar workers now in this organization
Page
5. Students how many satisfy by this system
Page

Documentation

Uploaded by

Copyright:

Available Formats

Documentation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Documentation

Uploaded by

Copyright:

Available Formats

HARAMBEE UNIVERSITY COLLEGE ONLINE REGISTRATION SYSYTEM

1.2. Establishment of the College

1.3. Infrastructure of the College

1.4. Statement of Problem

Not arrangement of Stored data

1.5. Purpose of the project for organization

1.5.2. General objectives

1.5.3. Specific objectives

1.6.1. Technical feasibility

Technical Feasibility - assessment is centered on the technical resources available to the

1.6.2. Economic feasibility

1. Hardware specification quantity Unit price Total price

11. Implementation 1000 1000

1.6.3. Scope and limitation

Our system does not include the following systems

1.7.1. Limitation of the project

1.7.2. Significance of the project

For HUCR office:-

 To easily retrieve user information.

1.8.1. Software development methodology

Figure 1.1. Software development methodology

 Hardware and Software specifications

Processing power  64 bit operating system

Memory & Secondary  RAM: 4GB MB and above

Peripherals  CD-ROM drives

Operating system windows 7

Documentation and  Microsoft office word 2007

Web browser Mozilla Firefox

Programming languages  My-SQL

Table 1-2: Hardware and Software specifications

 MySQL :-for database to create table, query

1.9. Unite test

Figure 1.2 Unit test

1.9.1. Integration test

1.9.2. Overview of project phase

Table 1-3 schedules

1.10.1. Team composition

Table 1-4. Team composition

This current system functions/worked

The current system problems include:-

 Defragmented documented data or not arrangements of documented data

2.1.3. Business rule of the current system

This online registration system is directly works:-

Hub (16 port or more)

The product requires:-

1) Browsers such as:-

Mozilla fire fox

Internet explorer and others

2) Operating systems such as:-

The Functional Requirements Specification is designed to be read by a general audience.

In general functions of the proposed system are:-

Placement: - enables students to select department and then register.

3.3. Non-functional requirement

3.4. System model

1) Functional model: represented by use case and Scenario

2) System object model: represented by classes and objects diagrams and

3) Dynamic model: represented by state chart and sequence diagram.

teachers (lecture), registrar and department head

3.5.2. Use case description and Diagram

Use case name Modify account