A

PROJECT REPORT
ON
Police complaint Reporting System
Towards partial fulfilment of the requirement in
5rd, BCA, 2020-2021
Submitted By: -
190510101157Khushi sinojiya
190510101164Jaykumar tarabada
190510101165 Gautam tekwani
Submitted To: -

Parul Institute of Computer Application,

Parul University.
Under the Guidance of
Prof. Payal Parekh
Assistant professor
 Acknowledgement
The success and final outcome of this project required a lot of guidance and assistance from
many people and we are extremely privileged to have got this all along the completion of our
project. All that we have done is only due to such supervision and assistance and we would
not forget to thank them.

 I respect and thank Dr. Priya Swaminarayan, Dean, and FITCS for providing us an
opportunity to do the project work in BCA and giving us all support and guidance, which
made us complete the project duly. We are extremely thankful to Mam for providing her
support and guidance, although she had busy schedule managing the academic affairs.

 We would not forget to remember Prof. Hina Chokshi, HOD, BCA department for her
encouragement and more over for her timely support and guidance till the completion of our
project work.

We owe our deep gratitude to our project guide Prof. Payal Parekh, who took keen interest
on our project work and guided us all along, till the completion of our project work by
providing all the necessary information for developing a good system.

 I am thankful to and fortunate enough to get constant encouragement, support and guidance
from our Parents, all Teaching staffs of BCA Department which helped us in successfully
completing our project work. Also, we would like to extend our sincere esteems to all staff in
laboratory for their timely support.

[khushi sinojiya] [190510101157]

[jaykumar tarabada] [190510101164]

[Gautam tekwani] [190510101165]

1
 PARUL INSTITUTE OF COMPUTER APPLICATION

CERTIFICATE

This is to certify that _Khushi, jay Kumar, Gautam the student(s) of Parul
Institute of Computer Application, has/have satisfactorily completed the project
entitled “_police complaint reporting system” as a part of course curriculum in
BCA / IMCA semester-V for the academic year 2020-2021 under guidance of
Prof. Payal Parekh.

Enrolment Number: 190510101157

Enrolment Number: 190510101164

Enrolment Number: 190510101165

Quality of work Grade Sign of Internal

guide
Poor / Average / B /B+ / A / A+/O
Good /
Excellent

Date of submission:

HOD. Principal.

Prof.Hina Chokshi Dr. Priya Swaminarayan

1
Index Page No.
1. Research:...........................................................................................................................................2
1.2 Types of research:........................................................................................................................2
2. Feasibility Study:...............................................................................................................................3
2.1 Technical Feasibility:...................................................................................................................3
2.2 Economical Feasibility:...............................................................................................................3
2.3 Operation Feasibility:..................................................................................................................4
3. System Requirements Specification:.................................................................................................5
3.1. Introduction of SRS:...................................................................................................................5
3.2 Abstract:......................................................................................................................................5
3.3 System Users:..............................................................................................................................5
3.4 Modules:......................................................................................................................................6
3.5 Module Description:....................................................................................................................6
3.5.1 admin module:....................................................................................................................6
3.5.2 citizen:..................................................................................................................................6
3.6 Hardware Requirements:...........................................................................................................6
3.7 Software Requirements:...............................................................................................................6
3.7. Timeline Chat:............................................................................................................................7
4. Technology Description:....................................................................................................................8
4.1 Limitations of system:.................................................................................................................8
4.2 Future Enhancement:...................................................................................................................8
5. Data Flow Diagram:..........................................................................................................................9
5.1 Context Level DFD’s:..................................................................................................................9
5.2 Level 1 DFD’s:..........................................................................................................................10
5.2.1 Admin Side Level 1 DFD’s:..............................................................................................10
5.2.2 User Side Level 1 DFD’s:.................................................................................................11
5.3 Level 2 DFD’s:..........................................................................................................................12
5.3.1 Admin Side Level 2 DFD’s:..............................................................................................12
5.3.2 User Side Level 2 DFD’s:.................................................................................................13
6. Use Case Diagram:..........................................................................................................................14
7. Class Diagram:................................................................................................................................15
8 Activity Diagram:.............................................................................................................................16
8.1 Admin Side Activity Diagram:..................................................................................................16
8.2 User Side Activity Diagram:......................................................................................................17
9. E-R Diagram:..................................................................................................................................18
10. Data Dictionary:............................................................................................................................19
11 Form Design:..................................................................................................................................22
11.1 Development Phase -1:............................................................................................................22
11.2 Development Phase -2:............................................................................................................24
11.3 Development Phase -3:............................................................................................................26
12. What is Testing?............................................................................................................................32
12.1 Why Is Testing Important: -.....................................................................................................32
13. References and Bibliography.........................................................................................................34

1
1. Research:

Research may be very broadly defined as systematic gathering of data and information and
its analysis for advancement of knowledge in any subject. Research attempts to find
answer intellectual and practical questions through application of systematic methods.

1.2 Types of research:

a. Surveys:

Surveys involve collecting information, usually from fairly large groups of people, by
means of questionnaires but other techniques such as interviews or telephoning may
also be used. There are different types of survey.
 
b. Case Studies:

Case studies usually involve the detailed study of a particular case (a person or small
group). Various methods of data collection and analysis are used but this typically
includes observation and interviews and may involve consulting other people and
personal or public records.

c. Experiment:

People who take part in research involving experiments might be asked to complete
various tests to measure their cognitive abilities (e.g., word recall, attention,
concentration, reasoning ability etc.) usually verbally, on paper or by computer.

d. Interviews:

Interviews are usually carried out in person i.e., face-to-face but can also be
administered by telephone or using more advance computer technology such as Skype.
Sometimes they are held in the interviewee’s home, sometimes at a more neutral place.

1
2. Feasibility Study:

Feasibility is the measure of how beneficial or practical the development of information

system will be to an organization. Feasibility study is a process to check possibilities of
system development. It is a method to check various different requirements and availability
of financial & technical resources There are three aspects in the feasibility study portion of
the preliminary investigation.

1) Technical Feasibility

2) Economical Feasibility

3) Operational Feasibility.

2.1 Technical Feasibility:

Evaluating the technical feasibility is the trickiest part of a feasibility study. This is
because, .at this point in time, not too many detailed designs of the system, making it
difficult to access issues like performance, costs on (on account of the kind of technology
to be deployed) etc. A number of issues have to be considered while doing a technical
analysis. Understand the different technologies involved in the proposed system before
commencing the project we have to be very clear about what are the technologies that are
to be required for the development of the new system. Find out whether the organization
currently possesses the required technologies. Is the required technology available with
the organization.
Frontend: HTML, CSS, PHP, JavaScript.
Backend: MySQL

2.2 Economical Feasibility:

Economic feasibility attempts 2 weigh the costs of developing and implementing a new
system, against the benefits that would accrue from having the new system in place. This
feasibility study gives the top management the economic justification for the new system.
A simple economic analysis which gives the actual comparison of costs and benefits are
much more meaningful in this case. In addition, this proves to be a useful point of
reference to compare actual costs as the project progresses. There could be various types
of intangible benefits on account of automation. These could include increased customer
satisfaction, improvement in product quality better decision-making timeliness of
information, expediting activities, improved accuracy of operations, better documentation
and record keeping, faster retrieval of information, better employee morale.

1
2.3 Operation Feasibility:

Proposed project is beneficial only if it can be turned into information systems that will
meet the organizations operating requirements. Simply stated, this test of feasibility asks
if the system will work when it is developed and installed. Are there major barriers to
Implementation? Here are questions that will help test the operational feasibility of a
project:

Is there sufficient support for the project from management from users? If the current
system is well liked and used to the extent that persons will not be able to see reasons for
change, there may be resistance. Are the current business methods acceptable to the
user? If they are not, Users may welcome a change that will bring about a more
operational and useful systems.

Has the user been involved in the planning and development of the project? Early
involvement reduces the chances of resistance to the system and in general and increases
the likelihood of successful project.

1
3. System Requirements Specification:

3.1. Introduction of SRS:

A software requirements specification (SRS) is a description of a software system to be

developed. It lays out functional and non-functional requirements, and may include a set
of use cases that describe user interactions that the software must provide.

Need of SRS?

In order to fully understand one’s project, it is very important that they come up with a
SRS listing out their requirements, how are they going to meet it and how will they
complete the project. It helps the team to save upon their time as they are able to
comprehend how are going to go about the project. Doing this also enables the team to
find out about the limitations and risks early on.

3.2 Abstract:

Online Crime Reporting System is an internet-based Project developed using PHP and
MySQL. The aim of Online Crime Reporting System will be to create a web-based
program using which people are able to report crime online. It gives the facility of
uploading videos or images of crime scenes to ensure that authorities can take action
immediately.

The idea behind the project title is to develop an online crime reporting system which is
easily accessible to the public. The police department (high authorities) and the
administrative department.

This system registers the complaints from people through online. It will also helpful to
police department in catching criminals. Person can give any complaint any time.
This website helps the public to report about the crime to the police without any fear in
correct time. By this website public can also report for missing things and can inform
police if have information related to wanted person and many more features.

3.3 System Users:

 Admin
 Police station
 Citizen (user)
 Police officer

1
3.4 Modules:

 Admin
 Police officer
 Citizen

3.5 Module Description:

3.5.1 admin module:

 Add/Update/Display/Delete Police Officer (Police Station)

 Add/Update/Display/Delete Citizen (User)
 Update/Display/Delete Complaint
 View/Delete Complaints Status
 View/Delete Emergency Complaint
 View Query
 View Feedback

3.5.2 citizen:

 Register
 Login
 Add Complaint
 View Complaint Status
 Add feedback
 Public (without create account)
 Add Emergency Complaint
 Track Emergency Complaint Status

3.6 Hardware Requirements:

 Processor: intel Pentium 4 or more

 Ram: 1GB or more
 Hard disk: 10GB and more

3.7 Software Requirements:

 OPERATING: MS windows OS
 DATA BASE: MYSQL and
 Tools: PHP

1
3.7. Timeline Chat:

Development Durati
phase on
0to1 11to20 21to30 31to40 41to50 51to9 N
0 days days days days 0 (days)
days days

Requirement 06
Gathering

Analysis 09

Design 09

Development 10
Phase 1

Development 11
Phase 2

Development 12
Phase 3

Documentation 11

Total time 68
(Days)

1
4. Technology Description:

1. PHP:

Hypertext Pre-processor (PHP) is a general-purpose scripting language especially

suited to web development. It was originally created by Danish-
Canadian programmer Ramus in 1994. The PHP reference implementation is now
produced by The PHP Group. PHP originally stood for Personal Home Page. but it now
stands for the recursive initialise PHP: Hypertext Pre-processor.

2. HTML:

Hypertext Mark-up Language (HTML) is the standard mark-up language for

documents designed to be displayed in a web browser. It can be assisted by technologies
such as Cascading Style Sheets (CSS) and scripting languages such as JavaScript. Web
browsers receive HTML documents from a web server or from local storage
and render the documents into multimedia web pages. HTML describes the structure of
a web page semantically and originally included cues for the appearance of the
document.

3. CSS:

Cascading Style Sheets (CSS) is a style sheet language used for describing

the presentation of a document written in a mark-up language such as HTML. CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript. CSS
is designed to enable the separation of presentation and content,
including layout, colours, and fonts. This separation can improve content accessibility,
provide more flexibility and control in the specification of presentation characteristics,
enable multiple web pages to share formatting by specifying the relevant CSS in a
separate .CSS file which reduces complexity and repetition in the structural content as
well as enabling the .CSS file to be cached to improve the page load speed between the
pages that share the file and its formatting.

4.1 Limitations of system:

 We need internet connection for control the system every time.

 This application does not allow users to recover their passwords.
 In our application live chat app functionality is not available.

4.2 Future Enhancement:

 In future system will provide mail facility to members, members can send mail to other
stations.
 In future, system will provide online live chat application.

1
5. Data Flow Diagram:

5.1 Context Level DFD’s:

Figure 1: context level DFD’s

1
5.2 Level 1 DFD’s:

5.2.1 Admin Side Level 1 DFD’s:

Figure 2: admin side level 1 DFD’s

1
5.2.2 User Side Level 1 DFD’s:

Figure 3: user side level 1 DFD’s

1
5.3 Level 2 DFD’s:

5.3.1 Admin Side Level 2 DFD’s:

Figure 4: admin side level 2 DFD’s

5.3.2 User Side Level 2 DFD’s:

1
Figure 5: user side level 2 DFD’s

1
6. Use Case Diagram:

Figure 6: Use Case Diagram

1
7. Class Diagram:

Figure 7: Class Diagram

1
8 Activity Diagram:

8.1 Admin Side Activity Diagram:

Figure 8: Admin Side Activity Diagram

1
8.2 User Side Activity Diagram:

Figure 9: Admin Side Activity Diagram

1
9. E-R Diagram:

Figure 9: Admin Side Activity Diagram

1
10. Data Dictionary:

Table Name: - Complaints

Table Description: - In this table store the complaints information.

Sr.n Field name Type Siz Description constrain example

o e t
1 Id Int 11 Id Auto 1
2 Complainant_i Int 30 Complainant_i PK 1
d d
3 Message Text Message Not null Abcde
4 Address Text Address Not null c-201
5 Date_created Datetim Date_created Not null 19/12/201
e 9
6 Status tinyint 1 Status Not null 1=pending
2=receive
3=action
made

Table Name: - Complainants

Table Description: - In this table store the user information.

Sr.no Field Type Size Description constraint example

name
1 Id Int 30 Id Auto 1
2 Name Varchar 200 Name Not null Khushi
3 Address Text Address Not null c-201
4 Contact Varchar 100 Contact Not null 1234567890
5 status Tinyint 1 status Not null 0=unverified
1=verified
6 Email Varchar 200 Email Not null abc@gmail.com
7 passwor text password Not null ******
d

1
Table Name: - Complaint_action

Table Description: - In this table store the complaints action information.

Sr.n Field name Type Siz Description constrain example

o e t
1 Id Int 30 Id Auto 1
2 Complaint_id Int 30 Complaint_id PK 1
3 Responder_id Int 30 Responder_id PK 1
4 Dispatched_b Int 30 Dispatched_b Not null 1
y y
5 Status Tinyint 1 Status Not null 0=pend
1=com
6 Remarks Text Remarks Not null Station 1
7 Date_created datetim Date_created Not null 19/12/20
e 0

Table Name: - responders_team

Table Description: - In this table store the responders team information.

Sr.no Field name Type Size Description constrain example

t
1 Id Int 30 Id Auto 1
2 Station_id Int 30 Station_id PK 1
3 Name Varchar 200 Name Not null Khushi
4 availability tinyint 4 availability Not null 1

1
Table Name: - Stations

Table Description: - In this table store the police station information.

Sr.n Field Name Type Siz Descriptio Constrain Example

o e n t
1 id int 30 id Auto 1
2 Name Varchar 200 Name Not Null Khushi
3 Address Text Address Not Null c-201
Vadodar
a
4 Date_create Datetim Date Not Null 1/2/2021
d e

Table Name: - Users

Table Description: - In this table store the admin and staff information.

Sr.no Field Type Size Description Constraint Example

Name
1 Id Int 30 Id Auto 1
2 Name Text Name Not Null Khushi
3 Username Varchar 200 Username Not Null Admin1
4 Password text Password Not Null *********
5 type Tiny int 1 type Not Null Admin,
staff

1
11 Form Design:

11.1 Development Phase -1:

User Side Home Page: This is a user side home page user can see the all
information About the system. And user can see the
home page, complaints Status and login the system.

Screenshot:1 Home page of user side police complaint reporting.

1
Admin Side Home Page: This is a admin side home page. admin can see the all
Information about the user and system setting.
Admin can see The all complaints.

Screenshot:2 Home page of Admin side police complaint reporting.

1
11.2 Development Phase -2:

Admin Side Login page: This is an admin side login page. Only admin can
Login the admin penal. Admin can login valid
Username and password.

Screenshot:3 Login page of Admin side.

1
User Side Login Page: This is a user side login page. User can Login the users
penal. User can login the valid email id and password.
Then after user can add the complaints.

Screenshot:4 Login page of User Side.

1
11.3 Development Phase -3:

11.3.1 User Side:

Account: user create a new account.

1
 Screenshot:5 create account of User Side.

Complaint status: user can see the own all complaint status.

Screenshot:7 complaint status of user Side.

1
Report: user can add the complaint report and see the all complaint.

Screenshot:8 report page of user Side.

1
11.3.2 admin Side:

Complaint page: admin can see the all complaints. And update the
Complaint’s status.

Screenshot:9 complaint page of admin Side.

1
Police station Page: admin can add the police station and delete the police
Station. And update the police station.

Screenshot:10 add station page of admin Side.

1
User information page: admin can see the all information about the use.
And update the users.

Screenshot:11 user information page of admin Side.

1
12. What is Testing?

Software Testing is a method to check whether the actual software product matches
expected requirements and to ensure that software product is Defect free. It involves
execution of software/system components using manual or automated tools to evaluate
one or more properties of interest. The purpose of software testing is to identify errors,
gaps or missing requirements in contrast to actual requirements.

Some prefer saying Software testing as a White box and Black box testing. In simple
terms, Software Testing means the Verification of Application Under Test (AUT). This
tutorial introduces testing software to the audience and justifies its importance.

12.1 Why Is Testing Important: -

Software Testing is Important because if there are any bugs or errors in the software, it
can be identified early and can be solved before delivery of the software product.
Properly tested software product ensures reliability, security and high performance
which further results in time saving, cost effectiveness and customer satisfaction.

Testing is important because software bugs could be expensive or even dangerous.

Software bugs can potentially cause monetary and human loss, and history is full of
such examples.

In April 2015, Bloomberg terminal in London crashed due to software glitch affected
more than 300,000 traders on financial markets. It forced the government to postpone a
3bn pound debt sale.

Nissan cars recalled over 1 million cars from the market due to software failure in the
airbag sensory detectors. There has been reported two accident due to this software
failure.

1
 Starbucks was forced to close about 60 percent of stores in the U.S and Canada due to
software failure in its POS system. At one point, the store served coffee for free as they
were unable to process the transaction.

Some of Amazon's third-party retailers saw their product price is reduced to 1p due to a
software glitch. They were left with heavy losses.

Vulnerability in Windows 10. This bug enables users to escape from security sandboxes
through a flaw in the win32k system.

In 2015 fighter plane F-35 fell victim to a software bug, making it unable to detect
targets correctly.

China Airlines Airbus A300 crashed due to a software bug on April 26, 1994, killing
264 innocents live

In 1985, Canada's Therac-25 radiation therapy machine malfunctioned due to software

bug and delivered lethal radiation doses to patients, leaving 3 people dead and critically
injuring 3 others.

In April of 1999, a software bug caused the failure of a $1.2 billion military satellite
launch, the costliest accident in history

In May of 1996, a software bug caused the bank accounts of 823 customers of a major
U.S. bank to be credited with 920 million US dollars.

12.2 Types of testing: -

Typically Testing is classified into three categories.

1. Functional Testing

2. Non-Functional Testing or Performance Testing

3. Maintenance (Regression and Maintenance)

1
13. References and Bibliography

Books: -
1. The Joy of PHP Programming: A Beginner’s Guide to Programming Interactive
Web Applications with PHP and MySQL

 Author – Alan Forbes

 Latest Edition – Fifth Edition
 Publisher – Plum Island

2. PHP: A Beginner’s Guide

 Author – Vikram Vaswani

 Latest Edition – First Edition
 Publisher – McGraw-Hill Education

Website:
 https://youtu.be/aIsu9SPcGbU
 https://www.w3schools.com

1
1