CRIME MANAGEMENT SYSTEM - Edited

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 17

.

MASINDE MULIORO UNIVERSITY OF SCIENCE AND


TECHNOLOGY

MMUST CRIME MANAGEMENT SYSTEM

Daniel Gatere
SIT/B/01-01618/2018

Project proposal documentation submitted to the Department of Information


Technology in partial fulfilment for the Requirement of the award of Bachelors of
Science in Information Technology from Masinde Muliro University of Science and
Technology.
DECLARATION
I hereby declare that this project proposal is my original work and has not been submitted for the
award of a Bachelor’s Degree in any other institution.

Sign…………………………. Date…………………………
DANIEL GATERE
SIT/B/01-01618/2018

Sign…………………………. Date……………………….

DR. MICHAEL UJUNJU


Project Supervisor, Information Technology Project II
Department of Information Technology
Masinde Muliro University of Science and Technology

i
TABLE CONTENTS
DECLARATION....................................................................................................................................i
ABSTRACT..............................................................................................................................................iii
1 CHAPTER ONE................................................................................................................................4
INTRODUCTION.....................................................................................................................................4
1.1 Background Information..............................................................................................................4
1.2 STATEMENT OF THE PROBLEM...........................................................................................1
1.3 MAIN OBJECTIVE....................................................................................................................1
1.3.1 SPECIFIC OBJECTIVES....................................................................................................1
1.4 JUSTIFICATION........................................................................................................................1
2 CHAPTER TWO...............................................................................................................................2
LITERATURE REVIEW.........................................................................................................................2
2.1 Introduction...............................................................................................................................2
2.2 Current System..........................................................................................................................2
2.3 Proposed system.........................................................................................................................3
3 CHAPTER THREE...........................................................................................................................4
METHODOLOGY....................................................................................................................................4
3.1 INTRODUCTION.......................................................................................................................4
3.2 PROJECT REQUIREMENT ANALYSIS AND SPECIFICATION...........................................4
3.2.1 Functional Requirements..................................................................................................4
3.2.2 Non-functional requirements............................................................................................4
3.3 CONCEPTUAL AND FUNCTIONAL DESIGN........................................................................5
3.4 DEVELOPMENT ENVIRONMENT..........................................................................................7
3.4.1 Software Requirements.....................................................................................................7
3.4.2 Hardware Requirements...................................................................................................7
3.5 DEVELOPMENT PROCESS DESIGN......................................................................................8
3.6 DEVELOPMENT SCHEDULE................................................................................................10
3.7 DEVELOPMENT BUDGET.....................................................................................................11
REFERENCES........................................................................................................................................12

ii
ABSTRACT
Nowadays, much of the crimes committed were unreported to the authorities. Given this fact,
the study presents the development of MMUST Crime Management System through online
and even offline and at the same time is the active participation of the students. The idea
draws its motivation from the inconvenience of going to the police station and personal
belief of the weak investigative capabilities of the authorities to resolve petty crimes and
limited spreading of crime information to the community. The project specifically looks into
the crime detection and prevention. This study aims to provide an overview of the
investigative process and, in doing so, identify effective and efficient approaches to the
investigation and detection of the volume of crimes. The review is particularly aimed to
highlight the research evidence those investigative practices and actions that are likely to
lead to a positive outcome. The development of software includes the process of
brainstorming and planning, requirements analysis, system analysis and designs,
implementation and testing, deployment, and maintenance.

iii
1 CHAPTER ONE

INTRODUCTION

1.1 Background Information


The “MMUST Crime Management System” is a web-based application for online
complaining and computerized management of crime records. Here in this web application, a
person who wishes to file a complaint or report an incident must register before log in and
once the admin authenticates the user he or she can login into the website and file a
complaint .This complaint will be received by security department and the security officials
can send a message regarding status of the complaint to the user who filed the complaint.
Security officials can use this software to manage different crimes and some of the works
which is done in security station manually. Security officials get their login password from
admin directly. Some of the modules like unidentified persons, missing persons, and most
wanted criminals can be viewed through the website without logging in. So this website
helps police to find out the problems in the university without them actually coming to the
security department station.
The purpose of Crime Reporting system is to automate the existing manual complaint
filing systems that are used in MMUST security departments by the help of computerized
systems and full-fledged computer software thus fulfilling he requirements of all security
officials and students. This system will provide a path for crime reporting. It allows students to
report incidents and get it verified by security officials. The victims can file the case through the
application under various sections and the user can send photo evidence if any online.

4
1.2 STATEMENT OF THE PROBLEM.

In the present scenario, filling a complaint is a hectic task since one must go through a
hectic task of searching for a nearby senior security officer, waiting until security officials take
on their request and also having to recite or even to provide a written statement for them to get
justice thus consuming too much of an individual’s time.

1.3 MAIN OBJECTIVE


The main objective of the system is to manage criminal details in a centralized database and
provide solution for public to give complaint through online means.

1.3.1 SPECIFIC OBJECTIVES.


To design an application that will enable students to report crime cases online with ease.

To develop a web application that will enable law enforcement personnel to remotely access
criminal data that will be useful during investigations.

To implement a web application that will enable students to record and submit e-evidence on
crime scenes to law enforcers remotely.

1.4 JUSTIFICATION
It’s through proper records in databases that data mining is performed to analyze criminal
data. Creating database would enhance easy updating of criminal records.
1. The system enhances accurate and fast processing of data.
2. The database created would be protected by password to avoid any alteration

1
2 CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction
Crime against students is increasing at an alarming rate in almost all parts of Kenya.
This system is designed for particular need of the university to carry out operations in a
smooth and effective manner. The application is reduced as much as possible to avoid errors
while entering the data and it also provide error message while entering invalid data. No
formal knowledge is needed for the user to use this system and hence it proves it is user
friendly. MMUST crime management system can lead to error free, secure, reliable and fast
management system and it can assist the user to concentrate on the other activities rather than
to concentrate on the record keeping. The purpose of the project is to automate the existing
manual system with the help of computerized equipment and to fulfill the requirements so
that the data can be stored for long period with easy accessing and manipulation. Behavioral
analysis of crime against students and women using a graph shows that Crime against
women is increasing at an alarming rate in almost all parts of Kenya and women in the
Kenyan universities have been victims of humiliation, torture and exploitation. It has even
existed in the past but only in the recent years the issues have been brought to the open for
concern.

2.2 Current System


In the existing system people who want to file a complaint must go to the police station
all by themselves which is time consuming. Police people usually maintain records manually
which is again time consuming and it is difficult to manage those records. There can be loss
of records and important crimes issued which needs to be solved quickly may get delayed.
Major limitations are;
 Time consuming
 Paper work needed
 Loss of records
 Information about criminals and common people are not properly maintained

2
2.3 Proposed system
The manual system has some drawbacks which can be overcome by using my web-
based software “MMUST Crime Management System”. Students need not go to the security
station to file a complaint. Security officials need not have to maintain records manually
since this software maintains all the records with centralized database. Main aims are;
 Reduced time consumption
 No paper work needed
 No loss of records
 Centralized database management
 Information about criminals and common people is properly maintained
 Reduce error scope

3
3 CHAPTER THREE

METHODOLOGY

3.1 INTRODUCTION.
This chapter discusses the methodology mechanism that will be used to design and
implement the project. This includes the conceptual and functional design, system
requirements and hardware requirements, the project schedule and the possible expenditures
for the project development. The project will use Prototype development phases will
include; system requirement analysis, system design, system implementation, system testing
and system maintenance. This will enable me to build a prototype before proceeding to the
implementation phase.

3.2 PROJECT REQUIREMENT ANALYSIS AND SPECIFICATION


3.2.1 Functional Requirements
There are functions done by the System such as:
1. To store information and criminal records, easily
2. To easily search for criminal data in the System.
3. To Update, Edit, delete and save criminal data generate a report.
4. To make paperless criminal Records.
5. To provide unlimited analytics to security officials.

3.2.2 Non-functional requirements


a. Security
b. Reliability
c. Performance
d. Accuracy
e. Maintainability
f. Usability

4
3.3 CONCEPTUAL AND FUNCTIONAL DESIGN
This System will have a well-designed and attractive user interface that has four system
users, that is, the system administrator, security personnel and the students. The System
Administrator will be majorly in charge of the system users, but he/She will also be in charge
of data management, and personal account management.
Main Features
Administrator

1. Manage System Users


2. Manage data in the system
3. Manage Personal Account
Security officials

1. Manage Criminal data


2. Respond to incidents reported to the system
3. Approve reported incidents
4. Manage reported cases
Students

1. Mage Personal Account


2. Report Incidents
3. Follow up reported incidents

5
Fig 1: Conceptual Design

MMUST CRIME
MANAGEMENT
SYSTEM

6
Fig 2: Functional Design

3.4 DEVELOPMENT ENVIRONMENT


3.4.1 Software Requirements
i. MYSQL DBMS for the systems’ database
ii. HTML, CSS and JavaScript for frontend
iii. Python Django for backend
iv. Web browsers: Google Chrome
v. Visual Studio an integrated development environment (IDE)

3.4.2 Hardware Requirements


i. The hardware requirement of the project would include desktop or laptop with at least
2.0 GHz Processor Speed, At least 500 GB Hard Disk Capacity and 4GB RAM.
ii. x86 64-bit CPU (Intel / AMD architecture)

7
3.5 DEVELOPMENT PROCESS DESIGN

Analyze requirements

In this phase, one needs to clearly identify all the requirements that will be needed during
the project. The requirements are divided into hardware and software requirements.
Documenting the requirements is required to help the developer have proper planning and
budgeting on how to develop the proposed project to avoid uncertainties and unexpected
expenses.

System Design

At this level of development, the developer starts designing the software after they have
identified requirements. In the design phase, you and the development team determine what your
software needs, how it will look, and what the timeline for development is going to be. The phase helps
the developer to understand what is expected at each stage of the development. The design may
be shown using the Data Flow Diagram and Charts, among other methods of representation.

8
Implementation

The implementation phase marks the beginning of bringing the project to work, and the
developer starts coding the project. The developer needs to use the designs made in the design
stage to ensure that the implementation works within the designed System. The developers start
constructing the whole framework using the programming language chosen to write code .

Testing

After the developer is done with the implementation of the design, the System is tested to
identify any defect in the System. If any defect is realized, then the developer fixes the defect,
and the testing process is repeated again—a regression test to see whether there are new defects
that were introduced.

Operate and Maintenance

At the maintenance phase, the team ensures that the system/application is running smoothly,
and any issues that are reported while the System is running, it will be fixed and tested.
Maintenance of the System is done through changing some parts of the code or even
reinstallation or updating the System to a newer version.

9
3.6 DEVELOPMENT SCHEDULE

TASKS IN WEEKS
1st 2nd 3rd 4th 5th 6th 7th 8th 9th 10th
REQUIREMENTS
1
ANALYSIS
2 PLANNING
3 DESIGNING
4 IMPLIMENTATION
5 TESTING
DOCUMENTATIO
6
N

10
3.7 DEVELOPMENT BUDGET

Items Required Amount Required (Ksh)

Laptop 20,000

Internet 1,500

Softwares 3,000

Miscellaneous 2,000

TOTAL 26,500

11
REFERENCES

Kamruzzaman, M. M. "E-crime management system for future smart city." Data processing techniques
and applications for cyber-physical systems (DPTA 2019). Springer, Singapore, 2020. 261-271.

Awodele, Oludele, et al. "A,“A REAL-TIME CRIME RECORDS MANAGEMENT SYSTEM FOR
NATIONAL SECURITY AGENCIES”." European Journal of Computer Science and Information
Technology 3.2 (2015): 1-12.

Brahan, John W., et al. "AICAMS: artificial intelligence crime analysis and management
system." Knowledge-Based Systems 11.5-6 (1998): 355-361.

12

You might also like