traffic accident records information system in

TRAFFIC ACCIDENT RECORDS INFORMATION SYSTEM IN METROPOLITAN

CITIES

CASE STUDY

CENTRAL POLICE STATION

KAMPALA

BY

MUMBERE TSONGO ANDREW

BCS/20018/82/DF

AND

WAMIMBI GILBERT

BIT/200021821DU

A PROJECT REPORT SUBMITTED TO THE COLLEGE OF APPLIED SCIENCES

AND TECHNOLOGY OF KAMPALA INTERNATIONAL UNIVERSITY IN

PARTIAL FULLFILLMENT FOR THE AWARD OF A

BACHELOR DEGREE IN COMPUTER SCIENCE

AND INFORMATION TECHNOLOGY

RESPECTIVELY

FEBRUARY, 2012

DECLARATION

I MUMBERE TSONGO ANDREW and WAMIMBI GILBERT do hereby declare to the best of

our knowledge that this graduation project is our original work and that it has never been

submitted to any university or any other institution.

Signedby.~~..........~... Signedby......g~

MUMBERE TSONGO ANDREW WAMIMBI GILBERT

BCSI2001 8182/DF BIT/20002/82/DU

APPROVAL

This is to certify that this project proposal entitled “Traffic Accident Records Information

System” is under my supervision and guidance and is now ready to be submitted to the School of

Computer Studies with my approval.

Signature. .

Mr. KAMULEGEYA GRACE

Supervisor

Date ..Jt?...I

DEDICATION

I Mumbere Tsongo Andrew, dedicate this research project to my dad, Mr. Paluku Buhimbo Jean

Pieffe, my mum Ms. Masika Mundala Jeanne whom through their unending love supported me

financially and morally throughout my study in the university. My brothers, sisters and friends

you’re all a great inspiration to me.

I Wamimbi Gilbert, dedicate this research project to my brother Herbert-who inspired me; to my

parents who natured me; my wife Jane and my children Reagan and Renee who always

persevered with the little I provided during the course of my studies. My family continues to be a

source of love, inspiration and motivation, Thank you.

‘H

ACKNOWLEDGEMENT

We wish to express our sincere gratitude to the Almighty God for granting us the opportunity to

study through university. Special thanks to our supervisor Mr. Kamulegeya Grace whose

guidance and effort made this dissertation a success.

We would also like to express our gratitude to our Head of Research in the School of Computer

Studies Engineer Kassawuli for his willingness and readiness to support and encourage us

always.

We recognize various persons of Central Police Station-Kampala who responded to our research

interviews and offered some documents to us for review; their valuable information helped us

accomplish the requirements for the research objectives.

iv

TABLE OF CONTENTS

DECLARATION

APPROVAL II

DEDICATION

ACKNOWLEDGEMENT iv

TABLE OF CONTENTS v

LIST OF FIGURES ix

LIST OF ACRONYMS xii

LIST OF TABLES xiii

CHAPTER ONE 1

1.0 Introduction 1

1.1 Background of the study 1

1.2 Problem statement 2

1.3 Main objective 2

1.4 Specific Objectives 2

1.5 Research questions 3

1.6 Scope of the Study 3

1.7 Significance of the study 3

1.8 Conceptual Framework 4

CHAPTER TWO s

LITERATURE REVIEW 5

2.0 Introduction 5

2.1 Traffic accident 5

2.2 System 5

V

2.3 Information System .5

2.4 Distributed System 6

2.5 Investigation of the TARTS 6

2.6 Analysis of the TARIS 6

2.7 Design of the TARTS 6

2.8 Implementation ofthe TARTS 7

2.9 Testing of the TARTS 7

2.10 Report of the TARTS 8

2.11 Conclusion 8

CHAPTER THREE 9

METHODOLOGY 9

3.1 Introduction 9

3.2 Organization to be studied 9

3.3 Requirements elicitation techniques 9

3.4 Adopted research techniques 9

3.4.1 Interviews 9

3.4.1.1 Advantages of Interviews 9

3.4.2 Document review 10

3.4.2.1 Advantages of document review 10

3.5 Development Methodology 10

3.5.1 Systems Development Life Cycle 10

3.5.1.1 Project identification and selection 11

3.5.1.2 Project initiation and planning

3.5.1.3 Analysis phase 12

3.5.1.4 Design phase 12

vi

4.3.2.11 Create New Account Page design .31

4.3.2.12 Data Output Design 32

4.3.3 UML Diagrams 32

4.3.3.1 UML Activity Diagram 32

4.3.2.12 Data Output Design 32

4.3,2.12 Data Output Design 32

4.3.3.2 UML Use case diagram 33

4.3.3.3 UML Sequence diagram 34

4.3.3.4 UML Class Diagram 35

CHAPTER FiVE 36

SYSTEM TESflNG, IMPLEMENTATION AN]) EVALUATION 36

5.1 The developed system 36

5.1.1 Home Page 36

5.1.2 User Login 37

5.1.3 Error message on unsuccessful login 38

5.1.4 Sample form design 38

5.1.5 About us page 40

5.1.6 Information page 40

5,1.7 Sample report 41

5.2 Program Testing 43

5.3 User training, operation and support 43

5.3.1 User Training 43

5.3.2 Operation and Support 44

CHAPTER SIX 45

DISCUSSION, RECOMMENDATIONS AND CONCLUSION 45

VIII

6.1 Discussion .45

6.2 Conclusion .45

6.3 Recommendations 46

6.5 Areas for Further Research 46

References 47

APPENDICES 49

Appendix A 49

AppendixB 50

Appendix C 51

ix

LIST OF FIGURES

Figure 1.0 Conceptual framework

Figure 3.1 SDLC life cycle

Figure 3.2 component based development life cycle

Figure 4.1 bar graph on response of an idea about using computers

Figure 4.2 numbers of respondents per station

Figure 4.3 responses ofOfficers who participate in sending accident records

Figure 4.4 responses ofOfficers who do not participate in sending accident records

Figure 4,5 respondents supporting the introduction of the new system

Figure 4.6 showing the structure of webpages

Figure 4.7 data entry form

Figure 4.8 Home Page design

Figure 4.9 about us page design

Figure 4.10 Information Page Design

Figure 4.11 Police Stations Page design

Figure 4.12 login page design

Figure 4.13 administrator login page design

Figure 4.14 Manage Accounts Page design

Figure 4.15 Create New Account Page design

Figure 4.17 TJML Activity Diagram

x

Figure 4.18 UML Use case diagram

Figure 4.19 UML Sequence diagram

Figure 4.20 UML Class Diagram

Figure 5.1 Home Page

Figure 5.2 User Login

Figure 5.3 Error message on unsuccessful login

Figure 5.4 Sample form design

Figure 5.5 About us page

Figure 5.6 Information page

Figure 5.7 Sample traffic report

xi

LIST OF ACRONYMS

SDLC — Systems Development Life Cycle

TARTS — Traffic Accident Records Information System

0/C — Officer in Charge

CBD — Component Based Development

TAR - Traffic Accident Records

TSD — Traffic Station Diary

PHP — Hypertext Pre-processor

HTML — Hypertext Markup Language

CPS — Central Police Station

o_h — Occurrence hour

o_t — Occurrence time

0_rn— Occurrence minute

r_h — Report hour

r_m — Report minute

r_t — Report time

nature acc — Nature of accident

nature dam — Nature of damage

Tarref— Traffic Accident Report Reference

Tsdref— Traffic Station Diary Reference

XH

o Keeping traffic accident records

Each station collects Traffic Accident records and sends them to Central Police Station on a daily

basis. These records are analyzed and compiled into monthly and yearly accident statistical

reports. Deductions can be made from the reports on whether accident occurrence has increased

or not, the probable causes of the accident, the nature of accident among others. This information

can be used to support decision making on the policies and strategies to be developed to reduce

road accidents.

The researchers would like to develop an information system for sending traffic accident records

to Central Police Station—Kampala. Once given the cooperation, sending of traffic accident

records to Central Police Station—Kampala will be made simpler since the developed system

shall ensure reliable, quick and secure access to information.

L2 Problem statementCentral Police Station Kampala uses a manual system to receive Traffic Accident records from

different Police Stations. The increased number of records kept about accidents has made this

process difficult and tedious. The System is uneconomical, not secure and time consuming. It is

in view of the above problem that we seek to computerize the existing information system.

L3 Main objectiveTo design and implement an on-line information system for sending traffic accident records to

Central Police Station.

L4 Specific Objectives• To investigate the existing problems with the information system used to send accident

records to Central Police Station-Kampala.

o To analyze the requirements for the Information System.

• To design and implement Information System

• To test the Information System

• To compile a project report

2

L8 Conceptual FrameworkThe system was designed in such a way that there will be multiple interfaces for performing

different functions. Interfaces will be designed using php scripts. Users will be required to enter

their credentials (username and password) before logging into the system to access the staff area.

Thereafter, the user will choose from the available choices to perform whatever task that they

want.

The above mechanism was implemented as follows:

o Interfaces for performing different functions such as sending accident records, login, creating

new users, creating new administrators.

. A database (mysql) for storing the data captured from the interfaces.

Accidentrenort viewer

Figure 2.1 Conceptual framework

4

CHAPTER TWO

LITERATURE REVIEW

2.0 IntroductionThis chapter was aimed at reviewing the related literature on the question under study. The

problem under study was to develop an information system for sending traffic accident records to

Central Police Station.

2.1 Traffic accidentThis is an unexpected incidence with potential for harm occurring through the movement or

collision of vessels, vehicles or persons along a land, water, air or space route.

(http://www.eionet.europa. eu/gemetlconcept?cp=8583. November, 2011).

2,2 SystemMicheal J. Powers, Paul H. Cheney and Gallen Crow(1990) define System as a set of

interrelated, interacting components that function together as an entity to achieve specific results

whereas Jeffrey A.Hoffer, Joey F. George defines System as an interrelated set of components,

with an identifiable boundary, working together for some purpose. According to Effy Oz (2002),

System is an array of components that work together to achieve a common goal or multiple

goals. Jean Warland (1991) defines System as a device that transforms inputs into outputs. These

definitions agree that System refers to a set of components working together for a common

purpose. However, they ignore the flict that a System follows an organized information process

which is considered as an important element of this research project.

2.3 Information SystemAccording to M. Kroenke (2000), an information system is an arrangement of people, data,

processes, information presentation and information technology that interact to support and

improve day to day operations in a business as well as support the problem solving and decision

making needs of management and users. In addition, information technology is a contemporary

term that describes the combination of computer technology with telecommunications

technology. It significantly expands the power and potential of most information systems.

Management Information system is an information system application that provides

management-oriented reporting. These reports are usually generated on a predetermined

5

schedule and appear in a pre-arranged format. Examples are budget forecasting and analysis,

financial report, inventory reporting, production scheduling, sales forecasting and many more.

2A Distributed SystemDavid M.Kroenke (2000) defines Distributed System as a system in which the application

programs of a database are processed on two or more computers. According to James A. O’Brien

(2003), Distributed system is a form of decentralization of information processing made possible

by a network of computers dispersed throughout an organization. Processing of user applications

is accomplished by several computers interconnected by a telecommunication network, rather

than relying on the one centralized computer facility or on the decentralized operation of several

independent computers. The researchers consider these defmitions suitable for the research

project due to the fact that data is processed on different computers in different locations

interconnected by a network.

2~5 Investigation of the TARTSAccording to Benson (2002), to investigate is to observe or study by close examination and

systematic inquiry.

2~6 Analysis of the TARTSJoseph S. Valacich, Joey F. George and Jeffrey A Hoffer (1996), define Analysis as the third

phase of SDLC in which the current system is studied and alternative replacement systems are

proposed whereas, Jeffrey L.Whitten and Lonnie D. Bently (1998), define analysis as the study

of a business problem domain to recommend improvements and specify the business

requirements for the solution. The above definitions agree that analysis is the study of a problem

in order to propose solutions but didn’t tell us how the study is done and whether the proposed

improvements are used or not. The definition that suits this project is derived from James A.

Senn (1984), who defines analysis as a process of gathering, examining and interpreting flicts,

diagonising problems and using 1~cts to improve the system. He emphasized that, often, the

larger problem is divided into smaller components that can be more easily examined and dealt

with.

2~7 Design of the TARTSAccording to Powers, Cheney, Crow (1990), design refers to a representation of an object to be

constructed. Meilir Page-Jones (2000) defines design as the act of representing a chosen

6

implementation for a set of requirements. The above definitions tell us that design is

representation of an object but didn’t explain what design is composed of and it’s possible

outcomes. The definition for this, project is derived from Paul S. Licker (1987) where design

refers to a set of actions that results in specifications for the construction of a new system or

improvement of an existing subsystem. In addition, design is of two types: that is logical design

that results in the specification of functions and data elements; physical design that produces

operational specifications for the system, its hardware and software components, data layouts

and operating procedures.

2.8 Implementation of the TARISMarvin Gore and John W. Stubbe (1988), define implementation, as the process of bridging a

developed system, into operational user and turning it to the user, while Donald Yeates and

Tonny Wakefield (2004), implementation refers to those activities that begin when the system

design has been completed, and end when the development team has withdrawn from the project

and the user acceptance has been signed off The definition for this project is derived from Chris

Mader (1979) who defines implementation as the tasks needed to transform the systems design

specifications into operable and documented software running on a suitable and available

hardware. This definition talks about the hardware to be used by the System unlike its

counterparts.

2.9 Testing of the TARTSAccording to Allan Evans, Kendal Martin and Mary Anne Poatsy (2005), testing refers to

checking to see whether the system is complete. Testing is the verification of the performance of

the entire computer based system. Gore (1988). These definitions agree that testing is

verification of the system. Verification establishes whether the system is complete or not but

doesn’t check whether the system meets the user requirements or not. The definition for the

Project is derived from K.Porinambalam and Tiuley Alguindigue (1997), where testing is the

verification and validation of the system. During verification, the system is checked to establish

whether it was implemented correctly. Validation, checks that the program provides what was

originally asked for, this is done using various choices of data.

7

2.10 Report of the TARISMelissa Walker (1993), defines report as a document of what was discovered during research

while Sharon Sorenson (1994), defines report as what you have read, summary of information

that was usually gleaned from a single source-an article, chapter, or book. For the purpose of this

project, a report refers to the documentation of all the deliverables from all the phases of the

SDLC.

2.11 ConclusionIn conclusion therefore, a combination of the above is what has been discussed by some scholars

about what traffic accidents are and building the Traffic Accident Records Information System

(TARIS).

8

CHAPTER THREE

METHODOLOGy

3.1 IntroductionThis chapter involves research methodology and development methodology. Research

methodology involves the techniques that will be used to collect, analyze and present data while

development methodology will involve how the system will be analyzed, designed and

developed.

3.2 Organization to be studiedThe study was focused, mainly on Central Police Station-Traffic department as an organizational

unit of the Uganda Police Force. However, consideration was taken to other Police stations since

they supply Central Police Station with relevant information required to update its operations.

3.3 Requirements elicitation techniquesThere were many data collection and analysis techniques that the researchers considered before

selecting the most suitable methods for this project. These techniques included:

• Observation

• Interviews

8 Questionnaires

• Document review

3.4 Adopted research techniquesThe researchers used Interview and Document review research techniques:

3,4.1 Interviews

This involves conducting face to face interaction with the respondents with set questions to be

asked.

3.4.1.1 Advantages of Interviews8 Does not require the respondent to be literate.

• The Interviewer can probe deeper into a response given by an interviewee.

8 Interviews produce a higher response rate.

9

3.4.2 Document review

Document review is a way of collecting data by reviewing existing documents. The documents

may be internal to a program or organization review?

3.4.2J Advantages of document review

Relatively inexpensive

o Good source of background information

° Unobtrusive

• Provides a behind-the-scenes look at a program that may not be directly observable

o May bring up issues not noted by other means better understand the program and

organization you are evaluating will help you formulate questions for interviews,

questionnaires, or focus groups or develop an observation guide.

3.5 Development Methodology

3.5.1 Systems Development Life Cycle

The systems development approach was based on the Systems Development Life Cycle (SDLC)

which includes; Project identification and selection, Project Initiation and Planning, analysis,

Logical design, Physical design, implementation, and Maintenance.

The systems development life cycle (SDLC) is a common methodology for systems development

in many organizations, featuring several phases that mark the progress of the systems analysis

and design effort. In the systems development life cycle, it is also possible to complete some

activities in one phase in parallel with some activities of another phase. Sometimes the life cycle

is iterative; that is, phases are repeated as required until an acceptable system is found. The

System development Lifecycle is illustrated below.

10

3.5.1.1 Project identification and selection

The first phase in the SDLC is called Project identification and selection. In this phase, the

researchers identified the need for a new system, information needs of the organization as whole

were examined, and projects to meet these needs were proactively identified.

3.5.1.2 Project initiation and planning

The second phase is project initiation and planning. In this phase, the researchers investigated

the system problem or opportunity at hand and the presentation of reasons why the system

should be developed by the organization.

Figure 3.1 SDLC life cycle

11

3.5.L3 Analysis phaseThe next phase is analysis, during this phase, the researchers thoroughly studied the

organization’s current procedures and the information system used to perform organizational

tasks. The first is requirement determination. In this phase, the researchers determined what the

users want from a proposed system. This involved the study of the current system. The next

involved the study of the requirements and structure them according to their inteffelationships

and eliminate any redundancies. The third involved the generation of alternative initial designs to

match the requirements. These alternatives were the compared to choose the best that can meet

the requirements within cost, labour and technical levels.

3.5.L4 Design phaseThe fourth and fifth phases were devoted to designing the new system. During design, the

researchers converted the description of the recommended alternative solution into logical and

then physical system specifications. The researchers designed the necessary aspects of the

system which involved input screens, output screens, a report, database and computer processes.

3.5.L5 Implementation phase

In the implementation phase, the researchers constructed a prototype of the system and tested it

to ensure that it performs as designed.

3.5.L6 Maintenance phase

Maintenance phase: This involves whatever happens when a system has been put into use. The

researchers are willing to provide the maintenance support if called upon.

3.6 Lifecycle reference modelsThere are a number of lifecycle reference models and they include:

o Spiral lifecycle model

o Waterfall lifecycle model(Linear lifecycle model)

o Proof-of-concept lifecycle model

o Component based lifecycle model

o Dynamic Software development lifecycle model(DSDM)

12

The researchers used the Component Based Development Lifecycle. This life cycle is an

emerging lifecycle for the development of distributed client-server systems using component

technology.

The Partial modeling phase involved carrying out enough business/application/system modeling.

Its purpose was to define a meaningful build scope. A build delivered a well defined set of

business functionalities that end-users can use to do real work.

Once a build scope was established, we decided on which of the required components can be

reused and which ones need to be developed. With all the components for a build in place, the

components were then integrated and tested.

Figure 32 component based deve[opment life cycle

13

CHAPTER FOUR

SYSTEM DESIGN AND ANALYSIS

41 Analysis of data collection

The data was collected through the use of interviews, observation and document review. The

targeted population was 30, though the researchers managed to research on 22 respondents.

Below is the analysis of the data collected during the field study.

4J~1 Respondents who had an idea about using a computerThe table below shows the no of respondents who had an idea about using a computer.

No of respondents

YES 15

7

Table 4.1 Response of Officers who have an idea of using a computer

14

16

14

12

10 _____

DYES8 DNO

6

4

2

0

No of respondents

Figure 4.1 bar graph on response of an idea about using computers

4.1.2 The total number of respondents per station

Station Number of respondents

CPS- Kampala 7

Kabalagala 5

Katwe 5

Jinja road 3

Kiira road 1

Wandegeya 1

Table 4.2 number of respondents per station

7

Number of respondents

Figure 4.2 numbers of respondents per station

4.1.3 Respondents who participate in sending accident records


CPS- Kampala 6

Kabalagala 3

Katwe 3

Jinja road 2

Kiira road 1

Wandegeya 1

Table 4.3 response of Officers who participate in sending accident records

6

5

4

3

2

1

0

DCPS- Kampala

O Kabagala

C Katwe

OJinja road

DKiira road

DWandegeya

16

6

5

4

3

2

1

0


Figure 4.3 responses of Officers who participate in sending accident records

4.1.4 Respondents who do not participate in sending accident records


CPS- Kampala 1

Kabalagala 2

Katwe 2

Jinja road 1

Kiira road 0

Wandegeya 0

o cps- Kampala

O Kabagala

DKatwe

Diinja road

O Kiira road

O Wandegeya

Table 4.4 response of Officers who do not participate in sending accident records

21.81.61.4 OCPS- Kampala1.2 lJKabagala

1 ~Katwe

0.8 Diinj road0.6 D Kiira road0.4 DWandegeya0.2

0


Figure 4.4 responses of Officers who do not participate in sending accident records

4.1.5 General perception of the respondents about the introduction of a TARIS

Categoiy No of respondents

Those in support of the system 11

Those against the introduction of the system 9

Those who are partial 2

Table 4.5 respondents supporting the introduction of the new system

18

12

10

8

6

4

2

0

No of respondents

Figure 4.5 respondents supporting the introduction of the new system

4.2 Analysis of the systemThis specifies the functionality of the system and the constraints under which it operates. System

analysis is intended to establish the services that are required from the system and the constraints

on the system’s operation and development

4.2.1Requirements analysis

The requirements were analyzed in the following categories:

4.2.2 Functional requirements

These are statements of the services that the system would provide, how the system would react

to particular inputs and how the system would behave in particular situations.

These would appear when all the system components worked together to achieve a common

goal. These include:

• Sending information through on-line forms to Central Police Station-Kampala.

• Retrieval of information sent by Police Stations to the database.

• Management of user accounts by the systems administrator.

• Acknowledgement of records submitted whether successful or not.

I] Those in support of thesystem

EJThose against theintroduction of the system

D Those who are partial

19

4~2~3 Non functional requirements

Constraints on the services or functions of the system that relate to the behavior of the system

in its operational environment. The expected non-functional requirements of the Traffic

accident records infonriation system were:

Reliability.

• Efficiency

• Security.

• Economical.

4~2A Hardware requirementsThe hardware requirements are as follows:

Computer (Pentium ifi of 500MHz and above)

• 50 GB of disk space (minimum)

o 256 MB ofRAM (minimum)

• VGA with 1024 x 768 minimum resolution>

42.5 Software Requirements

Besides determining the hardware requirements, the software requirements were also considered.

The software requirements were as follows:

• Java script.

o Php

• Windows XP, 7ultimate

o html

• WampServer2. 1.

4.3 System DesignThe logical and physical designs of the new system were developed by the researchers. Entity

relationship diagrams, data flow diagrams and UML diagrams were put into consideration. The

diagrams will serve to facilitate the users’ understanding of the new system.

20

4~3.1 Logical design

This was concerned with the design of the web pages, how they relate to each other and

conversion of logical records structures ofa data model supported by a database management

system identifying entities, their matching attributes and the relationship types determining the

attributes domain.

4~3.2 Physical designPhysical design shows not only what a system does, but also how the system was physically and

technically implemented. It transforms the logical design material into real computer work and

describes how the logical structure is to be physically implemented on the target system.

43~2.1 Structure of WebPagesThe researchers came up with the structure of the webpages during the logical design, to clearly

illustrate their layout and how they are interconnected.

21

The figure above is designed in such a way that, the home page is linked to three other pages and

that is: - About Us, Police Stations and Information. These links appear on all pages for purposes

of easy navigation. The Police Stations page is linked to other pages such as: - the login, create

new account, Administrator login, manage accounts, create new user, create new administrator

and logout.

43.2,2 Database structure

Based on the analysis of the user requirements, other information such as the kind of details sent,

the kind of details generated and the privilege levels required; the researchers came up with the

following database structure.

L~::~:0 Kiira roadPolice Station

Figure 4.6 showing the structure of webpages

22

The database consisted of eighteen (18) tables, six (6) of them store information about accidents

that happen within the jurisdiction of a particular Police Station, twelve (12), store the

usemames, passwords of the users and administrators. The field names and the data types are

shown below.

Field name Data type Field length

Tarref Varchar 15

Tsdref Varchar 15

occurrencedate Date

Occurrencetime Varchar 10

Reportdate Date

Reporttime ~ Varchar 10

Natureaccident Varchar 50

Naturedamage Varchar 50

Accidentplace Varchar 100

Partiesinvolved Varchar 200

Driverparticulars Varchar 250

Accidentcause Varchar 250

Othercauses Varchar 250

Victimdetails text

visitingofficer Varchar 100

Sender Varchar 100

Table 4.6 Police Station table


Usemame Varchar 65

Password Varchar 65

Table 4.7 Administrator login table

23


Usemame Varchar 65

Password Varchar 65

Table 4.8 user login table

43,2.3 Data Input Design

Data/command is input using the mouse and keyboard. There is a provision for the user to type

on a provided space to search for something in the database. The user will interact with the

system using a simple and user friendly graphical user interface. The data stored in the database

will be entered through the interface. The interface design for the webpage form is illustrated

below:

24

Data entry form

Label

Text box

Label

Textbox

Label

Text box

Please enter accident records

Label

Textbox

Label

Combo box

Police Officers

Label

Text box

(S~bmit D C Rese~)

Copyright 2012 Traffic Accident Records Kampala

Figure 4.7 data entry form

Label

Text box

Label

Combo box

Data is entered through the textboxes. When the user clicks submit, the data is sent to the

appropriate table in the database. When s/he clicks reset, the form clears and details of another

Welcome to Central Police station Kampala (CPS)

Header of the webpage

Navigation pane

Home

About Us

Police Stations

AdministrationArea

Logout Text boxLabel

Label Label

Text area Label LC0mb0 box Text area

Label Combo box

Label Label

Combo box L5t area

Label

Text area

25

4~3~2~5 About Us Page Design


Get to know more about the designers

Navigation pane

Home

About Us

Information

Police Stations

Footer of the webpage

Picture Text Picture Text

Text

Home I About Us J Information I Police Stations

Figure 4~9 about us page design

27

4~3~2~6 Information Page Design


Get to know more about accidents

Navigation pane

Home Picture

About Us

Information

Police Stations Text

Text

Home J About Us Information Police Stations


Figure 4.10 Information Page Design

28

4~3~2,7 Police Stations Page design


P~ease, S&ect your Police StatbnNavigation pane

Central Police Station Kamp~Home

Katwe Police StationAbout Us

_________ Jinja Road Police Stationlnformat~on

Police Stations Kabalagala Police Station

W~~geya Police Slaticp,

Kiira Road Police Station

Home About Us I Information I Police Stations


Figure 4.11 Police Stations Page design

29

~matiOflpassword

~Dc~D

~matiOn

4~3,2~8 Login Page Design

Navigation pane

th~rn~

About Us

Police Stations

Login to access your Police Station

Member Login~tbox

Usemame

~rn~l ~tUs ~mationl ~ce Stations

Figure 4.12 login page design

4~3~2~9 Administrator Login Page design

Header of the web page

Navigation pane

thQrn~

Administrator Login

Administrator Account

Police Stations

Usemame

password : [~e~oxl

~rn~l A~tUs ~mationl ~ce Stations

Figure 4.13 administrator login page design

30

4,3~2JO Manage Accounts Page design


Navigation paneManage Accounts

Home

. Create New AdminAbout Us

Information ~ Create New User

Police Stations

Home I About Us I Information I Police Stations


Figure 414 Manage Accounts Page design

43.2.11 Create New Account Page design


Navigation paneCreate New Account

Home

About Us F bUser Name 1 Text ox

Information Text boxPassword

Police Stations Text boxConfirm Password

~Create Account) ~ Reset

Home I About Us I Information I Police Stations


Figure 4.15 Create New Account Page design

31

4~3.2J2 Data Output Design

The system produced a report which was viewed via the computer screen or printed for use in

analysis and decision making by the relevant people.

tarref tsdref Occurrence Occur Report Report Nature Dam

Date Time Date Time accident age

Accident Parties Driver’s Accident Report Other Visiting sender

place involved particulars cause Date cause officer

Table 4.9 Data Output Design

4~3~3 UML Diagrams

4.3.3~1 UML Activity Diagram

The UML activity diagram below shows everything that takes place from the time the accident

happens until a report is sent to Central Police Station Kampala.

32

4.3.3.3 UML Sequence diagram

UML Sequence liagram

Figure 4.19 UML Sequence diagram

4~ds Central Pol

~Offlce~) (~~arn~l)

Sends accident records Receives accident records

Traffic AccidentRecords Information

System

(TARIS)

Figure 4.18 UML Use case diagram

Delivers accidentinformation

Traffic Officer

(Police Station)

Records Officer

(CPS)Records

0 ff~ c or

Updates

Views

Views

34

4.3.3.4 UML Class Diagram

The class diagrams describe the stmcture ofa system by showing the classes ofthe system, their

attributes, the relationships among the classes and also the operations performed on those

classes. In the diagram below, the Patient class interacts with the Doctor and System classes. The

Patient class sends request to the System which then sends a notification to the Doctor who

acknowledges receipt of the request and sends the diagnosis to the System Database.

The System then sends the condition and recommendations to the Patient.

/

Records Officer(Police Station)

Force Number

Rank

Name

Phone Number

Organises records ()

Sends accident records ()

Records Officer(CPS)

Figure 4.20 UML Class Diagram

Traffic Officer

Force Number

Rank

Na me

Phone Number

Belongs to a Police Station ()

Receives information ()

Visits the scene of accident ()

Database

Name

No of tables

URL

Receives accident records ()

Stores accident records ()

Force Number

Rank

Name

Phone Number

Receives records 0

Analyses accident records ()

Makes reports

35

CHAPTER FiVE

SYSTEM TESTING, IMPLEMENTATION AND EVALUATION

This chapter deals with how the new system was implemented. Details of system operation and

testing of the new system.

5.1 The developed systemThe system begins by showing the home page, which signifies the launch of the system. The

home page contains links to other pages.

5.1.1 Home PageTintt. AcodeteRrends

ft. jde ~vw ftpory floel.swh !enk tfdp

~C 4s

idoittrxded Øc Gail.g ti.itrd

nern I — t4wnker togA, tvns.ng fOld ‘AbA (~Vidm.. Q Pinto..

~. 0 - Dorat.~~ .101. C~ iw~ ~AodtIttAw- ~W.wh.r

raffic Accident Records

Uganda Po&a Force

Uganda Pekce Force became a bay fledged uist,tvbon on 20th May1Q06. Befor, that it was a Parv-oidcary fort. caked Th. UgandaAimed Casstakialary whose man, t,asct,on wa, to quid not, and .,esstci the different parts of the then Bnbst. Prot000teOte. Rood intro

Computer-based information systems

Coer.putcr-basod information systenor contnbute heavily towdith thesuet... of any organization. Once regarded, an organization canac~are acciwate and timely data about its operations. Suchinformation can be used to support pla’incig, staffing sieervsu,g.decision maIling and p061cm nelsong among atom’sUganda Pokce Force Bce any organcation uses a lot of pager work incamping o.,t its defy weeldy, siorittey arid yearly operations

Traffic Accddent

An orsespected incident witS, potential for harm (~)occsasing ttco.d, the movement or iroBejon ofvessels, v.1*1., or persons along a land wateror spar. route.

Who is responsible for a traffic accident?

tt may be obsioss that sonseene cawad the Please psi., stiovfdaccident arid there vist be no depute about flautty not diwik and doseHow~.~ thor. all be can., where it is not Road accident, haveobvious, or where the extent of tabllty ~ dfflc.dt claimed many foes ofto work out. For coaniplo, a, a general ride, the xi, dear ones.diver of a vidode .f,cls roan into the bad. ofanother s’eh.de wll be held fable for the accident.TI,. . th, cane even if the car ci front has brakedaharply or woupectedy. because driver. arereqlm’ed to dave a safe distance befliod othervel,.des

What must a driver involved in a trafficaccident do?

A driver involved ci a traffic accident sho.id stopwtmttvir or not to, accident was then taut it:

• anyon. other than thanmolve, is .npr.d or• another s’id.de or sca,eone else. ~operty

is damaged, or• an amnal Os another vefecle or nmnmg across

the road a

I Ham’ I Rcii≤tr$tolions I ltiiocmpHoj! Rbcis.Uio I

.01 . tiff.” A -rI-—il A i’i,I-.

Figure 5.1 Home Page

i’ni,c.:Si.,o.i.

Am,,:? Ii’.

-,

If. ~ ;1~≤~~~d

36

5.1.2 User LoginWhen the user tries to access the staff Area the login form appears immediately. It prompts for

the username and password. All the users have to login with a correct username and password to

gain access to the form.

~, Traffic Acc~deiaf Recacda -

Eiio Lxflt ~iew Ifl~toiy ~cth~ 10th ~

• - C ktp ohcet’traf& accidarn dhaa€ccrrac&nflcgm~pa.çnç

Mc~ Vis4~ ~e Gaftiag Started Lateat HeadStaea

Q~. !ea~fr the v~rb

•. Strare. Hoatp uddMot~e - — 0 Daiate P~I t~1- Egp4~4~jfi~.

Trof&AccadertL locitheat bctlho... locathost locafiro... TrtfflcAccidontL locathoat locotho... bcathcst bcatho.. TrofficAcadmtL TraffkAcodraatR...

Traffic Accident Records

Login to accesss Central Police Station formP~facø St~,hnnc

InformationKoanb~ Logm

About tIr,

Unername

Pastword

E~t

Figure 5.2 User Login

If the user enters the wrong password or username, a message appears informing the user that the

Usemame or password is incorrect as shown below.

5.1.3 Error message on unsuccessful login

TkrrdR~ccwds-M -. ______

fde jd~t 41ew Hi~toiy -~oobnarks look ~p - - - -

X A s~ ~JJ~Mc o!ticsstrific acodert~ase cue~icischogiscp~php _________________________

~ L

__________ Search

• ~‘O Donzte -fO)- j~JEins~Notif~rc ~ezdier”

balhostloc4hoj Iocoko~ Iocot~ Trd&A~4entP kcokogbca~io. bcihhoot Iocithe.~

Traffic Accident Records

• Access Central Police Station-kampala form• Po&t~Stdhions

• into ii,tiu:i Yot~ I emame or Password in incorrect! p!ease try again.

• About tic

Member Login

Usemaine

Password

Login Reset

Figure 5.3 Error message on unsuccessful login

5.1.4 Sample form design

If the login credentials are correct, the data entry form is loaded which gives the user the ability

to interact with the system for data entry, update and retrieval.

38

- Secrch the

Traffc Awdent Rereeds - Mo~a Rselee

E~’e Edit View t{eteey ~ookmirks loots ~

< ~ tTtt~RCC

Mv~tVi~~ted ~ Gdting Stsited Hmd~in~

Q 5~.o,sh th~ web — Searc

:4 eKotspct9eddMcbae ! :- Donste. -(i)] ~OjEmdNotdIer Westhor

TIA(csdentReccede bcaOsost tocafhog te~ ~dspMy.. ~ Ioui4iost locethoot t&~pI~4.. TficAcddesst Records

Traffic Accid - . .

Ilome

Potic~ St~s~ionc

• Irifuinistor,

• Abøu$ tt.~

• Cwato Hoe’Accs,unl

Logou(

To, tiumber

Tod Number

Academ~aco

-

Nohsre

Po)~e OFH’~ers

Ddserportsculars

Welcome to Kabalagala Police Station

Occunence Date Repeet Dote

Horns t3UssleS

Sender Name

Submit LResetJ

p’io~b~ 20t? Ti~5c A~adent R~.cosds t.arnpaa

Figure 5.4 Sample form design

39

5.1.5 About us page

This page shows a brief description of the users about the designers of this system. This includes:

- their photos, competences and contact.L3 Toc londewi Rimes- M~.ftiha

rae jiot isa~ fbgwy ~orhmat !oo~ ff~

C 4b htç- lrca5mniritro_acodertdtaas c005cse.t abn&ucclw

la.aVaaed ~ Owing lined Lame Hmdbin

IRID - - Wan — Unite tori Giaomg Polo WhdsN.w fl Vt Q Piotos Opines

lain, ~ Heftyct beddidelid. - ~j- - w Docile a -101 be) toad NoUn.- site

-~ r— —

About the designers.

Idiatere Toongo dn&ew. CompteterScience tamEst Kaspala tntoeiatonafLfleeeoty and. researcher el a projectenabed ‘Traffic Accident Recoedsfnfmsiabon System’

Personal Skills and Competendes

o ftcrosoft Office ApØcabonea Compute Mantanance and tooidd.dsooting• ~O7amiwi3IApp5cabml development• Datadase design and adenstoalion

Carrier Objective

To provide the best segiport aid promote tedwiologecafadvancemant. to eidis,eheafo and ergarnatans

Contact

Mob 0779507621

c-mad tsoiigoaiibewgeymad.cooi

Gdeert Want. Intonation Tecflnology Ena9stKaoifla tnteenaaonal tasveoety and a researcher na project entitled ‘Traffic accidenc Record.Inhaisation tyotaio

aPersonal Skills and Conspetencies

o felitcOsoft Office Aopbcateonsa Coogiutac l4it.nance and aoublesteoobngo Wqb desegoig (ptip)efsd)o Database deeego aid atewmtration (Ms Access, mys4o Infonoaban Rystmos Development (Essential Eusesess Modeler• P~sicaf secieity sfdh

Carrier Objective

To accept any esteal job that ohal best use the qjanbtative thowledga andI have with an obbon of enhasceeg and prsisoweg tecissology Øsbally.

Contact

Mob 0782150351

e-mad gwaovebtyaieoo cm

Pliers ltstene tisirnseta toos_ssi

c ~ ~,iji 2111:, cot-cu Inn

Figure 5.5 About us page

5.1.6 Information page

This page contains some information about traffic accidents and what happens after an accident

has occurred. It also has some information about computer based information system and some

navigational links to the Home page, Police Stations, and About Us.

40

.!~ Twist ‘endow kneels— tookfelt yow thotmy botbewlo !oob (hlp

lop /toc trdf~.todo4.thoto soerstmt1 ad sepop ¶) 1 ‘~a’

•~ ~—Sadist.

0 - them ~otsm~sucoi. - [~$ -~~] o~oa. -~ ISO!- loudhoithw- Wwths,

— losabo.5 brelboot — loselbow lord.sot TwiskAwOtoror.. Twiss&rldowRoroe.~ o j Trefik Ardthot Rot... ° L

Tr i nt Records

Get to know more about traffic accidents.

I’.,U,.

Tnforn,,,t,nn Traffic accident:5., do otsesp.cted incident nato potent~ for basis occsmwsg through the ov.5nent or token of vessels velades ‘

or persons ~ng a lami. water a. or space route.

Who is responsible for a traffic accident?It may be obidoiw that .on,ew.e caused to. acod.nt and there wel be no d.sput. about labety. However therewe be cases where it rS net ebs,ous. or top.,. Lot. eatant of liabety .5 ,atfic,it to —~ out P01 fot.eple as a ogeneral n.le. the thwer of a vefscte mfsctt two otto the back of another veltocle we be held bald. for to. ________________acc,dent Ties is trio case overt ,f the cas is front has braked elsarply or smespectesy. because drivers ertreqiared to dove a safe betance bdwsd ether oetscl.s Howev01, there may be onc,ao.ta,ces when dos doesnot apply, arid f bakelty is drsputed. legal adroce we be necessary radeas the eonaasce Company is deakflg tout.It . .

What must a driver involved in a traffic accident do?A driver e,vofoed es a traffic accident t0,Ctdd stop wt.othlr01 not too acodent was toes’ heit if -

• anyone, other than tosmuelves, w erpared; or• another stohele or groiseon. o4se~ property. .s damaged, or• an w.nat m another velsde or n#wwsg emotes the road’s eqie’ed, 01• a bolt01d sot-eec lamp or other .tem of sb-eet flaTsture is damaged.

If you hare to stop. you must rotsae. acer the veiScic leng enough for anyone who 0 motIved &rectly Oroutrecdy ot the accident to ask for detado. TOn, codd be. for exaniple the owner of an injured arsrnal, a re4abveof semeone who is oqured. or the poke The doss, must then gem thee russ. and address, the name andaddress of the owner of the siefed. (if the driver is not the osofter and to. rmpob’abon m,m.ber of the efisCie.The driver may also have to report the accident to a poke officer or at a pobce itabor. is person as soon aspracbcable and or any case widen 24 hours

and the ewiaance ro,tfrcate must be ~cn to a pelt. stabor. wades seven days of Low accident. However .fthe dover is asked at the Lowe of the accident to produce mswance detids and does so there is no furtherobtgabon to report the accident to the poRt., as tong as they have coorpfied with the dubes described aboveIn the cane of a damage-only accident, the driver must ~ve onawance detelts to anyone totir may wish to makea clem against then.

In at accidents. dnv.ss thoidd oilers, thee own mssovnc. company.

Cot. s.~.t 20;2, 1r3;: 4CccT.Dnt Rocoid. ~o

i-i

Figure 5.6 Information page

5.1.7 Sample report

The system can produce a report about traffic accident records. The report generated by the

system is as shown below.

Eae £ft ~inw I~toy ~oc1c,nofa Ioo~ ~

Most ~%aed ~. G~tiig Susted t~2.st Hood~nos

• tsrr~ • SearcI~

• -Ssduma R~*ud Mb 2~. • Shoe I4otsçot 9oeld Mob~e •

Acddast Rop.. x ••.

C Oone - f03• I~ Ema~ Noeiie•

DAIlY ACCIDENT RETURNS - CENTRAL POLiCE STATION KAMPALA

Pr-~ ~sos Heae PoIitc ~icns 1oio~-o~üoo .kbcut Us

t~rrpI Isdrcf occurrence date~ Irepor date ~l~i~naIure act na e_damlacctdeot_place ~part1esIrn~oIved

MV reg No UAD

TA~001 2012 01250112 ~JkN-2012 11 16 ~M 2G1242~1 I ~ N~~aalo~ MCregno~D

OS9F to~ta Ra’-4 Vs

~be road 334T Hondasa4,tmut~ blue a..

r0~r

s...’ “•_•i• -.-. •,...,‘ “•-..-, 2..e~psphp —— 52? A k~o~

~ Opt on

~J DonaTe 10) (601 E,na I Not,foe .,~Weat$toe —~ — —

T~affi~ A~.derst Ri.. T,aff~ Ast~rident R.. [3 A~e~dent Rap~oot tos~.lho~t os~Iho... ~Io~athott Iosr.Um~ -

cli-i~ erparticulers accident_cause other_cause ‘victim_details Ivisiting_offleer sender

~ ~eg n~-Sane ewe Feisal M a UAD 089F -~

aged 34 yeazsr~..i~Int Ruv4 lost -

,fEntebbe Kitooro C>vnetoading Dangeroua cooi~e1 and No. 35463 sat 36 143-Ssef’umn R~s1ud ).4 a Loadsog knocked ~s4tc .. Ejoet Ch~1es

• ~ aznasuba ~ aozmnbi29 ye~s. res,d~t of ~eg n~ D~Jamasizba Kilcaje 334T Honda Gilbert

supercuib

Figure 5.7 Sample traffic report

httpt/flc,ccalastjbnecoi,ecticnl MotwcpsØ~p

!ocaUso~t IocMho... ~ Incaliost! locatso... Toflic AcodentiL. ToflicAcc4ent IL. Acadeot Ropo3t

42

5.2 Program TestingThis was intended to ensure that the system is consistent and conforms to its specification and

that the system meets the expectations of the users. The testing process was proceeded in stages

where testing was carried out incrementally with system implementation. The following were the

stages followed:

Unit testing: - Individual components were tested to ensure that they operate correctly. In this

case, each form was tested independent of the other forms to ensure that it was working as

required.

Sub-system testing: - Each form was tested to ensure that there were no errors while interthcing

with other forms. This was concentrate on the detection of module interface errors by testing of

these interfaces. The database was also tested separately to ensure that the table relationships

were consistent. For instance, data was entered in two related tables. An attempt was then made

to modify data in one table. This was supposed to affect the data stored in the related table.

System testing: - The sub-systems were integrated to make up the system. The whole system

was then tested. This process was concerned with finding errors that result from manipulated

interactions between the various sub systems. In addition, it was concerned with validating that

the system meets its functional and non-functional requirements and testing the emergent system

properties.

Acceptance testing: - This was the final stage in the testing process before the system was

accepted for operational use. The system was tested with data supplied by the system users

rather than simulated test data. Acceptance test was to reveal errors and omissions in the system

requirements definition and user expectations.

5.3 User training, operation and support

5.3.1 User Training

The implementation of the new system would involve training individuals who will use the final

system. The deliverable of the system implementation and project implementation is the

operational system that will enter the operation and support stage.

User training would involve: helping the user understand the application’s user interface,

performing sample data entry and retrieval, explaining the actions! events that would cause the

application to behave improperly, highlighting the strengths! limitations of the application as far

43

as data entry, storage and retrieval is concerned. An explanation on how to generate and print

reports would also be explained.

5~3,2 Operation and SupportThe operation and support stage comes in once the system is operating. System support is the

ongoing technical support for users as well as the maintenance required to fix any errors,

omissions or new requirements that may arise.

System support consists of the following activities.

Assisting the users: - Regardless of how well the users have been trained and how good

the end-user documentation is, users will eventually require additional assistance because

unanticipated problems may arise or new users added in the organization.

Fixing software defects (bugs): - Software defects are errors that may have not been

detected during the testing phase.

Recovering the system: - A system failure may result in a program “crash” or loss of

data. Human error or hardware or software failure may have caused this. The researcher

may be called in to provide technical assistance which may include restoring the system

files and database.

• Adapting the system to new requirements: - New requirements may include business

problems, new user requirements, new technical problems or new technology

requirements which will need to be adapted into the new system.

£14

CHAPTER SIX

DISCUSSION, RECOMMENDATIONS AND CONCLUSION

6d DiscussionFrom the research conducted, the researcher came up with the following conclusions and

recommendations based on the research objectives for this study, which are stated below:

The researcher carried out a detailed study of the case study with an aim of learning how the

current system works; identifying its weaknesses and strengths. Data gathered was analyzed, and

a design document was developed and an information system suiting the case study was

developed to tackle the problems and shortcomings of the current system.

The new system was developed and implemented using Php, mysql, html and javascript. Security

of the new implemented system was enhanced by use of passwords and usernames.

The new system was characterized by improved and simplified data submission and storage.

Data is stored in a central location (that is the database) making it easier to backup and restore in

case of a system failure).

There is significant improvement on data retrieval; both in terms of accuracy and speed of

producing a report. It will be possible to search for an item from the database by entering the

details in the search textbox available.

6~2 Conclusion

The Traffic Accident Records Information System is designed to respond to the needs of the

Traffic department of Central Police Station and its counterparts. This system provides an

efficient and reliable way to send traffic accident records and reduce redundancy and

inconsistency.

The system has been developed with scalability in mind and can be updated to meet changing

requirements. Additional modules can also be integrated to enhance its functionality.

45

The system has been pre-tested to remove any bugs that may cause the system to perform

abnormally. Exhaustive testing needs to be carried out to isolate any bugs that may have not been

captured by during the initial testing phase.

6.3 Recommendations

It is recommended that the system be implemented on a computer running Windows XP,

Windows 7, free hard disk space of at least 1GB and RAM size of at least 256MB.

To enable user access control, the administrator has to set up usernames and assign passwords.

Once the system is in use, it should be run alongside manual files in order to prevent unexpected

challenges, that is, parallel conversion should be adopted for the system once in conversion

stage.

The system should be run concurrently with the manual file system until a point where the

system has been certified to run effectively and reliably.

We recommend the system to be used by all Police Stations in the entire Uganda Police Force for

efficient, economical and secure; submission, storage and retrieval of data.

6.5 Areas for Further Research

System operation is the day-to-day, week-to-week, month-to-month and year-to-year execution

of an information system’s business processes and application programs. For the Traffic

Accident Records Information System to be more comprehensive, the system is open to

improvements and enhancements. Research can be done in the area of reporting such that

necessary traffic accident statistics can be obtained by the system.

If need be, the database can also be migrated to Oracle or SQL for improved security and

performance especially when the number of users and database size increases.

46

References

Jean Warland (1991). Communication Networks, Richard D.Irwin, Inc., and Akesen Associates,

Inc.

Jeffrey A. Hoffer, Joey F.George, and Joseph S.Valacich (2002). Modem systems Analysis and

Design, Third Edition, Prentice Hall.

Micheal J. Powers, Paul H. Cheney and Gallen Crow. (1990). Structured Systems Development

Analysis, Design and Implementation 2~’ Edition. Boston. boyd & Fraser publishing.

Effy Oz (2002). Management Information Systems, Third Edition, Course Technology.

James A. O~ Brien (2003). Introduction to Information Systems, Essentials for the e-Business

Enterprise, Eleventh Edition, McGraw-Hill Companies.

David M. Kroenke, DATABASE PROCESSING: fundamentals, Design & Implementation 7tl~

ed. 1999

Uma G.Gupta (1999). Information Systems: success in the 2l~~ Century.

Booch, G. (1994). Object-Oriented Design with Applications. Redwood City, CA: Benjamin!

Cummings.

Martin, J., and J. Odell. (1992). Object-Oriented Analysis and Design. Englewood Cliff, NJ:

Prentice Hall.

Rumbaugh, J., M. Blaha, W. Premerlani, Freddy, and W.Lorensen. (1991). Object-Oriented

Modeling and Design. Englewood Cliff, NJ: Prentice Hall.

Jeffrey L. Whitten and Lonie D. Bently. (1998). System Analysis and Design Methods.

Newyork. Irwin/McGraw-Hill Companies,Inc.

47

James A. Senn, (1984). Analysis and Design of Information Systems. Newyork. McGraw

Hill,Jnc.

Meilir Page-Jones. (2000). Fundamentals of Object-Oriented Design in UML. Newyork. Dorset

house Publishing, 353 west 12th street.

Bertino, E., and L. Martino. (1993). Object-Oriented Database Systems. Reading, Mass.:

Addison-Wesley.

http://www.cdc.govlhealthyyouth/evaluation!pdf/briefl 8 .pdf

http://www.upfgo.ug

48

Time Frame

Period

APPENDICES

Appendix A

Activities Sep2011 Oct2011 Nov2011 Dec2011 Jan2012

Data collection

Proposal Writing

Data Analysis

>f ~ /~

Implementation

Typing Final Report

Slack

I

4g

Appendix B

Budget

ITEM COST UGX (ESTIMATEDI

Stationery 100, 000

Transport 20,000

Airtime 10,000

Internet 15,000

Consultation 150,000

Video Tutorial 5,000

Computer 1,100,000

Refreshments 10,000

Grand total 1 ,410~000

50

Appendix C

Code extracts

The following section provides the important code extracts used in the implementation stage of

the system.

/* code for creating the data entry form*/

<form id=”forml H name=”myform” method=11post”action=”insertcodekabalagalapolicestation.php”>

<table width~”658” border=”O”>

<tr>

<td colspan=”3 bgco1or~#OO2255 H><div align=~~centerH><blink><b><fontcoloi~=”white”>Please enter Accident Records</font></b></blink> </div><Itd>

<!tr>

<link rel=”stylesheet” type=”text!css” media=11a11” href=HjsDatePick_ltr.min,cssI~ 7>

OR if you want to use the calendar in a right-to-left webs ite

just use the other CSS file instead and don’t forget to switch gjsDatePickDirectionalityvariable to “rtl”!

<link rel=”stylesheet” type=”text/css” media=”all” href=”jsDatePick_ltr.css” I>

-->

<script type=”textljavascript” src=’~j sDatePick.min. 1.3 .js”></script>

After you copied those 2 lines of code , make sure you take also the files into the samefolder :-)

Next step will be to set the appropriate statement to “start-up” the calendar on the neededHTML element.

The first example ofJavascript snippet is for the most basic use , as a popup calendar

for a text field input.

<script type=”textljavascript”>

51

window.onload = fiinctionQ{

new JsDatePick( {useMode:2,

target: 11inputField11,

dateForrnat: “%d-%M-%Y”

/*selectedDate: {

This is an example ofwhat the full configuration offers.

day: 5,

For full documentation about these settings please see the full version of the code.

month:9,

year:2006

yearsRange:[1 978,2020],

limitToToday:false,

cellColorScheme: ~beige~,

dateFormat: 11%m-%d-%Y~,

imgPath: img/’~,

weekStartDay: 1*!

</script>

<tr>

<tdwidth”~ 185 “><label><br><b> &nbsp ; &nbsp, <font color~redH>*</font> TarNumber<!b><br> &flbsp;&nbsP;&flbsp;&flbsp; <input type~text” size~20”maxlength~1 511 name=”tarref~><br><br>

52

                    <strong>TsdNumber</strong><br>                    <input type=tttext”size”20” maxlength=”1 511 name”tsdref~>

</label><br></td>

<td width~’1 85”><label>

<div align=”left”><b><br>

Occurrence Date

    <input type”text” size=”1 811 id=”inputField” maxlength=”.l 5”name=”occurrence date”!>

<br/>

<br>

Hours    Minutes<br>

<select name”occurrence_hour”>

<option value”000” selected”selected”></option>

<option value=”1 :“>1 :</option><option

value=”2 : “>2 :</option><option

value”3 :“>3 :</option><option

value”4: “>4 :</option><option

value=”5 :“>5 :</option><option

value”6 : “>6 :</option><option

value=”7: 11>7 :</option><option


value=”9 “>9:<!option><option

value=” 10:11>1 0:</option><option

value” 11:11>11 :<!option><option

value”00: “>00:<!option><option </select>

53

<select name”occurrenceminut&’>

<option value=”000” selected=”selected”></option>

<option va1ue~00”>00</option><option

vaIue~01 “>01 </option><option

value~02”>02<!option><option

value=”03 “>03</option><option

value=”04”>04</option><option


value=”O6tt>06<Ioption><option

value=”O7tt>07</option><option



value” 10”> 1 0</option><option

value=” 11 “>11 </option><option

value” 12”> 1 2</option><option

value” 1311>1 3</option><option

value” 1 4”>1 4</option><option

value=”1 5”>1 5</option><option

value” 1 6”>1 6</option><option

value=” 1 7”>1 7</option><option

value”1 8”>1 8</option><option

value=” 1 9”>l 9</option><option


value”2 1 “>21 </option><option


value=”23 “>23 </option> <option

value=”24”>24</option> <option

54

value”25”>25</option><option

va1ue~’26”>26</option><option



va1ue~29”>29<!option><option

value=”30”>3O</option><option

value=”3 1 “>31 </option><option

value=”32”>3 2</option><option

value=”3 3 “>3 3</option><option





value=”3 8”>3 8<!option><option



value=”4 1 “>41 </option><option


value”43 “>43</option><option









55

value~52”>52</option><option

value”5 3 “>53</option><option


va1ue~5 5 “>5 5</option><option

value” 56”>56<!option><option


value~’5 811>5 8</option><option

va1ue~5911>59</option><option </select>

<select name=”occurrence_time11>

<option value=”00011 selected=”selected11></option>

<option value=”AM”>AM</option><option

value=HPMH>PM</option><option/select>

</b> <Idiv>

</label> <br></td>

<td width~ 185 ‘5<label><b>

<divalign=”left”><br>             Report Date<br I>

   &nbsp ; &nbsp,       <inputtype=~~textH size”l 8” id=”inputField2” maxlength=”lO” name=”report_date”>

<br /> <br>             Hours    Minutes<br>

&nbsp ; &nbsp ;&nbsp ;

<select name=”report_hour”>

<option value”OOO” selected”selected”></option>

<option value=”l :“>l :</option><option

value”2 “>2 :</option><option


56

value=~4: “>4:</option><option

value~”5 : ~>5 :<Ioption><option

va1ue=~6: ~>6 :</option><option

value=”7 : ~>7 :</option><option

va1ue~8 : “>8 :<!option><option

value=”9: “>9 :<option><option

value=” 10: ~> 1 0:</option><option

va1ue~1 1 :“>1 1 :</option><option

va1ue~O0: “>O0:</option><option <select>

<select name”report_mrnut&>

<option value=”000” selected=”selected’5’</option>

<option value=”OO”>OO</option><option

value=110 1 “>01 </option><option

value~”02”>02</option><option

va1ue=’~03 “>03</option><option


value”05 “>05</option><option





value”1 0”>1 0</option><option

va1ue~1 1”>1 1</option><option

value~ 12”> 1 2<!option><option

value=~1 3”>1 3</option> <option

value~ 14”> 1 4</option><option


57

value=” 16”> 1 6</option><option

va1ue~ 1 7”>1 7</option><option

value” 1 8”>l 8</option><option

value=” 19”> 1 9</option><option


va1ue=’~2 1 “>21 </option><option









value”3 O”>3 O</option><option


va1ue~32”>3 2</option><option

value”3 3 “>3 3</option><option


value=”3 5 “>3 5</option><option


va1ue=~’37”>3 7</option><option




value=”41 “>41 </option><option

va1ue~42”>42</option><option

58

va1ue=~’43 “>43</option><option

value~44~>44</option><option

value&’45~>45</option><option

va1ue=t’46~’>46</option><option


vaIue=”48~>48</option><option


va1ue=~5O”>5O</option><option

va1uer~”5 1 “>51 </option><option


value=”53 ~‘>53</option><option


value=”5 5”>55</option><option



va1ue~58”>5 8</option><option

value~’59”>59</option><option <select>

<select name=t’report_tlme”>

<option value=”000” selected=”selected”></option>

<option value=”AM”>AM</option>-<option

value=”PM”>PM</option><optionlselect>

<Idiv> <br> </td>

<!tr>

<tr>

<td> </td>

<td colspan”2”><label><b><br>

Accident place<br><Ib><input type”text” size=”53” maxlength=” I 00”name=”accidentplace”><br><br>

59

</label></td>

<Itr>

<tr>

<td colspan=”3 bgcolor~#888888~’><div a1ign=”center~><b><fontcolor=Hwhit&5</font><Ib> </div></td>

</tr>

<tr>

<td><label><b>Parties involved

<textarea rows~2 co1s~3 5 name=~’partiesinvo1ved”></textarea>

</label> <!td>

<td><p><br>

<b> Damage</b>

&nbsp ;<select name=11nature_damag&’>

<option value=”OOO” selected=”selected”></option>

<option value=11Maj or~’>

Major <Ioption>

<option value=$~MinorH>

Minor </option></select>

<Ip>

<b> Nature</b>

<select name=11nature accident”>

<option value=”000” selected=~’selected”></option>

<option value=”Fatal”>

Fatal </option>

<option value=ttSerious”>

Serious </option>

</option>

60

<option va1ue~’Minor”>

Minor </option>

</select>

</label>

</label></td></td>

<td> <label<b>Dnver particulars</b></label><textarea rows~2H cols”3 5name=”driverparticulers”></textarea><br><br><Itd>

<tr>

<tcl colspan=”3 H bgcolor=”#888888’5-<div align=”center11><b><fontco1or~’whit&’></font><Ib> </div></td>

<tr><br>-<br>

<tdcoIspan=~2”><1abe1><b><br> &nbsp ; &nbsp, Select the major cause of theaccident<Ib></label><br> &nbsp, &nbsp<selectname=”accident cause”>

<option value=”OOO” selected=”selected”></option>

<option value=”Vehicle Mechanical Defects”>

Vehicle Mechanical Defects </option>

<option value=”Reckless/Dangerous Driving”>

Reckless/Dangerous Driving </option>

<option value”Over speeding”>

Over speeding </option>

61

<option value=”Overloading/Dangerous Loading~>

Overloading/Dangerous Loading </option>

<option value=11lnfluence ofDrinks/Drugs~>

Influence ofDrinks/Drugs </option>

<option va1ue~Dazzled by Lights of another Vehicl&’>

Dazzled by Lights ofanother Vehicle </option>

<option value=11Careless Pedestrian11>

Careless Pedestrian </option>

<option value=~Passenger Falls from Vehicle11>

Passenger Falls from Vehicle </option>

<option value=11Obstacle on carriage way11>

Obstacle on carriage way </option>

<option value=”Unknown Cause(HitlRun)”>

Unknown Cause(Hit/Run) </option></select>

</p></td>

<td><label>-<b>Other Causes</b> </label>

<textarea name=11other caus&~ cols=”3 5 rows=112”> <!textarea>

<br><br> </td>

<tr>

<td colspan=113” bgcolor”#88888811><div align=11center”><b><fontcolor=”white”></font></b> </div>-</td>

</tr>

<tr>

<td colspan=~3 11><label><b>Victim details</b></label><br>

<textarea rows=11211 119~t name=~victim details 11></textarea><br><br></tr>

<tr>

62

<td colspan”3 bgco1or~#OO225 5 H><div a1ign=~!center~><b><font co1or~white”> PoliceOfficers</font><Ib> <Idiv><Itd>

<Itr>

<tr>

<td colspan=~3 ‘5<label>  &nbsp<b>Visiting Officer Name<Ib></label>

<br>   <input type=”text” size=~’5O11 maxlength=” 1 OO~name=”visiting_officer”>



<b>Sender Name</b>

<input type=11text” size=M8 max1ength=~1 OO~ name=~sender11>

</label></td>

<Itr>

<tr>

<td colspan=”3 “><label><br>

<div align”center11> <input type=11submit” name”Submit’~ value~Submit” />

&nbsp ;

<input type=flresetH name=”Submit2~ value=”Reset” />

</div>

<Ilabel><Itd>

<Itr>

</table>

<Ifonri>

/* code for sending to the database!

<?php

$connmysql_connect(”localhost11, 111111);

mysql_select_db(11test11,$conn);

63

$sql~INSERT INTO kabalagalapolicestationvalues(’$ POST[tarref]’,’$_POST[tsdref1’,’$_POST[occurrence_date]’~$_POST[occurrence hourJ’’$pOST[occuffeflccmiflute]’,’$pOST[occuffeflcetime}’’$pOSTfrepo~dateJ’~$pOST[report_hour]’,’$_POST[report_minutej’,’$_POST[report_time]’,’$_POST{nature_accidentj’,’$_POST[nature_damagej$_POST[accident_placej’,’$_POST[parties_involved]’,’$_POST[driverj,articulers]’,’$POST[accident_causeJ$_POST[other_causej’,’$_POST[victim_detai1s]~$_POST[visiting_officerj$_POST[senderj’)”;

if(mysql_query($sql,$conn))

{echo ~Record has been sent to the database successfully H;

}else{echo”Record has not been sent to the database, the Tar Number your entered already exists I”;}

1* Code for data validation I

<script language=”JavaScript” type=11textljavascript”

xml :space=”preserve”>/I< [CDATA[

I/You should create the validator only after the definition of the HTML form

var frmvalidator = new Validator(”myfon’n”);

frmvalidatoraddValidation(~tarref’, “req”,”Please, enter your Tar Number”);

frmvalidator.addValidation(”tarref’,”maxlen=l 5”, “Max length for Tar Number is 15”);

frmvalidator.addValidation(”tsdref’, “req”,”Please, enter your Tsd Number”);

frmvalidatoraddValidation(”tsdref’,”maxlen=15”, “Max length for Tsd Number is 15”);

frmvalidator.addValidation(”occurrence date”, “maxlen=l 5”);

frmvalidator.addValidation(”occurrence_date”,”req”,”Please, enter the occurrence date”);

frmvalidator.addValidation(”occurrence_date”,”date”);

frmvalidator.addValidation(”occurrence hour” ,“dontselect=OOO”);

frmvalidator.addValidation(”occurrence minute”,” dontselect=000”);

frmvalidator.addValidation(”occurrence_time”,”dontselect=OOO”);

64

frmvalidator~addValidation(”report_date”, “maxlen=1 5 H);

frmvalidator.addValidation(”report_date”, “req”, “Please, enter the Report date”);

frmvalidator.addValidation(”report_dat&’,“date”);

frmvalidator.addValidation(”report_hour”,”dontselect=OOO”);

frmvalidator.addValidation(”reportminute”,”dontselect=OOO”);

frmvalidator.addValidation(”reporttime”,”dontselect=OOO”);

frmvalidator.addValidation(”nature accident” ,“dontselect=OOO”);

frmvalidator.addValidation(”naturedamage”,”dontselect=zOOO”);

frmvalidator.addValidation(”accident_place”,”req”,”Please, enter the accident place”);

frmvalidator~addValidation(”accident_place”, “maxlen=l 00”, “Max length for Accident Placeis 100 “);

frmvalidator.addValidation(”partiesinvolved”,”req”, “Please, enter parties involved details”);

frmvalidator.addValidation(”parties_involved”,”maxlen=200”, “Max length for partiesinvolved details is 200”);

ftmvalidator.addValidation(”driver_particulers”, “req”, “Please, enter driver particulars”);

frmvalidator.addValidation(”driver_particulers”,”maxlen=250”, “Max length for driverparticulers is 250”);

frmvalidator.addValidation(”accidentcause”,”dontselect=OOO”);

frmvalidator.addValidation(”other_cause”,”req”,“Please, enter other causes”);

frmvalidator.addValidation(”other_cause”,”maxlen=250”, “Max length for other causes is250”);

fnnvalidator~addValidation(”victim_details”,”req”,”Please, enter Victim details”);

frmvalidator.addValidation(”victim_details”,”maxlen=500”, “Max length for victim details is500”);

fmivalidator.addValidation(”visiting_officer”,”req” ,“Please, specif~,i the visiting officer”);

frmvalidator.addValidation(”visiting_officer”,”maxlen=l 00”, “Max length for visiting officeris 100”);

frmvalidator.addValidation(”sender”,”req”,“Please, specify the Sender”);

frmvalidator.addValidation(”sender”,”maxlew=l00”, “Max length for the Sender is 100”);

!IJ}><Iscript~

65

/*Code for checking login /

<?php

$host=”localhost”; II Host name

$usemame=~’; II Mysqi usemame

$password=” ~; II Mysqi password

$dbname=”test”; I/Database name

$tbl_name=11userkabalagala~; II Table name

II Connect to server and select databse

mysql_connect(~$host11, “$usernam&, ~$password”)or die(11cannot connect”);

mysql_select_db(”$db_name”)or die(”cannot select DB”);

II username and password sent from form

$myusemame=$_POST[~myusemam&];

$mypassword=$POST[’mypassword’j;

II To protect MySQL injection (more detail about MySQL injection)

$myusemame = stripslashes($myusername);

$mypassword = stripslashes($mypassword);

$myusemame mysql_real_escapestring(Smyusemame);

$mypassword = mysql_real_escape_string($mypassword);

$sql=”SELECT * FROM $tbl_name WHERE username=~$myusername’ andpassword=~$mypassword”’;

$result=mysql_query($sql);

II Mysql_num_row is counting table row

$countmysql_num_rows($result);

I/If result matched $myusemame and $mypassword, table row must be 1 row

if~$count==1 ) {II Register $myusemame, $mypassword and redirect to file “kabalagalapolicestation.php”

header(”location:kabalagalapolicestation.php”);

66

}else

{echo ~Your Username or Password is incorrect! please try again. ~‘;

}?>

/*Code for creating new user /

<form action=”insertadduserkabalagala.php” name=”myform” method=”post” id=~myform~>

<table align=”center” cellspacing=”2” cellpadding=~2” border=11011>

<tr>

<td align=~right11> User Name <!td>

<td><input name=”username11 type~~text~# id~usernam&’ size=”2011 /></td>

</tr>

<tr>

<td align~right11> Password </td>

<td> <input name=11password~ type=”password” id=”password’~ size=~2O11 I> </td>

</tr>

<tr>

<td align=~right’t> Confirm Password </td>

<td> <input name=~conf~password~’ type=”password’t id~’conf~assword” size=~2O~I></td>

<Itr>

<tr>

<td align=”right11></td>

<td> <div id=Hmyform_errorlocH class~error_strings’>

</div> </td>

</tr>

67

<tr> <td align=11right”></td>

<td><input type=”submit” value=11Create Account11 I> <input type~=11reset” va1ue=HResett~I> </td>

<Itr>

</table>

</form>

I/Code for creating new administrator

<form action=~insertnewusercodecpskampala.php11 name=11myform11 method=”post11id”myform”>

<table cellspacing=11211 cellpadding=11211 border=11011>

<tr>

<td a1ign~°right~’>

User Name

<td> <input name=”usemame” type=”text11 id=”username11 size=”20 ‘~ I> </td>

<Itr>

<tr>

<td a1ign=”right~’> Password</td>

<td> <input name=”password” type=11text11 id=”password” size=”2011 /> </td>

<Itr>

<tr>

<td align=11righttt>Conflrm Password <Itd>

<td> <input name=”confpassword” type=11text” id=”conf~assword11 size=112011 7> </td>

<Itr>

<tr>

<td align=11right11></td>

<td>’<div id=11myform_errorloc11 class=11error strings11>

68

</div>

<tr>

<td a1ign=’~right”></td>

<td><input type=~submit11 value=11Submit” /> </td>

</table>

<Iform>

69

traffic accident records information system in

Documents