Final

AMBO UNIVERSTY
INSITUTE OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
TITLE: WEB BASED STUDENT INFORMATION
MANAGEMENT SYSTEM FOR SENKELE POLICE COLLEGE
NAME BY: ID NUMBER
HASSEN AHAMED BRT/2146/08

TASFAYE HIKA BRT/2243/08
NURADIN ABDUMALIK TBRT/0348/10
GALATA TESHOMA BRT/2289/08
ADMASU ADUGNA BRT/2185/08
BULCHA BEGNA BRT/2126/08
Project Submitted To Department Of Computer Science of Ambo University for Degree

of Bachelor of Science in Computer Science
ADVISOR: Dr. Nagarajan
JUNE 17, 2019
Ambo, Ethiopia
WEB BASED STUDENT INFORMATION MANAGEMENT SYSTEM FOR
SENKELE POLICE COLLAGE
AMBO UNIVERSTY
INSITUTE OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
TITLE: WEB BASED STUDENT INFORMATION
MANAGEMENT SYSTEM FOR SENKELE POLICE COLLEGE
BY
NAME SIGNATURE ID NUMBER

HASSEN AHAMED BRT/2146/08
TASFAYE HIKA BRT/2243/08
NURADIN ABDUMALIK TBRT/0348/10
GALATA TESHOMA BRT/2289/08
ADMASU ADUGNA BRT/2185/08
BULCHA BEGNA BRT/2126/08
NAME AND SIGNATURE OF MEMBERS OF THE EXAMAINING BOARD

NAME TITLE SIGNATURE DATE
Chairperson,
Dr. Nagarajan advisor,
Examiner,
Examiner,
DEPARTMENT OF COMPUTER SCIENCE Page i AMBO UNIVERSITY

SENKELE POLICE COLLEGE
Declaration
We declare that this project is our original work and it is being submitted for the degree
of Bachelor of Science in Computer Science at Ambo University. It has not been
presented for a degree in any other University.
NAME SIGNATURE DATE
HASSEN AHAMED
TASFAYE HIKA
NURADIN ABDUMALIK
GALATA TESHOMA
ADMASU ADUGNA
BULCHA BEGNA
THIS PROJECT HAS BEEN SUBMITTED FOR EXAMINATION WHIT OUR

APPROVAL AS UNIVERSITY ADVISOR.
NAME SIGNATURE DATE
DR.NAGARAJAN
Page ii
Acknowledgement
We would like to express our gratitude to Almighty God to enabling us to complete this
phase successfully.
Successfully completion of any type of project requires helps from a number of persons.
We have also taken help from different people for the preparation of project. Now, there
is a little effort to show our deep gratitude to those all who either directly or indirectly
helped to this project.
We want to express our gratitude mainly to Ambo University president, Dean of IOT
who gives infrastructure.
We express our sincere thanks to Oromia police college registrar, who gives different
information about current work flow of the senkele police college.
We deeply thank our department head for facilitating computer lab to do our project. We
are grateful to our advisor Dr. Nagarajan, Assistant Professor, department of Computer
Science for them rest less edition of our documentation, input to the quality of this
document, heart full guidance and providing to execute this project.
He allowed us to encourage upon his precious time freely right from the very beginning
of this project until the completion of our phase one project.
We have no hesitation to say that, without his constant support and valuable advice from
time-to-time.
We would probably fail to complete the work in an appropriate manner.
Finally, we are very grateful to our families who always give us constant support and
encouragement.
Page iii
Contents
Declaration......................................................................................................................... ii
Acknowledgement ............................................................................................................ iii
List of figure ................................................................................................................... viii
List of Table ...................................................................................................................... ix
List of Abbreviation .......................................................................................................... x
Abstract ............................................................................................................................. xi
CHAPTER ONE ............................................................................................................... 1
1.1 Introduction ................................................................................................................... 1
1.2 Background of the Study .............................................................................................. 2
1.3 Statement of the Problem. ............................................................................................. 2
1.4. Objective of the Project ............................................................................................... 3
1.4.1 General Objective ...................................................................................................... 3
1.4.2 Specific Objective ...................................................................................................... 3
1.5. Scope of the Project ..................................................................................................... 3
1.6. Significance of the Project ........................................................................................... 3
1.6.1Target beneficiaries of the system .............................................................................. 4
1.7 Methodology ................................................................................................................. 4
1.7.1 Data Source ................................................................................................................ 5
1.7.2 Fact Finding Technique ............................................................................................. 5
1.7.3 Systems Analysis and Design (approach) .................................................................. 6
1.7.4 Development Tools .................................................................................................... 6
1.7.5 Hardware Requirement .............................................................................................. 6
1.7.6 Software Requirement ............................................................................................... 6
1.7.7 Testing procedures ..................................................................................................... 7
1.7.8 Proposed Implementation method ............................................................................. 8
1.8 Limitation of the project ............................................................................................... 8
1.9 Risk and contiguous ...................................................................................................... 9
1.10 Assumptions and constraints....................................................................................... 9
1.10.1 Assumptions........................................................................................................... 10
Page iv
1.11 Scheduling................................................................................................................. 10
CHAPTER TWO ............................................................................................................ 11
2.1. Introduction of the existing system ............................................................................ 11
2.1.1 Major players of the Existing system....................................................................... 12
2.1.2 Functions / activities in the existing system ............................................................ 12
2.1.3 Business rules........................................................................................................... 13
2.1.4 Report generated in the existing system .................................................................. 14
2.1.5 Forms and other documents of the existing Systems ............................................... 14
2.1.6 Bottlenecks of the Existing system .......................................................................... 15
2.1.6.1 Performance: ......................................................................................................... 15
2.1.6.2 Information: .......................................................................................................... 16
2.1.6.3 Control and security: ............................................................................................. 16
2.1.6.4 Efficiency: ............................................................................................................. 16
2.2 Practices to be preserved ............................................................................................. 16
2.3 The Proposed System .................................................................................................. 17
2.3.1 Team composition .................................................................................................... 17
2.3.2 Feasibility Analysis .................................................................................................. 18
2.3.2.1 Operational feasibility........................................................................................... 19
2.3.2.2 Technical feasibility .............................................................................................. 19
2.3.2.3 Economical feasibility .......................................................................................... 19
2.3.2.4 Political feasibility ................................................................................................ 20
2.3.2.5 Schedule Feasibility .............................................................................................. 20
2.3.3 Requirement of the Proposed System ...................................................................... 21
2.3.3.1 Functional requirement ......................................................................................... 22
2.3.3.2 Non Functional Requirements .............................................................................. 22
CHAPTER THREE ........................................................................................................ 24
3.1 Introduction ................................................................................................................. 24
3.2 System requirement specification ............................................................................... 24
3.2.1 Use Case model........................................................................................................ 24
3.2.1.1 Actor and Use Case Identification ........................................................................ 25
Page v
3.2.1.2 System Use Case ................................................................................................... 28

3.2.1.3 Use Case Description ............................................................................................ 29
3.2.1.4 Scenarios ............................................................................................................... 39
3.2.2 Object model ............................................................................................................ 42
3.2.2.1 Class Diagram ....................................................................................................... 42
3.2.2.2 Description of Design Class Diagram................................................................... 44
3.2.3 Dynamic model ........................................................................................................ 47
3.2.3.1 Sequence Diagram ................................................................................................ 47
3.2.3.2 Activity Diagram .................................................................................................. 51
3.2.3.3 State chart Diagram............................................................................................... 55
3.2.4 User Interface Design .............................................................................................. 57
CHAPTER FOUR ........................................................................................................... 58
4.1 Introduction ................................................................................................................. 58
4.1.1. Purpose of the system ............................................................................................. 58
4.1.2. Design Goals ........................................................................................................... 59
4.2. Current Software Architecture ................................................................................... 59
4.3. Proposed software architecture .................................................................................. 60
4.3.1 Overview .................................................................................................................. 61
4.3.2 Subsystem Decomposition ....................................................................................... 61
4.3.3 Hardware and software mapping ............................................................................. 62
4.3.4 Persistent data management ..................................................................................... 62
4.3.5 Access control and security ..................................................................................... 63
4.3.6 Global Software control ........................................................................................... 65
4.3.7 Boundary condition .................................................................................................. 65
4.4 Subsystem services ..................................................................................................... 66
Chapter Five .................................................................................................................... 67
5.1 Introduction ................................................................................................................. 67
5.1.1 Final Testing of the System ..................................................................................... 67
5.1.2 Hardware software acquisitions ............................................................................... 75
5.1.3 User manual preparation .......................................................................................... 75
Page vi
5.2 Training ....................................................................................................................... 78

5.3 Installation Process ..................................................................................................... 78
5.4 Start-Up Strategy ........................................................................................................ 79
CHAPTER 6 .................................................................................................................... 80
Conclusion and Recommendation .................................................................................... 80
6.1 Conclusion .................................................................................................................. 80
6.2 Recommendation ........................................................................................................ 80
6.3. Reference ................................................................................................................... 81
Page vii
List of figure
Figure 1: Manage account essential use case .................................................................... 27
Figure 2: System Use Case ............................................................................................... 28
Figure 3: Analysis Class Diagram .................................................................................... 43
Figure 4: Login Sequence Diagram .................................................................................. 48
Figure 5: Student Registration Sequence Diagram ........................................................... 49
Figure 7: View Grade Report Sequence Diagram ............................................................ 50
Figure 8: Login Activity Diagram .................................................................................... 52
Figure 9: View Registered Student List Activity Diagram ............................................... 53
Figure 10: Register Student Activity Diagram ................................................................ 54
Figure 11: State chart diagram for login ........................................................................... 55
Figure 12: State chart diagram for help ............................................................................ 56
Figure 13:User Interface Diagram……………. ............................................................... 57
Figure 14:Persistent data Diagram .................................................................................... 63
Figure 15: Login page ....................................................................................................... 76
Figure 16:Admin page ...................................................................................................... 76
Figure 17:View course page ............................................................................................. 77
Figure 18:Block acount ..................................................................................................... 77
Figure 19:Edit student information ................................................................................... 78
Page viii
List of Table
Table 1: schedule .............................................................................................................. 10
Table 2: form of student .................................................................................................... 15
Table 3: Team composition and their duty ....................................................................... 18
Table 4: Schedule Feasibility ............................................................................................ 21
Table 5: Use Case and Actor Identification ...................................................................... 26
Table 6: Login Use Case Description ............................................................................... 30
Table 7: Register Student List Use Case Description ....................................................... 31
Table 8: Create Account Use Case Description ................................................................ 32
Table 9: Submit Grade Use Case Description .................................................................. 33
Table 10: Register Course Information Use Case Description ......................................... 35
Table 11: View Registered Student List Use Case Description ....................................... 35
Table 12: Edit Course Information Use Case Description................................................ 37
Table 13: Register In Course Use Case Description ......................................................... 38
Table 14: Register student’s health information Use Case Description ........................... 39
Table 15: Scenarios ........................................................................................................... 41
Table 16: Design Class Description for User ................................................................... 44
Table 17: Design Class Description for Student Class ..................................................... 45
Table 18: Design Class Description for Teacher .............................................................. 45
Table 19: Design Class Description for Interrogator ........................................................ 45
Table 20: Design Class Description for Director Class .................................................... 45
Table 21: Design Class Description for Registrar Officer Class ...................................... 46
Table 22: Design Class Description for Course Class ...................................................... 46
Table 23: Design Class Description for Account Class .................................................... 46
Table 24: Access control table .......................................................................................... 64
Table 25 : Test Case for Login ......................................................................................... 69
Table 26 : Test Case for View Grade Report .................................................................... 70
. Table 27 : Test Case for Register User ......................................................................... 72
Table 28 : Test Case for Block Acount ............................................................................. 73
Table 29: Test Case for Create Acount ............................................................................. 74
Page ix
List of Abbreviation
BSC: ……………………………… basic score card

CD: ………………………………….Compact Disk
CSS………………………………Cascading Style Sheet
Dept Head………………………….….Department Head
GB………………………………..Gigabyte
HTML: ……………………………….Hypertext Markup Language
MYSQL……………………………My Structured Query Language
OOSAD: …………………………… Object Oriented System Analysis
ORG: ……………………………….Oromia regional government
PC……………………………………Personal Computer
PHP: …………………………………Hypertext Preprocessor
RAM…………………………….......Random Access Memory
Reg Officer…………………………Registrar Officer
SPC………………………………..Senkele Police College
UC:…………………………………..Use Case
UI:.…………………………………User Interface
WAMP………………………..............Windows Apache Mysql Php
Page x
Abstract
Senkele police collage is found in ambo city. It is a well-organized collage and stands for
serving students and all peoples in Oromia regions. The head of collage has living with
keep rules of students and security of police as well and for the purpose of preventing
enemy. It works regardless of student information recording and give advice for all
persons break principles time to times. And we are doing this project only limited to
services the collage gives to senkele police students.
The collage is limited on manual work Submit student grade report manually using paper
s. This has limitation on controlling the work securely, for declaring the result on time,
and has high consumption on resources. Manual data processing system is not fast and
efficient way to accomplish tasks within short period of time and it is boring. To
overcome this problem we are proposing the new system for the college. To alleviate the
existing system problems we are using programming tools like:-Wamp server for
interfacing and coding, MySQL for database application, and Microsoft Visio for
designing different artifacts of the project. Finally the overall activity of this project work
is about design and implementation of web based student information management
system for senkele Police College.
Page xi
SENKELE POLICE COLLAGE
CHAPTER ONE
1.1 Introduction
The development of one country is analyzed from many angles. That there are many
factors such as peaceful security of the people and their property etc. those are protected
by police and peoples. The institution of Police College is standing to protect peoples and
their property from danger. Senkele Oromia police has been doing to implement different
reforms like civil service, business process reengineering (BPR), basic score card (BSC),
peace army and also struggling to demolish partiality, doing partial for partnership and
relatives, seeking rent, and destroying backward practice indoor to establish good
governance, giving service that has quality, transparency, activeness for the customers.
This made the relationship between police and community to be coming strong from time
to time. It has been working to make the customer to be happy by finishing his/her affair
on time.
On the case of investigating, it has been made that the flagrant criminals to get legal
penalty quickly by RTD and it was able to make so that the criminals prevent themselves
from committing crime. By making the police investigator and public prosecutor to do
together it has been made that the customer not to play for his/her concern. It has been
being done in order to work strongly with community and peace and security bodies to
ensure security of the region and sovereignty of rule of law. Senkele Oromia police has
been doing Profitable works and played great role on the case of expanding good
experience and creating good understanding of done good exemplary works and
identified for knowledge, warning, and experience especially, by press media like
magazine, brochure, and pamphlet and also transmitting by Oromia police TV and radio
programs, and on the other hand celebrating holydays with community and passing the
current government’s message and the work done in expanding good experiences from a
zone to another zone by occurring at community discussions by strengthening community
participation in creating community who hate and prevent crime by lining up with police.
DEPARTMENT OF COMPUTER SCIENCE Page 1 AMBO UNIVERSITY

1.2 Background of the Study

Senkele Police College is found Western Showa Zone of Ambo Branch 10km far away
from Ambo City. The college gives the following trainings types: leadership training
(regular diploma assistant constable, regular certificate assistant
Constable), Basic training (ORG police Commission regular police, ORG prison police
Commission regular police, cabal distributing), and Special training (road control, crime
and accident investigation, anti-Commission).
Our project is concerned on Senkele police college student information management
system in case of Ambo city. The main purpose of this project is to develop web based
student information management system for Senkele Police College. Our system will
provide proper security and reduces the manual work and tries to eliminate or reduce
difficulties up to some extent. Generally the new system will change the existing manual
system in to computerized system that will help to store student related data in a well-
organized manner. [1]
1.3 Statement of the Problem.

Problems of the existing system are:
 Submit student grade report manually using paper, so the present system is not
good enough because this paper will be damaged.
 Information retrieval of student detail is difficult and time consuming because
there is no way to search student information electronically.
 Little coordination among users (students, teachers and other college workers)
because there is no interface that helps user to access the system.
 Accessing students file is time consuming.
 When the number of students becomes huge (increase) storing of their data is
difficult and needs more cost.
 Difficult to update the student information. For example to change students result.
 Losses of data because the system uses MS excel and paper to store student
information, so data can be lost.

 The other big problem is security. As we have indicated in the above information
is stored in MS Excel and paper, every employee can edit others personal
information. But, the student information that is stored in the Registrar need highly
secure system and also needs care to prevent it from unauthorized access.
 Generally In the current system there is no mechanism for student to view grade
report online, to submit student grade, to register student, Documenting and storing
student records, Search student files rather than paper
1.4. Objective of the Project

1.4.1 General Objective
The general objective of this project is to develop web based information management
system for senkele police college students.
1.4.2 Specific Objective

The specific objectives of this project are:
 To develop a database system that store, manipulate, search and retrieve data.
 To develop easy and descriptive user interfaces to manipulate student records.
 To develop a mechanism for student grade report generation.
 To develop good security mechanism to keep students data.
 To develop a system that enables submission of students result.
1.5. Scope of the Project
Scope defines the coverage areas of the project, activities and operation done by the
system. The project team needs to develop web based student information management
system for senkele police College. The project team will develop a system.
 To register student.
 To generate grade report.
 To documenting and storing student records.
 To search student files.
1.6. Significance of the Project

After implementation our system will deliver different functions for senkele police
college student and staff workers such as:
 t will speed up the searching processes of student information.

 It will avoid loss of data.
 It will minimize the cost.
 It will increase user satisfaction
 It will save the time that is lost while recording student information manually.
 It will protect the student file from unauthorized access.
 It will handle student information in better way. .
1.6.1Target beneficiaries of the system
Managements:-gain knowledge of the Ethiopian police college education.
Develop their ability to managing all power of sub-head of collage and how to control
student in college.
Student:-they are encourages their level of education. Take so many experience of the
governments of Oromia regions and helps all parts of the governments the time of rule of
low is braked in anywhere around Oromia region.
1.7 Methodology
A methodology is a set of methods, processes, and practices that are carried out to deliver
a project.
 We use Rad (Rapid Application Development) System development approach by
the following reasons.
 It is useful for projects in which the user requirements are uncertain or imprecise.
 It encourages active user and management participation, which increases end-
user interest for the project.
 Projects have higher visibility and support because of the extensive user
involvement throughout the process.
 Errors and omissions tend to be detected earlier in prototypes than in system
models.
 The iterative approach is a more “natural” process because change is an expected
factor during development.
 RAD prototypes can easily solve the wrong problems.

 Generally produces a dramatic savings in time, money, and human effort.

System development methodology refers to the frame work that is used to structure plan
and control the flow of developing an information System.
 For this project the team used object oriented software development methodology.
 The reason why we selected object oriented system development is because it has
the following advantages.
 In an object-oriented environment, Object-oriented systems development is a way
to develop software by building self-contained modules or objects that can be
easily replaced, modified, and reused.
 Is used to manage the complexity of software systems.
 Identifying the source of errors becomes easier because objects are self-contained
(encapsulation).
1.7.1 Data Source
In order to develop the system, different data sources like primary data from the head of
this collage and secondary data which are found in store history of this collage are used.
The manual document which is found in the senkele police collage helps us to gathering
data in the current system. Internet in order to gathering related data about proposed
system.
1.7.2 Fact Finding Technique
We use data collection methods to collect the data need for the team
Project those are:
 Interview: The project team use Interview techniques to get information about
current flow of work by interviewing key workers of colleges such as registrar
officer, director, teacher as they told as the system uses manual way to register
student, to store student data by paper and MS Excel, generally they have no
electronic system to perform their task.
 Observation: To gather relevant information the project team observes how the
current system works. As we observe student data is recorded on paper and put on
the shelf.

 Document Analysis: The project team tried to discover written documents about
the college areas relevant to the project for example we get types of trainings that
the college gives from soft copy analysis.
1.7.3 Systems Analysis and Design (approach)

To develop this system we prefer OOSAD (Object Oriented System Analysis and
Design) methodology. This is because an OOSAD provides the following advantages.
Promotes better understanding of user requirements.
 Leads to clear design by using use case, activity diagrams and sequence diagram.
 Allows to breakdown complicated systems into smaller, clearly defined and more
Manageable parts.
 Enables the standardization of objects which increases design understanding and
decreases the risk associated with project development. [2]
1.7.4 Development Tools
Hardware and software tools required for successful completion of this project are listed
below with their respective significance.
1.7.5 Hardware Requirement
 Laptop: To do different activity or applications.
 Desktop Computer: To do different activity or applications.
 Processor: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3600 MHz, 2 Core(s), 4
Logical Processor(s)’
 RAM: 4GB.
 Flash Disk: To store data. The data in the computer may be lost because of
different cases and to take available data from different sources.
 Printer: For printing soft copy what we are doing in the project.
1.7.6 Software Requirement
To implement our project we will use the following software:
 Microsoft Visio: used to create simple or complicated diagrams. It offers a wide
variety of built-in shapes and objects to work with.so the team will use it for drawing
the UML diagrams.

 Microsoft power point 2010: for presentation of the documentation.

 Microsoft office word 2010: for writing the documentation.
 WAMP Server: manage our servers setting. The reason why we select WAMP
server.
 Due to its popularity to any web based applications.
 It is open source.
 The main purpose of a WAMP server is to run test applications before being
uploaded on to the actual server.
 MYSQL database: for storing the data because:
 Most of the time MYSQL is compatible with PHP programming language and
MYSQL portable.
 MYSQL it is an open source database.
 Its performance is high.
 Supports large number of surrounded applications which makes MYSQL very
flexible.
 Notepad++ and Code lobster PHP Edition: for code editing.
 Firefox browser: for run the code because:
 It works on all common operating systems, such as Windows, mac OS and Linux
operating systems.
 It fastest browser. [3]
1.7.7 Testing procedures

To test the entire system as a whole with all forms, code, modules, we use Black Box
testing or System tests. Thus the team members test all the functionalities in the System.
All errors in the forms, functions, modules are tested. Testing is the most important to
determine the quality of the system.
It used to identify what the error of the system or either to check the system has error or
not, either an expect input gives the actual output or not and check the integration of the
classes produce real object. For instance, we will use black box testing, unit testing and
integration testing.

Unit testing: first we will tests each unit at each system. So, if a problem is encountered
it will immediately maintain at which the problem is occurred.
Integration Testing: after we test each unit of the proposed system we will perform an
integration test to check whether the system meets all the functional requirements. When
a number of components are complete; it will test to ensure that they integrate well with
each other, the operating system, and other components. System testing for verifying as
the whole system is functioning in integrated manner and helping in striving planned
Goal System testing is comparing Function of the system developed in relation with
expected function of the system.
1.7.8 Proposed Implementation method
Implementation is the phase where objectives of physical operations of the system
turned into reality i.e. real working model. The crucial phase in the system development
life cycle is the successful implementation of the new system design. This part recognizes
that the system works correctly or not, accurate or not, updates the features if necessary.
The process of converting as new system into an operational one is known as system
implementation. This includes all those activities that take place to convert from an old
system to a new system. The proposed system will implement parallel with the existing
system until the awareness of the workers towards the proposed system improved
(parallel).
1.8 Limitation of the project
Limitation is element of factor or subsystem it restricts the system decision making from
achieving potential goal of the system. There are many constraints within our proposed
system that limit their effectiveness of performance.
Time: Is the main factor of limitation our proposed systems that limit its performance
because while we are developing the system it takes more time and we may not get
enough time to automate the system.
Resource: We have not enough laptop as an alternative when arbitrary failed the desktop
and also when the power is off for a long time.

1.9 Risk and contiguous

Unfortunate failure of system: To handle this problem the teams have some method to
resist not completely but partially by using back up mechanisms using flash disks and CD
and by storing the data in more than two computers.
Power problem: we use PC to cover the gap happened to our project during power
failure.
Virus attack: It is difficult to control data from virus but try to scan the data, installing
and updating antivirus software.
Time management problem: this problem by working cooperatively, divide our time by
schedule for each phase of the project and we try to use the effetely. Therefore whatever
situation happen or occurred that hinder during the progression of the project the team try
to select the best option to do what expected and reform it. Risk analyses are to solve the
above problems that have used different techniques for protecting the data from infection.
The methods include:-
 Making copies in CD-ROM, Flash, other materials for computer failure
 System Failure: to solve this problem the workers must take backup file by using
external hard drive daily.
 Power Failure:-when power failure occurs the organization must use a backup
generator.
 By updating the antivirus software.
1.10 Assumptions and constraints

Constraints are situations or uncomfortable conditions that restrict us from fully
achieving the Constraints goal of our project. The following are problems that hinder us
from successfully accomplishing our task.
Time:-since we start doing our project in the late manner, we can’t finish the work in this
short period of time because it requires enough time to do successful project
documentation and coding.

Technical problems: Our knowledge and experience towards project work is not such
enough for this reason we kill more of our time on studying and understanding some
references and supportive courses about project work.
1.10.1 Assumptions
 Every computer should have Ethernet connection.
 The users will have sufficient knowledge of computers.
 The users must know an English language properly.
1.11 Scheduling
Involves checking, if the project team can develop the proposed system with the time
allocated or not. Meeting project deadline may depend on the size the project team and
the availability of the key members of the user group.
Time line
Phase Start date End date
Information gathering 22/03/2011 30/03/2011
Planning phase 01//04/2011 20/04/2011
Analysis phase 21/04/2011 20/05/2011
Design phase 21/05/2011 30/05/2011
Implementation 01/06/2011 30/06/2011
Testing 01/07/2011 10/07/2011
Table 1: schedule

CHAPTER TWO
2.1. Introduction of the existing system
Senkele police college student information management system is currently uses a
manual system to view grade report, to submit student grade. Use MS Excel for calculate
and store student information. There is no well-organized database system in existing
system.
In this chapter overview of the existing system, overview of the proposed system,
functional and non-functional requirement of the system will be discussed.
The proposed system documentation involves the requirement elicitation, where the team
members gather requirements of the system from the customer. The project is intended to
advocate for the need of senkele police collage to use facilitated computerized police-
crime record management system. The project has got high involvement of users because
the approach employed is object oriented paradigm. As a result the team member
believed that the user will have the expected satisfaction of the service provided by the
police collage. The main purpose of studying the existing system is to develop a new
system which efficiently performs activities and solve the problems available in the
existing system.
The reason behind studying the existing system as follows
 To identify the existing system problems.
 To identify the scope and limitation of the new system.
 To know the business rules and constraints of the collage.
 To design the proposed system based on the boundary or the total activity of the
existing system of the department.
 To determine the system user requirement.
 To understand organizations facts, short & long term strategies, business values &
missions.
 To understand how work officially gets done in the organization this include
identifying:

 Terminologies, abbreviations, and acronyms used

 Policies& guidelines that describe the nature of the business
 Standards, procedural manuals and the work environment.
 It operates the sample business forms and reports
 Job description
2.1.1 Major players of the Existing system

The major players of the current system are:
Student: The student does not interact with the computerized system rather he/she
requests a service like: grade report, course information, registration and other services
from the registrar officer or from the department head.
Registrar officer: Registrar officer only interacts with some services at one
computer.particularly student registration, student course information registration and
student course grade information.
Teacher: Teacher only interacts with some services at one computer. Particularly
displaying student course result, student course grade calculation.
Interrogator: An interrogator investigates only new student health and records their
information then transfer this information to the registrar officer by a paper. Then the
registrar officer registers new student who are normal.
Department head: view all student information which is stored on the registrar and post
notice on the board for students of each department and generate paper based report for
director.
Director: view all student information which is stored on the registrar.
Registrar manager: View all student information which is stored on the registrar and
manage all issues of the registrar.
2.1.2 Functions / activities in the existing system

 Functions of student
 Registering course
 View grade report
 View posted assignment

 Submit assignment
 View course result
 Functions of Registrar officer
 Registering student
 Edit course information
 Edit student information
 Generate grade report
 Function of Teacher
 Post assignment
 View submitted assignment
 Displaying the course result
 Submit grade
 Edit grade
 Function of Interrogator
 Investigate
 Functions of department head
 View all student information
 Post notice on the board for students of each department.
 Generate paper based report for director.
 Functions of director
 Function of Registrar manager
2.1.3 Business rules

 The system does not continue if the student secure below 50 in more than three
subjects.
 If a student has course result below 50 in three courses it does not continue.
 To get the degree the student has to secure more than 50 in all subjects.

 Grade point for each course is calculated as credit hour multiply by marks
obtained by the student out of 100.
 If a student not fills registration slip on time she/he is not registered.
 User cannot access the system if they do not have authorization.
 Users must have username and password to login to the system.
2.1.4 Report generated in the existing system

Some reports are generated in the existing system. These reports are generated in the
form of files and forms.
In the existing system the report is generated as requirement for faculty of the senkele
police collage to monitor the students and instructors. The department head orders the
representative of the class to report attendance of the instructors. The instructor also
reports the daily attendance to the department. As we observed all these activities are
done manually and it is time consuming task.
2.1.5 Forms and other documents of the existing Systems

student Folder
Name of facility …………………………….. Date of Registration
(DD/MM/YY)…………………………..
MRN………………………………
Name………………………. Father Name………………………………………
Mobile Number……….. Email ID: ……………… City………..…
Date of Birth Day………… Month……………… Year……………..
Age………………
Address: Region…………………….. Woreda/Subscity…………………….
Kebele………………………. House_no………………………………

Master student Card(MSC)
MRN………………… Date of Registration
(DD/MM/YY)…………………….
Name…………………………. Father Name……………………..
Sex……………………………… Age………………………………
Mobile Number: ……………….Email ID……………….City………
Date of Birth Day……… Month…………….. Year………………..

Address Region………………………… Woreda………………….
Kebele…………………
House_no………………………………
Table 2: form of student
2.1.6 Bottlenecks of the Existing system

The bottlenecks of the existing system as follows:
 Absence of centralized system that performs each and every activity of the
society.
 No computerized system.
 It is time consuming process.
 It is difficult to manage or getting quick information about exact place where
 Student’s information placed.
2.1.6.1 Performance:
It is time consuming and less performance since every task is done manually and it
requires a long period of time to complete the task.
2.1.6.2 Information:
Redundancy of data because data is stored in paper and MS Excel the data may be record
or store many times. If someone want to find ones data it is difficult to capture the
correct data in short period of time because the data is stored manually.
2.1.6.3 Control and security:

The current system does not much secure or controlled because unauthorized user can
access or alter the data.
2.1.6.4 Efficiency:
Due to the manual operation most of the activities are easy to wastage of resources like
stationary materials, manpower, time etc. This makes the current system inefficient while
utilizing resources.
2.2 Practices to be preserved

Alternative Solution to solve the existing system Problems After analyzing the problems
in the existing system, our project team identified and evaluated the following alternative
solutions:
 Automating the system using computer software application to prevent form
decaying.
 Changing the manual system into desktop application to keep in good condition.
Analysis and the proposed new system
Analysis is evaluating the alternative solutions in terms of their advantages and
disadvantages.
Advantage:
 The new system can be implemented without changing the organization policy.
 Less cost and easy to install.
 The new system does not require more human power.
 Processing data with high speed.
 Data redundancy problem will be avoided with the proposed system.
Disadvantage:

 Have some features that will not be used and happened frequently such as
demotion, termination, manual tasks.
 Requires technical person to handle and manage the system.
 It does not address all the basic problems of the station rather focus on the
 The proposed new system based on the option analysis described above, we select
the first option that is developing an applications to be used by the collage.
2.3 The Proposed System

As previously mentioned in the statement of the problem, there are a lot of problems
associated with the current system of the senkele police system. To avoid all limitations
of the existing in the collage and make the operations and activities more accurate the
system needs to be computerized and should perform some of the activities online. The
aim of proposed system is to develop a system of improved facilities.
The proposed system can overcome all the limitations of the existing system.
The system provides proper security and reduces a wide range manual work.
2.3.1 Team composition

Team organization refers to how the group members are structured to do the
given project. To complete project successfully every task must be done by every
person of the group. As we know there is three type of Team organization;
Centralized-control team, Decentralized-control team and Mixed-control team
organization. We do not select Centralized-control Team organization because it
has problems like chief programmer(CP) overloaded, time usage ,single point of
failure, success depend on skill and ability of CP, size and complexity of the
problem and soon. For this reason we choose the Decentralized control Team
organization because of the entire members are at the same level, responsible to
do the project, job satisfaction, for reviewing each other’s work, reduce time
consumption and the member will fully knowledgeable.
We have organized our self (team member) in a decentralized way that every team
member communicates to each other in each topic. Every member of the group attends
On the discussion to do the project and share his/her idea freely from this we choose

decentralized team composition to do the project of web based student information

management system for senkele police collage. One student can communicate with other
six members.
This team composition is shown below in table
N0 Name ID No Responsibility(Duty)
1 Nuredin Abdumalik TBRT/0348/10 Data collector
2 Hassen Ahamed BRT/2146/08 Programmer and tester

3 Tasfaye Hika BRT/2243/08 Designer
4 Admasu Adugna BRT/2185/08 Data collector

5 Bulch Begna RT/2126/08 Data Analyzer
6 Galata Teshoma BRT/2289/08 Data Analyzer
Table 3: Team composition and their duty
2.3.2 Feasibility Analysis

Feasibility study is made to see if our project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study
lets us to see the future of the project and the usefulness. A feasibility study of our
systems proposal is according to its workability, which is the impact on the Senkele
Police Collage, ability to meet the user needs and effective use of resources. An analysis
and evaluation of a proposed project, is to determine if it is technical feasible, if it is
feasible within the estimated cost, and if it will be profitable. Feasibility studies are
almost always conducted where large sums are at stake. It also called feasibility analysis.
The main objective of the feasibility study is to test the technical, operational, legal and
economic feasibility of the new system. [14]

2.3.2.1 Operational feasibility

This is a standard that ensures interoperability to the benefit of the public in terms of
service quality. Our system will be operationally feasible and user friendly.
Operationally, our system will have capable of producing quick and qualitative services
for students and workers , so that to have immediate and satisfied services our system
will be more functional and acceptable to users because:
 It will be user friendly.
 It will provide better decision making.
 It will provide better service to the college.
 It will increase speed of activity.
The new system can be easily operated and accessed by the users who interact to the
system. It contains user friendly commands which leads users interact to the system
interfaces.
2.3.2.2 Technical feasibility

Does the necessary technology exist, does equipment’s exist? , can the user use the
system without or with less training? , the system that has been answering the above
listed question is said to be technically feasible.
It is the process of accessing the developed system by the organization. Technical
feasibility is the measure of practicality of the specific technical solution and the
availability of technical resources and expertise. Our system has all the necessary
technology and equipment like computer, connection and also users are knowledgeable
because student registered in the college must be grade ten and above so, they can use the
system without or with little trainings for this reason we can say that our system is
technically feasible
2.3.2.3 Economical feasibility

Economic feasibility is the process of identifying the financial benefits and costs
associated with the project being developed. Since this project is going to be
computerized system, there is reduction cost for material that used for manual operation

such as cost of paper and pen, save time and make comfortable working environment for
the users. Hence, our system will be economically feasible.
2.3.2.4 Political feasibility

It requires identifying the people that are going to be affected by the information system
to be developed and any power shifts it may bring within the organization.
Finding out what people affected by the IS think about it and how they will react is a part
of political feasibility. Our project will try as much as possible not to be a means to harm
anyone. The usage and application of the system will be in agreement to the basic rights
and polices of the government. So the proposed system is politically feasible.
2.3.2.5 Schedule Feasibility

Schedule feasibility is making sure whether the potential time frames and Completion
date can be met or not .The project team members expected the Project to be completed
on time without any delay.
Project plan Activities is the following:
Phases Activities and tasks Deliverables

Project planning Information gathering, Title approved, team
Team organizing, choose Composed
project title
Proposal writing Gathering information Proposal
about the title project
Requirement gathering Finding requirements for System Requirement
the new system, grouping specification
the requirements in similar
features
Requirement Definition / Deeply understanding Requirement analysis
Determination current system problems and documentation
and choose alternative
solutions to overcome the

problem, identifying
functional and non-
functional requirements to
address current system
problems, Designing
different artifacts of the
new system using object
oriented modeling tools
Business area analysis Studying the business rule Business rule
of the collage, understanding and
communicate with official documentation
leaders of the organization
to get information,
eliciting the requirements
from the users perspective
of the collage
Object oriented analysis Generally analyzing of the Object oriented

system according to object documentation/prelimi
oriented approach, design nary design
of different use case
System design In design sequence It gives the blue print
diagram, activity diagram, of the proposed
state chart diagram system.
Implementation Algorithm analysis, flow Implementation
chart modeling, testing
strategies
Table 4: Schedule Feasibility
2.3.3 Requirement of the Proposed System

A requirement is a feature that the system must have or a constraint that it must satisfy to
be accepted by the collage. This stage determines the need of everyone who will be the
user of the proposed system.

The following sections will introduce the numerous requirements of the system from the
point of View of different users and will introduce a number of decisions that have been
made regarding Implementation.
2.3.3.1 Functional requirement

Functional requirements are the intended/planned behaviors of the system. The functional
requirement is the study of what a system should be able to do our system used to
manage and process student data according to the rule & regulations of the college. The
new system provide services as functional requirement like modifying data (i.e. adding,
updating and deleting data) ,searching data of student, storing the data of student,
generate grade report of student and others.
The database of the system provides the following functionality:
Data entry: This is the functionality that data is entered to the systems. The system
serves different interface that can manage data entry mechanisms such as student
registration form, student grade result generation form etc.
Data processing: The system on input data provided the following data processing:
Student registration, verify the requested information, validate student information,
generate student grade report, allow student to submit assignment, provide the option
students to view grade report online, teachers able to submit student grade report, post
assignments online. [13]
2.3.3.2 Non Functional Requirements
Non-functional requirement is a requirement that specifies criteria that can be used to
judge the operation of a system. Non-functional requirements are often called qualities
which are expected from the system. Our project includes the following system
nonfunctional requirements associated with the new system:
Performance
Computer performance is characterized by the amount of useful work accomplished by a
computer system compared to the time and resources used.
User interface
The user interface of our system is displaying the overall information of system which is
the homepages. The developed system provides web application user interfaces that are
compatible browsers like Opera, Mozilla Firefox, Google chrome, etc.
And it will be friendly with any user.
Security and access permission
 The system support user name and password to authenticate.
 The system should give different privilege to protect interfering.
 The system administration must grant and revoke privilege of the user.
Backup and recovery
The system will back up all its information in to the server of organization server and, the
website will also be available in external storage devices like external hard disks.
Resources, usability, availability
The system consumes resource that required high processer speed both for server and
client and machine having more memory space as a server. We use computer, laptop,
disks, paper for layout and properly using them and protecting these resources from
damage. We use powerful mark-up languages which support graphical user interface
friendly. The proposed system can store any data inserted in to the system in appropriate
manner. The stored data can be kept in database permanently and can be retrieving easily
when the user accesses it from database.
 System allows only registered users to access clearance system and also
allows the users’ to view their own profile not the other users’ profile.
Usability: The system shall be very easy to learn, needs basic computer knowledge to
use and have a help menu to guide the user.
Availability: There is no delay in the availability of any information, whatever needed,
can be captured very quickly and easily. The server should be always on to be available

CHAPTER THREE
3.1 Introduction
The purpose of modeling is to determine how the system is going to build and to obtain
the information needed to drive the actual implementation of the system. It focuses on
understanding the model how the software will be built. In order to make the
implementation easy the design is very essential. The project development team used an
object oriented system Analysis and development methodology. [9]
Because the Object system development approach gives easier and natural way to break
down problems into simple, small and manageable components so that it reduces the
vague appearance of the big problem. Moreover, it is predominately used and popular
method in present software development trend. The major activities described in this
chapter are system requirement specification, constructing a use case diagram; use case
description, constructing sequence and activity diagram analysis level class diagram and
user interface prototype about the proposed system.
3.2 System requirement specification
The objective of this phase is to develop the requirement specification and analysis as it
started from last section by using the information planned. The requirement specification
is the phase that leads to the designing and implementation, that the correct and accurate
designing has a great role to the system implementation.
Under this system requirement specification we can describe the use case identification
and use case diagram.
3.2.1 Use Case model
Use case diagrams show the various activities the users can perform on the system. A use
case diagram illustrates a set of use cases for a system, actors of the use cases, the
relations between the actors and these use cases, and the relations among the use cases.
 An oval shape 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.
3.2.1.1 Actor and Use Case Identification

An actor represents a type of users of the system or external systems that interacts with
the system. Actors that interact with our system are:
 Student
 Teacher
 Admin
 Department Head
 Interrogator
 Registrar Officer
 Director
 Registrar Manager
ID Use Case Name Include/use Actor involved
UC1 Login Student, Registrar officer
,teacher, registrar manager
admin,, Department
head, director, interrogator
UC2 Register course information UC1 Registrar officer
UC3 Edit course information UC1 Registrar officer
UC4 Register in course UC1 Student
UC5 Enter(record) course result UC1 Teacher
UC6 View course result UC1 student
UC7 Submit grade(result) UC1 Teacher
UC8 Send grade change Request UC1 Teacher
UC9 Register submitted grade UC1 Registrar officer
UC10 Approve grade submission UC1 Department head
UC11 View grade report UC1 Student
UC12 Create account UC1 Admin, Department head,
registrar manager
UC13 Block account UC1 Admin, Department head,

registrar manager
UC14 Print grade report UC1 Registrar officer
UC15 View account UC1 Admin, Department head,
registrar manager
UC16 Register student information UC1 Registrar officer
UC17 View registered student Director, department head,
information UC1 registrar manager
UC18 Register students health UC1 Interrogator
information
UC19 Assign course UC1 Department head
UC20 post notice UC1 Director, registrar manager,
Finance manager,
department head
UC21 View notice UC1 Student, Registrar officer,
teacher,
admin, ,Department, head,
director,interrogator,regisrar
manager
UC22 View graduate student UC1 director, department head,
registrar manager
UC23 Approve grade change request Department
Head
UC24 View log file admin
UC25 Logout Student, Registrar officer,

teacher, admin ,Department
head, director, interrogator,
registrar manager
Table 5: Use Case and Actor Identification

Create account
Admin
View account
Dept head
Block account
Reg manager
Figure 1: Manage account essential use case

3.2.1.2 System Use Case
Web Based IMS for Senkele Police Collage

Register in Approve
course grade
View assigned
View course
notification
View grade «uses» Approve grade

View course Dept head
report «uses» change request
«uses» «uses»
student «uses» «uses»

View course «uses» Assign course Manage account
Post notice
result
View notification «uses» «uses»
«uses»
«uses»
«uses»
View submitted
grade Login View student
View assigned Reg manager
course
«uses» «uses» «uses»
Submit grade
«uses»
Teacher «uses»
Record course «uses» View log file
Send grade result «uses»
change request
«uses»
Restore database Director
«extends» «uses»
Register Register
student «uses»
department
Register Take database

Edit course course backup
information
Print grade
Reg officer Edit student report Register user
information
Admin
Record student
Logout health infornation
View
course
Interrogator
Figure 2: System Use Case

3.2.1.3 Use Case Description

Use case name Login
ID UC1
Actor Student, Registrar officer, teacher, admin

,Department
head, director, Finance manager, interrogator

,registrar manager
Description Users are authenticated and taken to their own

user page.
Pre-condition Users know his/her user name and password.
Post condition User is authenticated and taken to his/her own

user page
Basic course of action 1. The user opens the main home page.
2.the system display the Main Home

page(login page)
3. The user inputs user name and password and

submits
4. The system validates the account.
5. The user login into his/her page.
6.use case ends
Alternative course of action  If the login name or password is

invalid
 The system displays invalid user name

or password message.

 The use case continues from step 3 to

step 6
Table 6: Login Use Case Description
Use case name Register student information
ID UC16
Actor Register Office
Description The Registrar officer register student
Pre-condition The Registrar officer login to the system using

his/her user name and password
Post condition Student are registered
Basic course of action 1. The user opens the main home page.
2. the system display the Main Home

page(login page)
3. The Registrar officer enters user name

and password and click login button.
4. The system validates user name and

password.
5. The system displays the Registrar

officer page.
6. Click on Register student tab on the

menu.
7. The system displays student register

form.

8. Fill all the information at the form and

submit the form.
9. The system validates the information.
10. The system displays success message
11. End of use case.
Alternative course of action  The system displays error

message.
 The use case continues at step

3
Table 7: Register Student List Use Case Description
Use case name Create account
ID UC12
Actor Admin, Department head, registrar manager
Description Admin, Department head, registrar manager creates account for an

suitable user of the system
Pre-condition Login to the system using his/her user name and password
Post condition Users get his/her account.
Basic course of action 1. Admin, Department head, registrar manager opens the main
home page.
2. the system display the Main Home page(login page)
3. Admin, Department head, registrar manager enters user name

and password and click login button.
4. The system validates user name and password.

5. The system displays Admin, Department head, registrar

manager page.
6. Click on create account button.
7. The system displays create account form.
8. Fill all the required information at the form and submit the
form.
Alternative course of  If login detail is incomplete or mismatch at step 3.

action
 The system displays error message.
 The use case continues at step 3.
 If the information is incomplete at step 9.
Table 8: Create Account Use Case Description

Use case name Submit grade
ID UC7
Actor Teacher
Description Instructor submits student grade to Registrar officer and department

head.

Pre- condition The teacher login to the system using his/her user name and password
Post condition The teacher Easily submit student grade
Basic course of action 1. The teacher opens the main home page.
3. The teacher enters user name and password and click login
button.
5. The system displays teacher page.
6. Click on submit grade link.
7. The system displays submit form.
8. The teacher Fill all the required information at the form and
submit the form.
 If login detail is incomplete or mismatch at step 3.
Table 9: Submit Grade Use Case Description

Use case name Register course information
ID UC2
Actor Registrar officer
Description The Registrar officer can register course information the student take.
Pre- condition Registrar officer should log onto the system
Post condition Course information is registered
Basic course of 1. The Registrar officer opens the main home page.
action
3. The Registrar officer enters user name and password and click
login button.
5. The system displays Registrar officer page.
6. Click on register course information link.
7. The system displays the form.
8. The Registrar officer Fill all the required information at the form
and submit the form.
Alternative  If login detail is incomplete or mismatch at step 3.

course of action  The system displays error message.

Table 10: Register Course Information Use Case Description

Use case name View registered student list
ID UC17
Actor Director, department head,
Description Director, department head views registered student list
Pre-condition student should be registered on the database and actors log
onto the system
Post condition Director, department head, can views registered student list
Basic course of 1. Actor opens the main home page.

action
3. Actor enters user name and password and click login button.
5. The system displays actor’s page.
6. Click on view registered student link.
7. The system displays registered student list
8. End of use case.
Alternative course  If login detail is incomplete or mismatch at step 3.

of action  The system displays error message.
Table 11: View Registered Student List Use Case Description

Use case name Edit course information
ID UC3
Actor Registrar officer
Description The Registrar officer can edit course information in case if there is mistake
or if update is necessary.
Pre-condition course should be registered on the database and actors log onto the system
Post condition Course information is edited.
Basic course of 1 The Registrar officer opens the main home page.
action
3. The Registrar officer enters user name and password and click login
button.
5. Click on edit course information link.
6. The Registrar officer Fill all the required information at the form and
submit the form.
8.The system displays success message
9. End of use case.

of action

Table 12: Edit Course Information Use Case Description

Use case name Register in course
ID UC4
Actor Student
Description Student in each term should register.
Pre-condition Course should register and student has valid user name and
password.
Post condition Student are registered in course.
Basic course of 1. The student opens the main home page.

action
3. The student enters user name and password and click login
button.
5. The system displays student page.
6. Click on register in course link.
7. The system displays form.
8. The student Fill all the required information at the

form and submit the form.


of action
Table 13: Register In Course Use Case Description

Use case name Register students health information
ID UC18
Actor Interrogator
Description An interrogator investigates new student health and physical

appearance.
Pre-condition An interrogator should have valid username and password.
Post condition An interrogator registers new student health information.
Basic course of 1. Interrogator opens the main home page.

action
2.the system display the Main Home page(login page)
3. Interrogator enters user name and password and click login

button.

5. The system displays Interrogator page.
6. Interrogator Click on investigate link.
7. The system displays the form.
8. Interrogator fills student health information at the form and

submits the form.
10 .the system displays success message

of action
Table 14: Register student’s health information Use Case Description
3.2.1.4 Scenarios
Construct description Syntax

A sequence of action
including the function that
system can perform to Use case name
Use case interact with use case of
the system
Actor A sequence of action

including the function that
system can perform to
interact with actor of the
system
Actor name
System boundary Represents boundary

between physical system
and the actor who interact
with the physical system
Association The participation of actors

in use case that is instance
of actor and instance of use
case communicate with
each other
Extended The relationship from an

extension use case to base
use case specify how the

behavior for extension use
case can be inserted into
behavioral defined for the
base use case.
An extend relationship
between two use case
<<extend>>
indicates alternative
behavior.
Use or include A relationship from use

case to an inclusion use
case specifying how the
behaviors use case for the <<include>>
inclusion uses case inserted

to the behavior for the base
use case. <<uses>>
An include relationship
between use
Cases indicate where one

use case always includes
the behavior of another.
Table 15: Scenarios

3.2.2 Object model

An object model defines a hierarchy of objects that gives structure to an object-based
program. By defining the relationships between objects that are part of the program, an
object model organizes the objects in a way that makes programming easier.
The public object model of a component is especially important because it’s used by all
the programmers who employ the component as part of their applications.
3.2.2.1 Class Diagram
Analysis Class diagrams are:
UML class diagram static model show the classes of the system, their inter-relationships,
and the operations and attributes of the class that remain constant over the time. The
project team develops the following class diagram.
 A class describes a set of objects with similar structure, behavior, and

relationships.
 A binary association is a relationship between exactly two classes.

1
view
teach
Student *
1..* Result Course
-Region Department
-Result id -Module code 1..*
-Zone -Id has
-Year * -module code -Module title 1
-Name
-Semister * -user id -Chr
-CH * 1 Teacher
-Section
inherit *
-register in course()
inherit User
-view grade report() * -Record course result()
* Request
-view course result() -User ID -Submit grade()
-Notification() account -Fname -Rid 1
-view assigned courses()
-User name -Mname -Content -View submiited grade()
* -Password -Lname -User_id -View notification()
1..*
* -Role 1..* -date -send grade change request()
+Login()
* -Status +View Notice() send
Registeral officer
inherit +Logout() 1..*
inherit
1..*
-View student() view Director 1
*
-Register student() 1..* inherit inherit
-Register course()
-View student()
-Edit course information() view inherit
Admin -Post notice() approve
-Edit student information() 1
-Register department()
-View course()
Registeral Manager -register user()
-Print student grade report() 1 -create account()
-block account()
1 -View student() -view account() view
Notice Department Head -create account() -take database backup()
-ID -Block account()
inherit -restore database()
-Date -View account() -view log file()
1..* -Approve grade()
-Title -Post Notice()
-approve grade change request()
-content
-Assign course() Repons
-expired date
-View course()
* -View assigned course() * -Res_id
view-Content
-Post notice()
-Create account() send -User_id
* - *
1 -Block account()
-View account() 1 *
-View student()
post
investigate *
1 Interrogator
1 -Record student health information()

*
Figure 3: Analysis Class Diagram

Design Class Diagram is:
Class diagrams model is the static structure of a system. Class diagram provides an
overview of the target system by describing the objects and classes inside the system and
the relationship between them. [15]

3.2.2.2 Description of Design Class Diagram

Describing class model is used to document the detail about a class as well as the
reasoning behind any trade off .The following are the descriptions of the class model for
the student information management system.
Attribute Purpose Data type

ID Used as user unique identifier Varchar(15)
Fname Represent Name of user Varchar(20)
Mname Represent users father name Varchar(20)
Lname Represent users grandfather name Varchar(20)
Sex Represent gender of the user Varchar(10)
Age Represent age of the user Int
Method Purpose
View notice() Used to view the posted notices.
Login() Use to log into the system.
Table 16: Design Class Description for User

Department Represent in which department the student study. Varchar(20)
Region Represents the region the student Varchar(20)
Zone Represents the zone the student Varchar(20)
Year Represents the year of the student Varchar(10)
Status Represent the status of the student Varchar(10)
Academic year Represent the academic year in Ethiopian calendar. Date time
Year Represent academic year of the student Varchar(10)
Semester Represent at what term is the student study Varchar(10)
Method Purpose
Registered in course() Used to register on course

View grade report() Used to view students grade report

View posted assignment() Used to view posted assignments.
Submit assignment() Used to submit assignment.
View course result() Used to view result of each course.
View dormitory() Used to view dorm they assigned.
Table 17: Design Class Description for Student Class
Method Purpose
Post assignment() Used to post assignment
View submitted assignment() Used to view submitted assignment
register course result() Used to register course result
Submit grade() Used to submit grade
Edit grade() Used to edit grade
Table 18: Design Class Description for Teacher
Method Purpose
Investigate() Used to register students health information
health
Table 19: Design Class Description for Interrogator

Method Purpose
manage report() Used to post, edit and view report
post notice () Used to post notice.
View registered student() Used to view registered student
View graduate student() Used to view graduate student
Table 20: Design Class Description for Director Class

Method Purpose
Register student () Used to register student
Register course() Used to register course information
Edit course information() Used to edit course information
Edit student information() Used to edit student information
Register dormitory() Used to register dorm
Generate grade report() Used to prepare student grade report.
Assign dormitory() Used to assign dorm to student
Table 21: Design Class Description for Registrar Officer Class

module code Used to a unique identifier for course. Varchar(20)
module title Used to represent title for course Varchar(10)
credit hour Represent credit hour of the course Integer
Table 22: Design Class Description for Course Class

User name Uniquely identify the user to enter the system Varchar(20)
Password Used to enter to the system Varchar(20)
Role Represents privileges of the user Varchar(20)
Status Represents status of the user Varchar(8)
Table 23: Design Class Description for Account Class

Database Design
Database design is a collection of processes that facilitate the design, develop,
implementation and maintenance of enterprise data management systems.
3.2.3 Dynamic model
The dynamic model describes the behavior of a distributed parameter system in terms of
how one qualitative state can turn into another.
3.2.3.1 Sequence Diagram
A UML Sequence diagram shows the sequence of interactions among objects and used to
represent or model the flow of messages, events and actions between the objects or
components of a system. Generally, a sequence diagram shows object interactions
arranged in time sequence.
 An activation shows the time period during which an object or actor is

performing an action.
 An object lifeline represents the existence of an object at a particular time.
 A message is a communication between objects that conveys information

and results in an action.

user system login page Login controller User page database
1.open()
2.enter UN&PW
3.validate form()
4.validate()
5.error
6.load data()
8.check
9.error
10.display()
Figure 4: Login Sequence Diagram

Registrar Registrar Registration Register

database
officer Officer page controller
form
1.open(0
2.click registrartion link

3.display()
4.fill form()
5.validate form()
6.error
7.click register button()
8.check ()
10.error measage
9.if false
12.success measage
11.if true
Figure 5: Student Registration Sequence Diagram

student Student page search form view controller database
1.open()
2.click account link

3.display()
4.fill search form() 5.validate form 6.validate()
7.error
8.click view button()

9.check data()
11.unsuccess measage()
10.if false
13.display grade()
12.if true
Figure 6: View Grade Report Sequence Diagram

3.2.3.2 Activity Diagram

Activity diagrams are used to document the logic of a single operation/method, a single
use
Case or the flow of a business process. It includes modeling the sequential process.
 A simple transition is a relationship between two states or action states or

between a state and itself.
 A decision must have one or more incoming transitions and two or more
outgoing transitions.
 A control flow represents a relationship between two states or action states

and indicates that an object in the first state will enter the second state and
perform specified actions.
 An action state is a type of state that has an internal action and at least one
outgoing transition that involves the explicit events that complete the internal
action.

open the system
system displays login form
Enter user name

And password Click login button
/ fales
/ true
system display user page
Figure 7: Login Activity Diagram

open the system
Enter user name

And password click login button
/ invalid
/ valid
System display user page
Click view student link
System display students list
Figure 8: View Registered Student List Activity Diagram

open the system
Enter user name

And password click login button
/ invalid
/ valid
System display the registerar page
Click register student link
System display the form
Click register button

fill the form
/ invaild
System display success message
/ valid
Figure 9: Register Student Activity Diagram

3.2.3.3 State chart Diagram

State chart diagram shows the change of an object through time from one state to the
other state. State chart modeling is used to show the sequence of states that an object goes
through, the events that cause the transition from one state to the other and the actions
that result from a state change.
State chart diagram describes the flow of control of the proposed system from one state to
another state to describe the system dynamically. States are defined as a condition in
which an object exists and it changes when some event is triggered. [5]
open
loginPage
click Login
Click button of login

Select tpype of user & Enter PW & UN
Invalid
Valid
UserPage
Action Perform & Go to logout
Press
LoginPage LogOut
Close
Figure 10: State chart diagram for login

open the system
Click helppage
/ invalid Press read more Enter username and passward
/ valid
System display student link
Click student link
The system dispilay student link result
Figure 11: State chart diagram for help

3.2.4 User Interface Design

A user interface, also called a "UI" or simply an "interface," is the means in which a
person controls a software application or hardware device. A good user interface provides
A "user-friendly" experience, allowing the user to interact with a computer.
HOMEPAGE
HOME ABOUT US CONTACT US NOTICE FEEDBACK LOGIN HELP
ADDRESS TO
VISSION
CONTACT SYSTEM
ADMINISTROTE
R LINK
SEND GRADE VIEW VIEW

VIEWSUBMITE RECORD
CHANGE SUBMIT GRADE APPROVED ASSIGNED NOTIFICATION
DMARK COURS RESULT
REQUEST GRADE COURSE
Figure 12: User Interface Diagram

CHAPTER FOUR
SYSTEM DESIGN
4.1 Introduction
The purpose of designing is to show the direction how the web page is built and to obtain
clear and enough information needed to drive the actual implementation of the system. It
is based on understanding of the model the webpage built on.
System design is the transformation of the analysis model into a system design model.
System design is the first part to get into the solution domain in a software development.
This chapter focuses on transforming the analysis model into the design model that takes
in to account the functional requirements and constraints described in the problem
statement and requirement analysis sections discussed earlier.
The objectives of design are to model the system with high quality. Implementing of high
quality system depend on the nature of design created by the designer. If one wants to
change to the system after it has been put in to operation depends on the quality of the
system design. So if the system is design effectively, it will be easy to make changes to it.
Generally, this phase describes how the project is designed, what tasks done under this
project. [9]
4.1.1. Purpose of the system
The major purpose that the new proposed system to provide the following: -
Reduce the work load: this system manages the information in the senkele police
collage this reduce the work load in the college.
Improve the time wasting: The users of the proposed system can use the system using
their electronic device this reduce the time wasting at the college.
Performance: The performance of the proposed system provides fast response time
because it is easy to access data from the stored document.
Efficiency: The web based system by itself is short and clear and in this system there is
no duplication of data through the new system so it is powerful to manage things around

student information. The new system does not require more human labor, processing data
with high speed and short hand form.
4.1.2. Design Goals

The objectives of designing are to model a system with high quality. Implementing of
high quality system depends on the nature of the design created by the designer if one
wants to make changes to the system after it has been put in to operation depends on the
quality of the system design. So if the system is designed perfectly, it will be easy to
make changes to it. The goal of the system design is to manage complexity by dividing
the system in to manageable pieces. Some of the goals are listed below.
Security: The system should be secured from unauthorized user. [11]
Modifiability: The system should be modifiability to modify different services
depending on the need of the institute.
Flexibility: The system able to change to suit new condition or situation.
Efficiency: The system must do what it is supposed to do efficiently without the
problem.
Performance: The system should respond fast with high throughput
Reliability: System should be reliable to increase user’s confidence.
Usability: Usability is the extent to which a product can be used by specified users to
achieve specified goals with effectiveness, efficiency and satisfaction in a specified
context of use. From the end users’ perspective, the system should be designed in such a
way that it is easy to learn and use and efficient.
4.2. Current Software Architecture
 Currently there is no software architecture for Web based student information
Management System for college.
 The current system is a paper based system that is outdated and unorganized.
 There is no full computerized system for handling the data to delivers the
information of college as well as manages student.

 In order to handle or process the data for above mentioned categories of tasks
there is the manual system that is deployed within the Excel. The description is
disclosed as follows.
 Register to the manager office in manual way and then the manager keeps the
queue of the applicant and sends applicant data to them as documented in paper or
using calling on their phone. Whenever each employee generates and report on
the paper and as well as to identify data of student and status and search to
identify them.
4.3. Proposed software architecture

The proposed system of student information management system is the right software
to be incorporated into the computerized of the system for helping the organization needs
with respect to skillful Human Resource. The proposed system uses three-tier
architectures to design our system. Because 3-tierArchitecture increases performance,
flexibility, maintainability, Reusability, and scalability while hiding the complexity of
distributed processing from the users/clients.
The data Layer maintains the applications data such as student data, administrator data,
and result data. The middle layer (web/application server) implements the controller logic
and business logic to control the interaction between the application’s clients and data.
The controller logic processes client requests such as requests to view student result, to
retrieve data from the database. The business logic dictates how clients can and cannot
access application data and how applications process data.
A web server is a program that runs on a network server (computer) to respond to HTTP
requests. HTTP is the standard protocol for transfer data across the internet. The client
layer is the applications user interface containing data entry forms and client side
applications. It displays data to the user.
The client layer interacts with the web/application server to make requests and to retrieve
data from the database. It displays the data to the user.

4.3.1 Overview
The proposed system is expected to replace the existing manual system by web based
system. The proposed software architecture used for the system is a 3 tier Client/Server
Architecture. Those are
The database tier: The main purpose is to store a data entered by a user. It waits
requests from client or server and display the requested item or information.
A web server program: Its main purpose is to serve the web pages; which mean it waits
for requests from web browsers (also known as clients) and responds by sending the
required data back to the clients. The team uses the famous and popular server side
software called Apache.
The client tier: is the applications user interface containing data entry forms and client
side applications. Users interact directly with the application through user interface. The
client tier interacts with the web/application server to make requests and to retrieve data
from the database and displays the data to the user.
4.3.2 Subsystem Decomposition
In this proposed system we break down the system into its components subsystems,
analyzing separately and then aggregating them back into complete system. The
following are the sub systems that are derived from the functionality of the system.
Register sub system: In this sub system the student register in to the system in two
ways. The first way is the student register online and the other one is the student go to
college then the administrator register the student.
Search password sub system: In this sub system the users can change their account
password.
Post news sub system: In this sub system the administrator posts new health news.
Manage information sub system: In this sub system the administrator insert/delete the
information’s stored in the database.

4.3.3 Hardware and software mapping

In this section the team put down the overall hardware and software organization of the
system. One of the major task in system design deals with hardware/software mapping.
This deals with which components would be part in which hardware and so on. Our
proposed system has a physical connectivity to database server.
Hardware Mapping
The hardware tools to be used for transportation management system in this project
include.
 Personal computer,
 Computer server,
 CD,
 Flash, etc.
Software mapping
Software Mapping is defined as the use of the software in the system at the time of
development. The system uses
 Microsoft Windows 10 Operating System.
 HTML, PHP and JAVA Script to design the system.
 Microsoft Office 2007 for documentation purpose.
 Xampp Server and MYSQL to store data into the database.
4.3.4 Persistent data management
Persistence data modeling is a model that is used to communicate the designer of the
database, usually a relational database, to both user of the system and another developer.
Also it enables to design the schema of the database.
Persistence are used the schema of database. The strength of persistence data models is
that data entities are conceptually the same as the table of relation data base and that
attributes are the same as table columns.

1
view
teach
Student * Course Department

1..* Result
-Region:varchar(56) -Module code:varchar(16) -DId:varchar(24) 1..*
-Zone:varchar(76) -Result id
-Module title:varchar(100) -DName:varchar(56)
-Year:varchar(24) * -module code has
-Chr:varchar(12) 1 *
-Semister:varchar(24) * -user id *
-CH:varchar(12) 1
-Section:varchar(12) Teacher
-register in course() inherit inherit
-view grade report() * * User -Record course result()
-view course result() account -User ID:varchar(34) Request -Submit grade()
-Notification() 1..* -Fname:varchar(56) -view assigned courses() 1
-User name:varchar(56) -Rid:int
-Mname:varchar(56) -View submiited grade()
* -Password:varchar(100)
1..* -Content:text
-Lname:varchar(56) -View notification()
* -Role:varchar(56) -date:date time
+Login() -send grade change request()
-Status:varchar(25)
* Registeral officer +View Notice() send
+Logout() 1..*
inherit inherit
1..*
-View student() view * Director 1
-Register student() 1..* inherit inherit
-Register course()
-View student()
-Edit course information() view inherit
Admin -Post notice() approve
-Edit student information() 1
-Register department()
-View course()
Registeral Manager -register user()
-Print student grade report() 1 -create account()
-block account()
1 -View student() -view account() view
Notice Department Head -create account() -take database backup()
-NID:int -Block account()
inherit -restore database()
-Date:date time 1..* -View account() -view log file()
-Approve grade() -Post Notice()
-Title:text
-approve grade change request()
-content:text
-Assign course() Repons
-expired date:date taime
-View course()
* -View assigned course() * -Res_id:int
view
-Post notice() -Content:text
-Create account() send -User_id:varchar(24)
* - *
1 -Block account()
-View account() 1 *
-View student()
post
investigate *
1 Interrogator
1 -Record student health information()

*
Figure 13: Persistent data Diagram
4.3.5 Access control and security

The project is multi-user system and has different authority in the system. In this project
the users of the system must be identified, and authorized before having access to the
system’s services. Deleting, registering searching and inserting information of the
student. Only certain activities are permitted for authorized once controlled by the
system.

Users will have their own password and username through which they could gain access
the system. The password with which user are provide will protect them from student
threats, who could be jeopardizing their responsibility. Our system protects any
confidential information of the student as well as the student from unauthorized users by
verifying their user names and passwords. All actors, administrator, department head,
student can access the system based on their validation.
Actors Admi teache interrogato Departmen director Reg Reg

n r r t head manag officer
er
Taxes
Yes yes Yes yes yes yes yes
Login
No no No yes yes yes yes
View
student
No no No yes yes yes No
Post
note
Yes no No yes No yes No
Manage
account
yes No yes No no No
View
course
View yes N0 no No no No
notificat
ion
Yes Yes Yes yes yes yes yes
Logout
Table 24: Access control table

4.3.6 Global Software control

The senkele police college is to have an explicit, centralized software control. The
system's dynamic control is distributed among different controllers such that each object
delegates some responsibility to other objects. The request initiations are event-driven:
 The Manager initiates the UI Subsystem by logging into the system.
 The Main Subsystem initiates the employee subsystem by checking the
availability and notifying of the Response.
 The Database Subsystem can be initiated at any point by all Subsystems
except the UI Subsystem.
 Any request (add or update) to the repository initiates the DBase Subsystem.
 The system stores its contents in the database between executions. When the
application is run again, it retrieves the contents from the previous execution.
 Any change in the contents during this execution updates the database.
4.3.7 Boundary condition
Startup: go to system URL and login.
Shut Down: click log out and close browser.
Error Conditions:
 Logging in:
 Username or password field can be blank.
 Password is not 8 characters long.
 Password and username don’t match.
 Username is wrong or does not exist.
 User settings
 User is unable to change certain settings or changes don’t
reflect.
 Between the time of editing and updating, the system
crashes.
 Data Entry

 The system is fail when the manager is entering

information.
 Product availability
 There is no available product.
 Monitor display
 The system crashes or the backup also crashes.
 The system hangs up.
 The desktop application may fail up.
 Relative searching for a customer or product.
 Search criteria do not return any results.
 Logging out: Manager unable to logout.
4.4 Subsystem services
Subsystem services are services which are performed in each subsystems. Those
subsystems services are described each individually as below
student: A person who is using a web browser to access Database student police college
(DBSPC) web page to get service from the organization and responsible to apply
registration, view massage, order maintenance.
Department head: view all student information which is stored on the registrar and post
notice on the board for students of each department and generate paper based report for
director.
Director: view all student information which is stored on the registrar.
Registrar manager: View all student information which is stored on the registrar and
manage all issues of the registrar.

Chapter Five
Implementation and Testing

5.1 Introduction
Implementation refers to the coding of the all documents gathered starting from
requirement analysis to design phase. So now the team is in a position of converting all
documents gathered and designed into the code so that the system will be implemented
for the user to be used for the purpose it developed. The Implementation phase in the
software life-cycle is where the actual software is implemented. The result of this phase
consists of source code, together with documentation to make the code more readable.
This is what we call software implementation. The purpose of these activities is to
convert the final physical system specification into working model with reliable software
and hardware, document the work that has been done, and provide help for current and
future users and take care of the system. [6]
 After implementing the system, it must be tested.
 Testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step
in the software process that could be viewed as destructive rather than
constructive.
 A strategy for software testing integrates software test case design methods into a
well-planned series of steps that result in the successful construction of software
 Testing is the set of activities that can be planned in advance and conducted
systematically.
 The underlying motivation of program testing is to affirm software quality with
methods that can economically and effectively apply to both strategic to large and
small-scale systems. in this, coding, testing, installation and training etc.
5.1.1 Final Testing of the System

The tests will allow us to ensure correct program flow, and to determine the error-
handling capability of the system. As each program module is produced, it can be tested

individually, as part of the larger program, and then as part of larger system. Once code
has started, the testing process can begin and proceed in parallel. The tests will allow us
to ensure correct program flow, and to determine the error-handling capability of the
system. The following are different testing strategies.
Unit Testing
Unit test is a way of testing each of the system functionality independently. Accordingly,
the team has tested each one of the three major activities and the rest accompanying
activities independently using different user input, different login mechanisms and any
technique of fault finding so that an incorrect functioning of the activities was corrected
at the right time. To identify coding errors and omissions in the application components
and modules. Every module of the System is separately tested. I.e. the team tests every
module by applying some selection mechanism. If an error occurs correction will be
taken without affecting another module.
Test Case = TestCase1
Unit to Test = Authentication of login users
Assumptions = Login into appropriate page
Test Data =Username (empty, invalid username,

valid username)
Password (empty ,invalid password, valid

password)
Steps to be Executed Data Expected Results
Select incorrect
Username, password and
Click Login button “problem occurred”
Username =hase
Password=123 Please check your entry (enter
correct user email and
password)

Select empty username Username---------------

and Password is correct
and Click Any valid data for the “user’s email is empty” (please
other fields fill out these filled)
Login button
invalid username but
correct password and
Click Login button “invalid email”(error occurred
User name=hdufbudf
check your entry)
Select invalid username, All fields Fulfill with “problem occurred check your
and incorrect Password invalid data entry(invalid username and
and Click password please select a
Login button correct user name and
password”)
Select a valid username, All fields Fulfill with “it displays/shows the
and Password and Click valid data appropriate page”
Login button
Table 25 : Test Case for Login
Unit to Test = Authentication of View Grade

Report users
Assumptions =View Grade Report into appropriate
page
Test Data =Student ID (empty, invalid Student ID,

valid Student ID)
Year (empty ,invalid year, valid Year)

Semister ( empty ,invalid Semister, valid Semister)

Select incorrect Student

ID, Year, Semister and
Click View button Student ID =Tbrt/0231 “problem occurred”
Year=2
Semister= 1 Please check your entry (enter
correct Student ID, Year and
Semister)
Select empty Student ID, Student ID --------------
Year and Semister is
Year ……. “Student ID is empty” (please
correct and Click
View button fill out these filled)
Any valid data for the
other fields
invalid Student ID but
correct Year, Semister Student ID =
and Click View button Tbrt/0231 “invalid Student ID”(error
Year =1 occurred check your entry)
Select invalid Student ID All fields Fulfill with “problem occurred check your
,Year and incorrect invalid data entry(invalid Student ID ,Year
Semister and Click And Semister please select a
View button correct Student ID ,Year and
Semister”)
Select a valid Student ID All fields Fulfill with “it displays/shows the
, Year and Semister and valid data appropriate page”
Click View button
Table 26 : Test Case for View Grade Report
Unit to Test = Authentication of Register users
Assumptions = Register into appropriate page
Test Data =User ID ( empty, invalid ID, valid ID)
Test Data =Fname (empty, invalid Fname, valid

Fname)

Test Data=Lname (empty ,invalid Lname, valid

Lname)
Test Data=Department (empty ,invalid Department,

valid Department)
Test Data=Gender (empty ,invalid Gender, valid

Gender)
Test Data=Age (empty ,invalid Age, valid Age)
Test Data=User Role (empty ,invalid User Role,

valid User Role)
Test Data=Email(empty ,invalid Email, valid

Email)
Select incorrect| Fname , Fname=NURA

Lname, Department, Sex, Lname=TESFA
Age, User Role And Department= CS “problem occurred”
Email and Click Register
button Sex =male Please check your entry (enter
correct User Role and Email)
Age=20
User Role =Admin
Email=
nura@gmail.com
Select empty Fname , Fname---------------
Lname, Department, Sex,
Age, User Role And Lname--------------- “user’s email is empty” (please
Email is correct and Click Department-------------- fill out these filled)
Register button
Sex---------------
Age---------------
User Role…………….
Email---------------


other fields
invalid Fname And

Lname, but correct Fname=hdufbudf
Department, Sex, Age, Lname=hdufbudf “invalid email”(error occurred
User Role, Email and Department= Cs check your entry)
Click Register button
Sex =male
Age=20
User Role =Admin
Email=
nura@gmail.com
Select invalid Fname, and All fields Fulfill with “problem occurred check your
Lname incorrect invalid data entry(invalid Fname, Lname
Department, Sex, Age, Department, Sex, Age, User
User Role, Email and Role And Email please select
Click a correct Fname, Lname
Register button Department, Sex, Age, User
Role And Email”)
Select a valid Fname, All fields Fulfill with “it displays/shows the
Lname, Department, Sex, valid data appropriate page”
Age, User Role, And
Email and Click
Register button
. Table 27 : Test Case for Register User
Test Case = Test Case 4
Unit to Test = Authentication of Block Acount

users
Assumptions = Block Acount into appropriate
page


valid username)
User role (empty ,invalid User role, valid User

Role)
Select incorrect
Username, User role and
Click Search button “problem occurred”
Username =hasu
User Role= nura Please check your entry (enter
correct user name and User
role)
Select empty username Username=hase
and User role is correct
and Click
Any valid data for the “user’s name is empty” (please
other fields fill out these filled)
Search button
correct User Role and
Click Search button “user name”(error occurred
User name=hasu
check your entry)
and incorrect User Role invalid data entry(invalid username and
and Click User Role please select a
Search button correct user name and User
Role”)
and User Role and Click valid data appropriate page”
Search button
Table 28 : Test Case for Block Acount
Unit to Test = Authentication of Create Account

users
Assumptions = Create Account into appropriate

page

valid username)
User ID (empty ,invalid User ID, valid User ID)
password (empty ,invalid password, valid

password)
Select incorrect
Username, User ID,
Password and Click Username =hase “problem occurred”
Create button User ID = BRT/0988
Password=123 Please check your entry (enter
correct user name and
password)
Select empty username, Username---------------
User ID and Password is
correct and Click
User ID--------------- “user’s name is empty” (please
Create button fill out these filled)
other fields

correct, user ID, User name=hdufbudf
password and Click User ID=BRT/09887 “invalid user name”(error
Create button occurred check your entry)
and incorrect user ID, invalid data entry(invalid username, User
Password and Click ID and password please select
Create button a correct user name, User ID
and password”)
User ID and Password valid data appropriate page”
and Click Create button
Table 29: Test Case for Create Acount

Integration Testing
Verify the interfaces, communication between subcomponents and modules of the
application. All the tested modules are combined into sub systems, which are then
tested. In this testing part, all the modules will be combined together and tested for their
combinability with each other and with the systems functionality. If error occurs in
combining them, the module with problem will be identified and recombined. From this
the team can understand that how the system work using the separate module.
System Testing
It is the final step of testing. In this the team members tests the entire system as a whole
with all forms, code, modules. This form of testing is popularly known as Black Box
testing or System tests. In this we tested all the functionalities in the System. All errors in
the forms, functions, modules have been tested. Finally, by the system testing we had
ensured that the entire integrated software system meets the desired requirements.
5.1.2 Hardware software acquisitions
Hardware software acquisitions determine the system resource requirements, its
capability with other systems and networks, its interface requirements to existing systems
if any, its security capability, deficiencies and vulnerability and to make sure there are not
already existing software/system that provide equivalent functionality.
5.1.3 User manual preparation

In order to access the system, first of all every user must have an account or permission
from administrator. So administrator has the right to create an account for every user like
student, department head, director, interrogator, and teacher and for him/herself. Users
should enter into the system parts by using their Username/Email and Password in order
to access the system.

Figure 14: Login page
Figure 15: Admin page

Figure 16: View course page
Figure 17: Block acount

Figure 18: Edit student information

5.2 Training
Training is the process of teaching or learning a skill or job. During the development of
the system, the project group members will give short time training for the system
administrator and employee explaining how the system works and in what way they can
manage their system. Training is needed for two reasons:
 If users are not adequately trained they will not operate with the system
correctly or efficiently.
 If users fill the task they are being asked to perform are outside their
capabilities, they may become demoralized and separated.
User training must be provided to user of the system in order to help make them to equate
with the system. Users are vital part of any system.
5.3 Installation Process
Installation of our proposed system at minimum requires a computer to serve as a
computer to run the web based program. In addition, XAMP software needs to be
installed and configured so that the database and other web based interrelated functions
can be process.

After all hardware and software requirements have been fulfilled, you can install simply
by following steps:
Step1: Install XAMPP (X-so, Apache Sever, MySQL, PHP and Perl) on computer.
Step2: Get the folder “WBCCSMS “which contains files and source code of the system from
the Developers Team.
Step 2: Past the folder in the C:\Xampp\htdocs.
Step3: Run XAMPP control panel and start all services.
Step4: Installation is finished.
5.4 Start-Up Strategy

After our web page is configuring, the page starts up in three ways.
 One which needs password and username that is for all employees and system
administrator. To access his/her own authorized pages one should have password
and user name so that he/she can enter into and use the system. This accessibility
has also one which is restricted for system administrator.
 Second, before the customer access the page they must be registered as a
member. After he/she would be the member of the system, then the next step is
login to enter into the page and access system.
 Third, any user or customer can access the page without making registration or
without to be the member of the system but only view can’.

CHAPTER 6
Conclusion and Recommendation
6.1 Conclusion
The project is partitioned into five chapters and each chapter has a specific deliverable
which is essential and base for the next chapter.
But the team have tried its best and developed interesting system web based student
information management system for senkele police collage. It is flexible, accurate and
attractive. The system performs works better than existing system (usability, speed,
efficiency and effectiveness). Security also included in this system developed and
authorized user can access the required services. The system is also very useful in saving
time and other utilities wastage.
This project document deals all about information management system for senkele police.
Generally, project team would like to remark that the project has given us a great deal of
experience not only in the technical aspect but also in writing together as a team to
accomplish a certain goal, which is a much desired quality.
6.2 Recommendation
According to scope of our project the team develops web based system. Because of the
time and budget constraint we may have some limitations which should be taken in
considerations, but in the future the team believes that this system can be fully
operational by having some functionality that are not included in the proposed system
like online registration for the college.

6.3. Reference
[1]:- west Shewa police college Human resource and allocation office manual
documentation book.
[2]:- Jaffrey McManus, Home Encyclopedia Databases of SQL and Access, 1st edition
1997.
[3]:- RPT software, URL:http://www.rptsoftware.com/aboutus/microsoft access database/
retrieved on Jan 14, 2011
[4]:-Michael A. vine, complete reference for VB.NET 2008, 2nd edition, 2001.
[5]:- M. Jacob, complete reference for VB.NET 2008, 3rd edition, 2005.
[6]:-S.A Kalkar, Software Engineering, 3rd edition, 2007.
[7]:-Solomon Grudey, object oriented primer, 2nd edition, 2001.
[8]:- Solomon Grudey, object oriented primer, 2nd edition, 2001.
[9]:-Brian Wilkerson, Object oriented design 1st edition, 2004.
[11]:-Rebecca and Lauren Wienner object oriented design, 1st edition, 2004.
[12]:- Solomon Grudey, object oriented primer, 2nd edition, 2001.
[13]. Functional requirement: http://www.ops.fhwa.dot.gov/functional-requirement accessed:
17/03/2010E.C
[14]. Technical Feasibility, Economic Feasibility, Operational Feasibility, Legal
Feasibility:http://www.freetutes.com/systemanalysis/sa3-technical-economic-operational-
legal.html accessed:02/03/2010E.C
[15]. [Class diagram] https://www.visual-paradigm.com/VPGallery/diagrams/Class.html
accessed: 6/05/2010

Final

Uploaded by

Document Information

Original Description:

Original Title

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

Final

Uploaded by

Copyright:

Available Formats

AMBO UNIVERSTY

HASSEN AHAMED BRT/2146/08

Project Submitted To Department Of Computer Science of Ambo University for Degree

ADVISOR: Dr. Nagarajan

JUNE 17, 2019

NAME SIGNATURE ID NUMBER

BULCHA BEGNA BRT/2126/08

NAME AND SIGNATURE OF MEMBERS OF THE EXAMAINING BOARD

Dr. Nagarajan advisor,

DEPARTMENT OF COMPUTER SCIENCE Page i AMBO UNIVERSITY

NAME SIGNATURE DATE

THIS PROJECT HAS BEEN SUBMITTED FOR EXAMINATION WHIT OUR

NAME SIGNATURE DATE

3.2.1.2 System Use Case ................................................................................................... 28

5.2 Training ....................................................................................................................... 78

BSC: ……………………………… basic score card

DEPARTMENT OF COMPUTER SCIENCE Page 1 AMBO UNIVERSITY

1.2 Background of the Study

1.3 Statement of the Problem.

DEPARTMENT OF COMPUTER SCIENCE Page 2 AMBO UNIVERSITY

1.4. Objective of the Project

1.4.2 Specific Objective

1.6. Significance of the Project

 t will speed up the searching processes of student information.

DEPARTMENT OF COMPUTER SCIENCE Page 4 AMBO UNIVERSITY

 Generally produces a dramatic savings in time, money, and human effort.

DEPARTMENT OF COMPUTER SCIENCE Page 5 AMBO UNIVERSITY

1.7.3 Systems Analysis and Design (approach)

DEPARTMENT OF COMPUTER SCIENCE Page 6 AMBO UNIVERSITY

 Microsoft power point 2010: for presentation of the documentation.

1.7.7 Testing procedures

DEPARTMENT OF COMPUTER SCIENCE Page 7 AMBO UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE Page 8 AMBO UNIVERSITY

1.9 Risk and contiguous

1.10 Assumptions and constraints

DEPARTMENT OF COMPUTER SCIENCE Page 9 AMBO UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE Page 10 AMBO UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE Page 11 AMBO UNIVERSITY

 Terminologies, abbreviations, and acronyms used

2.1.1 Major players of the Existing system

2.1.2 Functions / activities in the existing system

DEPARTMENT OF COMPUTER SCIENCE Page 12 AMBO UNIVERSITY

2.1.3 Business rules

DEPARTMENT OF COMPUTER SCIENCE Page 13 AMBO UNIVERSITY

2.1.4 Report generated in the existing system

2.1.5 Forms and other documents of the existing Systems

DEPARTMENT OF COMPUTER SCIENCE Page 14 AMBO UNIVERSITY

Master student Card(MSC)

MRN………………… Date of Registration

Date of Birth Day……… Month…………….. Year………………..

Table 2: form of student

2.1.6 Bottlenecks of the Existing system

2.1.6.3 Control and security:

2.2 Practices to be preserved

DEPARTMENT OF COMPUTER SCIENCE Page 16 AMBO UNIVERSITY

2.3 The Proposed System

2.3.1 Team composition

DEPARTMENT OF COMPUTER SCIENCE Page 17 AMBO UNIVERSITY

decentralized team composition to do the project of web based student information

1 Nuredin Abdumalik TBRT/0348/10 Data collector

2 Hassen Ahamed BRT/2146/08 Programmer and tester

4 Admasu Adugna BRT/2185/08 Data collector