CRIMINAL RECORD MANAGEMENT

SYSTEM
A

Minor Project Report

Submitted

In Department of Computer Science & Engineering

Bachelor of Technology

Mentor: Submitted By:

Mr. Lokendra Pal Eshaan Belani [16BCON193]

Aditi Saini [16BCON199]
Rohit Jhansla [16BCON204]
Pratul Singh [16BCON217]

Department of Computer Science & Engineering

JECRC UNIVERSITY, JAIPUR

2019
 CERTIFICATE

This is to certify that Minor Project Report entitled “CRIMINAL RECORD

MANAGEMENT SYSTEM” has been duly submitted by

 Eshaan Belani 16BCON193

 Aditi Saini 16BCON199
 Rohit Jhansla 16BCON204
 Pratul Singh 16BCON217

for partial fulfilment of the Degree of Bachelor of Technology of JECRC University. It has
been found satisfactory and hence approved for submission as Minor Project during academic
session 2018-2019.

Mentor: Head of Department:

Mr.Lokendra Pal Dr. Naveen Hemrajani
(Dept. of Computer Science (Dept. of Computer Science
& Engineering) & Engineering)

2
 DECLARATION

We hereby declare that the report of the project entitled CRIMINAL RECORD
MANAGEMENT SYSTEM is a record of an original work done by us at JECRC
University under the mentorship of Mr. Lokendra Pal (Dept. of Computer Science
Engineering). This project report has been submitted as the proof of original work for the
partial fulfilment of the requirement for the award of the degree of Bachelor of Technology
(B.Tech). It has not been submitted anywhere else, under any other program to the best of our
knowledge and belief.

Team Members: Signatures:

Eshaan Belani [16BCON193]

Aditi Saini [16BCON199]

Rohit Jhansla [16BCON204]

Pratul Singh [16BCON217]

3
 ACKNOWLEDGMENT

A project of such a vast coverage cannot be realized without help from numerous sources and
people in the organization. We take this opportunity to express our gratitude to all those who
have been helping us in making this project successful.
We are highly indebted to our faculty mentor Mr. Lokendra Pal. He has been a guide,
motivator & source of inspiration for us to carry out the necessary proceedings for the project
to be completed successfully.
We would also like to convey our sincere thanks to Dr. Naveen Hemrajani, HOD,
Department of Computer Science & Engineering, for facilitating, motivating and supporting
us during each phase of development of the project. Also, we pay our sincere gratitude to all
the Faculty Members of JECRC University and all our Colleagues for their co-operation and
support.
Last but not least we would like to thank all those who have directly or indirectly helped and
cooperated in accomplishing this project.

4
 ABSTRACT

Crime file management system project abstract helps in understanding over view of the
project with module description, advantages of this system, existing and proposed system
differences, software and hardware requirements used in this system and introduction to data
flow diagram (dfd) database details. Main idea behind developing this project is to provide an
online application for police department to manage criminal and staff information in a
computerized manner.

Using this system citizen can file case through online; get updates on case, and
communication between different stations in sharing criminal information.

5
 INDEX
UNIT DESCRIPTION PAGE No.
I. TITLE PAGE 1
II. CERTIFICATE 2
III. DECLARATION 3
IV. ACKNOWLEDGEMENT 4
V. ABSTRACT 5
1. PROJECT CHARTER
1.1 Problem Statement & Objective 12
1.2 Investigation & Analysis 13
1.3 Introduction to Project 14
1.4 Solution 15
1.5 Scope of the Project 16
2. SYSTEM REQUIREMENT SPECIFICATION
2.1 Overall Description 17
2.1.1 Product Perspective 17
2.1.1.1 System Interfaces 17
2.1.1.2 User Interfaces 17
2.1.1.3 Hardware Interfaces 18
2.1.1.4 Software Interfaces 19
2.1.1.5 Communications Interfaces 20
2.1.1.6 Memory Constraints 20
2.1.1.7 Operations 20
2.1.1.8 Site Adaptations Requirements 20
2.1.2 Project Functions 20
2.1.3 User Characteristics 21
2.1.4 Constraints 21
2.1.5 Assumptions & Dependencies 21
2.2 Specific Requirements 21

2.2.1 System Product Features 22

6
 2.2.1.1 Maintainability 22
2.2.1.2 Portability 23

3 SYSTEM DESIGN SPECIFICATION

3.1 System Architecture 24
3.2 High Level Design Diagrams 25
3.2.1 Activity Diagram 26
3.2.2 Data-Flow Diagram 27
3.2.3 Entity Relationship Diagram 28
4. METHODOLOGY & TEAM
4.1 Introduction to Waterfall Framework 29
4.2 Team Members, Roles & Responsibilities 30
5. SYSTEM TESTING 31
6. TEST EXECUTION SUMMARY 34
7. CODING SCREENSHOTS 35
8. PROJECT SCREENSHOTS 41
9. PROJECT SUMMARY AND CONCLUSION 47
10. FUTURE SCOPES 48
11. APPENDIX 49
12. REFERENCES 50

7
 INDEX OF FIGURES

S.no. DESCRIPTION PAGE No.

1. ARCHITECTURE DIAGRAM 15
2. SYSTEM ARCHITECTURE 24
3. USECASE DIAGRAM 25
4. ACTIVITY DIAGRAM 26
5. DATA FLOW DIAGRAM 27
6. ENTITY RELATIONSHIP DIAGRAM 28
7. BASIC WATERFALL MODEL 29
8. FORGET PASSWORD 35
9. POLICE LOGIN 36
10. CHANGE PASSWORD 36
11. CRIMINAL REGISTRATION 37
12. POLICE REGISTRATION 37
13. LOGIN 38
14. HOME PAGE(HTML) 38
15. SEARCH CRIMINAL 39
16. FIR REGISTRATION 39
17. CONTACT US 40
18. LOGOUT 40
19. HOME PAGE 41
20. CONTACT US PAGE 41
21. LOGIN PAGE 42
22. SIGN UP PAGE 42
23. FORGET PASSWORD PAGE 43
24. SEARCH CRIMINAL 43
25. USER PAGE 44
26. FILE FIR 44

8
27. CRIMINAL REGISTRATION 45
28. POLICE OFFICER PROFILE 45
29. CHANGE PASSWORD 46
30. SIGN OUT 46

9
 INDEX OF TABLES

S.No. DESCRIPTION PAGE No.

1 Minimum client side hardware interfaces 17

2 Minimum server side hardware interfaces 17

3 Recommended client side hardware interfaces 18

4 Recommended server side hardware interfaces 18

5 Minimum Software Interfaces 19

6 Recommended software interfaces 19

3 Roles and Responsibilities 29

10
 ABBREVIATIONS USED

JSP JavaServer Pages

FIR First Information Report
DBMS Database Management System
OS Operating System
ICT Information and Communication Technologies
GPS Global Positioning System

11
 UNIT – 1 PROJECT CHARTER

1.1 Problem Statement & Objective

Problem: Less participation of people in the crime department.

Reasons: The project is aimed to develop a crime management system for maintain a
computerized record of all the fir against crime. The system is desktop application that can be
access throughout the police department. This system can be used as an application for the
crime file of the police department to manage the records of different activity of related to
first information report .In such desktop Crime management system we will manage all such
activities (like registration of the complaint updating information, search of particular
viewing of the respective reports of crimes) that will save time, manpower. This system will
provide better prospective for the enhancement of organization regarding to quality and
transparency.
Solution: This software is for police station which provides facility for reporting crimes,
complaints, FIR, charge sheet, prisoner records, show most wanted criminal’s details, law
and order details as well as court details. It also track police station constable details, police
information, attendance details, salary report, over time, etc. This Software Package allows
Police Departments to store all the details related to the department and use them whenever
necessary.

Objective: Make the Police functioning citizen friendly and more transparent by automating
the functioning of Police Departments. Improve delivery of citizen-centric services through
effective usage of ICT. Provide the Investigating Officers of the Civil Police with tools,
technology and information to facilitate investigation of crime and detection of criminals.
Improve Police functioning in various other areas such as Law and Order, Traffic
Management etc. Facilitate Interaction and sharing of Information among Police
Departments, Districts, State/ headquarters and other Police Agencies Assist senior Police
Officers in better management of Police Force. Keep track of the progress of Cases, including
in Courts. Reduce manual and redundant Records keeping

12
1.2 Investigation & Analysis

Criminality is part and parcel of human nature and society. That is why no society can claim
to be completely crime free. But the types of criminal behaviour tend to follow the pattern of
social and economic development of a given society. It is therefore not unexpected that a
society at a low level of development and as Madden and Chiu (1998) mentioned, uneven
distribution of income (and wealth) , tends to experience an upsurge in the rate of violent
crimes such as armed robbery, politically motivated killings, the use of illegal weapons,
ethnic and religious clashes and the like. What is worrisome, however, is that the police
which are meant to be the antidote to criminality appear to be getting overwhelmed by the
phenomenon. These include inadequate manpower, lack of expertise, lack of adequate
equipment, low level of education, low morale, lack of training facilities and lack of
technological knowhow, etc.

This highlights in detail the processing steps which convert input into output. The processing
tasks to be carried out by the Investigation If a match is found, the record is then displayed.
Otherwise, the system should display a message saying such record does not exist.

To retrieve all existing criminal details in the database, the user should click on the “Full
Records” button, the system the retrieves the records of all existing criminal. To access the
full detail of a criminal as well as all information about the crimes committed, user will then
click on any part of the retrieved criminal detail and click on open records. The system then
displays the full record of that particular criminal. Another processing task involves
comparing Finger prints.

Following a sequential order, the systems searches the available finger prints in the database
for a match and if a match is found it pops up a box that displays “A direct match was found
with the criminal’s convict number and the finger id”. The user should then click on the “ok”
button, the criminal convict number and names will be displayed. To have full access to such
criminal details, the user should click on “Open” and the crime full details will be retrieved
from the database.

1.3 Introduction to Project

Crime Management System is a system used to report crimes. This project is mainly useful
for police Departments. This system will help to manage all the activities in a police
13
Department using computers. Currently all the works are done manually, by computerizing
all the activities inside a police Department can be managed easily and effectively.

The police Departments in the country are, today, virtually unconnected islands. Thanks to
telephones and wireless, and especially thanks to mobile telephones, there is voice
connectivity between the police Department and senior police officers, but that is about all.
There is no system of data storage, data sharing and accessing data. There is no system under
which one police Department can talk to another directly. There is no record of crimes or
criminals that can be accessed by a Department House Officer, except the manual records
relating to that police Department. The goals of the system are to facilitate collection, storage,
retrieval, analysis, transfer and sharing of data and information at the police Department and
between the police Department and the State Headquarters and the Central Police Org.

Crime Management System is a system used to report crimes. This project is mainly useful
for police Departments. This system will help to manage all the activities in a police
Department using computers. Currently all the works are done manually, by computerizing
all the activities inside a police Department can be managed easily and effectively.

1.4 Solution

With the introduction of this application which is an advanced computer techniques now
widely adopted as a front line security measure for both identity verification and crime
detection, and also offers an effective crime deterrent.

In the system only we can see the details of particular information about the police stations in
our state, the existing system has more workload for the authorized person, but in the case of
Proposed System, the user can registered in our site and send the crime report and complaint
about a particular city or person.

14
 Figure 1.1- Architecture Diagram

1.5 Scope of the Project

 The system will be a Reporting application that will be used for automating the
manual process of register different case in police Department .This system will
manage the details of all the crime who register themselves in police Department. The
system provides an interface to store the crime details of criminals or prisoners and
allows the user to search and view records. The system should have a login. System
should support for Data Entry module for Nominal Roll, Case register for each
prisoner entering in the prison
 The system will greatly simplify the overall procedure of crime files.

15
 The proposed system includes the following features:
 Login for user and admin
 Complaint registration
 View complaint status
 Criminal register management
 FIR Management
 Case History Details management
 Prisoners register management.
 Manage list about most wanted criminals
 At its core, the system should offer the following basic functionalities.
 The system requests that the administrator to enter his/her name, password.
 The administrator enters his/her name, password.
 The system validates the entered name, password, logs the actor into the system.

16
 UNIT – 2 SYSTEM REQUIREMENT SPECIFICATION

2.1 Overall Description

This section and its subsections contain the description of the project components such as
interfaces, performance requirements, design constraints, assumptions and dependencies etc.

2.1.1 Product Perspective

The application will be a Windows / Linux based, self-contained and independent product.

2.1.1.1 System Interfaces

List each system interface and identify the functionality of the system (hardware and software both) to
accomplish the system requirement and interface description to match the system.

2.1.1.2 User Interfaces

The application will have a user friendly and menu based interface. Following screens will be
provided:

• There will be a screen to display registration of police officer.

• A login screen for entering username, password will be provided.

• There will be a screen for taking the information of the related to FIR.

• There will be screen to add information for criminal.

• There will be screen to edit the information for police officer.

2.1.1.3 Hardware Interfaces

 Screen resolution of at least 800 x 600 pixels is required for proper and complete viewing
of screens. Higher resolutions in wide-screen mode will be better for a better view.

17
 Support for printer (dot-matrix / deskjet / inkjet / laser) is required. This implies that
appropriate drivers should be installed and printer device should be connected for printing
of reports and marksheets.

 A network connection (internet / intranet) is required to make the web service accessible on
other systems connected over the network.

Other hardware interface specifications are as follows:

HARDWARE INTERFACES - CLIENT SIDE (Minimum)

HARDWARE SPECIFICATIONS

Processor Dual Core or Higher

Keyboard (U.S. Design) Qwerty

Mouse USB

Table 1 – Minimum Client Side Hardware Interfaces

HARDWARE INTERFACES - SERVER SIDE (Minimum)

HARDWARE RAM DISK SPACE

Intel Core i3 / i5 / i7 2.27 GHz and higher

2048 MB 20 GB

Table 2 – Minimum Server Side Hardware Interfaces

18
 HARDWARE INTERFACES - CLIENT SIDE (Recommended)

HARDWARE RAM DISK SPACE

Intel Core i3

QWERTY Keyboard (U.S. Design) 2048 MB 60 GB

USB 2.0 Optical Mouse

Table 3 – Recommended Client Side Hardware Interfaces

HARDWARE INTERFACES - SERVER SIDE (Recommended)

HARDWARE RAM DISK SPACE

Intel Xeon higher 4096 MB

Or AMD equivalent 100 GB

Table 4 – Recommended Server Side Hardware Interfaces

2.1.1.4 Software Interfaces

Software Tool Version Purpose of Use

Windows 7 and higher Installation and operational

Operating system or Linux with Kernel 3.x and platform
higher
Internet Explorer 6 Access to the web
Web Browser and other higher application

compatible

19
 Running the web
Web Server GlassFish application over internet /
intranet
Running and linking the
Database MySQL 5.1 database over internet /
intranet to the online web
application

Table 5 – Minimum Software Interfaces

SOFTWARE INTERFACES (Recommended)

Software Version Purpose of Use

Tool

Operating system Windows 8 & higher Installation and operational

or Linux with Kernel 4.x & platform
higher
Web Internet Explorer 11 and Access to the web
Browser other higher compatible application
Web Server GlassFish Running the web application
over internet / intranet
Running and linking the DB
Database MySQL 5.5 on internet / intranet

Table 6 – Recommended Software Interfaces

2.1.1.5 Communication Interfaces

Client (customer) on Internet will be using HTTP/HTTPS protocol.

Client (system user) on Internet will be using HTTP/HTTPS protocol

20
2.1.1.6 Memory Constraints

 At least 256 MB of RAM and 2 GB of space on hard disk will be required for running the
application on client end.

 Similarly, a minimum of 2048 MB of RAM and 20 GB of space on hard disk will be

required for running the application on server

2.1.1.7 Operations

 The DBA at the client side will be assumed responsible for manually deleting or achieving
obsolete or non-required data from the database as per clients requirements.

 This will include database backup and recovery options also.

 The Glass Fish webserver will hosted and maintained on a remote server addressed by a
URL based address.

The URL address may be intranet or internet based as per clients requirements.

2.1.1.8 Site Adaption Requirements

The computing terminals connected to network (internet / intranet) at the client end will be
required to support the hardware and software interfaces specified in above sections.

2.1.2 Project Functions

The system will allow access only to authorized users with specific roles (Administrator,
Police Officer). Depending upon the user’s role, he / she will be able to access only specific
modules of the system.

A summary of the major functions that the software will perform:

 A Login facility for enabling only authorized access to the system.

 Police Officer will able to add / modify their personal information.

21
  Police Officer will file FIR.

 Police Officer will add/modify information of criminal.

 Police Officer will search the records of criminal.

2.1.3 User Characteristics

 Educational Level: User should be at least graduate and comfortable with English.

 Experience: User should be well versed / informed about the structure of the program.
Data entry and modification can be done only by the user authorized for this job.

 Technical Expertise: User should be comfortable using general purpose applications on a

computer.

2.1.4 Constraints

 Since the DBMS being used in this project is MySQL, and the web server is Glassfish, the
server technologies are out of any guarantees, unless specifically purchased for enterprise
environment.
 Due to limited features of DBMS being used, performance tuning features will not be
applied to the queries and thus the system may become slow with the increase of data
records being stored.
 Due to limited features of DBMS, database auditing will also not be provided.

2.1.5 Assumptions & Dependencies

 The number of domains being selected by the user does not change.
 The subject types (i.e. elective, core, lab, term paper and dissertation) do not change.
The number of semester programs in the client organization remains unchanged.

22
2.2 Specific Requirements
This section presents the software requirements to a level of detail sufficiency to enable
designers to design and testers to test the system.

2.2.1 System Product Features

The application will be password protected. Users will have to enter correct username,
password and role in order to access the application modules allowed to their privilege.

2.2.1.1 Maintainability

The application will be designed in a manner to make it easy to incorporate new requirements
in individual modules such as subject info, student info, subject choices, marks info, report
generation and user accounts activation / deactivation.

2.2.1.2 Portability

The application will be easily portable among any windows or Linux based systems that have
Apaches web server and MySQL database installed.

23
 UNIT– 3 SYSTEM DESIGN SPECIFICATIONS

3.1 System Architecture

System architecture presents the schematic view of the complete system along with its major
components and their connectivity. The overall architecture of the proposed system will be as
follows.

Front End Client

Application (with data
Entry/ update/ cancel/ view Backend
And reporting facility) Database

Figure 3.1 - System Architecture

24
3.2 High Level Design Diagrams

Figure 3.1 - Usecase Diagram

25
3.2.1 Activity Diagram

Figure 3.2 – Admin Activity Diagram

26
3.2.2 Data-Flow Diagram

Figure 3.3- Level 1 DFD

27
3.2.3 Entity Relationship Diagram

Figure 3.4 – Entity Relationship Diagra

28
 UNIT– 4 METHODOLOGY & TEAM

4.1 Introduction to Waterfall Model

The Waterfall Model was first Process Model to be introduced. It is also referred to as a
linear-sequential life cycle model. It is very simple to understand and use. In a waterfall
model, each phase must be completed before the next phase can begin and there is no
overlapping in the phases.

The waterfall Model illustrates the software development process in a linear sequential flow;
hence it is also referred to as a linear-sequential life cycle model. This means that any phase
in the development process begins only if the previous phase is complete. In waterfall model
phases do not overlap. In "The Waterfall" approach, the whole process of software
development is divided into separate phases. In Waterfall model, typically, the outcome of
one phase acts as the input for the next phase sequentially.

Following is a diagrammatic representation of different phases of waterfall model.

Figure 4.1 – Basic Waterfall Model

The sequential phases in Waterfall model are:

 Requirement Gathering and analysis: All possible requirements of the system to

be developed are captured in this phase and documented in a requirement
specification doc.

29
  System Design: The requirement specifications from first phase are studied in this
phase and system design is prepared. System Design helps in specifying hardware
and system requirements and also helps in defining overall system architecture.

 Implementation: With inputs from system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality which is referred to as Unit Testing.

 Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system
is tested for any faults and failures.

 Deployment of system: Once the functional and non functional testing is done, the
product is deployed in the customer environment or released into the market.

 Maintenance: There are some issues which come up in the client environment. To
fix those issues patches are released. Also to enhance the product some better
versions are released. Maintenance is done to deliver these changes in the customer
environment.

4.2 Team Members, Roles & Responsibilities

Team Member Project Role Responsibilities

Aditi Saini Coding, Report UML Diag.,Code(Login)

Eshaan Belani Coding,Report Abstract, Code (Criminal reg.)

Rohit Jhansla Coding,Report SRS,Code(Officer reg.)

Pratul Singh Coding,Testing System Testing,Code(Criminal

record)

Table 7 – Roles and responsibilities

30
 UNIT– 5 SYSTEM TESTING
5.1 Functionality Testing
In testing the functionality of the web sites the following features were tested:
 Links
a) Internal Links:
All internal links of the website were checked by clicking each link individually and
providing the appropriate input to reach the other links within.
b) External Links
Till now no external links are provided in our website but for future enhancement we will
provide the links to the candidate’s actual profile available online and link up with the
elections updates online etc.
c) Mail Links
No mail links are provided in our website till this stage but this is also a future
enhancement of our website to trigger mails to people for keeping them updated about the
online registration dates, the polling dates and other details.
d) Broken Links
Broken link are those links which so not divert the page to specified page or any page at
all. By testing the links on our website there was no link found on clicking which we did
not find any page.

 Forms
a) Field validation
Checks on dates have been applied
For eg. The Date of birth should be less than the current date and after that we have
checked the age to be greater than or equal to 18 years (the eligible age for casting vote).
Checks have been applied on starting and ending dates, ie, the starting dates of elections
or registrations should always fall before their respective ending dates.

31
b) Error message for wrong input
Error messages have been displayed as and when we enter the wrong details (eg. Dates),
and when we do not enter any detail in the mandatory fields. For example: when we enter
wrong password we get error message for acknowledging us that we have entered it
wrong and when we do not enter the username and/or password we get the messages
displaying the respective errors.

c) Optional and Mandatory fields

All the mandatory fields have been marked with a red asterisk (*) and apart from that
there is a display of error messages when we do not enter the mandatory fields. For
example: As the first name is a compulsory field in all our forms so when we do not enter
that in our form and submit the form we get an error message asking for us to enter details
in that particular field.

 Database
Testing is done on the database connectivity.
In the database testing we included following cases:
a) Entries in database through frontend and checked for the same in the tables.
b) Checked for the data types.
c) Checked for range of each type of data.
d) If entries made in one table are affecting other tables then we have checked those entries
also.
e) We not just added details in the database by default but also did the same using the
frontend.

5.2 Performance Testing

Performance testing can be applied to understand the website’s scalability, or to benchmark
the performance in the environment of third party products such as servers and middleware
for potential purchase. This can only be done once it is put into use on the actual internet
server and tested by the users.
Till now it is done using the null modem on two systems.

32
The system load includes:
a) What is the number of users per time?
b) Checking for peak loads and how system behaves.
c) Amount of data accessed by user.
This is done using only 2 systems for now so cannot be tested for load unless we deploy it on
a real server machine.

5.3 Usability Testing

Usability testing is the process by which the human-computer interaction characteristics of a
system are measured, and weaknesses are identified for correction.
a) Ease of learning
b) Navigation
c) Subjective user satisfaction
d) General appearance
As system is not put into the real time use so it’s not yet tested for usability.

5.4 Server Side Interfacing

In this we tested the server side interface. This was done by verifying that communication is
done properly. Also the compatibility of server with software, hardware, network and
database was tested.

5.5 Client Side Compatibility

The client side compatibility is also tested using various browsers like Google Chrome,
Mozilla Firefox and Internet Explorer.

33
 UNIT– 6 TEST EXECUTION SUMMARY

Execution Test Summary Report is an overall view of Testing Process from start to end. Test
Plan comes at the starting of project while Test Summary Report comes at the end of testing
process. This report is given to the client for his understanding purpose.
The Test Summary Report contents are :
1. Test Case ID generated = 10
2. Total number of resources consumed = 6
3. Passed Test Cases = 8
4. Failed Test Cases = 2
5. Status of Test Cases = 80 % Successful

34
UNIT-7 CODING SCREENSHOTS

7.1 Forget Password

35
 7.2 Police Login

7.3 Change Password

36
7.4 Criminal Registration

7.5 Police Registration

37
 7.6 Login

7.7 Home Page(HTML)

38
7.8 Search Criminal

7.9 FIR Registration

39
7.10 Contact Us

7.11 Logout

40
UNIT– 8 PROJECT SCREENSHOTS

Figure 8.1 Home Page

Figure 8.2 Login Page

41
 Figure 8.3 Signup Page

Figure 8.4 Forgot Password Page

42
Figure 8.5 Search Criminal

Figure 8.6 User Page

43
 Figure 8.7 File FIR

Figure 8.8 Search Fir

44
Figure 8.9 Criminal Registration

Figure 8.10 Police Officer Profile

45
Figure 8.11 Change Password

Figure 8.12 Sign Out

46
 UNIT– 9 PROJECT SUMMARY AND CONCLUSIONS
Crime file management system initiates the objective of providing the user with customized
and powerful complaint registration and process management system side software. The
software is built with all options such as complaint registration, prisoner’s registration, and
post-mortem report generation etc…All the requirements specified during the analysis and
design phase are fully met, thus resulting in the formation of good software. The interface
provided is very user friendly and flexible for all times. The aim of proposed system is to
develop a system of improved facilities. The proposed system can overcome all the
limitations of the existing system. The system provides proper security and reduces the
manual work. The existing system has several disadvantages and many more difficulties to
work well. The proposed system tries to eliminate or reduce these difficulties up to some
extent. The proposed system will help the user to reduce the workload and mental conflict.
The proposed system helps the user to work user friendly and he can easily do his jobs
without time lagging.

47
 UNIT– 10 FUTURE SCOPES

The possible future scope of this application will be on mobile platform with following
enhancements:

1. Designing of mobile application for this project on Android / iPhone platforms.

2. Addition of GPS tracking unit to the mobile app for tracking its real time geographical
location.

3. Addition of a Self-Service panel for extended support to the boarding passengers.

4. Mandating introduction of ID-proof documents such as Adhaar, PAN, Driving Licence for
tracking, security and authentication of passengers.

5. In future system will provide facility to send message.

6. We will design an emergency button in our application through which if some emergency
occurs then user just have to press that button and get the help from that local area police
department.

48
 UNIT-11 APPENDIX
1. FORMAT
Size : A4
Normal Text Size : Times New Roman, font size 12.
Heading Text Size : Times New Roman, font size 14 (Bold face)
Sub-Heading Text Size : Times New Roman, font size 12 (Bold face)
Margins : 1.5 inch on the left and top, 1 inch at the
bottom and 1 inch on the right
Paragraph : At Single Spacing
Line Spacing : 1.5 spacing to be provided throughout report
Page number : Bottom centre of each page.
Binding : Spiral bound with specified colour coding.

2. ARRANGEMENT OF INITIAL PAGES

a. Front Cover Page (Black & White)
b. Certificate of the group members
c. Declaration
d. Acknowledgement
e. Abstract
f. List of figures

49
 UNIT– 12 REFERENCES
BOOKS:
1. Herbert Schildt, Java 2: The Complete Reference, Seventh Edition, McGraw Hill.

2. Jim Keogh, J2EE: The Complete Reference, Fourth Edition, McGraw Hill.

3. Marty Hall, Web Development with Java Server Pages.

WEBSITES:
1. http://www.stackoverflow.com/

2. http://w3schools.com

50