Online Crime Reporting

ONLINE CRIME REPORTING
A PROJECT REPORT Submitted by
NISHIT TRIVEDI 090570107019

In fulfilment for the award of the degree of
BACHELOR OF ENGINEERING
in
Computer Engineering
Faculty of Engineering Marwadi Education Foundations Group of Institutions, Rajkot Gujarat Technological University, Ahmedabad
May, 2013
DECLARATION
I hereby declare that the project entitled Online Crime Reporting submitted in partial fulfilment for the degree of Bachelor of Engineering in Computer Engineering to Gujarat Technological University, Ahmedabad, is a bonafide record of the project work carried out at Faculty of Engineering, Marwadi Education Foundations Group of Institutions under the supervision of Prof. Nishant Goswami and that no part of the IDP has been presented earlier for any degree, diploma, associate ship, fellowship or other similar title of any other university or institution.
Nishit Trivedi 090570107019
Faculty of Engineering Marwadi Education Foundations Group of Institutions, Rajkot Computer Engineering Department May, 2013
CERTIFICATE
This is to certify that the project entitled Online Crime Reporting has been carried out by Nishit Trivedi 090570107019 under my guidance in fulfilment of the degree of Bachelor of Engineering in Computer Engineering of Gujarat Technological University, Ahmedabad during the academic year 2012-13.
Date: ____________________
Internal Guide
Head of the Department
Prof. Nishant Goswami Assistant Professor
Prof.Vipul Vekariya Head of Department
TO WHOMSOEVER IT MAY CONCERN

This is to certify that Nishit Trivedi of Faculty of Engineering, Marwadi Education Foundations Group of Institutions has worked on an Industry Defined Project of Tech Securing. The work embodied in this project entitled, Online Crime Reporting has been carried out in fulfilment for the degree of Bachelor of Engineering. He has undergone the project for the required period. During this period we found him sincere, honest and diligent. We wish all success in his future endeavours.
For Tech Securing
Mr. Mitesh Goswami Date:
Acknowledgement
We are extremely grateful to Dr. Y P Costa, Director, MEFGI and Mr. V M Vekariya, Head of Department, Department of Computer Engineering, MEFGI for providing all the required resources for the successful completion of our project. My heartfelt gratitude to my project guide Mr. Nishant Goswami, Assistant Professor and project co-ordinator Mr. Hiren Kotadiya, Assistant Professor for his valuable suggestions and guidance in the preparation of the project report. We will be failing in duty if we do not acknowledge with grateful thanks to the authors of the references and other literatures referred to in this project. I express my thanks to all the Professors and all staff members and friends for all the help and co-ordination extended in bringing out this project report successfully in time. Last but not the least; we are very much thankful to my parents who guided me in every step which we took.
Abstract
TECH SECURING was formed to meet the growing needs of small and medium business. TECH SECURING can provide all the required technology services like web design and deployment, software deployment database development and management, strategic planning and project management, etc. Online Crime Reporting System projects main idea is to implement an automated software application for maintaining the proper common people complaints of different police departments. By using this application people who are afraid or dont have enough time to go police station for complaint about their personal legal issues here they can give their complaint through online to register any type of complaint. First people have to register their personal details along with login details using registration form. Once he/she register in the application, they can post their complaints. This project has 2 modules, 1) Admin 2) User. Here Police department management has the admin rights and all common people use the user function to register their issues. In existing system police department use manual methods for storing data and processing criminal information which is a time taking process. In this system data is maintained in the form of records which will cause chances of losing information. In order to overcome this problem we implement an online application where data is stored in to database and provide more secured and fast processing method. Initially different police stations should register with the application and get unique user id and password. then using station module they can enter entire details in to the system. Admin will look after maintenance of the system and handle technical issues inside application.
Table of Contents
Acknowledgement ............................................................................................................... iv Abstract ................................................................................................................................ v
Introduction ................................................................................................................. 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 Defination ............................................................................................................. 1 Purpose .................................................................................................................. 1 Objective ............................................................................................................... 1 Scope ..................................................................................................................... 1 Frontend and Backend .......................................................................................... 2 Technology and Literature Review........................................................................ 2 Function and main module of new system ............................................................ 3 1.7.1 User Module............................................................................................... 4 1.7.2 Admin Module ........................................................................................... 5 1.7.3 Main Admin Module.................................................................................. 6
Project Management ................................................................................................... 8 2.1 2.2 2.3 2.4 Project Plan ............................................................................................................ 8 Milestone and Deliverables ................................................................................... 9 Roles and Responsibilities ................................................................................... 10 Project Scheduling ............................................................................................... 11
System Requirements Study ..................................................................................... 12 3.1 3.2 3.3 User Characteristics ............................................................................................. 12 Hardware and Software Requirements ................................................................ 12 Constraints ........................................................................................................... 13
System Analysis.......................................................................................................... 14 4.1 4.2 4.3 Study of Current/Existing System ...................................................................... 14 Problem and Weakness of Current System ......................................................... 14 Requirements of New System ............................................................................. 14 4.3.1 User Requirements ................................................................................... 14 4.3.2 System Requirement ................................................................................ 15
4.4 5
Feasibility Study .................................................................................................. 16
System Design ............................................................................................................ 18 5.1 5.2 5.3 5.4 5.5 Design Methodology ........................................................................................... 18 Activity Diagram ................................................................................................. 19 Sequence Diagram ............................................................................................... 22 Class Diagram...................................................................................................... 25 Use Case Diagram ............................................................................................... 26
System Architecture .................................................................................................. 27 6.1 6.2 Types of Architecture .......................................................................................... 27 Description of roles of each tier........................................................................... 27
Implementation .......................................................................................................... 30 7.1 7.2 Security Features ................................................................................................. 30 Coding Standards................................................................................................. 30 7.2.1 Naming Convention ................................................................................. 30 7.2.2 Label and Comments ............................................................................... 31 7.3 Fuctionality .......................................................................................................... 31
Testing ........................................................................................................................ 48 8.1 8.2 Testing Strategy ................................................................................................... 48 Testing Methods .................................................................................................. 49 8.2.1 Teste Cases ............................................................................................... 50 8.2.2 Test Summary .......................................................................................... 53
Limitation and Future Enhancement ...................................................................... 54
10 Conclusion .................................................................................................................. 55 Appendix 1: Data Dictionary ............................................................................................ 56 References........................................................................................................................... 62
List of Tables
Table No Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table Description Unit Test at User Side Unit Test at Admin Side Unit Test at Main Admin Side Integration Test of all three modules Abusing FIR Main-Admin Registration Criminal Registration Form Police Registration Form Missing Person FIR Police-station Registration Form Robbery FIR Registration Form Feedback Form Page No 50 51 52 52 56 56 57 57 58 59 59 60 61
List of Figures
Figure No. Fig. 2(a) Fig. 2(b) Fig. 5(a) Fig. 5(b) Fig. 5(c) Fig. 5(d) Fig. 5(e) Fig. 5(f) Fig. 5(g) Fig. 5(h) Fig. 6(a) Fig. 6(b) Fig. 6(c) Fig. 7(a) Fig. 7(b) Fig. 7(c) Fig. 7(d) Fig. 7(e) Fig. 7(f) Fig. 7(g) Fig. 7(h) Fig. 7(i) Figure Description Waterfall Model Timeline chart Activity Diagram of Admin Module Activity Diagram of Main-Admin Module Activity Diagram of User Module Sequence Diagram of User Module Sequence Diagram of Admin Module Sequence Diagram of Main-Admin Module Class Diagram Use Case Diagram Server Communication Web Tier and J2EE Application Business and EIS Tiers User-Login Page Registration Form for User Forgot Password Page for User Home Page for User AboutUs ContactUs Search Page for User Criminal Search Record Individual Criminal Search Record Page No 8 11 19 20 21 22 23 24 25 26 27 28 29 31 32 33 33 34 35 36 37 37
Fig. 7(j) Fig. 7(k) Fig. 7(l) Fig. 7(m) Fig. 7(n) Fig. 7(o) Fig. 7(p) Fig. 7(q) Fig. 7(r) Fig. 7(s) Fig. 7(t) Fig. 7(u) Fig. 7(v) Fig. 7(w) Fig. 7(x) Fig. 7(y)
Police-station Search Record Individual Police-station Search Record Report FIR Reporting Robbery FIR Success Message Reporting Missing person FIR Reporting abuse person FIR NEWS Page Uttar Pradesh with Crime Status User FeedBack Form Criminal Add Form Search Categories Page On Admin Side Add Police on Main-Admin Side Add Police-Station Page On Main-Admin Side Feedback Record At Main-Admin Side User Profile Page
38 38 39 40 40 41 42 43 44 44 45 45 46 46 47 47
List of Symbols, Abbreviations and Nomenclature

Symbol JSP FIR HTML DHTML XML RAM SQL GUI J2EE TCP/IP Abbreviations Java Server Pages First Information Report Hyper Text Markup Language Dynamic Hyper Text Markup Language Extensible Markup Language Random Access Memory Structured Query Language Graphical User Interface Java 2 Enterprise Edition Transmission Control Protocol/Internet Protocol
Online Crime Reporting
1. Introduction
1.1 Definition
The ONLINE CRIME REPORTING is a web based system to register online Complaint/FIR. In this system there are mainly three modules: 1) User Module, 2) Admin Module, & 3) Main Admin Module.
1.2 Purpose
The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system.
This Document plays a vital role in the software development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
1.3 Objective
The objective of this project is to develop a web-site in which any citizen can report their FIR. If anybody wants to complaint against crimes he/she must do it through the police. The Crime Management and Reporting System make the reporting of crime easier. This project will be also useful for the Police Department. People could only report their FIR/Complaint and knows whether the FIR reported by them has been accepted. People can also see the criminal records. So, that they can see the criminal data also they can use different functionalities of this system like watching different crime videos, using Google map which is provided in this system people can also locate the nearest police station.
1.4 Scope
The main scope of this project is to develop an online crime report and managing system which is easily accessible to the people. This system provides proper security and reduces
1
the manual work. This proposed system tries to eliminate or reduce difficulties up to some extent. This system will help the user to reduce the workload and mental conflict. It helps the user to work user friendly and he can easily do his jobs without time lagging.The advantages are, Ensure data accuracys Proper control of the higher authority Minimize manual data entry Greater efficiency Better service User friendliness and interactive Minimum time required Minimum time needed for the various processing
1.5 Front end and Backend

Front End: ONLINE CRIME REPORTING is developed in NetBeans IDE 6.9.1 with the help of JSP. Back End: The back end database is developed in MySQL 2005 and coding is developed in J2EE.
1.6 Technology and Literature Review

I chose JSP to do this project. And reason behind to choose this technology is given below: JSP technology is the Java platform technology for building applications containing dynamic Web content such as HTML, DHTML and XML. The JSP technology enables the authoring of Web pages that create dynamic content easily but with maximum power and flexibility. The Java Server Pages technology offers a number of advantages: Write Once, Run Anywhere properties: The JSP technology is platform independent, both in its dynamic Web pages, its Web server, and its underlying server components. You can author JSP pages on
2
any platform, run them on any Web server or Web enabled application server, and access them from any Web browser. You can also build the server components on any platform and run them on any server. High quality tool support The Write Once, Run Anywhere properties of JSP allows the user to choose bestof-breed tools. Additionally, an explicit goal of the Java Server Pages design is to enable the creation of high quality portable tools. Reuse of components and tag libraries The Java Server Pages technology emphasizes the use of reusable components such as: JavaBeans components, Enterprise JavaBeans components and tag libraries. These components can be used in interactive tools for component development and page composition. This saves considerable development time while giving the cross-platform power and flexibility of the Java programming language and other scripting languages. Separation of dynamic and static content The Java Server Pages technology enables the separation of static content from dynamic content that is inserted into the static template. This greatly simplifies the creation of content. This separation is supported by beans specifically designed for the interaction with server-side objects. Support for scripting and actions The Java Server Pages technology supports scripting elements as well as actions. Actions permit the encapsulation of useful functionality in a convenient form that can also be manipulated by tools; scripts provide a mechanism to glue together this functionality in a per-page manner.
1.7 Functions and main modules of System

Functions o Login for User, Admin and Main-Admin.
3
o Complaint / FIR registration and management. o Criminal registration and management. o Feedback registration o Map-locator and different crime video management. o Police-station registration and management o Police-officer registration and management In Online Crime Reporting, there are mainly three modules: 1) User Module 2) Admin Module 3) Main-Admin Module 1.7.1 User Module In this module, first of all User will register with proper data (where username and E-mail id must be unique for everyone).Once User registered than he/she can login in this system and register their FIR. If user wants to see the nearest police-station than user can see that using the map-locator which is provide in this system. Also User can see the criminal records. Here User can search the different criminal with their name and also search the police-station using the city name. Here Session is applied on this system. So, once user logout he/she cannot go back, he/she must have to login first. When user logout, cookie was also deleted. Here complete flow of User Module and all the functionalities explain below: Home Login o User Name (if user is already Member) o Password o Forget Password Get an Email User name and original password of the user will be send to his/her respective Email ID New User o First Name o Middle Name
4
o Last Name o Gender o Birthdate o Address o State o City o Phone o Email id o Username o Set Password o Identity Proof(License number/ election card number/ PAN card number) o Unique number FIR o Select FIR type o Write down FIR in this section Search o Using this functionality user can search different criminal by their names and types and also search the nearest police-station according to city. Mapping o Here User can see the Google-map and find the nearest police-station. Crime report generation o User can see the graph of crime v/s years. News Feed o It gives the latest news to user. Videos Contact US About US Profile 1.7.2 Admin Module In this module, first of admin will login with proper email-id and password which is already registered by Main-Admin. Once admin will login, he/she can see all the FIR which is registered by users. Also admin can search particular FIR using different
5
parameters. Admin can add criminal information. Here admin cannot update his/her personal information. Admin can also see the feedback/complaint which is given by users. Here Session is applied on this system. So, once admin logout he/she cannot go back, he/she must have to login first. When admin logout, cookie was also deleted. Here complete flow of admin Module and all the functionalities explain below: Admin Login o Admin Name ( admin is already registered by main-admin) o Password o Forget Password Get an Email Admin Email-id and original password of the admin will be sending to his/her respective Email ID. FIR o Select FIR type o Search FIR using different parameter like name, date, city, etc. Criminal o Using this functionality admin can add criminals and also search them by their names and types. Feedback o Here admin can see all the feedback/complaint which is registered by users. 1.7.3 Main Admin Module In this module, Main admin will assign police-officer to their respective police-station with proper data. Here main-admin will assign police-officer or we can give them to email-id and password and also edit/update their database like if one police-officer will get promotion than his/her post will be updated. So main-admin will update that policeofficers post. Same way main-admin can register different police-station and also if police-station shifted from one place to another than main admin will update the database. Also in this module, session and cookie deleted code is applied. Here complete flow of main-admin Module and all the functionalities explain below: Main-admin Login o Main-admin Name (main-admin is already Member)
6
o Password Add police-officer and police-station o Using this functionality main-admin can add police-station and police-officer. Edit/Update police-officer and police-station o Using this functionality main-admin can edit/update police-station and policeofficer. Feedback o Here admin can see all the feedback/complaint which is registered by users.
2. Project Management
2.1 Project Plan
WATER FALL MODEL was being chosen because all requirements were known beforehand and the objective of our software development is the computerization/ automation of an already existing manual working system.
Fig 2(a) Waterfall Model

8
Reasons to choose waterfall model are: 1) Waterfall model is simple to implement and also the amount of resources required for it are minimal. 2) In this model, output is generated after each stage (as seen before), therefore it has high visibility. The client and project manager gets a feel that there is considerable progress. 3) Project management, both at internal level and client's level, is easy again because of visible outputs after each phase. Deadlines can be set for the completion of each phase and evaluation can be done from time to time, to check if project is going as per milestones. 4) This methodology is significantly better than the haphazard approach to develop software. It provides a template into which methods of analysis, design, coding, testing and maintenance can be placed. 5) This methodology is preferred in projects where quality is more important as compared to schedule or cost.
2.2 Milestones and Deliverables Milestones

o Analysis & requirement gathering. o Learning all the stuff which required to completing this project. o Designing UI. o Designing Database. o Coding. o Testing.
Deliverables
o Software Requirement Specification. The SRS document states in precise in explicit language those functions and capabilities a software system must provide. Also states any required constraints by which the system must abide. It contains all the necessary
functional and non-functional requirements of the application. SRS accomplishes four major goals: 1. It provides feedback to the customers 2. It decomposes the problems into different component parts 3. It serves as an input to the design specification. 4. It serves as a product validation check. 5. The SRS document contains all diagrams (use cases, sequence, activity and class), functional and non-functional requirements for the website. o Software Project Management Plan. Software project management is the art and science of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, monitored and controlled. Listing the details of the major functions, project resources, staff representations and scheduling. o Analysis and design of the Website. Containing the design issues and the UI diagrams. The design issues for any web application are: 1. Page load efficiency. 2. Simplicity. 3. Use the space wisely. o Project Report. A full project report, enlightening about the details of the project. o Working Website. A fully functional website at the end of the year.
2.3 Roles and Responsibilities

Here in this project, I am only one person to do all the roles. So like requirement gathering, design, coding, implementation, testing, etc. roles done by me.
10
2.4 Project Scheduling
Fig 2(b) Timeline chart
11
3. System Requirements Study

3.1 User Characteristics
User should be familiar with following: Working on a website Using a browser like navigating through the links Searching the required information User should know that how to search any police-station and criminal. User should know that how to register any FIR. Admin should be familiar with following: Working on a website Using a browser like navigating through the links Searching the required information Admin should know that how to search particular stuff. Admin should know that how to register any criminal.
3.2 Hardware & Software Requirements

At User Side: o Minimum RAM: 512 MB. Recommended RAM: 1 GB DDR2 o Internet: 2G Plan or above, bandwidth with at least 256 kbps. o Minimum Processor: 1.80 GHz P IV. Recommended Processor: 2.10 GHz Dual Core. At Admin / Main-Admin Side: o Minimum RAM: 2 GB. Recommended RAM: 4 GB DDR3 o Internet: 2G Plan or above, bandwidth with at least 1 mbps or above. o Minimum Processor: 2.20 GHz P IV. Recommended Processor: 3.10 GHz Core2Duo.
12
3.3 Constraints
My SQL Server For efficient function of the system; minimum 4 GB(DDR3) of RAM is required at Server Side The application is not multi-lingual. Only one administrative control is given; not distributed For full working Online Crime reporting requires Internet and Intranet Connection.
13
4. System Analysis
4.1 Study of Current/Existing System
In the existing crime management system, most of the operations are done manually like sending complaints, taking actions against crimes, viewing status etc. So with the existing system if anybody wants to complaint against crimes he must do it through the police. Also in general people in India are afraid to give a complaint in police station because they are filled with a false fear about the police department. If we are doing the system manually, so many minor errors will occur. Error detection in the previous entries made and data cross verification is another important function. These are done manually, and it would take time. The existing system has more workload for the authorized person.
4.2 Problem and Weaknesses of Current System

Lack of security for data. More man power. Time consuming. Consumes large volume of pare work. Needs manual calculations. Not very user friendly. Sometimes the complaints may be ignored by the police. Damage of machines due to lack of attention. No direct role for the higher officials.
4.3 Requirements of New System

4.3.1 User Requirements The following should be taken care of while designing the user interfaces The design or layout of every form will be very clear and very interactive to the user.
14
When the user open the software the welcome window will appear. In the login window the user can easily entered the desired password and login name. Then it will give the successfully login message. From each and every window the user can easily go to any desired window that is there is will be a absolute and relative linking. There will be a proper collection of GUI interface, which will provide better look and feel. In the screen layout the background color is very light and the graphics and font style will be in proper manner and well organized. In each and every window there will be alert, confirm etc message box for displaying message. The user will be able to search any data from the record by using proper guideline shown in the window & Linux. User can easily save its data in to the database and update as their need. This software will be easily understandable and operable by the user.
4.3.2 System Requirements 4.3.2.1 Hardware Requirements Processor RAM Hard Disk FDD Keyboard Mouse Monitor CD Drive : : : : : : : : Pentium 4 (P4) / AMD Athlon 512 MB 20 GB 1.44 MB 108 Keys 3 Button scroll VGA/SVGA 14 inch 52 X
4.3.2.2 Software Requirements OS Language Front End : : : Any java 2(EJB2.0, JDBC, JSP, Servlet, Java Mail) HTML, JavaScript
15
Back End Platform Web Server Browser
: : : :
MySQL J2EE Tomcat 5.0 Any
4.3.2.3 Communications Interfaces Following communication interfaces are used in system and data is actually transmitted through physical layer of OSI Layers. IPv4 will be used for connection. Web Browser Protocol : : Any HTTP supported web browser like IE, Firefox, etc. HTTP and TCP/IP
4.4 Feasibility Study

Feasibility study is made to see if the project on completion will serve the purpose of the organization for the amount of work, effort and the time that spend on it. Feasibility study lets the developer foresee the future of the project and the usefulness. A feasibility study of a system proposal is according to its workability, which is the impact on the organization, ability to meet their user needs and effective use of resources. The document provide the feasibility of the project that is being designed and lists various areas that were considered very carefully during The feasibility study of this project such as technical, economic and operational feasibilities. The following are its features: A. TECHNICAL FEASIBILITY The system must be evaluated from the technical point of view first. The assessment of this feasibility must be based on an outline design of the system requirement in the terms of input, output, programs and procedures. Having identified an outline system, the investigation must go on to suggest the type of equipment, required method developing the system, of running the system once it has been designed. Technical issues raised during the investigation are: Does the existing technology sufficient for the suggested one? Can the system expand if developed?
16
The project should be developed such that the necessary functions and performance are achieved within the constraints. The project is developed within latest technology. Through the technology may become obsolete after some period of time, due to the fact that never version of same software supports older versions, the system may still be used. So there are minimal constraints involved with this project. The system has been developed using Java the project is technically feasible for development. B. ECONOMIC FEASIBILITY The developing system must be justified by cost and benefit. Criteria to ensure that effort is concentrated on project, which will give best, return at the earliest. One of the factors, which affect the development of a new system, is the cost it would require. The following are some of the important financial questions asked during preliminary investigation: The costs conduct a full system investigation. The cost of the hardware and software. The benefits in the form of reduced costs or fewer costly errors. Since the system is developed as part of project work, there is no manual cost to spend for the proposed system. Also all the resources are already available, it give an indication of the system is economically possible for development. C. BEHAVIORAL FEASIBILITY This includes the following questions: Is there sufficient support for the users? Will the proposed system cause harm?
The project would be beneficial because it satisfies the objectives when developed and installed. All behavioural aspects are considered carefully and conclude that the project is behaviourally feasible.
17
5. System Design
5.1 Design Methodology
Here in this project, I used WATER FALL MODEL to complete this project. The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/ Implementation, and Maintenance. It states that the phases are organized in a linear manner. There are variations of the waterfall model depending on the nature of activities and the flow of control between them. In a typical model, a project begins with feasibility analysis. On successfully demonstrating the feasibility of a project, the requirement analysis and project planning begins. The design starts after the requirements analysis is complete, and coding begins after the design is complete. Once the programming is completed, the code is installed. After this, the regular operation and maintenance of the system takes place. With the waterfall model, the sequence of activities performed in a software development project is: requirement analysis, project planning, system design, detailed design, coding and unit testing, system integration and testing. There are two basic assumptions for justifying the linear ordering of phases in the manner proposed by the waterfall mode. The various phases in this model are: Conception Initiation Analysis Design Construction Testing Deployment
18
5.2 Activity Diagram

5.2.1 Activity diagram of Admin
Admin
Login
Select FIR type

Search Police-Station's details Search Criminal's details
Add Criminal View details
Search Police-Officer's details
Do process
Save View details
Logout
Fig 5(a) Activity diagram of Admin module
19
5.2.2 Activity diagram of Main-Admin
Main-Admin
Login
Add / Edit PoliceOfficer's details
Add / Edit Policestation's details
Save
Logout
Fig 5(b) Activity diagram of Main-Admin module

20
5.2.3 Activity diagram of User
User
Login
Select FIR type
Show Map
Show / Edit Profile
Search Police-Station's details
Search Criminal's details
Give details Show Graph Watch Videos
Save View details
Logout
Fig 5(c) Activity diagram of User module
21
5.3 Sequence Diagram

5.3.1 Sequence diagram of User
User Login Login successful
Register complaint
System
Police Officer Verify Response
Database
complaint stored Response
gives unique ID
gives approx. time duration
Search Criminal Response

Search Policestation Response Watch videos / Maps
Request Response Request Response Request Response
Response Feedback Response Logout

Logout successful Feedback stored
Response
Fig 5(d) Sequence diagram of User module
22
5.3.2 Sequence diagram of Admin
Police Officer Login Login successful Select FIR type Show all FIR
Search Individual FIR Display FIR details
System Verify Response Request Response Request Response
Database
Add Criminal
Criminal's detail stored successfully
Search Police/ Police-station Show detail
Request Response
Request Response
Logout
Logout successful
Fig 5(e) Sequence diagram of Admin module
23
5.3.2 Sequence diagram of Main-Admin
Main-Admin Login Login successful

Add/Edit Police-officer's details Details stored successfully Add/Edit Police-station's details Details stored successfully
System Verify Response
Database
detail's stored Response
Detail stored Response
Show all feedback Logout

Logout successful
Request Response
Fig 5(f) Sequence diagram of Main-Admin module
24
5.4 Class Diagram

User
First Name Middle Name Last Name Gender Birth Date Address State City Phone E-mail Id User Name Password Identity Proof Unique Number
Register FIR Register Feedback Update Profile Show Video See map
1 1 1 *
Police-officer(admin) Main-admin
1 * *
Admin name Password
Admin name Password

Add Police Details Edit Police Details Add Police-station Details Edit Police-Station Details See Feedback
*
FeedBack
User Id Subject Description
Add Criminal Search FIR Search Police-station
Police Station
Police-station Id Center code Name State city Phone No.
* *
Abusing FIR
*
Robbery FIR
AbuseId Report's First name Report's Phone No. Abuse First Name Abuse Last Name Address State City Religion Abused by Reason
Missing FIR
RobberyId Date Place Suspact Robbed things
MissingId Missing Person's Details Reporter's First Name Reporter's Phone No
Fig 5(g) Class Diagram
25
5.5 Use Case Diagram
Login
Registration
Register FIR / Feedback
View Map / Video
User
View Criminal Detail
View FIR
Search Police Station
Policeofficer (admin)
Add criminal
Add / Edit PoliceOfficer
Main Admin
Add / Edit PoliceStation
Search PoliceOfficer
FeedBack
Logout
Fig 5(h) Use Case Diagram

26
6. System Architecture
6.1 Types of Architecture
There are mainly three types of architecture which are mostly used at present. 1) Two Tier architecture 2) Three Tier architecture 3) Four Tier architecture
6.2 Description of roles of each tier

Here in this system, I used three tier architecture. The client communicates with the business tier running on the J2EE server either directly or, as in the case of a client running in a browser, by going through JSP pages or servlets running in the Web tier. J2EE application uses a thin browser-based client or thick application client. In deciding which one to use, you should be aware of the trade-offs between keeping functionality on the client and close to the user (thick client) and off-loading as much functionality as possible to the server (thin client). The more functionality you off-load to the server, the easier it is to distribute, deploy, and manage the application; however, keeping more functionality on the client can make for a better perceived user experience.
Fig 6(a) Server Communications
27
Web Components J2EE Web components can be either servlets or JSP pages. Servlets are Java programming language classes that dynamically process requests and construct responses. JSP pages are text-based documents that execute as servlets but allow a more natural approach to creating static content. Static HTML pages and applets are bundled with Web components during application assembly, but are not considered Web components by the J2EE specification. Server-side utility classes can also be bundled with Web components and, like HTML pages, are not considered Web components. Like the client tier and as shown in Fig 6(b), the Web tier might include a JavaBeans component to manage the user input and send that input to enterprise beans running in the business tier for processing.
Fig 6(b) Web Tier and J2EE Application Business Components Business code, which is logic that solves or meets the needs of a particular business domain such as banking, retail, or finance, is handled by enterprise beans running in the business tier. An enterprise bean also retrieves data from storage, processes it (if necessary), and sends it back to the client program.
28
There are three kinds of enterprise beans: session beans, entity beans, and messagedriven beans. A session bean represents a transient conversation with a client. When the client finishes executing, the session bean and its data are gone. In contrast, an entity bean represents persistent data stored in one row of a database table. If the client terminates or if the server shuts down, the underlying services ensure that the entity bean data is saved. A message-driven bean combines features of a session bean and a Java Message Service (JMS) message listener, allowing a business component to receive JMS messages asynchronously. This tutorial describes entity beans and session beans.
Fig 6(c) Business and EIS Tiers
Enterprise Information System Tier The enterprise information system tier handles enterprise information system software and includes enterprise infrastructure systems such as enterprise resource planning (ERP), mainframe transaction processing, database systems, and other legacy information systems. J2EE application components might need access to enterprise information systems for database connectivity.
29
7. Implementation
7.1 Security Features
As the system will run on browser, the following security requirement will be fulfilling. The system will use session Identifier to identify the user. The system will maintain the cookie on client side. Session will be maintain in such a way that user cannot log-in for same account in different browser at same time. The secure connection will be used to provide the security. Cookie will not contain any information like user password. Cookie will also not contain any confidential data on client side. Web browser will never display the user password. The system front end will access by the general user while the back end will be access by the administration only. For user security, if user forgot password than original password will be sent to the users email-id with username.
7.2 Coding Standards

The purpose of code is to facilitate the identification, retrieval of the items and information. A code is an oriented collection of symbols design to provide unique identification of an entry or attribute. Code is built with manually exclusive features. Codes in all cases specify object which are physical or on performance characteristics. They are used to give optimal distraction and other information. Codes are used for identifying, accessing, storing and matching records. The codes insure that only one value of the code with a single meaning is correctly applied to give entity or attribute as described in various ways. Code can also be design in a manner easily understood and applied by the user. This coding standard includes naming conversions of variables, constants and objects, standardized formats or labelling and commenting code, spacing, formatting and indenting. 7.2.1 Naming Convention Classes names and interface names are meaning full so anyone can easily understand this. The function names will start with small letters.
30
7.2.2 Labels and Comments Sufficient labels and comments are included in the description of it for the benefits if the developer and other programmers who might examine or modified it later.
7.3 Functionalities
Fig 7(a) User-Login Page
31
Fig 7(b) Registration Form for User
32
Fig 7(c) Forgot Password Page for User
Fig 7(d) Home Page of User

33
Fig 7(e) AboutUs
34
Fig 7(f) ContactUs
35
Fig 7(g) Search Page for User
36
Fig 7(h) Criminal Search Record
Fig 7(i) Individual Criminal Search Record
37
Fig 7(j) Police-station Search Record
Fig 7(k) Individual Police-station Search Record
38
Fig 7(l) Report FIR

39
Fig 7(m) Reporting Robbery FIR
Fig 7(n) Success Message

40
Fig 7(o) Reporting Missing person FIR
41
Fig 7(p) Reporting abuse person FIR
42
Fig 7(q) News Page
43
Fig 7(r) Uttar Pradesh Map with Crime Status
Fig 7(s) User FeedBack Form

44
Fig 7(t) Criminal Add Form
Fig 7(u) Search Categories Page On Admin Side

45
Fig 7(v) Add Police Page On Main-Admin Side
Fig 7(w) Add Police-Station Page On Main-Admin Side
46
Fig 7(y) FeedBack Record At Main-Admin Side
Fig 7(y) User Profile Page
47
8. Testing
Testing is the process of executing the program to find if there are any errors. It is the final verification and validation activity .In testing phase we have tried to affirm the quality of the product. We have also tried to eliminate errors in the previous stages.
8.1 Testing Strategy

Unit Testing Unit test comprises of a set tests performed by an individual program prior to the integration of the unit into large system. A program unit is usually the smallest free functioning part of the whole system. Module unit testing should be as exhaustive as possible to ensure that each representation handled by each module has been tested. All the units that makeup the system must be tested independently to ensure that they work as required. During unit testing some errors were raised and all of them were rectified and handled well. The result was quiet satisfactory and it worked well. Integration Testing Integration testing is a system technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested modules and build a program structure that has been dictated by design. Bottom-up integration is the traditional strategy used to integrate the components of a software system into functioning whole. Bottom-up integration consists of unit test followed by testing of the entire system. A sub-system consists of several modules that communicated with other defined interface. The system was done the integration testing. All the modules were tested for their compatibility with other modules .They test was almost successful. All the modules coexisted very well, with almost no bugs. All the modules were encapsulated very well so as to not hamper the execution of other modules.
48
Validation Testing After validation testing, software is completely assembled as a package, interfacing errors that have been uncovered and corrected and the final series of software test; the validation test begins. Steps taken during software design and testing can greatly improve the probability of successful integration in the larger system. System testing is actually a series of different tests whose primary purpose is to fully exercise the compute based system.
Recovery Testing It is a system that forces the software to fail in a variety of ways and verifies that the recovery is properly performed.
Security Testing It attempts to verify that protection mechanisms built into a system will in fact protect it from improper penetration. The systems security must of course be tested from in vulnerability form frontal attack.
Black Box Testing Black box testing is done to find out the following information as shown in below: o o o o o Incorrect or missing functions. Interface errors. Errors or database access. Performance error. Termination error.
The mentioned testing is carried out successfully for this application according to the users requirement specification. Test Data Output After preparing test data, the system under study is tested using the test data. While testing the system using test data, errors are again uncovered and corrected by using above testing and corrections are also noted for future use.
49
8.2 Testing Methods

I used two types of testing methods: 1) Unit testing & 2) Integration Testing. 8.2.1.1 Unit Testing User Module Table 1: Unit test at User side No 1 Unit Registration Input Expected Output Give all the Check with details database for duplication Obtained Output Details inserted Status Remedies
Login
Robbery FIR Missing FIR
User Name Check with and database for Password their relevance and redirect to the home page. Date, Place, Insert into robed thing, database suspect Missing Inserted into persons database details, reporters details Abused person details, reason Feedback persons details, subject, description Inserted database
Database is verified and application redirected to admin home page Data inserted Success into database
Success Username, Email-id, UniqueNo must be UNIQUE. Success
Abusing FIR
Data inserted Success Reporters into database Phone number must be on working mode into Data inserted Success into database
Feedback
Inserted database
into Data inserted Success Person into database name is compulsory
50
Admin Module Table 2: Unit test at Admin side
No
Unit
Input
Expected Output Inserted into database
Obtained Output Data inserted into database
Status
Remedies
Add Criminal
Name, Type, City, State, Nationality
Success Criminal name and type is compulsory
Show different FIR reports
Select FIR type
FIR record will FIR record show showed.
Success
Search FIR
Enter value
Show
Particular FIR showed.
Success Entered value must be there in database.
according to particular FIR different search according to search parameter
51
Main-Admin Module Table 3: Unit test at Main-Admin side
No 1
Unit Add Policeofficer
Input
Edit Policeofficer
Add Policestation
Edit Policestation
Show feedback
Expected Obtained Output Output Full name, Insert into Data inserted post, state, database into database city, phone no, email-id Select Update Data updated police-id database into database and change details Name, Insert into Data inserted center code, database into database state, city, phone, address Select Update Data updated policedatabase into database station id and change details Select Feedback table Feedback feedback show table showed field
Status Success
Remedies
Success Police-id must be there into database Success
Success Policestation id must be there into database Success
8.2.1.2 Integration Testing Table 4: Integration test of all three modules No 1 2 Unit User Module Admin Module Input Expected Output Insert FIR Obtained Output FIR inserted Status Remedies
MainAdmin Module
Register Success FIR Select FIR FIR record FIR record Success type or add show or showed or criminal criminal insert criminal details inserted Add/ edit Insert/update Database Success police or database inserted/ policeupdated station
52
8.2.2 Test Summary

Developer will test all the above tests after every 7-10 days at starting of this system. Here after 1 year developer will test the entire above test once in a month because after 1 year system will stable and easily handle and more error free.
53
9. Limitation and Future Enhancement

Limitation
o The size of the database increases day-by-day, increasing the load on the database. At present there is no back up and data maintenance activity. o Training for simple computer operations is necessary for the users working on the system.
Future Enhancement
Nothing can be ended in a single step. It is the fact that nothing is permanent in this world. So this project also has some future enhancements in the evergreen and booming IT industry. Change is inevitable. The project entitled Online Crime Reporting was successfully designed developed and tested. The system and the architecture is a compatible one, so addition of new modules can be done without much difficulty. Since this module has its unique properties it can extend further to make this system a complete one. o We look forward to working with the Government in implementing the recommendations and seeing an improvement in the effectiveness of the Police Department. o Assign each case to particular officer and other details are user will show. o The method of video conferencing can be added to make the project livelier. o Users can view the progress of their complaint online. o By the future technology user can view the case details and progress of the complaints on their mobile phones. o Back up will automatically generated every 24 hours.
54
10. Conclusion
The project titled as Online Crime Reporting is a web based application. This software provides facility for reporting online crimes, complaints, missing persons, show criminal details. This software is developed with scalability in mind. Additional modules can be easily added when necessary. The software is developed with modular approach. All modules in the system have been tested with valid data and invalid data and everything work successfully. Thus the system has fulfilled all the objectives identified and is able to replace the existing system. The project has been completed successfully with the maximum satisfaction of the organization. The constraints are met and overcome successfully. The system is designed as like it was decided in the design phase. The project gives good idea on developing a fullfledged application satisfying the user requirements. The system is very flexible and versatile. This software has a user-friendly screen that enables the user to use without any inconvenience. Validation checks induced have greatly reduced errors. Provisions have been made to upgrade the software. The application has been tested with live data and has provided a successful result. Hence the software has proved to work efficiently.
55
Appendix 1: Data Dictionary

abusingform Table 5: Abusing FIR Column Name abuseid reportfname reportphone abusefname abuselname abuseaddress abusestate abusecity abusereligion abusedby abusereason adminreg Table 6: Main-Admin Registration Column Name adminName adminPass Data Type varchar varchar Length 8 10 Extra Primary Key Data Type int varchar int varchar varchar varchar varchar varchar varchar varchar varchar Length 6 20 10 20 20 50 20 20 20 20 50 Extra Auto_Increament, Primary Key -
56
criminalform Table 7: Criminal Registration Form Column Name criminalid cfname cmname clname cgender cbdate cnationality crimetype policeform Table 8: Police Registration Form Column Name policeid pfname plname pstate pcity pphone pemail ppassword ppost Data Type int varchar varchar varchar varchar varchar varchar varchar varchar Length 6 20 20 20 20 20 20 20 20 Extra Auto_Increament, Primary Key Unique Key Data Type int varchar varchar varchar varchar varchar varchar varchar Length 6 20 20 20 20 20 20 20 Extra Auto_Increament, Primary Key -
57
kidnappedform Table 9: Missing Person FIR Column Name missingid missingfname missingmname missinglname missinggender reportfname reportphone relationmissing missingage missingdate missingfromaddress missingaddress missingstate missingcity missingphone missingoccupation missingheight Data Type int varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar Length 6 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 Extra Auto_Increament, primary key -
58
policestattionform Table 10: Police-station Registration Form Column Name policestationid pstationcentercode pstationname pstationaddress pstationstate pstationcity pstationcity robberyform Table 11: Robbery FIR Column Name robid robdate robplace robsuspect robthings Data Type int varchar varchar varchar varchar Length 6 20 20 20 200 Extra Auto_Increament, Primary Key Data Type int varchar varchar varchar varchar varchar varchar Length 6 11 20 20 20 20 20 Extra Auto_Increament, Primary Key -
59
registrationform Table 12: Registration Form Column Name userid ufname umname ulname ugender ubdate uaddress ustate ucity uphone uemail username password uidproof Uniquenum Data Type int varchar varchar varchar varchar varchar varchar varchar varchar int varchar varchar varchar varchar varchar Length 6 20 20 20 6 20 100 20 20 10 30 20 20 20 13 Extra Auto_Increament, Primary Key Unique Key Unique Key Unique Key
60
visitedfeedbackform Table 13: Feedback Form Column Name vfname vmname vlname vgender vphone vemail vsubject vfeedback Data Type varchar varchar varchar varchar varchar varchar varchar varchar Length 20 20 20 20 20 30 20 500 Extra -
61
References
Books:
o Charles Hampfed (2000)-Instant Java Server Pages-University of Toronto o Elmasri Navathe-Fundamentals of database systems o Herbert Schildt (2000)-Java Complete Reference- Tata McGraw Hill o Jamie Jaworsky-J2EE Bible-Techmedia o Rajeev mall-Software engineering o Advance Java Technology-Dreamtech
Online Reference:
o www.theserverside.com o www.java.sun.com o www.developer.com
62

Online Crime Reporting

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Online Crime Reporting

Enviado por

Direitos autorais:

Formatos disponíveis

ONLINE CRIME REPORTING

A PROJECT REPORT Submitted by

NISHIT TRIVEDI 090570107019

Nishit Trivedi 090570107019

Head of the Department

Prof. Nishant Goswami Assistant Professor

Prof.Vipul Vekariya Head of Department

TO WHOMSOEVER IT MAY CONCERN

For Tech Securing

Mr. Mitesh Goswami Date:

Feasibility Study .................................................................................................. 16

Limitation and Future Enhancement ...................................................................... 54

List of Symbols, Abbreviations and Nomenclature