INTRODUCTION

The Online Crime Reporting System used to report crime. This project is mainly useful

for police stations. This system will help to manage all the activities in a police station using

computers. Currently all the works are done manually, by computerizing all the activities inside a

police station can be managed easily and effectively. This system helps the users to report a

crime and view the case details and status of the case and also see the most wanted criminals.

In manual system wants lots of man power and paper work. And also the registration of

FIR was not done 100% accurately for various reasons. In the manual system the part of the

force was engaged for carrying out unproductive jobs such as delivering FIRs to higher officials.

There are many other such problems which decrease the efficiency of the department to provide

right justice to the common people. The solution for this problem is to create the crime reports by

sharing the information within the organization especially the information on Crime & Criminals

which help in effective working of Police.

1.1 Objectives:

This Online Crime Reporting System is fully functional and flexible.

It provides security of data.

It ensures data accuracy’s.

It provides proper control of the higher officials.

It minimizes manual data entry.

It needs minimum time for the various processing.

It has Greater efficiency.

Survey of Technologies

ABOUT MICROSOFT .NET

.NET Framework (pronounced dot net) is a software framework developed by

Microsoft that runs primarily on Microsoft Windows. It is open source and Microsoft

with .NET 2015 is extending it to run on Mac OS platforms and Linux.[3] It includes a

large class library known as Framework Class Library(FCL) and provides language

interoperability (each language can use code written in other languages) across several

programming languages. Programs written for .NET Framework execute in a software

environment (as contrasted to hardware environment), known as Common Language

Runtime (CLR), an application virtual machine that provides services such as security,

memory management, and exception handling. FCL and CLR together constitute .NET

Framework.FCL provides user interface, data access, database connectivity, cryptography,

web application development, numeric algorithms, and network communications.

Programmers produce software by combining their own source code with .NET Framework

and other libraries. .NET Framework is intended to be used by most new applications

created for Windows platform. Microsoft also produces an integrated development

environment largely for .NET software called Visual Studio.

ASP.NET

ASP.NET is a unified Web development model that includes the services necessary for you

to build enterprise-class Web applications with a minimum of coding. ASP.NET is part of

the .NET Framework, and when coding ASP.NETapplications you have access to classes in

the .NET Framework. You can code your applications in any language compatible with the

common language runtime (CLR), including Microsoft Visual Basic, C#, JScript .NET, and

J#.

These languages enable you to develop ASP.NET applications that benefit from the

common language runtime, type safety, inheritance, and so on.

The ASP.NET page and controls framework is a programming framework that

runs on a Web server to dynamically produce and render ASP.NET Web pages. ASP.NET Web

pages can be requested from any browser or client device, and ASP.NET renders markup (such

as HTML) to the requesting browser. As a rule, you can use the same page for multiple browsers,

because ASP.NET renders the appropriate markup for the browser making the request. However,

you can design your ASP.NET Web page to target a specific browser, such as Microsoft Internet

Explorer 6, and take advantage of the features of that browser. ASP.NET supports mobile

controls for Web-enabled devices such as cellular phones, handheld computers, and personal

digital assistants (PDAs).

ASP.NET Web pages are completely object-oriented. Within ASP.NET Web pages you

can work with HTML elements using properties, methods, and events. The ASP.NET page

framework removes the implementation details of the separation of client and server inherent in

Web-based applications by presenting a unified model for responding to client events in code

that runs at the server. The framework also automatically maintains the state of a page and the

controls on that page during the page processing life cycle. The ASP.NET page and controls

framework also enables you to encapsulate common UI functionality in easy-to-use, reusable

controls. Controls are written once, can be used in many pages, and are integrated into the

ASP.NET Web page that they are placed in during rendering.

In addition to themes, you can define master pages that you use to create a consistent

layout for the pages in your application. A single master page defines the layout and standard

behavior that you want for all the pages (or a group of pages) in your application. You can then

create individual content pages that contain the page-specific content you want to display. When

users request the content pages, they merge with the master page to produce output that

combines the layout of the master page with the content from the content page.

C#.NET

Visual C#.net is currently part of the visual studio.NET. Microsoft Visual C#. .NET is the

tool set for creating XML Web services and Microsoft. NET-connected applications for

Microsoft Windows and the Web. This robust development package, which uses the component-

oriented C# development language, offers a language and environment for creating next-

generation software.

MICROSOFT SQL SERVER

SQL Server 2008 (formerly codenamed "Katmai") was released on August 6, 2008 and

aims to make data management self-tuning, self-organizing, and self-maintaining with the

development of SQL Server Always On technologies, to provide near-zero downtime. SQL

Server 2008 also includes support for structured and semi-structured data, including digital

media formats for pictures, audio, video and other multimedia data. In current versions,

such multimedia data can be stored as BLOBs (binary large objects), but they are generic

bit streams. Intrinsic awareness of multimedia data will allow specialized functions to be

performed on them.

Feasibility Study

The preliminary investigation should examine the project feasibility. Feasibility is the

determination of whether or not a project is worth doing. It deals with the assertion of the

profitability of the working end product. The process following in making this determination is

called a ‘Feasibility study’.

Once it has been determined that a project is feasible the analyst can go ahead and

prepare the project specification which finalizes project requirements. Three test of feasibility

should be conducted which are technical, economical and operational feasibility.

Feasibility study is conducted once the problem is clearly understood. Feasibility study is

a high level capsule version of the entire system analysis and design process. The objective is to

determine quickly at a minimum expense how to solve a problem. The purpose of feasibility is

not to solve the problem but to determine if the problem is worth solving. The system has been

tested for feasibility in the following points.

Technical Feasibility:

Existing equipment and technology can be used for the project thus requiring no

additional cost for the project, so the system is technically feasible.

Economic Feasibility:

The system is economically feasible as we use only the open source technologies and the

benefits of the project outweigh the cost involved.

Operational Feasibility:

The new system doesn’t affect current procedures and work practices, so the

system is operationally feasible.

Project Planning and Scheduling

The planning and scheduling of the software Online Crime Reporting System, is done

with the help of Gantt chart. A Gantt chart is a graphical representation of the duration of tasks

against the progression of time. A Gantt chart is a useful tool for planning and scheduling

projects. A Gantt chart is helpful when monitoring a project’s progress. Use a Gantt chart to plan

how long a project should take.

A Gantt chart lays out the order in which the tasks need to be carried out. A Gantt chart

lets us see immediately what should have been achieved at any point in time. A Gantt chart lets

us see how remedial action may bring the project back on course. Most Gantt charts include

milestones which are technically not available on Gantt charts. However, for representing

deadline and other significant events, it is very useful to include this feature on a Gantt chart.

A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt chart

illustrates the start and finish dates of the terminal elements and summary elements of a project.

Terminal elements and summary elements comprise the work breakdown structure of the project.

Some Gantt charts also show the dependency relationships between activities. Gantt charts can

be used to show current schedule status using percent-complete shading and a vertical

“TODAY” line as shown here(time period is taken in days).

Pert Chart

PERT is a method to analyze the involved tasks in completing a given project, especially

the time needed to complete each task, and to identify the minimum time needed to complete the

total project. PERT was developed primarily to simplify the planning and scheduling of large

and complex projects.

It was developed for the U.S Navy Special Projects in 1957 to supports to the U.S Navy’s

Polaris nuclear submarine project. It was able to incorporate uncertainty by making it possible to

schedule a project while not knowing precisely the details and durations of all the activities. It is

more of an event-oriented technique rather than start and completion-oriented, and is used more

in projects were time is the major factor rather than cost. It is applied to very large scale, one-

time, complex, non-routine infrastructure and research and Development projects

Software Requirement Specification

The software requirement specification is produced at the culmination of analysis task.

The function and performance allocated to software as part of system engineering are refined by

establishing a complete information description, a detailed functional description, a

representation of system behavior, an indication of performance requirements and design

constraints, appropriate validation criteria, and information pertinent to requirements.

The introduction of the software requirements specification states the goals and

objectives of the software, describing in the context of the computer based system. Actually, the

introduction may be nothing more than the software scope of planning document.

The information description provides a detailed description of the problem that the

software must solve. Information content, flow and structure are documented.

Hardware, software and human interfaces are described for external system elements and

internal software functions.

A description of each function required to solve the problem is presented in the functional

description. A processing narrative is provided for each function, design constraints are stated

and justified, performance characteristics are tested, and one or more diagrams are included to

graphically represent the overall structure of the software and interplay among software

functions and other system elements. The behavioral description section of the specification

examines the operation of the software as a consequence of external events and internally

generated control characteristics. Validation criteria are probably the most important and

ironically the most often neglected section of the software requirement specification. For each

screen and each field in the screen the validation criteria is done as part of the software testing.

The specification of validation criteria act as an implicit review of all other requirements. When

considering a software project, two main different types of habitat are required.

SOFTWARE SPEC IFICATION

Operating System : Windows 2000/XP

Front end : ASP.NET with C#

Back end : Micro Soft SQL Server 2008

Markup Language : HTML

Style Sheets : CSS

HARDWARE CONFIGURATION

Processor : Pentium 4

Clock speed : 3.8 GHZ or Higher

RAM : 512 MB or more

Hard disk : 160 GB or more

Cache : 1 MB or more

Video Resolution : 1 GB or Higher

Monitor : VGA/SVGA

Keyboard : 104 Keys

Mouse : 2 buttons/ 3 buttons

2.6 Data Models

A data flow diagram is graphical tool used to describe and analyze movement of data

through a system. These are the central tool and the basis from which the other components are

developed. The transformation of data from input to output, through processed, may be

described logically and independently of physical components associated with the system. These

are known as the logical data flow diagrams.

A full description of a system actually consists of a set of data flow diagrams. Using two

familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each

component in a DFD is labeled with a descriptive name. Process is further identified with a

number that will be used for identification purpose. The development of DFD’s is done in

several levels. Each process in lower level diagrams can be broken down into a more detailed

DFD in the next level. The lop-level diagram is often called context diagram. It consists a single

process bit, which plays vital role in studying the current system. The process in the context

level diagram is exploded into other process at the first level DFD.

The idea behind the explosion of a process into more process is that understanding at one

level of detail is exploded into greater detail at the next level. This is done until further

explosion is necessary and an adequate amount of detail is described for analyst to understand

the process.

There are two types of DFD:

Logical DFD

Physical DFD

DFD Symbols:

In the DFD, there are four symbols

Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

Level 0:

User

Administrator

Data Base

Police 0.0

Online Crime Reporting System

. Level 1:

User

5

Status

4

Login

2

Viewstatus

Administrator

Police 6

Criminals

7

Add station

3

Addcomplaint

Data Base

8

Officer approval

9

Feedback

Level 2 for User:

Request Tbl_Feedaback

Response

Request Tbl_userRegister

Response Response

Request Response

Request

Request Response Tbl_ComplaintStatus

Response

Request Request

Response Tbl_CrimeRegister

Response

Request

Response

Request

Tbl_login

User

1.4

Login

1.2

Viewstatus

1.3

Addcomplaint

1.1

Register

1.3

Give feedback

Level 2 for Police:

Request Tbl_Criminal

Response

Request Response

Request

Request Response Tbl_ComplaintStatus

Response

Request Request

Response Tbl_PoliceStations

Response

Request Request

Response

Request

Tbl_login

Response

Request Tbl_ComplaintReply

Response

Police

2.5

Login

2.3

Status

2.4

Stations

2.2

Criminals

2.6

Complaint reply

Level 2 for Admin:

Request

Request Response Tbl_PoliceStations

Response

Request

Response Request

Response Tbl_officerapproval

Modularization Details

This project has three modules,

Admin

User

Police

3.2 Modules and their Details

Admin:

The options given to the Admin are:

Login

Administrator

3.1

Add station

3.2

Officer approval

Add new Stations

Officer approvals

View feedbacks

User:

The options given to the User are:

Registration

Login

Complaint registration

View complaint status

View wanted criminals

Give feedbacks

Police:

The options given to the Police are:

Registration

Login

Complaint view

Complaint reply

Status update

Add wanted criminals

3.3 Database DesignA data dictionary is a catalogue-a repository-of the elements in a system. As the name

suggests, these elements center on data the way they are structured to meet user requirements and

organization needs. In a data dictionary you will find a list of all the elements composing the data

flow through a system.

Login Table:

Field Data type ConstraintsUserID int Primary keyUsername Varchar(50) Not nullPassword Varchar(50) Not nullAutho Varchar(50) Not nullQuest Varchar(50) Not nullansw Varchar(50) Not nullRegID int Not null

User Registration Table:

Field Data type ConstraintsUser_ID Int Not nullName Varchar(50) Not nullPlace Varchar(50) Not nullDOB Varchar(50) Not nullGender Varchar(50) Not nullAddress Varchar(50) Not nullPhone Varchar(50) Not nullE-mail Varchar(50) Not nullOccupation Varchar(50) Not nullID Proof Varchar(50) Not nullID Proof Number Varchar(50) Not nullUsername Varchar(50) Not nullPassword Varchar(50) Not nullQust Varchar(MAX) Nut nullansw Varchar(MAX) Not null

Police Registration Table:

Field Data type ConstraintsOfficer_ID varchar(50) Primary keyOfficer_Name varchar(50) Not nullDesignation varchar(50) Not nullGender varchar(50) Not null

Address varchar(50) Not nullPolice_Station varchar(50) Not nullPhone_Number varchar(50) Not nullE_mailid varchar(50) Not nullusername varchar(50) Not nullpassword varchar(50) Not nullQustn varchar(50) Not nullanswer varchar(50) Not nullStatus varchar(50) Not nullimage varchar(50) Not null

Admin Table:

Field Data type ConstraintsAdmin_ID Int Primary keyUsername Varchar(50) NotnullPassword Varchar(50) NotnullDesignation Varchar(50) NotnullPhoneNumber Varchar(50) Notnull

Crime Register Table:

Field Data type ConstraintsFIRNO Varchar(50) Primary keyPetitioner_Name Varchar(50) Not nullNearestpoliceSTN Varchar(50) Not nullCity Varchar(50) Not nullCRM_place Varchar(50) Not nullCRM_Date Varchar(50) Not nullCRM_Time Varchar(50) Not nullCriminal_Detls Varchar(MAX) Not nullCRM_Detls Varchar(MAX) Not nullVictim_Detls Varchar(MAX) Not nullWitness_Detls Varchar(MAX) Not nullProof Varchar(MAX) Not null

Complaint Status Table:

Field Data type ConstraintsFIRNO Varchar(50) Primary keypetitionerName Varchar(50) Not nullStaffincharge Varchar(50) Not nullComplaintstatus Varchar(50) Not nullDetails Varchar(MAX) Not nullcourtorder Varchar(50) Not null

Complaint Reply Table:

Field Data type ConstraintsFIRNO Varchar(50) Not nullPetitioner Varchar(50) Not nullPolice_station Varchar(50) Not nullStaffincharge Varchar(50) Not nullStatus Varchar(MAX) Not nullCourt_order Varchar(50) Not null

Criminal Table:

Field Data type ConstraintsCriminal_ID int Primary keyCriminal_Name Varchar(50) Not nullAge int Not nullgender Varchar(50) Not nullPhysical_Details Varchar(50) Not nullPhoto Varchar(MAX) Not nullStatus Varchar(50) Not null

Police Station Table:

Field Data type ConstraintsStation_ID int Primary keyStation_Name Varchar(50) Not nullAddress Varchar(50) Not nullDistrict Varchar(50) Not nullPhone_Number1 Varchar(50) Not nullPhone_Number2 Varchar(50) Not nullEMailID Varchar(50) Not null

Feedback Table:

Field Data type ConstraintsF_ID int Not nullFIRNO Varchar(50) Not nullStaff_In_Charge Varchar(50) Not nullSubject Varchar(50) Not nullFeedback Varchar(50) Not null

Image Table:

Field Data type ConstraintsImageId int Not nullImageName varchar(50) Not null

Imagepath varchar(50) Not null

3.4 Procedural Design:

ALGORITHM FOR LOGIN

Step 1: Start

Step 2: Input login name and password

Step 3: Verify the name and password

Step 4: If login name and password is valid then go to step 6

Step 5: Otherwise go to step 1

Step 6: Print the message valid user and login successful

Step 7: Stop