FINAL Project

Bule hora town traffic management system
In partial fulfillment of the requirement for the degree of Bachelor of Science in

electrical and computer engineering (computer engineering)
TITLE: TRAFFIC MANAGEMENT SYSTEM FOR

BULE HORA TOWN
DEVELOPED AND SUBMITTED BY:

Name ID
1.SISAY G/MEDHIN FE/R/098712
2.RESHID ABDULA FE/R/1051/12
3.TADESS TESFAYE FE/R/0935/12
4.UMER MOHAMMED FE/R/0885/12
5.REGASSA MITKU FE/R/1110/12
SUBMITTED TO DEPARTMENTS OF ELECTRICALAND
COMPUTER ENGINEERING
Advisor, BEHAYLU.S(BSc) June 2017

BULE HORA, ETHIOPIA
ACKNOWLEDGMENT
This project was started with the high organized team group. We express thanks and
gratitude (appreciation) to our advisor Daniel Bekele (MSC) an instructor in Wollo
University for his day to day encouraging, support and guidance in carrying out the
project. We would like to express gratitude and obligation to our department staff
members for their valuable advice and guidance. Without them this project would not have
seen the light of the day. In addition to this we would like to thanks for Kombolcha town
traffic police officers, traffic police members and workers of the station who gave any
information concerning about our project and their politeness during interviews. Finally,
we would like to thank our parents for their moral support throughout our study of higher
institute and all the administration body of wollo university Kombolcha campus.
i
ABSTRACT
Bule hora traffic police station is early established police station in bule hora town. It is a
well organized police station and stands for serving local communities living with high life
freedoms and well being of their property as well. For the purpose of preventing criminal
activities, the station works regardless of crime recording, making judgments over
criminals and assign legal punishments towards their wrong actions. This station limited
on manual works. This is limited 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 automated system for the station. To
alleviate the existing system problems we are using programming tools like HTML, PHP
for interfacing and coding, My_Sql for database application, rational roses for designing
different artifacts of the project. Finally the overall activity of this project work is about
design and implementation of automated traffic police accident record management system
for Bule hora town.
ii
Chapter one
Tables
Table 1.1 Task breakdown of the project team.7
Table 1.2 Gantt chart..8
Chapter three
Table 3.1 reduced for decision table .26
Table 3.2 un normalized table ...35
Table 3.3 first normalized table.....36
Table 3.4 Second normalized table....36
Table 3.4.1 victim table .36
Table 3.4.2 traffic table ......37
Table 3.4.3 driver table ....37
Table 3.5 third normalized victim table ...37
iii
Chapter Two
Figures
Fig 2.1 context diagram of the current working system14
Fig 2.2 Level-0 diagram of the existing system.15
Fig 2.3 Context diagram of the new system.19
Fig 2.4 Level-0 diagram of new System (DFD).. 20
Chapter three
Figures
Fig 3.1 the relation between police station and head of KTMS.30
Fig3. 2 the relation among, police station, head of KTMS and traffic police...31
Fig 3. 3the relation among all entities.33
Fig 3.4 E-R diagram34
Fig 3.5 Interface for home page..42
Fig 3.6 Interface for traffic police login page..44
Fig 3.7 Interface for head of KTMS login page45
Fig 3.8 create account page..46
Fig 3.9 modify traffic account page.47
Fig 3.10 delete user account page....48
Fig 3.11 traffic police home page.49
Fig 3.12traffic police register page50
Fig 3.13 traffic police update page....51
Fig 3.14 traffic police delete page.52
iv
Fig 3.15 traffic police search page53
Fig 3.16 accident register page.54
Fig 3.17 accident modify page..55
Fig 3.18 accident delete page....56
Fig 3.19 accident search page57
Fig 3.20 driver home page.....58
Fig 3.21 driver register page....59
Fig 3.22 driver modify page.60
Fig 3.23 driver delete page...61
Fig 3.24 driver search page......62
Fig 3.25 owner home page........63
Fig 3.26 driver register page..64
Fig 3.27 driver modify page..65
Fig 3.28 driver search page66
Fig 3.29 driver delete page.....67
Fig 3. 30 victim register page........68
Fig 3. 31 victim modify page....69
Fig 3. 32victim delete page...70
Fig 3. 33 victim search page......71
Fig 3. 34 head of KTMS home page....72
v
Acronyms and Abbreviations

KTMS: Kombolcha town Traffic Management System
MS: Microsoft
SQL: structural query language
Fig: figure
PHP: Hyper text preprocessor
HTML: Hyper text markup language
DFD: Data flow diagram
E_R: Entity relationship
vi
Table of contents
Contents
CHAPTER -ONE ................................................................................................................................................. 1
1. INTRODUCTION ........................................................................................................................................... 1
1.1 BACKGROUND/OVERVIEW ..................................................................................................................................1

1.1.1MISSION ................................................................................................................................................ 2
1.1.2 VISION ................................................................................................................................................ 2
1.1.3 VALUES ............................................................................................................................................... 2
1.2 STATEMENTS OF THE PROBLEM .......................................................................................................................2
1.3 OBJECTIVES OF THE PROJECT ..............................................................................................................................3
1.3.1 GENERAL OBJECTIVE ............................................................................................................................. 3
1.3.2 SPECIFIC OBJECTIVEs ............................................................................................................................. 3
1.4 SCOPE AND LIMITATION OF THE PROJECT ....................................................................................................3
1.4.1 SCOPE OF THE PROJECT ......................................................................................................................... 3
1.4.2 LIMITATION OF THE PROJECT ................................................................................................................ 4
1.5 METHDOLOOGY ...................................................................................................................................................4
1.5.1 DATA COLLECTION ................................................................................................................................ 4
1.5.2 SYSTEM ANALYASIS AND DESIGN .......................................................................................................... 4
1.5.3 DEVELOPMENT TOOLS .......................................................................................................................... 5
1.6 SIGNIFICANCE AND BENEFICARIES OF THE PROJECT ..........................................................................................6
1.6.1 SIGNIFICANCE FOR THE ORGANIZATION .............................................................................................. 6
1.6.2 SIGNIFICANCE FOR USERS ..................................................................................................................... 6
1.6.3 SIGNIFICANCE FOR TEAM ...................................................................................................................... 6
1.7. FEASIBILITY ANALYSIS .........................................................................................................................................6
1.7.1 ECONOMIC FEASIBILITY......................................................................................................................... 6
1.7.2 TECHINICAL FEASIBILITY ........................................................................................................................ 6
1.7.3 OPERATIONAL FEASIBILITY .................................................................................................................... 7
1.7.4 TIME FEASIBILITY .................................................................................................................................. 7
1.7.5 LEGAL AND CONTRACTUAL FEASIBILITY ................................................................................................ 7
1.8 TASK BREAKDOWN AND DELIVERABLES ..............................................................................................................7
TABLE 1.1TASK BREAKDOWN OF THE PROJECT TEAM .............................................................................................................7
1.9 COMMUNICATION PLAN .....................................................................................................................................7
1.10 PROJECT SCHEDULE ...........................................................................................................................................8
TABLE 1.2 GANTT CHART ................................................................................................................................................8
CHAPTER- TWO ...................................................................................................................................................... 9
2. BUSINESS AREA ANALYSIS .................................................................................................................................. 9
2.1 SYSTEM ANALYSIS OVERVIEW .....................................................................................................................................9

2.1.1 System Analysis Objectives ................................................................................................................... 9
2.1.2 Overview of the existing system ........................................................................................................... 9
2.2 GRAPHICAL REPRESENTATION OF THE CURRENT SYSTEM..................................................................................................12
vii
2.2.1 Data Flow Diagram (DFD) ................................................................................................................... 12
2.3 NEW SYSTEM .........................................................................................................................................................17
2.3.1 Graphical representation of the new system....................................................................................... 18
2.4 REQUIREMENT ANALYSIS..........................................................................................................................................21
2.4.1 Functional requirements ..................................................................................................................... 21
2.4.2. Non-functional requirements ............................................................................................................. 23
CHAPTER-THREE .................................................................................................................................................. 25
3. SYSTEM DESIGN ............................................................................................................................................... 25
3.1 INTRODUCTION ...................................................................................................................................................25

3.2 OBJECTIVE AND SCOPE ...........................................................................................................................................25
OF DESIGN ...................................................................................................................... ERROR! BOOKMARK NOT DEFINED.
3.3 OVERVIEW OF SOFTWARE STRUCTURE .................................................................................................................26
3.4 LOGICAL MODELING FOR VICTIM ................................................................................................................................26
3.1 REDUCED DECISION TABLE FOR KTMS SYSTEM..............................................................................................................26
3.4.1 Decision tree ....................................................................................................................................... 26
A /Decision tree ................................................................................................................. 27
3.5 CONCEPTUAL MODELING .........................................................................................................................................30
3.5.1 The relationship between an entity .................................................................................................... 30
3.5.2 E-R diagram with its attribute ........................................................................................................... 32
3.6 NORMALIZATION ..................................................................................................................................................32
3.6.1 Unnormalized Table .......................................................................................................................... 33
3.2 UN NORMALIZED TABLE ............................................................................................................................................33
3.6.2 First normalized form ........................................................................................................................ 33
3.3 FIRST NORMALIZED TABLE .........................................................................................................................................33
3.6.3 Second normalized form ..................................................................................................................... 34
3.4.2 Traffic table ........................................................................................................................................ 34
3.4.3 Deriver table ....................................................................................................................................... 34
3.6.4 THIRD NORMALIZATION ..................................................................................................................... 34
3.5 VICTIM TABLE ........................................................................................................................................................35
3.7 PHYSICAL DATA BASE DESIGN ...................................................................................................................................35
3.7 .1 My_sql database system ................................................................................................................... 35
3.8 TABLE IN ONLINE SYSTEM .........................................................................................................................................36
3.8.1 Database creation .............................................................................................................................. 37
3.8.2 Interface Design .................................................................................................................................. 38
CHAPTER-FOUR .................................................................................................................................................... 70
4. IMPLEMENTATION AND TESTING DOCUMENTS ............................................................................................... 70
4.1 OBJECTIVE OF IMPLEMENTATION .............................................................................................................................70

4.2 TESTING BY SCOPE..................................................................................................................................................72
UNIT TESTING: .............................................................................................................................................................72
4.3 SAMPLE CODES AND SAMPLE OUTPUT SCREENS ............................................................................................................72
4.4 SUMMARY, CONCLUSION AND RECOMMENDATION .....................................................................................105
4.4.1 COMMENDATIONS ........................................................................................................................... 106
4.5 REFERENCES ....................................................................................................................................................108
viii
ix
x
Chapter -one
1. INTRODUCTION
1.1 BACKGROUND/OVERVIEW
Kombolcha town is found in the north western parts of Addis Ababa at 376 kilometers from
the capital city of Ethiopia and 25 km far apart from Dessie town. The town has early civilized
like other early towns of Ethiopia. It is the main industry center in Amhara region and has its
own administration structure to organize, control and manage the local communities.
In Kombolcha town there are governmental and non-governmental organizations which

facilitate the development of the town and provide services to the community. From those
governmental institution Traffic police station is one part which controls the emergency of
vehicles and stranger in the town.
Kombolcha Town Traffic management system (KTMS) was established in 1933 E.C as police
station for the purpose of protecting local communities from criminal activities. KTMS is found
around piassia area at north part of Gumruk that far away 300 meters.
KTMS gives services to the society who lives around and within the town. Since KTMS is
found with in kombolcha town, it plays a vital role for the surrounding society by providing the
immediate treatment including emergency. Currently the traffic police station processes tasks in
the form of document based applications or traditional file systems .on the other hand the current
system of kombolcha town traffic police station recording personal information of accidents on
traditional document formats.
Our project proposed system, processing of the accident record can be automated by KTMS,
which is newly implemented. The proposed system can be taken as to automate processing tasks
with less efforts and resources (like, reducing accessing times and material requirements).
Bule hora University Department of ECE Page 1

1.1.1MISSION
To reduce the number of car and others related accidents that occur in the town.
By participating the societies to overcome radical change about traffic well-being.
To create the relationship with schools for organized activity and wise traffic police by
giving awareness for the society.
Giving the service for the society without any biased and corruption everywhere and
every time attentively.
To increase awareness in the society about the danger of vehicle accident.
1.1.2 VISION
The organization vision states that the town is free from any transport loadness and any
emergency. Since the organization can be distribute experienced traffic police that come
up with changes to kombolcha town.
1.1.3 VALUES
To satisfy customers need.
To create smooth relationship between the members with the head of traffic office.
To perform successfulness and concurrent action.
To give services those are free from any biased and corruption.
To perform clear and fair use of resources in order to avoid extravagancy.
1.2 STATEMENTS OF THE PROBLEM

The current method or technique used to recording and reporting vehicle accident in
Bule hora town traffic police is manual. As the number of vehicle increases in the town from
year to year, this manual system does not satisfy the need of the customers and difficult to handle
all the activities that have been done in the office.
There are various problems that the traffic office faces due to the file manual handling of its
daily activity.
The most possible problems that faces on the current system are as follows:-
It is difficult to prepare report.

It is difficult to give necessary information for organization, like court system.
The manual system is much time consuming to work with, it means it takes time.
It is difficult to handle data properly or wisely.
Lack of security.
It is difficult to identify the owner of the vehicle.
The extra power required to be with the manual system creates a gap in other
sectors of professions.
The data handles huge amount of space due to the manual system.
1.3 OBJECTIVES OF THE PROJECT

Our project has two objectives. Such as:-
1.3.1 GENERAL OBJECTIVE

The general objective of the project is to develop an automated traffic management system that
allows the traffic officers and other stakeholders to get reliable and quick information about the
car accident.
1.3.2 SPECIFIC OBJECTIVEs

The specific objectives of our project are:-
To study and analysis the existing system thoroughly.

To design data base traffic management system.
To develop the system
To test the system.
To prepare documentation about the system.
1.4 SCOPE AND LIMITATION OF THE PROJECT

1.4.1 SCOPE OF THE PROJECT
The proposed system is only applicable on:
With less effort and cost, the system is able to maintain and store vehicle accident
information.
Accurate way of recording or processing vehicle accidents information and set records
into organized database.

Presence of centralized database and organized records.
Produce reports for only vehicle accident records.
The proposed system is limited on recording, storing, updating and retrieving vehicle
accidents information
1.4.2 LIMITATION OF THE PROJECT

The system works in English language only.
1.5 METHDOLOOGY
1.5.1 DATA COLLECTION
1.5.1.1 PRIMARY DATA COLLECTION

A. Interview: we use interview to gather data or information from the members of traffic
office by face to face communication.
B. Reading documents: consulted and analyzed written materials that describe the operations
conducted in the station to further strengthen and support the information that applied the
technique.
C. Observation: was used to gather additional data by observing the actual work being done by
the staff and consolidated (combine) with what was obtained through interview.
1.5.2 SYSTEM ANALYASIS AND DESIGN

In the analysis part, we determine how the current system of KTMS works functionally. There is
a process such as Data -Flow Diagram (DFD), it includes Context Diagram and Level-0
Diagram. In the design part Conceptual Data Modeling (E_R diagram) is include. Due to the
reason that we are familiar with Structure System Analysis and Design more, So that we use it.
Hence, system planning, Analysis, Design, Implementation and operation (testing) are the main
phases in this project.
Follow this approach helps us:
To simplify the design and implementation phase.

If there is well-designed documented system analysis, which is a blue print, it
will be easy to follow the document and perform the design and implementation.

To play a major role in avoiding time wastage. While designing and
implementing the system is possible simultaneously.
To see the internal functioning of the system clearly and completely.
1.5.3 DEVELOPMENT TOOLS

A. Software Tools
Programming development tool

PHP & HTML
Database software
MY_SQL for database purpose
Documentation
MS-word 2010
MS-Visio 2007
Edraws UML Diagram
Operating system
Window 7
Window xp
Interface language: English Language
B. Hardware Components
CPU: Intel(R) core(tm)2 Duo CPU
T6400@2.00GHZ
RAM:1.99GB
Hard disk:310 GB
Monitor: LCD

1.6 SIGNIFICANCE AND BENEFICARIES OF THE PROJECT

1.6.1 SIGNIFICANCE FOR THE ORGANIZATION
Ensures data accuracy.
Minimum time need for various data process.
To provide better service.
To Minimize data duplication
Minimize paper work required.
To provide cost efficient.
1.6.2 SIGNIFICANCE FOR USERS

User friendly and interactive environment.
Data security and reliability.
Fast data insertion and retrieval.
Easy to access.
1.6.3 SIGNIFICANCE FOR TEAM

To develop project development skill.
To improve communication skill.
1.7. FEASIBILITY ANALYSIS

Feasibility study is an evaluation of a proposal designed to determine the difficulty in carrying
out a designated task. The objectives of feasibility study are to find out if an information system
project can be done and suggest possible alternative solution. We can view feasibility study in
different ways:-
1.7.1 ECONOMIC FEASIBILITY

Our project is economically feasible. Because, it does not require much more money and also the
materials to implement the system.
1.7.2 TECHINICAL FEASIBILITY

Our project is technically feasible. Because, the project is practically applicable with in the
current technology. The head of KTMS has approved technology. He can currently acquire the
necessary technology and get skilled man-power that has the technical know-how.

1.7.3 OPERATIONAL FEASIBILITY
Our project is operationally feasible. Because, the members of the office require the data base to
facilitate their day-to-day activities in considerable resource and time.
1.7.4 TIME FEASIBILITY

Our project is timely feasible. Because, when we search files from the system, it takes short
period of time.
1.7.5 LEGAL AND CONTRACTUAL FEASIBILITY

Legally the system can copy only by the group members. In contractual aspect we will finish the
project within the stipulated time.
1.8 TASK BREAKDOWN AND DELIVERABLES

The project team was compromised of a group of 5 students.
Table 1.1Task breakdown of the project team
Task Sisay Reshid Regassa Taddese Umer

Project planning
Resource list
Feasibility analysis
Problem definition
Requirement analysis
Context diagram(DFD)
Decision Table/Tree x x x x X
Design x x x x X
Database Design x x x x X
Implementation x x x x X
1.9 COMMUNICATION PLAN

To develop the web based system, the team members are decided to meet every day from
Monday to Friday on. All the members are assigned a particular task to do at their home,
and they came up with tasks done. Then, we discussed all we contact our advisor MR.

Behaylu now and using Telephone. Beside this we have a regular session two days a
week for direct the whole work done.
1.10 PROJECT SCHEDULE
Table 1.2 Gantt Chart

Nov Dec Jan Feb March April May
Task name
2005 2005 2005 2005 2005 2005 2005
1.list problem
opportunities and
directories
2.problem analysis
3.analyze system
requirement
4.design analysis
5.physical design

Chapter- two
2. Business Area Analysis

2.1 System Analysis Overview
The analysis part of this project determines how the current or existing system of traffic
management system works and problem encounters with existing traffic management system. It
also describes the newly proposed system and the functionality will be added in the new system.
2.1.1 System Analysis Objectives

The objective of system analysis is:
To identify the problem that faces on the current system.

To suggest a solution for these potential problems.
To prerequisite for design and implementation phase.
It will also play a major role to minimize time wastage while design and implementing
the system.
To see the function of the current and the new system clearly.
2.1.2 Overview of the existing system

The current system used to record and reporting vehicle accident is manual system. It
describes a person who interacts to the current system such as traffic police head and
traffic police. The traffic police head receives information about the accident from field
traffic and other traffic who observe the accident.
The main activities of existing system are as follow:
Prepare time schedule, work breakdown and distribution.
To evaluate each traffic road controller, in order to perform any
work from any biased.
Remarking customer based on 1/4th and other year standard.

Existing recording form


2.1.3 Problem of existing system
The current traffic system uses paper and pen to record accident information, which retards the
organization health running. Many files keep in file cabinet (shelves). Such kind of file keeping
system is vulnerable to loss and a lot of error can happen during registration.
2.2 Graphical representation of the current system

2.2.1 Data Flow Diagram (DFD)
DFD: is a graphic that illustrates the flow of data between external entities and process
and data store in the system. It is excellent communication tool for analysts to model processes
and functional requirements.
DFDs Tools
Data flow: directional movement of data to and from external entities

Symbol:
External entities: it is a source or a sink (it is the origin and destination
of data)
Symbol:
Data store: a repository of information.

Symbol:
Process: it is a work or action performed on data so that transformed,

stored or distributed.
Symbol:
Entities of the existing system:

Police station
Customer
Head of BTMS
Examiner
Traffic police
Responsibility of each entity:
Police station:
To plan rule and regulation of the overall administration system.
To distribute checklist for each administration level.
To control the overall activity of the organization.
Customer:
Accept the principle of the traffic policy.
To provide some valuable information to the organization.
They participate to prevent the violation of the rule.
Head of KTMS:
Plan the overall activities of traffic management system.
Control the activities of the system.
Generate report and to provide for the police station.
To initiate the traffic police in order to achieve their day to day activities.
To organize and offer order to workers.
Examiner:
To identify when, where, how and what the victim was happen.
Filter out the level of the victim such as very high, high, medium and low
level of victim.
Traffic police:
To create awareness for the society.
To create the organized group such as student traffic police.
To control the violation of the policy.
To adjust the left and right condition of the road.

POLICE STATION
Traffic Police List
ordered
Request information HEAD OF
CUSTOMER Traffic material list
KTMS
Provide information Traffic Management
System
Traffic information
CUSTOMER
Fig:2.1 context diagram of the current working system

POLICE STATION
Transfer
General report
Provide
checklist
Request report
1.0 Committed
Receive new checklist
checklist document
D1 new
checklist
Add new
record checklist
2.0 6.0
Registered General report
New transfer documented checklist analysis
checklist
Transfer checklist
Transfer order
3.0
TRAFFIC POLICE Offer order
Provide information
Provide customer information

D2 new
customer
record
4.0 Transfer
information Generate
Commit customer document Receive new report
customer EXAMINER
Committed
Registeration request customer
CUSTOMER document
Add new customer
5.0
Registered
Customer list
customer
Request Provide
report report
HEAD OF KTMS
Fig: 2.2 Level-0 diagram of the existing system

The current system faces the following main problems:
It takes long time to prepare report and respond to the stakeholders.

Important data can be easily changed.
It is difficult to manually search for a particular record to obtain information
about it.
Maintaining record is very difficult.
Security issue is the main problem of the system.
Generally the existing system has the following major problems.
These are:
Performance problem:
Due to manual system of working, unable to provide or retrieve
customer information on time.
- Wastage of time to organize and integrate related files.
-Low response time.
Information problem:
It explains the information content of the existing system in terms of

input, process, output and data storage.
Input:
Loss of data may occur.
Output:
Inaccuracy of information may produce.
Poor flow of information between departments.

Data storage:
Lack of well organize file cabinet system.
Data are not easily accessible due to its integration placed in
different location.
Data redundancy and inconsistency.
Control problem:
Due to manual work the input data are not editing properly. To say the system is
fully functional, most of the functionalities will be fulfilled. We try to solve by
including those functionalities in our new system. We generate new system that
overcomes the problem. This new system will be described in the following
manner:
2.3 New system

This new system focus on work specialization for optimization. Generally it
accepting new customers that are getting emerged by the driver for giving good
treatments to customers.
To appointments:
Select the files of the emergent and the criminal one from the
document when they are appointed.
To generate a good decision and solution.
To control the vehicle by using their code number until they commit
to penalize.
The system changes from manual to computerized system.
The system is free from vulnerable and to minimize data duplication

when the system changes to from manual to computerize.

As described in the proposal the newly system uses automated way of

manipulation to operate its task.
The system has the following main solutions:
Fast and quick response in real time.
The system avoids data redundancy and duplication.
The system troubleshooting and keeping track of customers
records as the number of customer increase.
The system becomes secure.
2.3.1 Graphical representation of the new system

Entities of the new system:
Police station
victim
Traffic police
Owner of the car
Driver
Head of KTMS
System administrator

POLICE STATION
TRAFFIC
CUSTOMER
POLICE
Service
request Traffic
Service response list
service ordered
0
Give the Traffic
DRIVER rule and regulation
Management register
SYSTEM
system ADMINSTRATOR
order
Identity request
OWNER OF
Response request
THE CAR Generate Request
report report
HEAD OF KTMS
Fig 2.3 Context diagram of the new system

Transfer
General report
POLICE STATION
TRAFFIC CUSTOMER
POLICE
Traffic
list Service
request
Service response
ordered
1.0
Service
Service request report
Control Request report
service
6.0
D1 traffic police General report
and analysis
customer
Identity request
Fault maker report

2.0 OWNER
Examination OF CAR
service
DRIVER Give the
rule and regulation Response request
Trips resualt
D2 trips file
Generate
report
3.0
Data organize register
service COMPUTER
Trips report order ADMINSTRAT
OR
provide Request
report report
HEAD OF KTMS
Fig 2.4 Level-0 diagram of new System (DFD)

2.4 Requirement Analysis

2.4.1 Functional requirements:
The Functional requirement is concerned with actual performance of the system

that is going to be developed. Functional requirements describe the functionality or
service provided by the new system.
2.4.1.1. Input requirements:
The new system should:

o Record car information such as car plate, whether it is insured or not
that is grouped under third party insurance.
o Record the information of owner of the car such as name, sex, age,
address.
o Record driver information such as name, sex, age, address, license.
o Record traffic police information such as name, sex, age, address.
o Record human causality
o Record animal causality
o Record property damage information.
o Record the amount of birr is paid by driver for breaking traffic law.

2.4.1.2. Process requirements:
The new system should:

o Modify criminal profile.
o Update the information stored in the database.
o Search car with car plate.
o Search a person that was injured in the accident.
o Retrieve data
2.4.1.3. Output requirements:
Generate various reports.

Produce a driver, who frequently offends the law.
Report the overall profile of criminal.
2.4.1.4. Storage and retrieval requirements:
All the records should be stored for future use.

The data is stored in a database with a name of KTTO.
It provides information and available, when it is needed.

2.4.2. Non-functional requirements
Non functional requirements describe user-visible aspects of the system that are
not directly related with the functional behavior of the system.
The non functional requirements of the systems are:
Security
Since security is the primary concern of any computerized system, in the
new system security is enforced /implemented to protect the system from
threats. Like: -
Unauthorized access.
Accidental introduction of inconsistency
Insider attack.
To protect the system from threats we implement security using:
User name
Password
Performance
The system shall be available all time of the working day. The system shall
respond in a very minimal duration of response time
Maintainability
The system can be easily recovered when it fails.
Reliability
The new system is reliable when we store data and information within it.

E.g. security
Modifiability
The new system is easily modified when we want to add additional features.
Portability
It can be run across different operating system.
Error handling:
The system should have error handling mechanism. Even if failure
happens or occurs, it should not stop function rather than provide error
message should guide the user through what to do next.
Advantage of the new system
The new system can be implemented without changing the

organization policy.
The new system does not require more human labor.
Processing data with high speed and short hand form.
Data redundancy problem will be avoid.
Disadvantage of the new system
Requires technical person to handle and manage the system.

It does not address all the basic problems of the station rather focus on
the station sub department that means the new system implemented only
for crime record management system.

Chapter-Three
3. System design
3.1 Introduction:
This document describing the design of our project. In this document the main
design goal, the proposed software structure and its overview, the process model
and subsystem service, data storage facilities such as refined logical database and
physical database design, the access control and the security system are included.
3.2 Objective and Scope of Design

The new system changes many parts of the current working system.
The new system works in such a way that by providing a suitable Graphical
User Interface (GUI).
The range of the new system is preparing a report for on the monthly and
quarterly report on each particular movement for each particular place.
Automate the overall activities in the operational department.

3.3 Overview of Software Structure
Our new system will use client-server architecture and the whole database
system will install on server computer and client computer. The software that will
be installed on client pc will typically responsible for accepting user request and
displaying the necessary output information. The servers will validate client
request on restricted system and sends the data has been required on a format form.
But for restricted information the client server check permission and provides
permission processes.
3.4 Logical modeling for victim
3.1 reduced decision table for KTMS system

Rules
Conditions/actions 1 2 3 4
accident type insured Insurance1 Insurance2 Insurance3
Very high 10 25,000 15,500 15,000
high 12 14,600 12,400 10,400
medium 2 8,000 8,200 7,800
low 3 1000 900 500
3.4.1 Decision tree

A decision tree is a graphical representation of a decision situation
Decision situation points (nodes) are connected together by arcs and

terminate in ovals
Main components
Decision points represented by nodes

Actions represented by ovals
Particular choices from a decision point represented by arcs
To read a decision tree begin at root node on far left
Each node is numbered and each number corresponds to a choice
Choices are spelled out in a legend
From each node there are at least two paths leading to next step another
decision point or an action
All possible actions are listed on the far right in leaf nodes
Each rule is represented by tracing a series of paths from root node to the
next node and so on until an action oval is reached
Accident with very
A /Decision tree high level insurance
yes
1
Accident with high
level insurance
No
Yes
2
Accident with
medium level
insurance
No yes
3
No
Accident with low
level insurance
Legend
1) very high insured

2) High insured
3) Medium insured
4) Low insured
B/ Decision tree
Insured
Accident with
1 very high level
insurance
Accident 25,000
14,600 Accident with

2
high level
8000 insurance
1000 Accident with

medium level
Accident with
low level
insurance
Legend
1) Types of Accident
2) Amount of payment
The symbols that used to draw E_R diagram

Represents the entity
Represents the relationship
Represents an attribute
Represents Derived attribute
Represents primary key of an entity
Represents composite attribute
Represents the foreign key of an attribute
The line connects the attribute and entities with each

other

3.5 Conceptual modeling
3.5.1 The relationship between an entity

Entity of the new system
Police station
Head of KTMS
Traffic police
Driver
Owner
Victim
System administrator
Police station: is an organization that has different heads within it. From this, head
of BTMS is one of them. This organization has its own attribute like, name of
police station, region, zone, woreda, kebele, description and etc.
Head of BTMS: is an employee for BTMS system who has right to control over all
of the BTMS system. That control and assign all the traffic police activity around
the BTMS and solve the problem that occur around there. One head can control
more than one traffic police. He has his own attribute like
FirstName,MiddleName,LastName, ID, sex, age, address,Salary (region, woreda,
kebele, e-mail, and phone no). The head ID the primary key of ktms.
Figure 3.1 the relationship between police station and head of tms
Traffic police: is an employee which controls the day to activity of the society. One
traffic police can control money society. The attribute of traffic are like, traffic ID
Fname, Mname, Lname, position, current place, new place, coverage area,
responsibility, examination and length of time.
Deriver: is an employee for the owner of the car that derives the assigned vehicles.
The deriver may injure different property including human being .One deriver

may injure many society.He has His own

attributes.Like,DriverID,Date,Vehicleplate,Vehicletype,FirstName,MiddleName,L
astName,Sex,Citizenship,Age,Region,Zone,Woreda,Kebele,Driver Licens,Crime
type,HealthDescription,CrimeLocation,PaintistTraffic home.Changed number,
Punishment location,Date,Serialcode,Amuant,Control Property.
FIGURE 3.2 the relationship among police station, head of ktms, and traffic police.
Owners: Are the owner of the car that assigns a car to the Driver. Owner may have
many cars/vehicles, then He can assign many Drivers for that Cars. He has an
attribute that describes himself
like:OwnerID,FirstName,MiddleName,LastName,Sex,Age,Address,Carplate,Type
of car,Citizenship,Region,Zone,Woreda,Kebele,Description.
Victim: This is a thing including persons that injured by a driver. Many victims
may injured by money drivers or a single driver. They have their own attributes
like, victim ID date, fname, mname, lname, sex, age, Car plate, citizenship, region,
zone, woreda, and kebele.
System administrator: System administrator is a responsible person that controls

and handles information and data. And also record processed and unprocessed
data. In addition to this, system administrator has many responsibility like,
maintaining system settings, maintaining system performance (setup security
policy)and also like other entities he/she has his or her own attribute like,
ID,fname, mname, lname, sex, age, address (region, zone, woreda, kebele, phone
no, e-mail etc).
POLICE STATION Has HEAPOLICE STATIOND OF KTMS
Accept 1
Has
M
SYSTEM
Given to
ADMINISTRATOR
TRAFFIC POLICE control

Figure 3.3 the relationship among all entities
M treated
M
M
control
Wo Age Addr
Zo Sex
Regi red Keb ID ess
ne ele Nam
on a
Nam e
e Salary
POLICESTAT HEAD OF
Has
ION KTMS
Description
treated
has accepted
Name
Salary
ID
Address SYSTEM
ADMINISTRATER
3.5.2 E-R diagram with its attribute Sex
Age TRAFFICPOLI control
CE
Sex Age Name
given to
Address ID
ID
Salar
Fig: 3.4control
E-R diagram
Name y
Sex
Name
ID Age
DERIVER assigned by OWNER Address

License
Sex
Address Carplate
Age
injured
ID Sex Type of car
Age
Na
me Address
VICTIM
asked
Level
Carplate
3.6 Normalization
Normalization: refers to the activity of stream lining a database design by
eliminating redundancies and repeated values. Most often redundancies are
eliminated by placing repeated groups of values into separate table and linking
them through foreign keys. This is not only makes the database more compact and
reduces the disk space it occupies, but it also simplifies the task of making change.
In non-normalized database, because values are usually repeated in different table.

Altering them in manual (and error prone) find and replace process. In a
normalized database because values appear only once, making change is a simple
one step update. The normalization process also includes validating the database

relationship to ensure that there are not any crossed wires and to eliminate
incorrect dependency.
3.6.1 Unnormalized Table
3.2 un normalized table

I Fname Mname Lname Traffic Traffic S Kebele House Vechelep Deriver Deriver
D Name Address e late name Address
x
N
O
1 habtamu feleke belay wosen kombolcha M 01 0134 AA123 Tefera mekele
2 Tigist kebede wube mitku dessie F 03 02-34 AA645 Masresha kemssie
3 Wolela meku fikre john kocha M 10 0123 AA76 Seid Boru
4 Wolela meku Fikire john kocha M 10 0123 AA76 Seid Boru
5 habtamu feleke belay wosen kombolcha M 01 0134 AA123 Tefera mekele
6 Tigist kebede wube mitku dessie F 03 02-34 AA645 Masresha kemssie
A normal form: is simply a set of rules that a database must conform to. Five such
normal forms exist, ranging from completely non normalized database to fully
normalized one. We select only three of them, because third normal form is
generally accepted as being good enough for most applications. Normal forms are
standards of database regulation that promote efficiency predictability of results,
and unambiguousness.
3.6.2 First normalized form
In the first nomalized form the main tasks are removing repeating groups and
decide composite primary key of the table. Validating entity integrity rule (PK is
could not be null) it has primary key no duplicate rows and each row must contain
atomic value or no repeating groups. Therefore, in our table we will have
composite key of victim number or ID, kebele, house no, sex, age, name( fname,
mname, and lname).
3.3 first normalized table
ID TNAME SEX AGE ADDRESS HOUSE
NO
1 WOSEN M 30 KOCHA 0134
2 MITKU M 24 DESSIE 0234
3 JHON M 10 KOCHA 0123
4 HABTAMU M 30 GOJAM 0447

5 TIGIST F 23 DESSIE 04223

6 WOLELA F 12 KEMSSIE 03123
3.6.3 Second normalized form
Second normalized form based on functional dependency[FD],removing partial
functional dependency.FD is relation between attribute of relation( table).classifies
into determinant and dependant attribute.Example ID,Victim name, ID is
determinant and name is dependant of ID.ID,First name,middle name,last
name,sex,and carplate.This is also classification of dependency ,that is full and
partial dependencies .Partial dependency example ID ,victim name and
carplate,carplate.Full dependency example kebele(house no) ,traffic address.Here
we can break the table in three namely victim table ,traffic table and deriver table.
3.4.1 Victim table
ID Fname Mname Lame Sex Age Address

4 HABTAMU FELEKE BELAY M 30 GJAM
5 TIGIST KEBEDE WUBE F 23 DESSIE
6 WOLELA MEKU FIKIRE F 12 KEMSSIE
3.4.2 Traffic table

ID Fname Mname Lname Sex Age Address
2 WOSEN TEFERA Wube M 30 Kocha
5 MITKU Wubu Masresha M 30 DESSIE
8 MASTE Worku Asmare F 22 Kocha
3.4.3 Deriver table

ID Fname Mname Lname Sex License Address
1 Tefera Fente Kebede M 3rd MEKELE
23 MASRESHA Amsalu Bayih M 5th KEMSSIE
4 SEID Tibebu Yitayih M 4th BORU
3.6.4 THIRD NORMALIZATION
It works based on transitivity of FD, it removes transitivity of function
dependency. It happens when a non primary key attribute determines the value of
another attribute. Here we have the transitivity of Traffic ID with victim address or
victim name.
3.5 Victim table
ID Fname Mname Lame Address
4 HABTAMU FELEKE BELAY GJAM
5 TIGIST KEBEDE WUBE DESSIE
6 WOLELA MEKU FIKIRE KEMSSIE
3.7 Physical data base design

In this part of the phase includes:
Physical database /the table includes in the KTMS system. /

The schema of the database.
The graphical user interface.
3.7 .1 My_sql database system
In this system use client _server architecture that centers on the server,
mysql.The server is the program that actually manipulate database. The client
program cannot do directely rather they communicate your entry to the server
by means of queens written in structure query language (sql).The client
programs are installed locally on the machine from which you wish to access
MY-SQL, but the server can be installed anywhere as long as client can connect
to it. MY-SQL is an inherently networked database system, so clients can
communicate with the server that is running locally on your machine or one that
is running somewhere else. Mysql is a very power full program in its own right
it handle a large subset of the functionality of the most expensive and power
full database package. It uses a standard form of the well known sql data
language. MY-SQL is released under an open source license and is available for
free. It works on many operating systems and with many languages. It works
very quickly and works well even with large data sets.
Advantage of using mysql database system
My_sql is a relational database management system
My_sql software is open source

My_sql database service is very test reliable and easy to use
My_sql server works in client or server or embedded system.
Large amount contributed My_sql software is available.

My_sql version
Version 5.0.15 release in October 2005
Advantage of using this version 5.0.15

BIT type: can be used to store number of binary notation.
Information schema: the introduction of the INFORMATION- SCHEMA

database in mysql 5.0 provides a standard compliant means for accessing mysql
servers meta data, that is data about the database or schema on the server and
the objects which they contain.
Instance manager: can be used to start and stop the mysql server, even from
remote host.
Precision mat: mysql 5.0 introduced stricter criteria for acceptance or rejection
of data and implemented a new library for fixed point arithmetic. This
contributed to much higher degree of occurrence for mathematical operation
and greater control over invalid values.
Stored routing: support for name stored procedures and a stored function was
implemented.
Strict mode and standard error handling: mysql 5.0 added a strict mode whereby
it flow, standard in sql in a number of way in which it did not previously
support for standard SQL STATE error message was also implemented.
3.8 Table in online system
From the conceptual database design each entity become table and attribute for
each entity becomes columns of each table. This are five normalized table in the
database this are victim, derive r, traffic police, head of ktms, owner, system
administrator. Since mysql is structure query language table creation in sql.

Before creation table in the mysql there should be database creation by the
following simple sql.
3.8.1 Database creation
<?php
$mysql_hostname = "localhost";
$mysql_user = "root";
$mysql_password = "";
$mysql_database = "ktto_db";
$prefix = "";
$bd = mysql_connect($mysql_hostname, $mysql_user, $mysql_password) or die("Could not connect database");
if(mysql_query("CREATE DATABASE IF NOT EXISTS ktto_db",$bd))
echo "Success.....DataBase is Created!";
else

echo"Error in Creating Database!: " . mysql_error();
mysql_close($bd);
?>
3.8.2 Interface Design

The interface part is the medium of communication media between the user of the
online KTMS system with the application part of the system.
The interface is completely based on the web application technology.
In this application there are different interfaces with different functions.

Home page Interface

Home interface is the main interface of the system. This interface contains all other
interface buttons and extra information about KTMS system.
Fig:3.5 Interface of home page

Login interface
It is used for administrative parts to control the KTMS system.
Each user has different privileges they have different login forms.
That is username and login password.
The following form enables the system to be secured from unauthorized access.
The new system can be accessed by authorized personal only. The security system
is having two different levels of login system.
1) Administrator: The administrator is having full permission to access

including changing the setting, Viewing Reports generated form the
recorded data.
2) Data Recorder: Is having the permission to add, edit, delete and modify the
data record.
Traffic police login page
The User enter user name

The User enter password
The user selects their privilege from the drop down box
Click login
After doing the tasks success fully the user get the page he wants according to the
privilege they have.

Fig:3.6 Traffic police login page
Head of KTMS login page

This login form used to access all services that are included within our system.
The services are: 1. Traffic police interface form
1. victim interface form

2. accident interface form
3. driver interface form
4. owner interface form
5. etc

Fig.3.7 Head of KTMS login page

Create user account
This form is used to create new traffic police account.
Fig:3.8 Create account page

Modify user account:
This form is used to change the pre-existing traffic police account.
Fig:3.9 modify traffic account page

Delete user account :

This form is used to delete when the users want to change the traffic police
account by using user id.
Fig:3.10 Delete user account page

Traffic police home page
Home interface is the main interface of the system. This interface contains all other
interface buttons and extra information about traffic police in the system.
Fig:3.11 Traffic police home page

Traffic police Register page
The register page is the register interface of the system. This interface all r
otheinterface buttons and extra information about traffic police system
contains.
Fig:3.12 Traffic police register page

Traffic police update page
The update page is used for changing the information when it is necessary in this
form of the system. This interface contains all other interface buttons and extra
information about traffic police system.
Fig :3.13 Traffic police Update page

Traffic police Delete page
The delete page is used for deleting the information when it is necessary in this
information about traffic police system.
Fig :3.14 Traffic police delete page

Traffic police Search page
The search page is used for searching the information when it is necessary in this
form of the system by using traffic ID. This interface contains all other interface
buttons and extra information about traffic police system.
Fig :3.15 Traffic police search page

Accident Register page
This page used to describe or fills the general description about the accident
and also damaged description, accident description, and road description are filled
in this accident form
Fig : 3.16 Accident register page

Accident modify page
The modify page is used for modifying the information when it is necessary in this
information about accident information in the system.
Fig :3.17 Accident modify page

Accident Delete page
form of the system by using accident ID.This interface contains all other interface
buttons and extra information about accident in the system
Fig :3.18 Accident Delete page

Accident Search page
form of the system by using accident ID. This interface contains all other interface
buttons and extra information about accident in the system.
Fig : 3.19 Accident search page

Driver home page
The home page is the main interface of the deriver form in the system. This
interface contains all other interface buttons and extra information about the
deriver in the system.
Fig :3.20 Driver Home page

Driver Register page
This page used to describe or fills the general description of about the deriver
information.
Fig :3.21 Driver register page

Driver Modify page
information about deriver information in the system.

Fig :3.22 Driver modify page
Driver Delete page
form of the system by using vehicle plate. This interface contains all other
interface buttons and extra information about deriver in the system
Fig :3.23 Driver Delete page

Driver Search page
form of the system by using vehicle plate. This interface contains all other
interface buttons and extra information about deriver in the system.
Fig:3.24 Driver Search page

Owner Home page

The home page is the main interface of the owner form in the system. This
interface contains all other interface buttons and extra information about the owner
in the system.
Fig:3.25 Owner Home page

Owner Register page
This page used to fill the description 0f the owner like owner id, first name, last
name, age, sex, region, zone, woreda, Kebele and etc.

Fig:3.26 Owner Register page
Owner Modify page
information about owner in the system.

Fig:3.27 Owner Modify page
Owner Search page
form of the system by using owner ID. This interface contains all other interface
buttons and extra information about owner in the system.

Fig:3.28 Owner search page
Owner Delete page
form of the system by using owner ID. This interface contains all other interface
buttons and extra information about owner in the system .

Fig:3.29 Owner Delete page
Victim Register page

This page used to describe or fills the general description(information) about

the victim.
Fig:3.30 Victim Register page
Victim Modify page

form of the system by using victim ID.This interface contains all other interface
buttons and extra information about victim in the system
Fig :3.31victim modify page
Victim Delete page

form of the system by using victim ID. This interface contains all other interface
Fig: 3.32 Victim Delete page
Victim Search page

form of the system by using victim ID. This interface contains all other interface
Fig: 3.33 Victim Search page
Head of KTMS Home page

The home page is the main interface of the head of KTMS form in the system. This
interface contains all other interface buttons and extra information about the head
of KTMS in the system.
Fig :3.34 Head of KTMS Home page
Chapter-four
4. Implementation and testing documents

4.1 Objective of Implementation

The objective of systems implementation phase is to convert the final physical

system specifications into working and reliable software and hardware, document
the work that has been done, and provide help for current and future users and care
takers of the system.
Constraints on implementation
Constraints are situations that limits on implementing the new system. Some of the
things that limit us on developing the new system are:
the RAM speed of the computes

Scarcity of the experiance
Deficiency of resources
The software ( E -draw 2) needs a lot of time to copy and install
Testing by Requirements
3.1.1. Error handling Error handling are summarized in the following
table.
Expected Result Error Handling
Data Type Validation Accepts only valid data Displays the
corresponding message
box
Password Checking Allows only authorized Display Password or
person to login into the user name error
system massage
No Inputs Allows the new Displays an error
application to accept the message box
needed data rather than
null.
Calculations Allows the system to
calculate automatically --------
rather than performing
calculations by the user
Date Allows the new system
to recognize the current ------------
date of the pc.

4.2 Testing by scope
Unit testing:
- Each unit of component is tested alone in an attempt to discover any
errors that may exist in the code.
-Login into the system using different access levels.
-Tasks related with user accounts like creating new user accounts,
change passwords, Disabling or removing currently available accounts.
-Performing different operations like add, update, search and delete.
-Viewing currently recorded data from the database.
-Viewing Reports generated from the currently available data.
Integration and system testing:
In integration testing the entire sub systems are tested together as one
system. The overall system is tested on the basis of functionality and
error handling. This testing also primarily checks the correctness of
the data entered in to the database and retrieved out of the database.
4.3 Sample codes and sample output screens

The detailed specifications produced during the design phase are translated into
hardware, communication, and executable software. The coding is mainly done for
the four main modularitys (operations) that are performed in accessing the
database, these are the add, update, search and delete in addition, codes related to
with user access and privilege like login, change password, remove user (existing)
and error handling .
Login (Security)
This code enters into the specified page as the authorized person selects or needs to
perform some operations. A sample code for login into KTMS is stated as follows:

Adminstrator login form
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>login form</title> </head>
<body>
<form name="loginform" action="login_exec.php" method="post">
<fieldset style="background-color:#99FF99;">
<table width="50" border="0" align="center" cellpadding="-10" cellspacing="-

10" bgcolor='red'>
<tr>
<td colspan="1">


<font color="#0000FF" size="2">
<?php
if( isset($_SESSION['ERRMSG_ARR']) &&

is_array($_SESSION['ERRMSG_ARR']) &&
count($_SESSION['ERRMSG_ARR']) >0 ) {
echo '<ul class="err">';
foreach($_SESSION['ERRMSG_ARR'] as $msg) {
echo '<li>',$msg,'</li>';
echo '</ul>';
unset($_SESSION['ERRMSG_ARR']);
?> </td>
</tr>
<tr><center><h1><font face="Monotype Corsiva">Adminstrator Login

Form</font></h1></center>
<td ><div align="right"><b>Username:</b></div></td>
<td ><input name="username" type="text" /></td>
</tr>
<tr>

<td><div align="right"><b>Password:</b></div></td>
<td><input name="password" type="password" /></td>
</tr>
<tr>
<td><div align="right"></div></td>
<td><b><input type="submit" value="Login" /></b>
<input type="reset" value="Clear" /></td>
</tr>
</table>
</center>
</fieldset>
</form>
</body>
</html>
User login form

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

<head>
<title>login form</title> </head>
<body>
<form name="loginform" action="trafficlogin_exec.php"

method="post">
<table width="309" border="0" align="center"

cellpadding="2" cellspacing="5"bgcolor='#FFCCF0'>

<tr><legend align="center"><h1><font color="blue">User Login

page</font></h1>
</legend>
<td colspan="2">
<?php

echo '</ul>';
?>
</td>
</tr>
<tr>
<td width="116"><div align="right"><font color="black"

><h4><i>Username</i></h4></font></div></td>
<td width="177"><input name="username" type="text" /></td>
</tr>

<tr>
<td><div align="right"><font
color="black"><h4><i>Password</i></h4></font></div></td>
</tr>
<tr>
<td><input name="" type="submit" value="login" /></td>
</tr>
</table>
</form>
</body>
</html>
Home page implementation code
< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

<head>
<title>Home page</title>
<?php
//Start session
session_start();
//Unset the variables stored in session
unset($_SESSION['SESS_ADMINSTRATOR_ID']);
unset($_SESSION['SESS_USER_NAME']);
unset($_SESSION['SESS_PASSWORD_NAME']);
?>
<?php
$prefix = "";
$bd = mysql_connect($mysql_hostname, $mysql_user, $mysql_password) or

die("Could not connect database");
if(mysql_query("CREATE DATABASE IF NOT EXISTS ktto_db",$bd))
echo "Success.....DataBase is Created!";
else

echo"Error in Creating Database!: " . mysql_error();
mysql_close($bd);
?>
<?php
//create accident form table
$prefix = "";

DIE('Connection to host is failed, perhaps the service is down!');
if (!$bd)
die('Could not connect!: ' . mysql_error());
mysql_select_db("ktto_db",$bd) or die("Could not select database");
$qry="CREATE TABLE IF NOT EXISTS adminstrator(
admin_id int(10) NOT NULL,
username varchar(25) NOT NULL,
password varchar(15) NOT NULL,

retype_password varchar(15) NOT NULL,
firstname varchar(30) NOT NULL,
lastname varchar(30) NOT NULL,
sex varchar(10) NOT NULL,
Email varchar(30) NOT NULL,
contact varchar(30) NOT NULL,PRIMARY KEY(admin_id))";
// Execute query
mysql_query($qry,$bd);
mysql_close($bd);
?>
<?php
//create accident form table
$prefix = "";

if (!$bd)

$qry="CREATE TABLE IF NOT EXISTS headofktto_account(
head_id int(10) NOT NULL,
Email varchar(30) NOT NULL,
contact varchar(30) NOT NULL,PRIMARY KEY(head_id))";
// Execute query
mysql_close($bd);
?>
<?php
//create tarfficaccount table
$prefix = "";

if (!$bd)
$qry="CREATE TABLE IF NOT EXISTS trafficaccount1(
user_id int(10) NOT NULL,
email varchar(100) NOT NULL,
contact varchar(30) NOT NULL,PRIMARY KEY (user_id))";
// Execute query
mysql_close($bd);
?>

<?php
//create tarfficform table
$prefix = "";

if (!$bd)
$qry="CREATE TABLE IF NOT EXISTS trafficform(
traffic_id int(15) NOT NULL,
date varchar(15) NOT NULL,
middlename varchar(15) NOT NULL,
privilege varchar(30) NOT NULL,
currentplace varchar(30) NOT NULL,

newplace varchar(100) NOT NULL,
coveragearea varchar(100) NOT NULL,
responsibility varchar(100) NOT NULL,
examination varchar(100) NOT NULL,
lengthoftime varchar(100) NOT NULL,
contact varchar(30) NOT NULL,PRIMARY KEY (traffic_id))";
// Execute query
mysql_close($bd);
?>
<?php
//create ownerform table
$prefix = "";

if (!$bd)

$qry="CREATE TABLE IF NOT EXISTS ownerform(
owner_id int(15) NOT NULL,
age int(30) NOT NULL,
citzen varchar(100) NOT NULL,
region int(10) NOT NULL,
zone varchar(100) NOT NULL,
woreda varchar(100) NOT NULL,
kebele varchar(100) NOT NULL,
description varchar(500) NOT NULL,PRIMARY KEY(owner_id))";
// Execute query
mysql_close($bd);
?>
<?php
//create ownerform table
$prefix = "";

if (!$bd)
$qry="CREATE TABLE IF NOT EXISTS commentform(your_name varchar(35)

NOT NULL,
e_mail varchar(35) NOT NULL,
type_your_comment_here varchar(500) NOT NULL)";
// Execute query
mysql_close($bd);
?>
<?php

//create driverform table
$prefix = "";

if (!$bd)
$qry="CREATE TABLE IF NOT EXISTS driverform(
vehicle_plate varchar(254) NOT NULL,
driver_id int(354) NOT NULL,
date date(3544) NOT NULL,
vehicle_type varchar(35) NOT NULL,

drivers_licences varchar(30) NOT NULL,
crime_type varchar(25) NOT NULL,
health_description varchar(25) NOT

NULL,
crime_location varchar(25) NOT NULL,
Paintiff_traffic_name varchar(25) NOT

NULL,
charged_no int(25) NOT NULL,
punishement_location varchar(10) NOT

NULL,
punishement_date int(20) NOT NULL,
serial_code int(18) NOT NULL,
amount int(50) NOT NULL,
control_property varchar(25) NOT NULL,
PRIMARY KEY(vehicle_plate))";
// Execute query
mysql_close($bd);
?>
<?php
//create tarfficform table
$prefix = "";

if (!$bd)
$qry="CREATE TABLE IF NOT EXISTS accidentform(
accident_id int(18) NOT NULL,
recentevent varchar(300) NOT NULL,
Hour varchar(300) NOT NULL,

quantity int(30) NOT NULL,
educational_level varchar(100) NOT

NULL,
relationship varchar(100) NOT NULL,
experiance varchar(100) NOT NULL,
drivers_licences varchar(100) NOT

NULL,
vehicle_worked_duration varchar(102)
NOT NULL,
vehicle_type varchar(30) NOT NULL,
owner_vehicle varchar(100) NOT NULL,
vehicle_problem varchar(100) NOT NULL,
road_of_an_accident varchar(100) NOT

NULL,
accident_area varchar(100) NOT NULL,
division_of_road varchar(100) NOT

NULL,
structure_of_road varchar(30) NOT NULL,
joinment_area varchar(30) NOT NULL,

road_safety varchar(30) NOT NULL,
road_condition varchar(30) NOT NULL,
light_condition varchar(30) NOT NULL,
weather_condition varchar(30) NOT

NULL,
type_of_accident varchar(30) NOT NULL,
movement_of_vehicle varchar(30) NOT

NULL,
PRIMARY KEY (accident_id))";
// Execute query
mysql_close($bd);
?>
<?php
//create victimform table
$prefix = "";

if (!$bd)
$qry="CREATE TABLE IF NOT EXISTS victimform(victim_id varchar(10) NOT

NULL,
PRIMARY KEY(victim_id))";
// Execute query
mysql_close($bd);
?>
<?php

echo date("d-m-y") . "<br>";
?>
<script type="text/javascript">
var d=new Date()
var weekday=new
Array("Sunday","Monday","Tuesday","Wednesday","Thursday","Friday","Saturda
y")
var monthname=new
Array("Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec
")
document.write(weekday[d.getDay()] + " ")
document.write(d.getDate() + "th ")
document.write(monthname[d.getMonth()] + " ")
document.write(d.getFullYear())
</script>
<script>
function displayDate()
document.getElementById("demo").innerHTML=Date();
</script>
<script>
function printpage()

window.print();
</script>
<script>
function goBack()
window.history.back()
</script>
<script>
function goForward()
window.history.forward()
</script>
<style>
input[type="text"]
background-color:#99FFCC;
input[type="button"]
{
background-color: #CCFF33;
input[type="reset"]
background-color: #CCFFFF;
input[type="password"]
background-color:#99FFCC;
input[type="submit"]
background-color:#99FFFF;
</style>
<style type="text/css">
ul {
font-family: Arial, Verdana;
font-size: 14px;
margin: 0;
padding: 0;
list-style: none;
}
ul li {
display: block;
position: relative;
float: left;
li ul {
display: none;
ul li a {
display: block;
text-decoration: none;
color: green;
border-top: 1px solid #CCCC66;
padding: 5px 15px 5px 15px;
background: #CCCC33;
margin-left: 1px;
white-space: nowrap;
ul li a:hover {
background: #FF66CC;
li:hover ul {
display: block;
position: absolute;
li:hover li {
float: none;
font-size: 11px;
li:hover a { background: #99FF99; }
li:hover li a:hover {
background: white";
h3 {
color:white;
</style>
</head>
<body>
<table width="1197" height="117" border="1">
<tr>
<div>
<td width="1187" height="111" background="3a.jpeg"><span class="style4">
<center>
<i><B><font color="#6633FF" size="4" >

<img src='t1.jpeg' width="233" height="102"/>WEL COME TO
KOMBOLCHA TOWN TRAFFIC MANAGEMENT SYSTEM<img

src='t1.jpeg' width="272" height="101"/>
</font></B></i>
</center></span></td>
</div>
</tr>
</table>
<table width="1194" height="12" border="1" align"center">
<tr>
<td height="8"><ul id="menu">
<li><a href="../kttohomepage.php"><font color='#336600' face="Monotype

Corsiva"size="+2">        &nb
sp;          &nbsp
;    HOME  </font></a></li>
<li><a href="#"><font color='#336600'size="+2" face="Monotype

Corsiva">  ABOUT US  </font></a>
<ul>
<li><a href="../bg.html"><font color="#6600FF"

>Background</font></a></li>
<li><a href="../mission.html"><font
color="#6600FF">Mission</font></a></li>
<li><a href="../vision.html"><font
color="#6600FF">Vision</font></a></li>
<li><a href="../values.html"><font
color="#6600FF">Values</font></a></li>

</ul>
</li>
<li><a href="../c1.php"><font color='#336600'size="+2" face="Monotype

Corsiva">  CONTACT US    </font></a>
<ul>
<li><a href="../contact.html"><font
color="#6600FF">Address</font></a></li>
</ul>
</li>
<li><a href="kttohomepage.php"><font
color='#336600'size="+2"face="Monotype Corsiva"
>  SERVICES   </font></a>
<ul>
<li><a href="loginpage.php"><font color="#6600FF">Traffic police

</font></a></li>
<li><a href="headofktto.php"><font
color="#6600FF">Head of KTMS</font></a></li>
</ul>
</li>
<li><a href="../c1.php"><font color='#336600' size="+2" face="Monotype

Corsiva">   FEEDBACK   </font></a>
<ul>
<li><a href="../comment.html"><font color="#6600FF">Send your

comment</font></a></li>
</ul></li>

<li><a href=""><font color='#336600' size="+2"

face="Monotype
Corsiva">  &nbsp   &nbsp
&nbsp   &nbsp   &nbsp  &nb
sp;&nbsp   &nbsp   &nbsp
&nbsp     </font></a>
<ul>
<li><a href=""><font color="#6600FF"></font></a></li>
</ul></li>
</fieldset>
</table>
<table bgcolor='#FFFF99' width="1201" height="478" border="1" align="t">
<tbody>
<tr >
<td height="472">
<td width ="50" height="50" valign="top" ><font color="green"

face="Monotype Corsiva" size="+3"></br>
<p id="demo"> </p>
<marquee id=m1 SCROLLDELAY=2 SCROLLAMOUNT=2 direction=left>
<p><font color="green"><b>Wel-come to Kombolcha

town</font><font color="cyan">Traffic</font> <font color="red">Managment
System</b></font></p>
</marquee>
</font>
<form name="loginform" action="login_exec.php" method="post">

<table width="50" border="0" align="center" cellpadding="-10" cellspacing="-

10" bgcolor='red'>
<tr>
<td colspan="1">
<font color="#0000FF" size="2">
<?php

echo '</ul>';
?> </td>
</tr>
<tr><center><h1><font face="Monotype Corsiva">Adminstrator Login

Form</font></h1></center>
<td ><div align="right"><b>Username:</b></div></td>
<td ><input name="username" type="text" /></td>

</tr>
<tr>
<td><div align="right"><b>Password:</b></div></td>
</tr>
<tr>
<td><b><input type="submit" value="Login" /></b>
<input type="reset" value="Clear" /></td>
</tr>
</table>
</center>
</fieldset>
</form>
<td background="t3.jpeg" width="603" valign=" width=""><center> <h1

align="center" style="text-decoration:blink">
<legend ><font color=#FF00FF face="Monotype Corsiva" size="22">Wel-come

to kombolcha Traffic Managmenet System</legend>
</font>
</h1>
</td>
<td width="336" valign="top" width="311">

<tr>
<td background="kocha6.jpg"><span class="style4"><span

class="style3"><span class="style2"> </span> </td>
</tr>
</table>
<tr>
<td ><span class="style3">
<marquee id=m1 SCROLLDELAY=2 SCROLLAMOUNT=2 direction=up>
<p><font color="green"><b>Wel-come to Kombolcha

</font><br/><font color="cyan">Town Traffic</font><br/> <font color="red">
managment system</b></font></p>
</marquee>
</span> </td>
</tr>
</table></td>
</tr>
</table>
<tr>
<div>
<td width="1187" height="25" background="blue2.jpeg"/><span

class="style4">
<center>

<i><B><font color='#FFFFFF' size="4"><font face="Monotype

Corsiva">Copyright Group members of IT 4th year students</font></B></i>
</center></span></td>
</div>
</tr>
</table>
<div align="center">
<input type="button" value="Back" onClick="goBack>
<input type="button" value="Forward" onClick="goForward()"></div>
</body>
</html>
4.4 SUMMARY, CONCLUSION AND RECOMMENDATION

In developing this system we have observed that there are other systems that need
to be Automated in the kombolcha town traffic management system is relation to
our project.The manual System hinders the management system not to use its
resources efficiently and serve its people effectively. However, we have seen great
interest of the stakeholders of the management system to automate some manual

systems that needs to be automated. After spending seven to nine months on

developing this project, we have tried to automate the new computerized traffic
record management system of the station.
We have come to conclusion that
The record system needs some improvements before it is applied to a real

application; which is created due to the time shortage, shortage of experience and
other technical Problems. Taking these problems in to account, if the materials
requested are provided and all the installation process is completed; the victim
information system will work well.
More over, the system will bring a radical change on current working
condition of the traffic station. Specially, to operations concerned the record
system.
The record management system conversion from the old system to this new
system is based on a radical change which needs a complete acceptance from the
users of the system as
Was hoped and agreed with stakeholders at the beginning of this project.
Finally, we concluded that the traffic crime record management system will
be taken as a means for the Police station to deliver efficient and effective report
generating, crime recording and information sharing to the traffic station.
4.4.1 COMMENDATIONS
Finally, we the project team members recommend the following points:
This system will give a solution for somt the station should prepare a conducive
environment to test such systems.

There should be a healthy working environment, specifically in regard to the

database
Administration that we are going to assign the total authority to view the security
database and handle problems that may arise in the application of the traffic crime
record management system. So it is better to assign this position to some one who
is trustworthy, accountable and responsible person.
The station has to fulfill all the infrastructures needed for the system
implementations.
In addition, all the specifications mentioned for the hard wares and soft wares are
Mandatory.
The different data manipulators in the traffic crime record management

system, who are the main users of the record management system, must have
knowledge about this technology.
We recommend to the Universitys department of Information Technologys
to provide its
Students the opportunity to work on developing systems that are aimed in solving
the real Problems of the society.
The last but not least, developed considering the expansions that the record office
of the station will undergo in the near future, we recommend the
The traffic station uses this system as a basement and sees how its problems can be
solved.

4.5 References
nd
1, System Analysis and Design 2 Edition
2, sample project of Wollo University Dormitory system.
3, Internet access.
4, PHP books, java script, and CSS books.

FINAL Project

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

FINAL Project

Hochgeladen von

Copyright:

Verfügbare Formate

Bule hora town traffic management system

In partial fulfillment of the requirement for the degree of Bachelor of Science in

TITLE: TRAFFIC MANAGEMENT SYSTEM FOR

DEVELOPED AND SUBMITTED BY:

Advisor, BEHAYLU.S(BSc) June 2017

Table 1.2 Gantt chart..8

Table 3.2 un normalized table ...35

Table 3.3 first normalized table.....36

Table 3.4 Second normalized table....36

Table 3.4.1 victim table .36

Table 3.4.2 traffic table ......37

Table 3.4.3 driver table ....37

Table 3.5 third normalized victim table ...37

Fig 2.2 Level-0 diagram of the existing system.15

Fig 2.3 Context diagram of the new system.19

Fig 2.4 Level-0 diagram of new System (DFD).. 20

Fig 3. 3the relation among all entities.33

Fig 3.4 E-R diagram34

Fig 3.5 Interface for home page..42

Fig 3.6 Interface for traffic police login page..44

Fig 3.7 Interface for head of KTMS login page45

Fig 3.8 create account page..46

Fig 3.9 modify traffic account page.47

Fig 3.10 delete user account page....48

Fig 3.11 traffic police home page.49

Fig 3.12traffic police register page50

Fig 3.13 traffic police update page....51

Fig 3.14 traffic police delete page.52

Fig 3.16 accident register page.54

Fig 3.17 accident modify page..55

Fig 3.18 accident delete page....56

Fig 3.19 accident search page57

Fig 3.20 driver home page.....58

Fig 3.21 driver register page....59

Fig 3.22 driver modify page.60

Fig 3.23 driver delete page...61

Fig 3.24 driver search page......62

Fig 3.25 owner home page........63

Fig 3.26 driver register page..64

Fig 3.27 driver modify page..65

Fig 3.28 driver search page66

Fig 3.29 driver delete page.....67

Fig 3. 30 victim register page........68

Fig 3. 31 victim modify page....69

Fig 3. 32victim delete page...70

Fig 3. 33 victim search page......71

Fig 3. 34 head of KTMS home page....72

Acronyms and Abbreviations

SQL: structural query language

PHP: Hyper text preprocessor

HTML: Hyper text markup language

DFD: Data flow diagram

E_R: Entity relationship

1.1 BACKGROUND/OVERVIEW ..................................................................................................................................1

CHAPTER- TWO ...................................................................................................................................................... 9

2. BUSINESS AREA ANALYSIS .................................................................................................................................. 9

2.1 SYSTEM ANALYSIS OVERVIEW .....................................................................................................................................9

3. SYSTEM DESIGN ............................................................................................................................................... 25

3.1 INTRODUCTION ...................................................................................................................................................25

4. IMPLEMENTATION AND TESTING DOCUMENTS ............................................................................................... 70

4.1 OBJECTIVE OF IMPLEMENTATION .............................................................................................................................70

In Kombolcha town there are governmental and non-governmental organizations which

Bule hora University Department of ECE Page 1