AIMS Presentation

HARAMBE UNIVERSITY HOLETA CAMPUS
FACULTY OF TECHNOLOGY
DEPARTMENT OF COPMUTER SCIENCE
WEB-BASED ACCIDENT MANAGEMENT SYSTEM ON HOLETA CITY POLICE STATION
Submitted By
Name ID-NO
1. Abduselam Shanko 8024
2. Bethelehem Mulegeta 8016
3. Biniam Keneni 8026
4. Daba Tolosa 8025
5. Seifu Girma 8022
ADVISOR: MR. Bezu. T(Msc) June 2024 Holeta, Ethiopia
Chapter 1 Introduction
• The development of one country is analyzed from many direction or
factors such as peaceful, security of the people and their property etc.
• Those are protected by accident management station such as police and
society.
• The institution accident management station stands to protect peoples
and their property from danger.
• Our project aimed to develop new web based accident management
system.
• Accidents are a major concern in Ethiopia, leading to significant loss of
life, injuries, and property damage.
June 15/2024 WEB-BASED ACCIDENT MANAGEMENT SYSTEM ON HOLETA CITY POLICE STATION 1
Introduction…
• Efficient management of accident data is crucial for the Holeta City
Police Station to effectively investigate incidents, identify accident
trends, and develop targeted prevention strategies.
• The proposed system applies to accident management institution
all across the country and specially looks in the subject of accident
management system of Holeta city.
• It is well understood that accident prevention and detection of
accident depend on highly responsive back bone to information
management system.
• The efficiency of the accident controlling and the effectiveness
with which it deals with accident depend on what quality of
information it can drive or received from where the accident is
occur and how fast it can have response to it.
1.2. Statement of the problem
 The Holeta City Police Station currently relies on a paper-based system
for managing accident information. This system is inefficient and
presents several challenges:
Difficulty in storing and retrieving accident records
Time-consuming data collection and analysis
Inaccuracy of data due to manual entry errors
Limited accessibility of data for stakeholders
Inability to generate comprehensive reports for accident trends
Difficult to manage the overall system.
Accident file control mechanism is very tedious and complicated.
Data redundancy and inconsistency.
Data redundancy and inconsistency.
Difficult of communication of field office, society and the station to give
and get real time response to the accident.
1.3. Methodologies
1.3.1 Requirement analysis
1.3.1.1 Data gathering Methodology
• The requirement of the system is gathered using primary data
collecting techniques. These are listed below.
 Interview
 Observation
 Document Analysis
 Fact Finding Techniques
1.4. Research questions
• This project aims to answer the following questions:
 How can an Accident Information Management System improve
the efficiency and accuracy of accident data management in the
Holeta City Police Station?
 What are the functionalities and features required for an effective
AIMS for the station?
 What are the challenges associated with implementing an AIMS at
the station and how can they be mitigated/imporoved?
 How can user adoption and data security be ensured with the
implementation of a new AIMS?
1.5. Objectives of the Project
1.5.1 General objective
• To develop and implement an web-based Accident Information
Management System (AIMS) for the Holeta City Police Station to improve
the efficiency, accuracy, and accessibility of accident data.
1.5.2 Specific Objectives
The specific objective of the accident management in HCPS are-
• To analyze the existing accident data management process and identify
areas for improvement.
• To design a user-friendly and efficient AIMS to meet the specific needs of
the Holeta City Police Station.
• To develop and implement the AIMS using appropriate technologies.
• To provide training for police officers on the use of the AIMS
• To analyze the current system to design new data base system operated
easily using web based system.
1.5. Objectives of the Project…
• To enabling the workers to communicate easily across the
station and with their external environment.
• To automate the process of accident data collection and entry.
• To facilitate efficient storage, retrieval, and analysis of accident
information.
• To generate comprehensive reports on accident trends,
causes, and outcomes.
• To improve communication and collaboration between
different departments within the police station regarding
accident data.
• To perform a requirement analysis to find out the system
functional and nonfunctional requirements.
• To design and Implementation the new proposed system
1.6. Significance of the project
• Web-based accident management is a system that is customized to
the Holeta city police station. Generally, the significance of the new
system.
 The most important feature of the developed system is that it is an
accurate, easy, and efficient system to detect accidents as well as
record accidental information such as the date and time when the
accident occurs, location, and level of the accident.
 Also, the cause and effect of the accident are carefully recorded and
documented.
 It enabled searching the required information by using keys
 Report generation is done when necessary or required at any time.
 Avoidance of document missing
 Used to record data on the database.
 Used to manage accidents information easily.
1.6. Significance of the project…
• Ensure data accuracy.
• Used to make recording and retrieving very fast.
• Reducing the time required for accident data collection and
reporting.
• Increasing the accuracy and reliability of accident data.
• Enabling data-driven decision making for accident prevention
strategies.
• Facilitating communication and collaboration between police
officers and other stakeholders.
• Simple and user friendly.
• Report generation is done when necessary or required any time.
• Generally, the purpose of this accident information management
system is to solve all the problem of the organization and to satisfy
the requirement of the people.
1.7. Benefit and Beneficiaries of the project
1.7.1. Benefits
• Improved efficiency and accuracy of accident data management.
• Enhanced data analysis capabilities for accident trends and causes.
• Faster and more informed decision-making.
• Streamlined/easy communication and collaboration.
• Reduced paperwork and administrative burden/accident.
1.7.2 Beneficiary of the Project
1.7.2.1. Benefits to the police station
• Avoid improper resource consumption like paper, pens.
• Avoiding data loss because of improper data storage
• Neat investigation files in the station can be transferred from
generation to generation
• Enhance security mechanisms to protect crime records
1.7. Benefit and Beneficiaries of the project…
1.7.2.2. Benefits to Citizens
• Multiple channels to access services from police
• Simplified process for reporting the accident.
• Can view posted information’s by the station anywhere at any
time
• Faster and assured response from police to an accident.
1.7.2.3 Benefits to Police Department
• Enhanced tools for investigation
• Facilitates fast and efficient retrieval of data
• Can post necessary information to society easily.
• The reduced workload of the police station back-office activities
such as preparation of reports and station records management
• Can easily control the system.
1.7. Benefit and Beneficiaries of the project…
1.7.2.4 Benefits to Team member

• The team member can get additional knowledge.
• Support the team member for the next working.
1.8. Scope and limitation of the project
1.8.1 Scope of the project
• This project developed a web-based system for the Holeta city
police station accident management system. The developed project
is:-
 The system can easily retrieve the accident information.
 The systems can accurate way of recording and storing information
in the database.
 The system allows manages accident files using the web-based
system in a manner that is more secure than the previous system.
 The system can post news for the society to make them informed
by some additional information.
 The system can search, Insert, delete and update the accident
information when it is needed.
1.8. Scope and limitation of the project…
• In the proposed system they can update easily because all data
are in the database so we can update easily and in a short time.
• Presence of centralized documented and organized record.
• Enabling the workers of the system to get reliable information
where and when occurred as well as the type and level of the
accident to give reliable to response on detecting the accident.
• They can use either the Afan Oromo, Amharic nor English
language.
• The total number of each accident can be seen easily.
• They can prepare reports easily.
• The system easily manages accident report because everything
should be done web-based
1.8. Scope and limitation of the project…
1.8.2 Limitation of the project
• There are many constraints within our system, which limit their following
effectiveness of performance.
• Our system is limited only in the process of web based accident information
management system of the HCPS, but does not include about crime file
management system, the system depends on electric power and network
connection. The above activities or subsystems are proposed system imitations
because of the following reason.
 The system will not manage data for other types of incidents handled by the
police station.
 Times were the main factor of limitation, since the system can’t use other
languages.
 Resources, we have not laptop as an alternative when arbitrary failed the desktop
and also when the power is off for a long time.
 The system can’t detect an accident.
1.9 Constraint and risks
• Availability of resources (budget, personnel)
• User acceptance and training needs
• System security and data integrity/honesty concerns
1.10 Backup and recovery
• Develop a comprehensive backup and recovery plan to ensure data
security and system availability.
• Regular backups of data will be conducted and stored securely.
1.11 Feasibility study
• Most of information system projects have budgets and deadlines,
and analysis of factors for the feasibility forms the business case
(analysis of assumptions like resource availability and potential
problem and system costs and benefits) that justifies the
expenditure on the project.
1.11 Feasibility study
1.11.1 Operational feasibility
• The system we develop provides accurate, secured service and
decrease the labor work load.
• Also the system can be easily operated.
• It does not affect the existing organization structure. So, the
system is operationally feasible.
• The system we developed will provide accurate, active, secured
service and on every page, all the operable components such as
links, buttons and so on will be easy, understandable to use by the
users meanwhile these components shall operate, would be
functional for every required task so, the system is operationally
feasible.
• This system solves the problems of the existing system so the
system is operationally feasible.
1.11 Feasibility study…
1.11.2 Technical feasibility
• General study in the project area has shown that the current
technology and ability exists in order to complete objectives our
system.
• That is, our project can be done with current equipment, existing
software technology and available personnel and therefore it can
be conclude that the system is technically feasible.
• The developed system will be easily maintained/ retained and
repaired without requiring high Experts or Technical supports
because the system will be installed in adaptable technology’s and
the employees of the organization have some knowledge about
technology by providing training and Help how to use the system
and can use the system easily.
1.11.2 Technical feasibility …Cont.
• So the system we developed is technically feasible.
• The required technologies such that PHP, MySQL,
XAMPP/WAMP SERVER, JAVASCRIPT, MS Word 2010/2013
which we will use to work for this project are available,
familiar/Popular, free, widely used, maintainable, repair
and are compatible with the hardware that we will use.
• The environment that we deployed the system is available,
thus our system is technically feasible.
1.11.3 Economic feasibility
• The system we develop is economically feasible and the benefit is
out weighting the cost, since this project already computerizes the
existing system by the reduction of cost for materials used in
manual operation becomes beneficiary to the organization.
• As part of this, the costs and benefits associated with the
developed system are compared and the project is economically
feasible only if tangible or intangible benefits outweigh costs.
• When we analyze our developed system economically, it is cost-
effective.
• In economic analysis, the procedure is to determine the benefits
and savings that are expected from a candidate system and
compare them with costs.
...Cont
• So this system can estimate or minimize the cost of materials (paper,
pen, pencil) and Cost of employees' time relatively. A small amount of
budget is going to be used to build the developed system.
• Economically, the system will profit the organization by providing a better
means of managing accident management system for Holeta city police
station.
• Generally, the system that we developed Holeta city police station
accident management brought several tangible and intangible benefits.
1.11.4 Political feasibility
• The system we develop is not conflict with any government directly or
indirectly, because this new web based accident information
management gives service to citizens and the government Due to this, it
is politically feasible.
Chapter 3
3. Requirement Definition and Analysis
Introduction
• This proposal outlines the development and implementation of a web-based
Accident Information Management System (AIMS) for the Holeta City Police
Station.
• The system aims to revolutionize accident data management by leveraging
the power of the internet, enhancing efficiency, accuracy, and accessibility.
3.1 Current system
 The current accident management system at the Holeta City Police Station
relies heavily on paper-based records. This section will delve into the
specifics of the existing system, including:
• Data collection methods:-Describe the forms used for accident reporting,
the information captured, and the process followed by officers.
• Data storage:-Explain how accident records are currently stored (e.g., filing
cabinets, binders).
Current System…
…Cont.
• Data retrieval:-Describe the process of searching and retrieving
accident data from paper records.
• Accident Reporting Forms:-Officers fill out paper forms
capturing details like date, time, location, parties involved,
vehicle information, witness statements, and a narrative of
the accident.
• Manual Data Entry:-Completed forms are manually entered
into a central accident register or spreadsheet.
• Paper-based Filing:-Accident reports are physically stored in
files or folders, making retrieval time-consuming
3.2 Business rules
 A business rule of the existing system is successfully an operating standard or
policy that will explain the existing system of Holeta city police.
 The existing system has many business rules or principles some of them are:
 BR1: New accident reports (first information reports) have to be received and
organized by the accident control team.
 BR2: Emergency accidents should get a fast response as much as possible.
 BR3: accident file should be investigated by the Accident control team.
 BR4: The accident should be happened in Holeta city or around the city, in order
to start the investigation process.
 BR5: any accidental emergency should be reported in 24 hours
 BR6: society had right to report any accident
 BR7: Dispatcher works to accept report detail information from society (place,
location, time, and type of accident)
 BR8: field officer find a witness to compile a report for dispatcher
 BR9: dispatcher set order based on the investigation result
3.3 Forms that used to in existing system.
• Provide a detailed analysis of the existing paper forms used for

accident reporting. This includes:
 Identifying the specific forms used (e.g., accident report form,
witness statement form).
 Describing the data fields captured on each form.
 Highlighting any redundancies or inconsistencies in data
collection across different forms.
3.4 Problems of current system.
• The current paper-based system suffers from several
limitations:
3.4.1 Performance problem.
• Time-consuming data entry and retrieval processes.
• Difficulty in generating reports and analyzing trends.
• Data entry and retrieval are slow and laborious.
• Compiling accident reports and statistics requires manual effort
and analysis.
• The response time for performing every process is very slow.
• Documents are stored physically this increases the space
complexity.
• There is always delay time in information search and retrieval
3.4.2. Response time problem.
• Delay in producing different reports.
• Delay in identifying employee status.
• Inaccuracy in updating important information because of manual
processing.
• No centralized database
• No computerized data gathering, storing, processing, and
disseminating facilities.
• To provide information, it may take inevitably long time by
searching the necessary facts to which it is intended for
3.4.3. Stored data Problem:
• Data is stored repeatedly in different files formats – The same
information is stored in many copies repeatedly in different forms.
• Data is not secured. Due to this, some secret information is
opened for unauthorized users or agents.
06/22/2024
3.4.4.Economics Problem
• The economic problem is mainly concerned with cost control and
profit incremental issues.
• Manual handling of data is expensive as compared to an automated
system. In general, the cost in terms of time is very high.
• As the business entry increases, the existing manual system will
incur costs to handle those requirements.
• As the number of controlling teams to handle the task of manual
processing increases, the accident management system will spend a
lot of money on its staff.
3.4.5. Efficiency problem
• Waste of time.
• Data is redundantly input or copied.
• Data is redundantly processed.
• Information is redundantly generated
3.4.6. Data Redundancy and Inconsistency
• Data may be entered multiple times, leading to inconsistencies
and duplication.
• Maintaining consistent data quality across reports is
challenging.
• Repetitive data entry across different forms leads to errors and
inconsistencies.
• Difficulty in ensuring data accuracy and completeness.
3.4.7 Data Storage Problem.
• Physical storage space for paper records is limited and prone to
damage or loss.
• Retrieving specific accident reports can be time-consuming.
• Limited storage space for paper records.
• Risk of damage, loss, or misplacement of records
3.4.8 Low Data Retrieval.
• Extracting specific information or trends from accident data is

difficult and requires manual analysis.
• Generating reports on accident patterns or causes is a lengthy
process.
• Manual searching of paper records is slow and laborious.
• Difficulty in retrieving specific data points or filtering
information based on criteria.
3.4.9. Security and Control Problem.
• Limited access control mechanisms for paper-based records.
• Increased risk of unauthorized access or data tampering.
• Paper records are susceptible to unauthorized access, damage, or loss.
• Maintaining data integrity and audit trails is difficult without proper
controls.
• Difficult of getting available resource to control and detect the accident at
real time and to save human life and property since there is no organized
detective in the system to control the accident rather than the society
and police are tries to detect the accident as much as possible.
• Difficult to manage the overall system.
• Someone come from other place suddenly die in accident the person
have not id or something about himself tell, Only thing is write report and
stored it.
• Accident file control mechanism is very tedious and complicated.
3.4.10. No Backup and Recovery.
• Paper records are vulnerable to loss due to fire, theft, or natural
disasters and war.
• No system exists for recovering lost or damaged data.
• No formal backup system exists for paper records.
• Data loss due to damage, misplacement, or theft of paper documents
is a significant risk.
3.5 The Proposed system.
• The proposed Accident Information Management System (AIMS) will be
address the limitations of the current system by:
3.5.1 Faster Data Processing and Accessing.
• A digital platform will enable faster data entry and retrieval of accident
reports.
• Users can easily search and filter data based on specific criteria.
• Streamlined data entry process through user-friendly web interface.
• Efficient search and retrieval functionalities based on various criteria.
3.5.2 Data Integrity.
• Data validation rules will ensure accuracy and consistency in accident
information.
• Version control will track changes made to reports, maintaining data integrity.
• Data validation rules to ensure accuracy and completeness of information.
• Elimination of data redundancy across forms.
3.5. The Proposed system…
3.5.3 Data Security.
• User access will be controlled with different permission levels based
on roles.
• Secure data storage with encryption will safeguard sensitive
information.
• User authentication and authorization mechanisms to control access.
• Secure data storage practices to prevent unauthorized access.
3.5.4 Backup and Recovery.
• A comprehensive data backup and recovery plan will be
implemented.
• Regular system backups will be stored securely for disaster recovery
purposes.
• Regular data backups to ensure information security and availability.
• Disaster recovery plan to restore data in case of system failures.
3.6 System Requirements of the Proposed System
3.6.1 Functional Requirements.
3.6.1.1. Introduction
• Under This topic mainly deals with the description of the
proposed system.
• Through the proposed system, we are going to solve the
problems under the existing system.
• The existing system has its problem and drawbacks.
• Therefore, the project team tries to develop a system, which
solves problems under the existing system.
• The proposed system will enable the system to store
information on the database.
3.6 System Requirements of the Proposed System…
• Generally, the new system follows the appropriate system
development methodologies as the only option for addressing
and solving those problems associated with the current
system, and this new system is a web-based application that
enables the users to access the services given by the system
through the Internet.
3.6.1.2. Functional Requirements
• The new system will be a networked application that will run
on client-server and provide case-to-use user interfaces to the
users and window server for the server-side application.
• The new system will also perform a record management
function that the system should record all the modifications on
the record management system.
• All in all the functionalities that will be provided by the system are the
following.
User account management
• The Dispatcher/administrator manage user Account according to the
followings:-
 Create User Account: the system Dispatcher creates an Account for new users.
 Update User Profile: The Dispatcher updates the user profile as needed
 Delete User Account: The Dispatcher Delete the user account when it is
needed
 View user Account: The Dispatcher view the user account information as
needed.
 The system allows the dispatcher to post information
 The system allows the dispatcher to view report
 The system allows manage report
 The system allows the dispatcher to open request.
Accident control team
The Accident control team manage files in the following manner:
• Add new file: the system Accident controlling team add new
files
• Delete file: The Accident controlling team delete file as needed
• Update file: The Accident controlling team update file as
needed
• View file: The Accident controlling team view file as needed
• The system allows generate report
• The system allows generate view request
3.6.2 Nonfunctional Requirements
• Non-functional requirements describe user-visible aspects of
the system that are not directly related with the functional
behavior of the system.
• These requirements do not directly affect the performance of
the system but are none the less important .
• They are concerned with security, performance,
internationalization, usability, maintainability, reliability,
modifiability, efficiency, portability across operating systems,
testability, understandability.
• Generally the non-functional requirements of the system are presented
below.
 Speed: The system will perform at 1 second or less at normal circumstances
while appending and retrieving data to and from the database respectively
(i.e. when networks and nodes are ok).
 Reliability: The system allows reliable communication between the main
station with sub-stations, and society. It also allows reliability while
searching and displaying data from the database, while appending data in
the database and data are passed to the correct end user. The developed
system should able to perform a required function under stated Conditions
 Security: The system database will be secured from accessed by any
unauthorized person by making the login to the system only restricted to
legal persons. We use strong password so it does not accessed by illegal
person.
 Quality: The system allows putting backup of data and it fulfills all
user requirements.
 User friendly interface Simple and interactive user interface
components should be part of the system. This user friendly
interface requirement of the system will be available in any end
user and system administrator interface of the application.
 Usability: The system provides a help and support menu in all
interfaces or give direct input for the user to interact with the
system. The user can use the system by reading help and support.
 Performance: Our system speed operation is very high. That means
the accuracy and response time of The system should be very fast.
 Availability: The system should always be available for access at 24
hours, 7 days a week. Also in the occurrence of any major system
malfunctioning.
• Portability: The system supports every operating system.
• Maintenance: New additional features can be added if required and
also the system components i.e. memory, disk, drives shall be easily
serviceable without much alteration in the code.
• Back up:-The system should have back up using external hard disk.
The backup is taken weekly.
• Error handling: Our system handles error by showing the message”
invalid input” when the user enter invalid input.
3.6.3. Documentation
• Our systems have a well-defined document that helps the database
maintain the system.
• We will also prepare a short and precise helping guide for the
system users which helps users how to use the system.
3.7 System Development and Implementation Tools…
3.7.1. System Development Tools.
• Implementation is a phase where all the work during analysis and design will be
turned to a functional system.
• Prototype is divided into three sub phase: interface implementation, database
implementation, and logical implementation.
• In interface implementation, we have tried to implement user- interface.
• Logical implementation implements the server-side functionality of the system.
S.NO Activities Tools
1 Client side coding HTML
2 Database Server MY SQL database
3 Web server Apache server
4 Server Side Script PHP
5 Browser Chrome
6 Editors Visual Studio Code
7 Documentation Microsoft office Word 2007
8 Design Visio and Edraw-max
Thank you for

your attention!
Thank You!!
Galatoomaa!!
እናመሰግናለነን፡፡
June 15/2024
Shukren!! 44

AIMS Presentation

Uploaded by

Copyright:

Available Formats

You might also like

AIMS Presentation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AIMS Presentation

Uploaded by

Copyright:

Available Formats

HARAMBE UNIVERSITY HOLETA CAMPUS

1.7.2.4 Benefits to Team member

• Provide a detailed analysis of the existing paper forms used for

• Extracting specific information or trends from accident data is

Thank you for

You might also like