Professional Documents
Culture Documents
I
Acknowledgement
First of all, we would like express our heartfelt appreciation and gratitude to almighty God
for helping as through all the challenges we faced particularly in the past four years.
We would like to express our heartfelt appreciation and gratitude to all persons who provided
us with their unreserved support, encouragements, and comments which have been critically
helpful to accomplish our project successfully.
We indebted a special gratitude to Instructor Mr. Daniel Bekele (Msc), our adviser for his
constructive and supportive comments, materials and professional advice in each phase of the
project. We would like to express our heartfelt gratitude to the Director of school Mr.Tesfaye
Nemera who advise us how we make the project for the organization. And, finally we are
very much grateful to all the staff of Wollega University Gimbi Campus that provided us
with all the necessary information as well as comments and encouragements that made this
project possible.
II
Abstract
III
Abbreviations
IV
Chapter one
1 Introduction
1. Background of the organization
Gimbi Comprehensive high school is located in Gimbi town near wollega university Gimbi
campus. It started giving teaching service for the first time in 1950 E.C. At that time, the school
started the teaching-learning process by registering 74 students out of which 43 were male and
31 were females, by 8 male teachers and 2 female teachers totally 10 teachers and having for
supporting staff workers out of which 3 were males and 1 was female. Now days, The school is
carrying out its learning-teaching process having 36 male and 13 female teacher with 7 male and
3 female supporting staff workers. Currently the school have already registered 1508 students
and continued its teaching-learning process.
The School compound contains library, laboratory rooms and conference hall apart from
classrooms. The general objective of the establishment of the school was to provide access of
high school education for students those who completed their primary education.
The school registers only students those who have passed the grade 8 national exam. This project
is intended to replace the manual registration system of the school with computerized registration
system. The student registration system is used to provide efficient and reliable service for
Student and staffs. The Registrar office is giving various services such as admission, registration,
generating report, and marks of student for each subject, determine status and updating student
information. Doing these services manually is exhaustive. Due to this reason GCHSSIMS
(Gimbi Comprehensive high school student information management system) solution are
designed to enable the registrar to do every activity effectively.
1
1.2 Organizational Structure
Director of GCHS
Registrar Library
Gimbi comprehensive high school relies on paper based record /registration system to perform
its daily task. Records are not properly maintained. This creates a lot of problems like lack of
update, search and information retrieval and storage.
2
The other problem is that the manual system performs a number of operations incorrectly and
lacks accuracy of work appropriately. Due to redundant data, more space is occupied by file
cabinets. In addition to this it is difficult to add some additional requirements to the existing
system’s stored data (i.e. it is not flexible).
There is no control and security mechanism with in the office. Student’s information is not
secured and it can be seen by other peoples, because there is no authentication mechanism.
The services provided by the office are not as fast as possible because the service providers are
busy with the paper and paper related activities
1.4 Objectives
Online registration
Update mark of student and subject name
Determine status rank
Insert mark of student
Add mark of student
3
Delete mark of student
Compute average of the mark
Generating report
1.7 Methodology
Personal observation: assessing and analyzing the overall registrar system has been
carried out by personally observing the current working system.
Interview: This is one of the methods used for the collection of data in which the project
designers have the chance of asking different questions. We conducted the interview at
work by going to the organization and interviewing the workers, the users and as well as
the manager of the organization. We get so many information how the organization
looks in detail.
Document analysis: the team analyzed different kinds of secondary (published) sources,
unpublished documents from the institution which helps as to understand the existing
system. In order to collect basic information for the project we are sought to use
questionnaire, interview, observation and document analysis .Open ended and close
ended questionnaire are intended to be used.
4
1.8 System analysis and design methodology
Throughout the system development of this project we planned to use object oriented system
analysis and design methodology to develop the system. Reasons we select object oriented
approach are its nature of:
Reusability of code
Simple to implement
Easy to adopt changes at any level
Models the real world
Technical feasibility: This system provides help description to the user about how to use
the system. And other technical modification on the system is done by the developers.
5
Operational feasibility: Today there is no automated system in Gimbi Comprehensive
high school. The system will provide adequate through put at desired time to the user and
also give the needed information in a timely usefully formatted way.
Economic feasibility: As cost/benefit analysis, show the new system is developed using
a very minimum cost and it give a lot of benefits such as advancing the services of the
registration, decreasing the work load of the registrar office, students will register and see
their grade
6
1.13 Team members roles & responsibly
The success full completion of the project indeed requires the sincerely corporation of the team
members. Each team member has valuable contribution in each aspect of the project.
In addition each member also will be responsible for the overall activity. The group also has
responsibility to arrange communication plan for meeting and perform their work. Collect
information and documentation also discuss it as well as group members have the responsibility
of accepting the advisor comment and perform what they told to do. Also have responsibility of
reporting their work to the advisor
The project team contains six members and each member has their own tasks, activities and
responsibility to the delivery of the project.
Project Oversees the project and ensures that it meets its Milion Mitiku
Manager objective in time, function, and cost according to the
project plan
System Design the information system and ensure the Geremu Begire
Analyst system conforms to information systems standards
and analyze the system requirement
System Design the project structure and interface Mengistu Diriba and
Design Tadele Birahanu
7
Students should not allow making any changes to the database.
The system does not support personal signature.
The system can’t support online payment.
Password should not be null
2. Assumption
Assumption that Gimbi comprehensive high school has sufficient internet access.
There is a practice and method of taking backup.
Assume that the users know the basic computer skills
Assume that the hardware used to interact with the system will be a standard keyboard,
mouse, monitor, and a standard printer for taking hard copy of the reports generated as
and when required.
Assume that the users know how to start a program from the GUI, and can interact with a
user interface using standard keyboard, mouse, and monitor.
1.15 Plan
Hardware resources such as storage devices (CD/DVD, Flesh disk) and papers
Software resources such as Wamp server package (web server and Mysql RDBMS).
8
4 Purchasing of flash disk 6 piece 180.00 1080.00
9
Chapter Two
2.1.1 Introduction
This chapter focuses on the objectives, purposes, procedures and goals of the existing system. It
tells how the current system performs its activities within the school. The team members collect
the necessary information of the current manual system using different methodologies such as;
Interview and observation. The process of the interviewing prepared all the interviewees were
asked to understand the existing system the work flow of the registrar system from the registrar
officer to the subject. Using the observation the team members proposed it will be good if
automated system is done for such activities.
Oromia TVET Agency
2.2 Overview of the existing system
Gimbi Comprehensive high school registration system focuses on student registration, updating
Cluster
subject of Nekemte
name, modifying student records when necessary and also it transfers information
(reports) to other class that are concerned to the report. In the current system activities such as
searching,
Board ofdeleting,
Limu TVETupdating students record; and generating a report is a tedious and a time
consuming task.
2.3Dean of Functions
Major TVET of the current system
Functionalities
Register students mark list.
Register existing student (Registration).
Training process Administrative office
Finance office
Generating report
Update mark of student and subject name.
Major activities
o Registering new students
Registrar Library Students should have student transcript and mark list.
They receive student admission application form.
They fill the appropriate information on the form and attach his/her
photos, and then they submitted to registrar.
The registrar workers check whether they are valid or not.
10
If valid students give photo to get ID.
Registrar gives ID.
o Registering existing students
They receive Registration from registrar.
They fill the appropriate information on the form and attach his/her
photos, and then they submitted to registrar.
The registrar checks the form and stamp on it.
The students show their ID and clearance paper.
The registrar checks the status of student if it is ok, they give student ID
11
Processing the input data in order to get an output takes much time because of
the manual system (like Marks of student takes time, compute average,
determine status and update mark of student).
The data stored takes more rooms.
Since students fills different forms during registration and these forms are
checked by concerned registrar employee on different offices this process
takes much time.
After students submit registration form the registrar employee check the
validity of student’s information line by line the student’s response time is
low.
Since the system currently uses manual system it is not economically
sufficient i.e. there is a redundancy of activities, unnecessary ID is given to
student and main registrar (wastage of material and time), transcript is
prepared each and every semester with an unnecessary number of copies
(wastage of material).
Currently almost there is no control and security mechanism with in the office.
Student’s information especially transcript is not secured that is it can be seen
by other peoples, because there is no authentication mechanism.
The current system takes time during student registration because they use
some workers for a number of students, which makes the student to wait a lot
until they get their turn.
The services provided by the office are not as fast as possible because the
service providers are busy with the paper and paper related activities.
12
Chapter Three
3.3Product functions
The registration system has the following functionalities:
Registering students.
Inserting students mark
Updating students mark
Preparing mark list
Preparing Roster
Allow users to view information.
Generating report
3.4User characteristics
User classes User Characteristics Technical skills
13
Good understanding of HSSIMS Ability Use different system from past.
Administrator operations. Have basic knowledge of using the
Responsible for the whole operations. system in a networked environment
Have the good knowledge and Experience in how to manage the
understanding about the HSSIMS overall system.
system.
Constraints
Students should not be allowed making any changes to the database.
The system does not support personal signature
The system can’t support online Schedule and fees
14
Assumption & dependencies
Assumption that GCHS has sufficient internet access.
There is a practice and method of taking backup.
Assume that the users know the basic computer skills a standard keyboard, mouse,
monitor, and a standard printer for taking hard copy of the reports generated as and when
required.
Assume that the users know how to start a program from the GUI, and can interact with a
user interface using standard keyboard, mouse, and monitor.
The below listed equipment and software are required by the system so as to run effectively.
Hardware requirements
The following sub-sections discuss the various aspects of hardware requirements.
Database server computers and web server computers having 6 GB of RAM and 500 GB hard
disk and Intel(R) core™i3 CPU 550@3.20GHz processing speed
Network devices, NIC etc.
Software requirements
Platform
Typical platforms include a computer's
Operating system: Microsoft Windows 7, windows 10
Web browser( fire fox, Internet Explorer )
Programming language: PHP, JavaScript
It supports all browser application but Internet Explorer is recommended.
Other requirements
Uninterrupted power supply
Network connection
15
3.7 Functional requirements
Functional requirement is a description of activities and services a system must provide. 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. Functional requirements that must be included in the system are listed below:
1. Student’s data process:
Registration of student
2. Create account: the system allows user account creation and user management
3. Reports: The system generates different kinds of report like number of promoted,
detained, incomplete and drop out students and show the total number of Students. Etc
Update: The system allows Updating all available file relate to student information found
in the data base
4. Forms: This requirement is related to preparation of the various forms that the registrar
uses in its day to day activity. Those forms are: Student’s registration form, Student’s
readmission form, student mark list form and etc
5. Compute Rank: the system allows to calculate average and rank of student’s
6. Control and checking mechanism: the system should able to prevent unauthorized
user but allow authorized user to get access to the system and control each user access
according to their privilege.
1. Availability
The system should be available 24 hours in a day and 7 days in a week except
during maintenance.
2. Data integrity
Data will be critical to its success as a system.
Systems data integrity needs the consistency, correctness and complete of data
registered the following features improve the data integrity of the system.
16
Since the system performs data validation mechanism while entering the data
that makes data consistency.
Extensive data validation and review will be performed both before data are
uploading to the system and as part of upload process which supports the system
to keep data integrity.
Administrator
Recorder
Student
Teacher
17
3.9.3 Use Case Diagram
A use case diagram illustrates a set of use cases for a system, the actors of these use cases, the
relations between the actors and these use cases, and the relations among the use cases. The
UML notation for a use case diagram is shown on the figure below, in which
An oval represents a use case,
A stick figure represents an actor,
A line between an actor and a use case represents that the actor initiates and/or participates in the
process.
18
Use case diagram
Scenario
Scenario 1
Entry condition:
Flow of events:
1. He/she click on the create account link from the HSSIMS home page, Administrator
Page.
2. The system displays the create account form.
3. He/she fills the form and click on create button.
4. The system generates new user account with username and password.
Alternate Case:
1. If he/she made error when he fill the form and click on create button with error, the
system displays an error message and it allows him to try again.
2. He/she clicks on the clear button to clear the text field.
Exit condition: The system saves all necessary users’ information in the user table.
Special requirement: when he/she performs this task connection should not be down.
19
Scenario 2
Entry condition:
Flow of events:
1. In the HSSIMS login page the user enter his/her user name and password
2. The user clicks on the login button.
3. The system displays the Student or Recorder or Teacher or Administrator page.
Alternate Case:
1. If the username and password are invalid, the system displays an error message and
allows the user to try again.
Exit condition:
2. The system saves all necessary information’s of the user’s activity when he/she interacts
with system.
Special requirement: when the user performs this task connection should not be down.
Scenario 3
Entry condition: He/she logs in to the system using his user name and password.
Flow of events:
20
2. The system displays Student registration form.
3. He/she fills the form and click on Register button.
4. The system displays successfully registered message
Alternate Case:
1. If the registered record exists in the database, the system displays the Student already
registered message.
2. If the input data has error, the system display error message & allow him to try again
Special requirement: when he performs this task connection should not be down.
Scenario 4
Flow of events:
1. He/she clicks on modify account link from the Administrator, Teacher and Recorder page.
2. He /she clicks on update user account button.
3. The System displays search options (by SID).
4. The system displays the user’s old user name and password.
5. He clicks on the update button to modify account.
Alternate Case:
1. If there is a mistake in the data entry, the system displays error message and it allows to
him /her to make correction.
Special requirement: when he/she performs this task connection should not be down.
21
Scenario 5
Flow of events:
1. He/she clicks on “Generate Report” link from the HSSIMS home page.
2. The System displays the Report form.
3. He/she fills the form properly and clicks on generate button.
4. The system generates the Student Report.
Alternate Case:
1. If there is a mistake in the data entry the system displays error message and it allows to
him/her to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 6
Flow of events:
Alternate Case:
22
1. If there is a mistake in the data entry, the system displays error message and it allows to
him to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 7
Entry condition: The student logs in to the system using his/her account.
Flow of events:
1. The user clicks on view status button from the Student page.
2. The Student enters ID to view status form.
3. The user clicks on view button.
4. The System displays the user’s status.
Alternate Case:
1. If there is a mistake in the data entry, the system displays error message and it allows to
the user to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 8
23
Flow of events:
Alternate Case:
2. If there is a mistake in the data entry, the system displays error message and it allows to
him /her to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 9
Flow of events:
Alternate Case:
24
1. If there is a mistake in the data entry, the system displays error message and it allows to
him /her to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 10
Flow of events:
Alternate Case:
1. If there is a mistake in the data entry, the system displays error message and it allows to
him /her to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 11
Flow of events:
25
1. He/she clicks on Delete account link from the Administrator page.
2. The System displays search options (by SID).
3. He/she type the user’s account ID.
4. He clicks on the delete button to delete account.
Alternate Case:
1. If there is a mistake in the data entry, the system displays error message and it allows to
him /her to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 12
Flow of events:
Alternate Case:
2. If there is a mistake in the data entry, the system displays error message and it allows to
him /her to make correction.
Special requirement: when he/she performs this task connection should not be down.
Scenario 13
26
Name of use case: Insert Mark
Flow of events:
Alternate Case:
1. If there is a mistake in the data entry, the system displays error message and it allows to
him /her to make correction.
Special requirement: when he/she performs this task connection should not be down.
Flow of events - The system is a login link when users click the link.
- The user inserts username and password.
- The system checks the username and password whether it is
valid or not.
27
- The system allows the user to login into the system.
- If the user insert invalid username and password, the system
display an error message and allows trying again.
Alternative flow of If the user forget or want to change username or password the
events system allows them to change the username or password by
asking same security questions.
Table 3 login
Description 2
Flow of events He/she clicks on “insert mark” link from HSSIMS home page.
The System displays the form.
Teacher fills the form properly and clicks on insert button.
The system displays the inserted mark.
Alternative flow of If there is a mistake in the data entry the system displays error
events message and it allows making correction.
Description 3
28
use case name Generate report
Flow of events He/she clicks on “prepare student report” link from the
HSSIMS home page.
The System displays the student report form.
He/she fills the form properly and clicks on generate button.
The system generates the student report.
Alternative flow of If there is a mistake in the data entry the system displays
events error message and it allows to him to make correction.
Description 4
29
The system displays the create account form.
He/she fills the form and click on create button.
The system generates new user account with
username and password.
Post condition The system display successful message.
Alternative flow of If there is a mistake in the data entry, the system displays
events error message and it allows to the user to make correction.
Description 5
Flow of events The user clicks on view status link from the HSSIMS
home page.
The System displays view status form.
`The user fills the form properly and clicks on view
button.
Post condition The System displays the user’s status.
Alternative flow of If there is a mistake in the data entry, the system displays
events error message and it allows to the user to make correction.
Description 6
Flow of events The user clicks on the “view report information” link
from the HSSIMS home page.
The System displays search options (module code)
The user searches the module using module code.
The system displays the searched module.
The user selects that module.
The system displays the full module information.
Post condition The user views the module information.
Alternative flow of If there is a mistake in the searching module case, the system
events displays error message and it allows to the user to make
correction.
Description 7
31
The system displays the registration form
Student fills registration data and click on Register
button.
Post condition The system displays successfully registered message.
Alternative flow of If the input data has error the system display error message &
events allow to try again
Table 9 Register
Description 8
Flow of events Administrator clicks on modify account link from the home
page of the HSSIMS.
Administrator, Recorder, Teacher clicks on search user
account button.
The System displays search options (by ID).
Administrator searches using one search method.
The system displays the user’s profile.
-Administrator, Recorder, Teacher clicks on the update
button to modify account.
Post condition The system modify successfully.
Alternative flow of If there is a mistake in the data entry the system displays error
events message and it allows making correction.
Pre-condition Administrator should login and the entry should be within the
database
Flow of event
Administrator clicks on delete account link from the
home page of the HSSIMS.
Administrator clicks on search user account button.
The System displays search options (by ID).
Administrator searches using one search method.
The system displays the user’s profile.
Alternate flow of event The system display error message when some information is
missed and it must be corrected.
Post-condition If the activity was successful, account information is deleted
from the system. Otherwise, the system state is unchanged
Description 10
33
Use case Description To delete mark of student in the system
Pre-condition Teachers should login and the entry should be within the
database
Flow of event
Teacher clicks on delete mark link from the home
page of the HSSIMS.
Teacher clicks on search user account button.
The System displays search options (by ID).
Teacher searches using one search method.
The system displays the user’s Mark.
Alternate flow of event The system display error message when some information is
missed and it must be corrected.
Post-condition If the activity was successful, mark of student is deleted from
the system. Otherwise, the system state is unchanged
3.10 Class/objects
34
The top one indicates the name of the class
The third one lists the methods. By including those 3 sections class name, an attribute and a
method box in the class we are arguably making design decisions in the model.
35
Fig 3.1 class Diagram
36
3.12 Analysis Model
EAsd12.0
createUnregistered
account Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
EA 12.0 UnregisteredHSSIMS
Trial VersionAccount
EA 12.0 Unregistered
creation
button
Trial Version
Account creation
form
EA 12.0 Unregistered
Account controller Database server
Trial Version EA 12.0
Administrator
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
login()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
click create account button()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
initiate form()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
:view form
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
fill form()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
activated()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
:validated filled data
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered
check for redendancy() Trial Version EA 12.0
save()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
:return state
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
successfull message()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0
Fig 3.2 Sequence diagram for account creation
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
sd insert,update and delete
EA 12.0 Unregistered
Insert mark
Trial Version EA
Update Mark
12.0 Unregistered
Delete Mark Submit Mark
Trial Version
Form
EA Controller
12.0 Unregistered Trial Version EA 12.0 U
Database
Teacher
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
click()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
show()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
click()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
show()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
click()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
show()
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered
:success
Trial Version EA 12.0 U
:successfull
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
Fig 3.3 sequence diagram for Insert, Update and Delete Mark
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
3.13 Activities Diagram
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
An activity diagram describes a system in terms of activities. Activities are states that represent
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
the execution of a set of operations. The completion of these operations triggers a transition to
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
another activity. Activity diagrams are similar to flowchart diagrams in that they can be used to
EA 12.0
represent Unregistered
control Trial the
flow (i.e., Version
orderEA
in 12.0
whichUnregistered
operationsTrial Version
occur) EA 12.0
and data Unregistered
flow Trial Version EA 12.0 U
(i.e., the objects
that EA
are12.0
exchanged among
Unregistered operations).
Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
38
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 Unregistered Trial Version EA 12.0 U
Fig 3.4 Activity Diagram
39
Chapter Four
4. System Design
Design Goals
The design goals stated for the system defines the qualities that the system should incorporate.
Most of these design goals are the refinements of the non-functional requirements identified
during requirement gathering, and some of the design goals may not state explicitly in the
requirements specification. However, if the system is to be efficient, these design goals need to
be incorporated.
PRESENTATION TIER
MIDDLE TIER
DATA TIER
40
Figure 4.1.Shows the three-tier architecture of the Registrar Web Application.
In presentation tier user interfaces are placed on the middle tier business models and rules are
applied and in the data tier database schemas are placed and retrieved by different sql queries
when needed.
41
4.5 Database Design
The solution that we have given to Gimbi comprehensive high school Registrar System to solve
the listed problems are web application, so based on this we have implemented the PHP
programming language and for database MYSQL. So the following physical database design are
implemented using MYSQL Relational Database Management System
rooster user
enrollment stud_id
stud_id user_id
section_id
section_id user_name
Sem
Ac_year password
Ac_year
status role
Afan_oromo
Remark
Amharic
English
Maths
Physics
course
course_no
course_title
ministry
reg_no
sid
Ac_year
school_name student
zone stud_id
Average sname
sex
mark_list
Persentile
sid
status age
course_no
zone
Ac_year
woreda
section_id
sem
test1
test2
test3
mid
final
total
42
Fig 4.4 State Chart Diagram
43
Fig 4.5 user interface design
4.7Physical schemas:
Table 4.1: Student Table
44
Table 4.2: User Table
45
Afan Oromo Int 5 NO
English Int 5 NO
Maths Int 5 NO
Physics Int 5 NO
Chemistry Int 5 NO
Biology Int 5 NO
Civic Int 5 NO
IT Int 5 NO
Amharic Int 5 NO
Physical_Edu Int 5 NO
Geography Int 5 NO
History Int 5 NO
Total Int 10 NO
Average Int 10 NO
Rank Int 10 NO
46
SQL Code That Generates the Above Table Structures
Create Database ‘gchs’;
47
[Chemistry] [int] NULL,
[Biology] [int] NULL,
[Civic] [int] NULL,
[IT] [int] NULL,
[Geography] [int] NULL,
[History] [int] NULL,
[Physical_edu] [int] NULL,
[total] [int] NULL,
[Average] [int] NULL,
[Rank] [int] NULL,
Conclusion
As we describe above this system is mainly focus on the Gimbi comprehensive high school web
based service. The main cause that initiates us to develop this system is the necessity of the
system for the high school to perform their work effectively and efficiently. High school student
information management System is capable to be used in the organization through internet (local
internet) for the success of activity for its member client and other users that need service from
this organization. The system also the capacity of the expansion is increased highly interims of
the benefit of the organization.
REFERENCES
Test Planning, http://www.vietnamesetestingboard.org
C. Kaner, J. Bach, and B. Pettichord, Lessons Learned in Software Testing: John Wiley
& Sons, 2002.
Object primer Agile Modeling: Scot W. Ambler
48
www.codeproject.com
www.w3schools.com
49