Project Report Crime Record System

Project Report Crime Record
System
CONTENTS PAGE NO
1.INTRODUCTION
1.1 Introduction To The Project 3
2.INITIAL REQUIREMENTS
2.1 Purpose of The System 6
2.2 Objectives of the Project 6
3.ANALYSIS
3.1 Existing And Problems In Existing System 8
3.2 Proposed System 9
3.3 Benefits To The Organization 10
3.5 System Requirement Specification 13
3.6 Feasibility Study 14
3.7 Technical Specification 16
4. DESIGN
4.1 UML Diagrams 35
4.2 GUI Design 51
4.3 Database Tables 60
5. CODING 66
6. TESTING 79
7. IMPLEMENTATION 82
8. OUTPUT SCREENS 85
9. CONCLUSION 119
10. BIBILOGRAPHY 120
Computer Science Department Page 1

System
INTRODUCTION

System
The Government of Andhra Pradesh has a clear vision to create a
knowledge society by using Information Technology in all aspects of development
and governance. Pioneering efforts are being made to reach the benefits of IT to the
citizens-urban and rural, rich and poor, literate and illiterate. The Government is
conscious of the dangers of ‘Digital Divide’, and is making special provisions for
reaching the ‘Information Have-nots’.
Some of the basic users (police) perspectives of our project are:

• Better investigation due to availability of computerized Crime & Criminal
Records.
• Better supervision due to automation of Processes (Workflow).
• Building of District/State/National level Database for better Information
Sharing and Crime Analysis
Here in this crime record system we have three modules
1. New Crime Record
2. View Records
3. Update Records
For entering a new crime record i.e. an FIR the person has to first enter a
centralized password and then they have to select their position and enter user id and
password to prove their identity.
Here we have three positions,

1. Circle Inspector
2. Sub Inspector
3. Constable
The circle inspector can access all the three modules i.e.
 Can enter a NEW CRIME RECORD.
 Can VIEW the records in the database.
 Can UPDATE records present in the database.

System
Whereas the sub inspector can only,
 Enter a NEW CRIME RECORD
 VIEW the records
He cannot update the records.
And the constable has very limited access; he can only enter NEW CRIME
RECORDS, he cannot view or update the records.
For entering a NEW CRIME RECORD i.e. for lodging an FIR, all the details related
to the crime are noted in a sequence a follows
 Fir is entered.
 Act and section under which the crime has been done are assigned.
 Complainant details are taken.
 Place and time when the offence has taken place.
 Then the officer is assigned for the task.
 Property details, if stolen or damaged are noted.
 Accused or suspect details are taken.
 If any person is arrested or has surrendered, details are noted.
 If any property is seized or search made are noted.
 Court disposal i.e. which advocate is handling the case and the witness details
are taken.
 Result of appeal-whether the person has obtained the bail or has been sent to
the jail i.e. the result of the case is note.
To view records the officer needs to enter the FIR number of the case and can find
all the details of the case, he can view either the general details or the full details of
the case. He can also view the details of the crime
 By dates
 By any particular police station
 By district
To update the records the circle inspector is asked to enter the FIR number and a
page is displayed with all links to the details of the crime record.

System
INITIAL REQUIREMENT

System
PURPOSE
The purpose of this application “CRIME RECORD SYSTEM” is to improve the

efficiency of department of the police by take all the important matter from the
complainant and to lodge an FIR with all the details of the criminal and to find out
whether he is a known criminal or a new and to proceed with the case. This also
makes note of the address of the criminal arrested and also other details related to the
complainant. This also allows the working officers to speed up the process by easily
rectifying the person who has committed the crime.
OBJECTIVE
The objectives of the CRIME RECORD SYSTEM are:
 To study similarities in the Modus Operandi of criminals and on its basis

suggest makes of suspects to the Investigating Officers.
 To tell the I.Os any old crimes, which might have been committed by an
arrested person.
 To help in establishing the identity of criminal and to furnish reliable data on
the antecedents, associates, hide-outs, previous convictions etc. of an arrested
person.
 To coordinate recovered property with that of the stolen.
 To disseminates information to keep Police Officers alert and in the look out
for any suspects/missing persons.

System
ANALYSIS

System
Analysis is a detailed study of the various operations performed by a system and
their relationships within and outside the system. One aspect of analysis is defining
the boundaries of the system and determining whether or not a candidate should
consider other related systems. During analysis, data is collected from the available
files, decision points, and transactions handled by the present system.
Logical system models and tools are used in analysis. Training, experience, and
common sense are required for collection of the information needed to do the
analysis.
EXISTING SYSTEM
The present system insists for systematic collection of data without missing the
important details. Documents are seen by supervisory officials. The senior officers are
in a position to keep track of all the cases registered, including those transferred.
As the system is in a position to give the details of arrests made at various Police
Stations, which helps the investigating Officer to elicit the information from the
accused without resorting to human right violations thus making the life of Police
Officer more content.
Before computerization, the part of the force was engaged for carrying out
unproductive jobs such as delivering FIRs to higher officials, collecting Post-mortem
reports, wound certificates etc. They were also utilized for entering, filling individual
registers, preparing periodical reports etc Work force is now used for the purpose for
which they were trained (Policing) and not on unproductive tasks.
PROBLEMS IN THE EXISTING SYSTEM
 Time Consuming
 Inconsistency of Data
 Difficult to identify the records
 Tracing errors is impossible

System
PROPOSED SYSTEM
This application envisages information sharing within the organization and

across the States in the country especially the information on Crime & Criminals for
effective working of Police. For integration at National level, the following Seven
Integrated Police Forms standardized by National Crime Records Bureau have been
adopted as the basis for Crime Module development. These integrated forms cover
most of the information needed by Criminal Justice System. And the database records
the following information:-
1. FIR (First Information Register) (act, section, occurrence, complaint, accused
property detail, brief complaint)
2. Crime Detail Form (type of crime, features, physical evidence, witness, place of
crime)
3. Property Search & Seizure
4. Arrest/Court Surrender (arrest details, bail details, personal items recovered)
5. Charge Sheet & Case Disposal Reports (charge sheet information, property
recovered/ seized, and action taken)
6. Court Disposal (adult, juvenile, punishment)
7. Result of Appeals
8. Other registers (interrogation details, case diary, witness details, remand diary,
case calendar etc)
Effective coordination among different departments / entities in criminal justice

system i.e. Forensic Science Laboratories and Prosecution Department is being
ensured by interfacing for access and transfer of information between departments –
thus making it easier to collect inputs needed for proper and quicker investigation of a
case. Crime record is being integrated with the fully computerized Fingerprint
Analysis Criminal Tracing System (FACTS). This also makes obligatory for these
Departments to respond promptly improving their accountability.

System
Benefits to the Organization:
1. Crime – analysis guides the Investigating Officer on the right track. Data available
and analyzed information from the system enables a new comer to get vast
information with least delay and allows him to plan and settle down in his work at the
earliest.
2. The present system insists for systematic collection of data without missing the
important details. Documents are seen by supervisory officials. The senior officers are
in a position to keep track of all the cases registered, including those transferred.
3. The Police personnel are not keen in using third degree methods to extract
information from the accused. As the system is in a position to give the details of
arrests made at various Police Stations, which helps the investigating Officer to elicit
the information from the accused without resorting to human right violations thus
making the life of Police Officer more content.
4. In the manual system, when property is recovered by some other Police Station
other than the PS where the crime is registered, it was a tedious task to match the PS
with the lost property and the PS which recovered the property. Today crime record
can match the lost and recovered property and there by pin point the real efficiency /
productivity of the individual officer / Unit Productivity of men is established with
correct supporting data making it a reality to evaluate the performance and
productivity of Officials on scientific lines. This is now being realized through this
application.
. 5. Before computerization, the part of the force was engaged for carrying out
unproductive jobs such as delivering FIRs to higher officials, collecting Postmortem
reports, wound certificates etc. They were also utilized for entering, filling individual
registers, preparing periodical reports etc Work force is now used for the purpose for
which they were trained (Policing) and not on unproductive tasks.
6. When a Grave Crime is registered by the Police station, System immediately transfers
the Grave Crime details to the Server at Unit Headquarters which in turn by reverse

System
dialling process alerts the concerned Officers up the line of Police Station thus
improving the sensitivity of the System manifold.
Solution requirements:
 The first part of the solution requirement involves constructing the basic
recording system for the Crime System. This involves capturing details of the
organizational structure, district/zone details, Police station details and other
important entities.
 There is a need to create a comprehensive categorization for the entities of

Crime, Modus-operandi, Motive and Suspects. There is also a need to create
appropriate classification for types of evidence.
 The basic transaction to be captured in the system is the filing of the FIR. Thereafter,
the FIR becomes the central entity around which additional information in terms of
evidence, suspects, etc would be added.
 The system needs to provide for a Comprehensive Querying mechanism which

would the heart of the system. Using this mechanism, the Investigating officer should
be able to answer the following types of questions:
 What is the current status of Case X?
 FIR filed
 Status of Completion of evidence gathering
 Status of Completion of questioning of suspects
 Motive established
 Modus operandi established
 Charges filed.
 Trial in progress
 Trial Completion
 Conviction/Acquittal

System
 Does Suspect A have a previous criminal record?
 What crimes have been committed by Suspect B?
 Give a listing of crimes committed with Modus Operandi O.

System
SYSTEM REQUIREMENT SPECIFICATIONS
HARDWARE REQUIREMENTS:
Processor : Pentium3/Pentium4
Processor speed: 600 MHz
Ram : 512 MB
Disk space : 40 GB
SOFTWARE REQUIREMENTS:
Operating systems: windows 2000server
Frame work : 2.0 and above
Front end : ASP.net
Language : C#.net
Back end : SQL server 2000

System
FEASIBILITY STUDY
A feasibility analysis usually involves a through assessment of the financial

(value), technical (practicality), and operational (need) aspects of a proposal . In
systems development project, Business managers are primarily responsible for
assessing the operational feasibility of the system, and information technology (IT)
analysts are responsible for assessing technical feasibility. Both then work together to
prepare a cost benefit analysis of the proposed system to determine its economic
feasibility.
TECHNICAL FEASIBILITY
A system development project may be regarded as technically feasible or

practical if the organization has the necessary expertise and infrastructure to develop,
install, operate and maintain the proposed system.
Organization s will need to make this assessment based on:
 Knowledge of the current and emerging technological solutions.

 Availability of technical quantified staff in-house for the duration of the
project and subsequent maintenance phase. To support the development
and maintenance of the proposed system.
 Availability of infrastructure in-house to support the development and
maintenance of the proposed system.
 Where necessary, the financial system and/or technical capacity to procure
appropriate infrastructure and expertise from outside.
 Capacity of the proposed system to accommodate increasing levels of user
over the medium term.
 The capacity of the proposed system to accommodate to meet initial
performance expectations and accommodate new functionality over the
medium term.

System
OPERATIONAL FEASIBILITY
A system development project is likely to be operationally feasible if it meets

the ‘need’ and expectations of the organization. User acceptance is an importance is
an important determinant of operational feasibility.
 Corporate culture.
 Staff resistance or receptivity to change.
 Management support for the new system.
 The nature and level of user involvement in the development and
implementation of the system.
 Direct and indirect impacts of the new system on work practices.
 Anticipated performance and outcomes of the new system compared
with the existing system.
 Viability of the proposed development and implementation schedule.
 Training requirements and other change management strategies.
 ‘Pay back ‘periods (i.e. trade-off between long term organizational
benefits and short term inefficiencies during system development and
implementation).

System
Technical Specification:
Microsoft.NET Framework
The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfill the following objectives:
To provide a consistent object-oriented programming environment whether object

code is stored and executed locally, executed locally but Internet-distributed, or
executed remotely.
To provide a code-execution environment that minimizes software deployment and

versioning conflicts.
To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.
To provide a code-execution environment that eliminates the performance problems

of scripted or interpreted environments.
To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.
To build all communication on industry standards to ensure that code based on the
.NET Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and
the .NET Framework class library. The common language runtime is the foundation
of the .NET Framework. You can think of the runtime as an agent that manages code
at execution time, providing core services such as memory management, thread
management, and remoting, while also enforcing strict type safety and other forms of
code accuracy that ensure security and robustness. In fact, the concept of code
management is a fundamental principle of the runtime. Code that targets the runtime
is known as managed code, while code that does not target the runtime is known as
unmanaged code. The class library, the other main component of the .NET

System
Framework, is a comprehensive, object-oriented collection of reusable types that you
can use to develop applications ranging from traditional command-line or graphical
user interface (GUI) applications to applications based on the latest innovations
provided by ASP.NET, such as Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed
code, thereby creating a software environment that can exploit both managed and
unmanaged features. The .NET Framework not only provides several runtime hosts,
but also supports the development of third-party runtime hosts.
Internet Explorer is an example of an unmanaged application that hosts the runtime

(in the form of a MIME type extension). Using Internet Explorer to host the runtime
enables you to embed managed components or Windows Forms controls in HTML
documents. Hosting the runtime in this way makes managed mobile code (similar to
Microsoft® ActiveX® controls) possible, but with significant improvements that only
managed code can offer, such as semi-trusted execution and secure isolated file
storage.
The following illustration shows the relationship of the common language runtime
and the class library to your applications and to the overall system. The illustration
also shows how managed code operates within a larger architecture.

System
Features of the Common Language Runtime
The common language runtime manages memory, thread execution, code execution,
code safety verification, compilation, and other system services. These features are
intrinsic to the managed code that runs on the common language runtime.
With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet,
enterprise network, or local computer). This means that a managed component might
or might not be able to perform file-access operations, registry-access operations, or
other sensitive functions, even if it is being used in the same active application.
The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song,
but cannot access their personal data, file system, or network. The security features of
the runtime thus enable legitimate Internet-deployed software to be exceptionally
featuring rich.
The runtime also enforces code robustness by implementing a strict type- and code-
verification infrastructure called the common type system (CTS). The CTS ensures
that all managed code is self-describing. The various Microsoft and third-party
language compilers
Generate managed code that conforms to the CTS. This means that managed code can
consume other managed types and instances, while strictly enforcing type fidelity and
type safety.
In addition, the managed environment of the runtime eliminates many common

software issues. For example, the runtime automatically handles object layout and
manages references to objects, releasing them when they are no longer being used.
This automatic memory management resolves the two most common application
errors, memory leaks and invalid memory references.
The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of
the runtime, the class library, and components written in other languages by other

System
developers. Any compiler vendor who chooses to target the runtime can do so.
Language compilers that target the .NET Framework make the features of the .NET
Framework available to existing code written in that language, greatly easing the
migration process for existing applications.
While the runtime is designed for the software of the future, it also supports software
of today and yesterday. Interoperability between managed and unmanaged code
enables developers to continue to use necessary COM components and DLLs.
The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted.
A feature called just-in-time (JIT) compiling enables all managed code to run in the
native machine language of the system on which it is executing. Meanwhile, the
memory manager removes the possibilities of fragmented memory and increases
memory locality-of-reference to further increase performance.
Finally, the runtime can be hosted by high-performance, server-side applications, such

as Microsoft® SQL Server™ and Internet Information Services (IIS). This
infrastructure enables you to use managed code to write your business logic, while
still enjoying the superior performance of the industry's best enterprise servers that
support runtime hosting.
.NET Framework Class Library
The .NET Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object-oriented,
providing types from which your own managed code can derive functionality. This
not only makes the .NET Framework types easy to use, but also reduces the time
associated with learning new
Features of the ‘ .NET Framework’. In addition, third-party components can integrate

seamlessly with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of interfaces
that you can use to develop your own collection classes. Your collection classes will
blend seamlessly with the classes in the .NET Framework.

System
As you would expect from an object-oriented class library, the .NET Framework
types enable you to accomplish a range of common programming tasks, including
tasks such as string management, data collection, database connectivity, and file
access. In addition to these common tasks, the class library includes types that support
a variety of specialized development scenarios. For example, you can use the .NET
Framework to develop the following types of applications and services:
 Console applications.
 Scripted or hosted applications.
 Windows GUI applications (Windows Forms).
 ASP.NET applications.
 XML Web services.
 Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types
that vastly simplify Windows GUI development. If you write an ASP.NET Web Form
application, you can use the Web Forms classes.
Client Application Development
Client applications are the closest to a traditional style of application in Windows-

based programming. These are the types of applications that display windows or
forms on the desktop, enabling a user to perform a task. Client applications include
applications such as word processors and spreadsheets, as well as custom business
applications such as data-entry tools, reporting tools, and so on. Client applications
usually employ windows, menus, buttons, and other GUI elements, and they likely
access local resources such as the file system and peripherals such as printers.
Another kind of client application is the traditional ActiveX control (now replaced by
the managed Windows Forms control) deployed over the Internet as a Web page. This

System
application is much like other client applications: it is executed natively, has access to
local resources, and includes graphical elements.
In the past, developers created such applications using C/C++ in conjunction with the
Microsoft Foundation Classes (MFC) or with a rapid application development (RAD)
environment such as Microsoft® Visual Basic®. The .NET Framework incorporates
aspects of these existing products into a single, consistent development environment
that drastically simplifies the development of client applications.
The Windows Forms classes contained in the .NET Framework are designed to be
used for GUI development. You can easily create command windows, buttons, menus,
toolbars, and other screen elements with the flexibility necessary to accommodate
shifting business needs.
For example, the .NET Framework provides simple properties to adjust visual
attributes associated with forms. In some cases the underlying operating system does
not support changing these attributes directly, and in these cases the .NET Framework
automatically recreates the forms. This is one of many ways in which the .NET
Framework integrates the developer interface, making coding simpler and more
consistent.
Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a

user's computer. This means that binary or natively executing code can access some of
the resources on the user's system (such as GUI elements and limited file access)
without being able to access or compromise other resources. Because of code access
security, many applications that once needed to be installed on a user's system can
now be safely deployed through the Web. Your applications can implement the
features of a local application while being deployed like a Web page.

System
C#.NET
Introduction to Windows Forms (C#.NET)
ACTIVE X DATA OBJECTS.NET
ADO.NET Overview
ADO.NET is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the
web with scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command objects,
and also introduces new objects. Key new ADO.NET objects include the DataSet,
DataReader, and DataAdapter.
The important distinction between this evolved stage of ADO.NET and previous data
architectures is that there exists an object -- the DataSet -- that is separate and distinct
from any data stores. Because of that, the DataSet functions as a standalone entity.
You can think of the DataSet as an always disconnected record-set that knows nothing

System
about the source or destination of the data it contains. Inside a DataSet, much like in a
database, there are tables, columns, relationships, constraints, views, and so forth.
A DataAdapter is the object that connects to the database to fill the DataSet. Then, it
connects back to the database to update the data there, based on operations performed
while the DataSet held the data. In the past, data processing has been primarily
connection-based. Now, in an effort to make multi-tiered apps more efficient, data
processing is turning to a message-based approach that revolves around chunks of
information. At the center of this approach is the DataAdapter, which provides a
bridge to retrieve and save data between a DataSet and its source data store. It
accomplishes this by means of requests to the appropriate SQL commands made
against the data store.
The XML-based DataSet object provides a consistent programming model that works
with all models of data storage: flat, relational, and hierarchical. It does this by having
no 'knowledge' of the source of its data, and by representing the data that it holds as
collections and data types. No matter what the source of the data within the DataSet
is, it is manipulated through the same set of standard APIs exposed through the
DataSet and its subordinate objects.
While the DataSet has no knowledge of the source of its data, the managed provider
has detailed and specific information. The role of the managed provider is to connect,
fill, and persist the DataSet to and from data stores. The OLE DB and SQL Server
.NET Data Providers (System.Data.OleDb and System.Data.SqlClient) that are part of
the .Net Framework provide four basic objects: the Command, Connection,
DataReader and DataAdapter. In the remaining sections of this document, we'll walk
through each part of the DataSet and the OLE DB/SQL Server .NET Data Providers
explaining what they are, and how to program against them.
The following sections will introduce you to some objects that have evolved, and
some that are new. These objects are:
 Connections. For connection to and managing transactions against a database.
 Commands. For issuing SQL commands against a database.

System
 DataReaders. For reading a forward-only stream of data records from a SQL
Server data source.
 DataSets. For storing, remoting and programming against flat data, XML data
and relational data.
 DataAdapters. For pushing data into a DataSet, and reconciling data against a
database.
When dealing with connections to a database, there are two different options: SQL
Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data
Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET
Data Provider. These are written to talk directly to Microsoft SQL Server. The OLE
DB .NET Data Provider is used to talk to any OLE DB provider (as it uses OLE DB
underneath).
Connections
Connections are used to 'talk to' databases, and are represented by provider-specific
classes such as SQLConnection. Commands travel over connections and result sets
are returned in the form of streams which can be read by a DataReader object, or
pushed into a DataSet object.
Commands
Commands contain the information that is submitted to a database, and are
represented by provider-specific classes such as SQLCommand. A command can be a
stored procedure call, an UPDATE statement, or a statement that returns results. You
can also use input and output parameters, and return values as part of your command
syntax. The example below shows how to issue an INSERT statement against the
Northwind database.
DataReaders
The DataReader object is somewhat synonymous with a read-only/forward-only
cursor over data. The DataReader API supports flat as well as hierarchical data. A
DataReader object is returned after executing a command against a database. The
format of the returned DataReader object is different from a record-set. For example,
you might use the DataReader to show the results of a search list in a web page.

System
DataSets and DataAdapters
DataSets
The DataSet object is similar to the ADO Record-set object, but more powerful, and
with one other important distinction: the DataSet is always disconnected. The DataSet
object represents a cache of data, with database-like structures such as tables,
columns, relationships, and constraints. However, though a DataSet can and does
behave much like a database, it is important to remember that DataSet objects do not
interact directly with databases, or other source data. This allows the developer to
work with a programming model that is always consistent, regardless of where the
source data resides. Data coming from a database, an XML file, from code, or user
input can all be placed into DataSet objects. Then, as changes are made to the DataSet
they can be tracked and verified before updating the source data. The GetChanges
method of the DataSet object actually creates a second DataSet that contains only the
changes to the data. This DataSet is then used by a DataAdapter (or other objects) to
update the original data source.
The DataSet has many XML characteristics, including the ability to produce and
consume XML data and XML schemas. XML schemas can be used to describe
schemas interchanged via WebServices. In fact, a DataSet with a schema can actually
be compiled for type safety and statement completion.
DataAdapters (OLEDB/SQL)
The DataAdapter object works as a bridge between the DataSet and the source data.
Using the provider-specific SqlDataAdapter (along with its associated SqlCommand
and SqlConnection) can increase overall performance when working with a Microsoft
SQL Server databases. For other OLE DB-supported databases, you would use the
OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection
objects.
The DataAdapter object uses commands to update the data source after changes have
been made to the DataSet. Using the Fill method of the DataAdapter calls the
SELECT command; using the Update method calls the INSERT, UPDATE or
DELETE command for each changed row. You can explicitly set these commands in
order to control the statements used at runtime to resolve changes, including the use of

System
stored procedures. For ad-hoc scenarios, a CommandBuilder object can generate these
at run-time based upon a select statement. However, this run-time generation requires
an extra round-trip to the server in order to gather required metadata, so explicitly
providing the INSERT, UPDATE, and DELETE commands at design time will result
in better run-time performance.
ASP.Net
Server Application Development
Server-side applications in the managed world are implemented through runtime

hosts. Unmanaged applications host the common language runtime, which allows
your custom managed code to control the behavior of the server. This model provides
you with all the features of the common language runtime and class library while
gaining the performance and scalability of the host server.
The following illustration shows a basic network schema with managed code running
in different server environments. Servers such as IIS and SQL Server can perform
standard operations while your application logic executes through the managed code.
Server-side managed code
ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services use
IIS and ASP.NET as the publishing mechanism for applications, and both have a
collection of supporting classes in the .NET Framework.
XML Web services, an important evolution in Web-based technology, are distributed,

server-side application components similar to common Web sites. However, unlike
Web-based applications, XML Web services components have no UI and are not
targeted for browsers such as Internet Explorer and Netscape Navigator. Instead,
XML Web services consist of reusable software components designed to be consumed
by other applications, such as traditional client applications, Web-based applications,
or even other XML Web services. As a result, XML Web services technology is

System
rapidly moving application development and deployment into the highly distributed
environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop
Web Forms pages in any language that supports the .NET Framework. In addition,
your code no longer needs to share the same file with your HTTP text (although it can
continue to do so if you prefer). Web Forms pages execute in native machine
language because, like any other managed application, they take full advantage of the
runtime. In contrast, unmanaged ASP pages are always scripted and interpreted.
ASP.NET pages are faster, more functional, and easier to develop than unmanaged
ASP pages because they interact with the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web
services are built on standards such as SOAP (a remote procedure-call protocol),
XML (an extensible data format), and WSDL ( the Web Services Description
Language). The .NET Framework is built on these standards to promote
interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with the .NET
Framework SDK can query an XML Web service published on the Web, parse its
WSDL description, and produce C# or Visual Basic source code that your application
can use to become a client of the XML Web service. The source code can create
classes derived from classes in the class library that handle all the underlying
communication using SOAP and XML parsing. Although you can use the class
library to consume XML Web services directly, the Web Services Description
Language tool and the other tools contained in the SDK facilitate your development
efforts with the .NET Framework.
If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication standards,
such as SOAP, WSDL, and XML. Using those classes enables you to focus on the
logic of your service, without concerning yourself with the communications
infrastructure required by distributed software development.

System
Finally, like Web Forms pages in the managed environment, your XML Web service
will run with the speed of native machine language using the scalable communication
of IIS.
SQL SERVER
DATABASE
A database management, or DBMS, gives the user access to their data and
helps them transform the data into information. Such database management systems
include dBase, paradox, IMS, Sql Server and SQL Server. These systems allow users
to create, update and extract information from their database.
A database is a structured collection of data. Data refers to the characteristics

of people, things and events. SQL Server stores each data item in its own fields. In
SQL Server, the fields relating to a particular person, thing or event are bundled
together to form a single complete unit of data, called a record (it can also be referred
to as raw or an occurrence). Each record is made up of a number of fields. No two
fields in a record can have the same field name.
During an SQL Server Database design project, the analysis of your business
needs identifies all the fields or attributes of interest. If your business needs change
over time, you define any additional fields or change the definition of existing fields.
SQL Server Tables
SQL Server stores records relating to each other in a table. Different tables are
created for the various groups of information. Related tables are grouped together to
form a database.
Primary Key
Every table in SQL Server has a field or a combination of fields that uniquely
identifies each record in the table. The Unique identifier is called the Primary Key, or

System
simply the Key. The primary key provides the means to distinguish one record from
all other in a table. It allows the user and the database system to identify, locate and
refer to one particular record in the database.
Relational Database
Sometimes all the information of interest to a business operation can be stored

in one table. SQL Server makes it very easy to link the data in multiple tables.
Matching an employee to the department in which they work is one example. This is
what makes SQL Server a relational database management system, or RDBMS. It
stores data in two or more tables and enables you to define relationships between the
tables and enables you to define relationships between the tables.
Foreign Key
When a field is one table matches the primary key of another field is referred
to as a foreign key. A foreign key is a field or a group of fields in one table whose
values match those of the primary key of another table.
Referential Integrity
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.
Data Abstraction
A major purpose of a database system is to provide users with an abstract view

of the data. This system hides certain details of how the data is stored and
maintained. Data abstraction is divided into three levels.
Physical level:
This is the lowest level of abstraction at which one describes how the data are
actually stored.

System
Conceptual Level:
At this level of database abstraction all the attributed and what data are actually
stored is described and entries and relationship among them.
View level:
This is the highest level of abstraction at which one describes only part of the
database.
FEATURES OF SQL SERVER (RDBMS)
SQL SERVER is one of the leading database management systems (DBMS)

because it is the only Database that meets the uncompromising requirements of
today’s most demanding information systems. From complex decision support
systems (DSS) to the most rigorous online transaction processing (OLTP) application,
even application that require simultaneous DSS and OLTP access to the same critical
data, SQL Server leads the industry in both performance and capability
SQL SERVER is a truly portable, distributed, and open DBMS that delivers
unmatched performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially
designed for online transactions processing and for handling large database
application.
SQL SERVER with transactions processing option offers two features which
contribute to very high level of transaction processing throughput, which are
 The row level locks manager
 Enterprise wide Data Sharing
The unrivaled portability and connectivity of the SQL SERVER DBMS
enables all the systems in the organization to be linked into a singular, integrated
computing resource.
Portability
SQL SERVER is fully portable to more than 80 distinct hardware and operating
systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of

System
proprietary platforms. This portability gives complete freedom to choose the database
sever platform that meets the system requirements.
Open Systems
SQL SERVER offers a leading implementation of industry –standard SQL.
SQL Server’s open architecture integrates SQL SERVER and non –SQL SERVER
DBMS with industry’s most comprehensive collection of tools, application, and third
party software products SQL Server’s Open architecture provides transparent access
to data from other relational database and even non-relational database.
Distributed Data Sharing
SQL Server’s networking and distributed database capabilities to access data
stored on remote server with the same ease as if the information was stored on a
single local computer. A single SQL statement can access data at multiple sites. You
can store data where system requirements such as performance, security or
availability dictate.
Unmatched Performance
The most advanced architecture in the industry allows the SQL SERVER
DBMS to deliver unmatched performance.
Sophisticated Concurrency Control

Real World applications demand access to critical data. With most database
Systems application becomes “contention bound” – which performance is limited not
by the CPU power or by disk I/O, but user waiting on one another for data access .
SQL Server employs full, unrestricted row-level locking and contention free queries
to minimize and in many cases entirely eliminates contention wait times.

System
ARCHITECTURE
a) System Interfaces
The application enables users to login directly to Web site / Intranet from their
desktop using a conventional Web browser.
Crime Record system is an Internet / Intranet Application.
Crime Record is an independent, totally self-contained application runs on web

server like IIS and on Windows Operating System. This web enabled application
works with browser like Internet explorer 5.0 and above at client side.
Crime Record will be based on Internet architecture and the layout of the application
is explained in the following diagram.
Inspector
Sub Web Database

Inspector
Server Server
IIS 2.0
Constable
Architecture of CRIME RECORD SYSTEM
A. User: Who ever uses the system

B. Web Server: The Business Logic / Validations / Security of the Crime Record will
be implemented here.
C. Database Server: The information of the Crime Record will be stored in the
Database Server. It can also be called as Data Services (SQL Server 2000).

System
b) User interfaces:
This section describes the application with the help of word document proto type
screen flow design.
c) Hardware Interfaces
This application is purely Internet Application, which runs through HTTP Protocol.
d) Software Interfaces
1. Application installed on Web server. Clients can access server through any client
by using WEB browser like Internet explorer 5.0 and above.
2. Client network should support any network protocol like TCP/IP.
e) Communication Interfaces
For the establishment of Internet following Communication protocols are necessary.
1. TCP/IP protocol.
2. HTTP protocol.
f). Memory constraints:
There are no constraints on memory related issues. Normal server and client
Configuration is sufficient to run this application.

System
DESIGN

System
UML DIAGRAMS
CLASS DIAGRAM:
A class is a description of a set of objects that share the same attributes,

operations, relationships and semantics. A class is a software unit that implements one
or more interfaces.
A class diagram is a graphic view of the static structural model. The individual
class diagrams do not represent divisions in the underlying model.
A class diagram does not necessarily match a single semantic entity. A
package within the static structural model may be represented by one or more class
diagrams. The division of the presentation into separate diagrams is for graphical
convenience and does not imply a partitioning of the model itself. The contents of a
diagram map into elements in the static semantic model. If a diagram is part of a
package, then its contents map into elements in the same package (including possible
references to elements accessed or imported from other packages).

System
CLASS DIAGRAM OF CRIME RECORD SYSTEM:
user
update records
new crime record view records
firno
submit()
fir crime details
reports fir no
firno is
enter fir date
update details police station
occurence of offence crime details
firno general details investigation officer
full details
occurence of offence date & time firno service number
complaint details info received at police station date & time date rank
firno type of information time property details
act and section
complaintaint name place of occurence district accused and suspect details firno save()
fathers/husbands name firno
address details police station firno property details
dob date
act no of accused total value complaint details
age district
save() section accused person physical features
gender grave firno
accused person name save()
nationality act section complaintaint name
fathers name
passport no fathers/husbands name
crime details dob
hno property details dob
age
street/village fir no occurence of offence age
firno gender
city/district date firno gender
property details nationality
state police station occurence of offence date & time nationality
total value passport no
phone no crime details
house no info received at police station date & time passport no
mobile no investigation officer type of information hno
save() street
service number place of occurence street/village
city
save() rank address details city/district
state
state
accused and suspect details ph no
save() save() phone no
firno mobile no
no of accused save()
arrest/surrendered
accused person physical features save()
firno
accused person name result of appeal property search court disposal
police station arrest/surrendered
fathers name firno
place,date& time of arrest fir no firno
dob court name firno
place of surrendered appeal no police station
age date police station
accused person details appealent name date
gender prosecutor name place,date& time of arrest
physical apperaence court name time
nationality withness details place of surrendered
finger prints taken result of appeal address
passport no judgement given accused person details
accused current position surity details person details
house no physical apperaence
bail obtained withness details
street save() finger prints taken
save() bail details property details
city accused current position
state
save() save()
ph no save()
property search court disposal
firno firno save()
police station court name
date date
prosecutor name result of appeal
time
withness details fir no
address
judgement given appeal no
person details
appealent name
withness details
save() court name
property details
result of appeal
surity details
save()
bail obtained
bail details
save()

System
USE CASE DIAGRAMS:
A use case diagram is a diagram that shows a set of use cases and actors, and
their relationships. It is central to modelling the functions of the system. A use case
diagram puts everything together. It is used to visualize the functions of a system, so
that:
a) Users can comprehend how to use the system and
b) Developers can understand how to implement it.
The use case diagram shows the position or context of the use case among
other use cases. As an organizing mechanism, a set of consistent, coherent use cases
promotes a useful picture of system behaviour, a common understanding between the
customer/owner/user and the development team.
The only relationship allowed between actors on a use case diagram is

generalization. This is useful in defining overlapping roles between actors. The
notation is a solid line ending in a hollow triangle drawn from the specialized to the
more general actor.

System
USE CASE DIAGRAM FOR CIRCLE INSPECTOR:
complainant details
occurence of of f ence
crime details
property details
new crime record

accused/suspect details
arrest/ surrendered details
property search
court disposal
result of appeal
general details
v iew record
circle inspector f ull details
complainant details
crime details
update record property details
arrest/ surrendered details
property search
court disposal
result of appeal

System
USE CASE DIAGRAM FOR SUB – INSPECTOR:
complainant details
crime details property details
new crime record

property search arrest/ surrendered details
court disposal
result of appeal
sub inspector
general details
v iew record
f ull details
USE CASE DIAGRAM FOR CONSTABLE:
complainant details
crime details property details
new crime record

constable property search arrest/ surrendered details
court disposal
result of appeal

System
SEQUENCE DIAGRAMS:
A sequence diagram is a kind of interaction diagram in UML that shows how

processes operate one with another and in what order. It is a construct of a Message
Sequence Chart.
A sequence diagram shows, as parallel vertical lines ("lifelines"), different

processes or objects that live simultaneously, and, as horizontal arrows, the messages
exchanged between them, in the order in which they occur. This allows the
specification of simple runtime scenarios in a graphical manner.
The UML 2.0 Sequence Diagram supports similar notation to the UML 1.
Sequence Diagram with added support for modeling variations to the standard flow of
events. If the lifeline is that of an object, it is underlined (if not it is a role).Note that
leaving the instance name blank can represent anonymous and unnamed instances. In
order to display interaction, messages are used. These are horizontal arrows with the
message name written above them. Solid arrows with full heads are synchronous
calls, solid arrows with stick heads are asynchronous calls and dashed arrows with
stick heads are return messages. This definition is true as of UML 2, considerably
different from UML 1.
Sequence diagrams can show object activation and deactivation.

Activation means that an object is occupied performing a task.
Deactivation means that the object is idle, waiting for a message.

System
SEQUENCE DIAGRAM FOR CENTRAL LOGIN:
user crime record database
1: centralized password 2: validate
3: valid
4: new login page
SEQUENCE DIAGRAM FOR USER LOGIN:
1: password
2: validate
3: valid
4: user option page

System
SEQUENCE DIAGRAM FOR ENTERING DATA AND SAVING:
3: valid
4: continue
5: enter details
6: save details
7: response
8: saved

System
SEQUENCE DIAGRAM FOR UPDATING DATA:
3: valid
4: continue
5: update
6: save
7: response
8: updated

System
COLLABORATION DIAGRAM:
A pattern of interactions among instances is shown on an interaction diagram.

Interaction diagrams come in two forms based on the same underlying information,
Specified by an interaction, but each form emphasizing a particular aspect of it. The
Two forms are: sequence diagrams and collaboration diagrams. Collaboration
Diagram shows an interaction organized around the roles in the interaction and their
links to each other. Unlike a sequence diagram, a collaboration diagram shows the
relationships among the objects playing the different roles. On the other hand, a
collaboration diagram does not show time as a separate dimension, so the sequence of
interactions and the concurrent threads must be determined using sequence numbers.
Hence, sequence diagrams show the explicit sequence of stimuli and are better for
real-time specifications and for complex scenarios.
A collaboration diagram can be given in two different forms: either at

specification level (the diagram shows Classifier Roles, Association Roles, and
Messages) or atinstance level (the diagram shows Objects, Links, and Stimuli). The
former presentsthe roles and their structure as defined in the underlying Collaboration,
while the latterfocuses on instance that conforms to the roles in the Collaboration.
COLLABORATION DIAGRAM FOR CENTRAL LOGIN:

4: new login page 3: valid
COLLABORATION DIAGRAM FOR USER LOGIN:

System
1: password 2: validate
4: user option page 3: valid
COLLABORATION DIAGRAM FOR ENTERING DATA AND SAVING:

5: enter details 6: save details
4: continue 3: valid
8: saved 7: response
COLLABORATION DIAGRAM FOR UPDATING DATA:

5: update 6: save
4: continue 3: valid
8: updated 7: response

System
ACTIVITY DIAGRAM:
An activity diagram is a diagram that shows activities and actions to describe

workflows. In the Unified Modelling Language an activity diagram represents the
business and operational step-by-step workflows of components in a system. An
activity diagram shows the overall flow of control.
Activity diagrams should be used in conjunction with other modeling

techniques such as interaction diagrams and state diagrams. The main reason to use
activity diagrams is to model the workflow behind the system being designed.
Activity Diagrams are also useful for: analyzing a use case by describing what actions
need to take place and when they should occur; describing a complicated sequential
algorithm; and modeling applications with parallel processes.
However, activity diagrams should not take the place of interaction diagrams
and state diagrams. Activity diagrams do not give detail about how objects behave or
how objects collaborate.
Activity diagrams show the flow of activities through the system. Diagrams
are read from top to bottom and have branches and forks to describe conditions and
parallel activities. A fork is used when multiple activities are occurring at the same
time
Activity diagrams are typically used for business process modelling. They consist of:
 Initial node.
 Activity final node.
 Activities
The starting point of the diagram is the initial node, and the activity final node is
the ending. An activity diagram can have zero or more activity final nodes. In
between activities are represented by rounded rectangles

System
ACTIVITY DIAGRAM FOR CRIME RECORD SYSTEM

System
COMPONENT DIAGRAM:
A component type represents a distributable piece of implementation of a

system, including software code (source, binary, or executable) but also including
business documents, etc., in a human system. Components may be used to show
dependencies, such as compiler and run-time dependencies or information
dependencies in a human organization. A component instance represents a run-time
implementation unit and may be used to show implementation units that have identity
at run time, including their location on nodes.
Component diagrams are used to model the static implementation view of a

system.
To model this view, it is possible to use component diagrams in one of four ways:
1) To model source code
2) To model executable releases
3) To model physical databases
4) To model adaptable systems
A component is a physical, replaceable part that conforms to and provides the

realization of a set of interfaces. In the current component diagram of CRIME
RECORD SYSTEM, the different components used are database, user and admin. A
component diagram shows various interactions between different components. Here a
user and an administrator interact with the database in order to do certain operations.

System
COMPOENT DIAGRAM FOR CRIME RECORD SYSTEM:
crime database
record
displaying various
modules and
theirconnections to
database
users

System
DEPLOYMENT DIAGRAM:
Deployment diagram show the configuration of run-time processing nodes and

the components that live on them. They model the distribution, delivery, and
installation of the parts that make up the physical system. They involve modelling the
topology of the hardware on which the system executes.
Deployment diagrams essentially focus on a system’s nodes, and include:
a) Nodes
b) Dependencies and associations relationships
c) Components
d) Packages
The below figure depicts the deployment diagram of CRIME
RECORDSYSTEM. A deployment diagram has nodes, subsystems, objects;
interfaces etc. A deployment diagram addresses the static design view of the system.
A deployment diagram is a structural diagram which portraits the relationship
between the various hardware components.
DEPLOYMENT DIAGRAM FOR CRIME RECORD SYSTEM:
crime record database

system
web server

System
GUI DESIGN
CODE FOR NEW USER LOGIN
<%@ Page language="c#" Inherits="WebApplication4.forms.new_user_option"

CodeFile="new_user_option.aspx.cs" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >
<HTML>
<HEAD>
<title>new_user_option</title>
<meta content="Microsoft Visual Studio .NET 7.1" name="GENERATOR">
<meta content="C#" name="CODE_LANGUAGE">
<meta content="JavaScript" name="vs_defaultClientScript">
<meta content="http://schemas.microsoft.com/intellisense/ie5"
name="vs_targetSchema">
</HEAD>
<body background="file:///C:\Inetpub\wwwroot\WebApplication4\untitled.JPG">
<form id="Form1" method="post" runat="server">
<asp:button id="btnenter" style="Z-INDEX: 101; LEFT: 424px;
POSITION: absolute; TOP: 96px" runat="server"
BorderWidth="3px" BorderStyle="Outset" BorderColor="Maroon"
BackColor="#E0E0E0" Width="161"
Text="NEW CRIME RECORD"
onclick="btnenter_Click"></asp:button><asp:textbox id="txtptn" style="Z-INDEX: 105; LEFT: 8px;
Width="8px" Height="8px"
Visible="False"></asp:textbox><asp:button id="Button4" style="Z-INDEX: 104; LEFT: 424px;
BackColor="#E0E0E0" Width="161px" Text="Logoff"
onclick="Button4_Click"></asp:button><asp:button id="btnupdate" style="Z-INDEX: 103; LEFT:
424px; POSITION: absolute; TOP: 176px"
runat="server" BorderWidth="3px" BorderStyle="Outset"
BorderColor="Maroon" BackColor="#E0E0E0" Width="161" Text="UPDATE RECORDS"
onclick="btnupdate_Click"></asp:button><asp:button id="btnview" style="Z-INDEX: 102; LEFT:
424px; POSITION: absolute; TOP: 136px" runat="server"
BackColor="#E0E0E0" Width="161" Text="VIEW RECORDS"
onclick="btnview_Click"></asp:button></form>
</body>
</HTML>

System
CODE FOR ENTERING DETAILS
<%@ Page language="c#" Inherits="WebApplication4.WebForm14"

CodeFile="arrest_surrender_form.aspx.cs" %>
<HTML>
<HEAD>
<title>WebForm14</title>
</HEAD>
<body background="file:///C:\Inetpub\wwwroot\WebApplication4\8.JPG">
<asp:label id="Label1" style="Z-INDEX: 100; LEFT: 216px; POSITION:
absolute; TOP: 16px" runat="server"
Width="320px" Height="16px" Font-Size="X-Large" Font-
Italic="True" Font-Bold="True" ForeColor="Maroon"> Arrest/Surrenderd form</asp:label>
<asp:RequiredFieldValidator id="RequiredFieldValidator2" style="Z-
INDEX: 182; LEFT: 624px; POSITION: absolute; TOP: 808px"
runat="server" Width="132px" ControlToValidate="rb2"
ErrorMessage="*Select one option"></asp:RequiredFieldValidator>
<asp:RequiredFieldValidator id="RequiredFieldValidator1" style="Z-
runat="server" ControlToValidate="rb1" ErrorMessage="*Select
one option"></asp:RequiredFieldValidator>
<asp:label id="Label7" style="Z-INDEX: 180; LEFT: 64px; POSITION:
ForeColor="Black" Font-Bold="True" Width="164px">Place of
Surrendered</asp:label>
<asp:RangeValidator id="RangeValidator2" style="Z-INDEX: 179; LEFT:
runat="server" ErrorMessage="Enter Valid age"
ControlToValidate="txtaage" MaximumValue="5"
MinimumValue="100"></asp:RangeValidator><asp:dropdownlist id="ddlps" style="Z-INDEX: 178;
LEFT: 160px; POSITION: absolute; TOP: 128px" runat="server"
Width="142px" ForeColor="#804000">
<asp:ListItem Value="kukatpally">kukatpally</asp:ListItem>
<asp:ListItem Value="S.R.nagar">S.R.nagar</asp:ListItem>
<asp:ListItem Value="PanjaGutta">PanjaGutta</asp:ListItem>
<asp:ListItem Value="Jubllihills">Jubllihills</asp:ListItem>
<asp:ListItem Value="BanjaraHills">BanjaraHills</asp:ListItem>
<asp:ListItem Value="Nampally">Nampally</asp:ListItem>
<asp:ListItem
Value="TukaramGate">TukaramGate</asp:ListItem>
<asp:ListItem Value="Balanagar">Balanagar</asp:ListItem>
</asp:dropdownlist><asp:dropdownlist id="ddldist" style="Z-INDEX: 177;
LEFT: 384px; POSITION: absolute; TOP: 128px" tabIndex="1"
runat="server" Width="88px" ForeColor="#804000">
<asp:ListItem Value="Medak">Medak</asp:ListItem>
<asp:ListItem Value="RangaReddy">RangaReddy</asp:ListItem>
<asp:ListItem Value="Hyderabad">Hyderabad</asp:ListItem>
<asp:ListItem Value="Adilabad">Adilabad</asp:ListItem>
<asp:ListItem Value="Nizamabad">Nizamabad</asp:ListItem>

System
<asp:ListItem Value="Nalgonda">Nalgonda</asp:ListItem>
<asp:ListItem Value="Krishna">Krishna</asp:ListItem>
<asp:ListItem Value="Guntur">Guntur</asp:ListItem>
</asp:dropdownlist><asp:regularexpressionvalidator
id="RegularExpressionValidator1" style="Z-INDEX: 176; LEFT: 608px; POSITION: absolute; TOP:
656px"
runat="server" ValidationExpression="\d{8}"
ControlToValidate="txtaphno" ErrorMessage="Enter valid phno"></asp:regularexpressionvalidator>
<TABLE id="Table1" style="Z-INDEX: 175; LEFT: 80px; WIDTH:
496px; POSITION: absolute; TOP: 704px; HEIGHT: 75px"
cellSpacing="1" cellPadding="1" width="496" border="1">
<TR>
<TD style="WIDTH: 127px"><asp:label id="Label2"
runat="server" Width="128px" ForeColor="Maroon">Approximatly Height</asp:label></TD>
<TD style="WIDTH: 153px"><asp:textbox id="txtaht"
tabIndex="35" runat="server"></asp:textbox></TD>
runat="server" Width="48px" ForeColor="Maroon">Colour</asp:label></TD>
<TD><asp:textbox id="txtacol" tabIndex="36"
runat="server"></asp:textbox></TD>
</TR>
<TR>
<TD style="WIDTH: 127px; HEIGHT: 27px"><asp:label
id="Label17" runat="server" Width="128px" ForeColor="Maroon">Body
Language</asp:label></TD>
<TD style="WIDTH: 153px; HEIGHT:
27px"><asp:textbox id="txtabl" tabIndex="37" runat="server"></asp:textbox></TD>
<TD style="WIDTH: 9px; HEIGHT: 27px"><asp:label
id="Label14" runat="server" Width="136px" ForeColor="Maroon">Way of
Talking</asp:label></TD>
<TD style="HEIGHT: 27px"><asp:textbox id="txtawt"
</TR>
<TR>
runat="server" Width="136px" ForeColor="Maroon">Language of Criminals</asp:label></TD>
<TD style="WIDTH: 153px"><asp:textbox id="txtalan"
runat="server" Width="136px" ForeColor="Maroon">Identification Marks</asp:label></TD>
<TD><asp:textbox id="txtaid" tabIndex="40"
runat="server"></asp:textbox></TD>
</TR>
</TABLE>
<asp:radiobuttonlist id="rb2" style="Z-INDEX: 174; LEFT: 376px;
POSITION: absolute; TOP: 840px" tabIndex="42"
runat="server" Width="384px" Height="108px"
ForeColor="Maroon">
<asp:ListItem Value="Arrested & Farwarded">Arrested
& Farwarded</asp:ListItem>
<asp:ListItem Value="Arrested & Relesed on Bail">Arrested
& Relesed on Bail</asp:ListItem>
<asp:ListItem Value="Arrested & Relesed on Anticipatory
Bail">Arrested & Relesed on Anticipatory Bail</asp:ListItem>
<asp:ListItem Value="Arrested &Remanded to police
custody">Arrested &Remanded to police custody</asp:ListItem>
<asp:ListItem Value="Surrendered in Court and Bailed
out">Surrendered in Court and Bailed out</asp:ListItem>
<asp:ListItem Value="Surrendered in Court and Sent to Judicial
Custody">Surrendered in Court and Sent to Judicial Custody</asp:ListItem>

System
</asp:radiobuttonlist><asp:radiobuttonlist id="rb1" style="Z-INDEX: 173;
runat="server" Width="168px" ForeColor="Maroon">
<asp:ListItem Value="Yes">Yes</asp:ListItem>
<asp:ListItem Value="No">No</asp:ListItem>
</asp:radiobuttonlist><asp:textbox id="txtfirno" style="Z-INDEX: 172;
LEFT: 160px; POSITION: absolute; TOP: 88px" runat="server"
ReadOnly="True" Width="96px"
BackColor="#FFE0C0"></asp:textbox><asp:label id="lable1" style="Z-INDEX: 171; LEFT: 64px;
Font-Bold="True">Fir No</asp:label><asp:dropdownlist
id="ddlam_pm" style="Z-INDEX: 170; LEFT: 408px; POSITION: absolute; TOP: 208px"
tabIndex="8" runat="server" Width="80px"
ForeColor="#804000">
<asp:ListItem Value="AM">AM</asp:ListItem>
<asp:ListItem Value="PM">PM</asp:ListItem>
</asp:dropdownlist><asp:label id="Label20" style="Z-INDEX: 169; LEFT:
Font-Bold="True" ForeColor="Black">Accused Person's Current
Position:</asp:label><asp:label id="Label9" style="Z-INDEX: 168; LEFT: 40px; POSITION:
Font-Bold="True" ForeColor="Black">Whether Accused Person's
Finger Prints Taken :</asp:label><asp:label id="Label16" style="Z-INDEX: 167; LEFT: 40px;
Font-Bold="True" ForeColor="Black">Physical Appearence of
Accused Person :</asp:label><asp:dropdownlist id="DropDownList7" style="Z-INDEX: 162; LEFT:
runat="server" Width="40px"
ForeColor="#804000"></asp:dropdownlist><asp:dropdownlist id="DropDownList6" style="Z-
ForeColor="#804000"></asp:dropdownlist><asp:dropdownlist id="ddlmin" style="Z-INDEX: 166;
ForeColor="#804000"></asp:dropdownlist><asp:dropdownlist id="ddlhr" style="Z-INDEX: 165;
ForeColor="#804000"></asp:dropdownlist><asp:dropdownlist id="ddlyear" style="Z-INDEX: 164;
ForeColor="#804000"></asp:dropdownlist><asp:dropdownlist id="ddlday" style="Z-INDEX: 163;
ForeColor="#804000"></asp:dropdownlist><asp:dropdownlist id="ddlmonth" style="Z-INDEX: 161;
LEFT: 144px; POSITION: absolute; TOP: 208px"
ForeColor="#804000"></asp:dropdownlist><asp:textbox id="txtaphno" style="Z-INDEX: 159; LEFT:
tabIndex="34" runat="server"
Width="108px"></asp:textbox><asp:label id="Label78" style="Z-INDEX: 158; LEFT: 504px;
ForeColor="Maroon">PHONE No</asp:label><asp:textbox
id="txtastate" style="Z-INDEX: 157; LEFT: 392px; POSITION: absolute; TOP: 624px"
ForeColor="Maroon">State</asp:label><asp:textbox id="txtacity"
style="Z-INDEX: 155; LEFT: 160px; POSITION: absolute; TOP: 624px"

System
ForeColor="Maroon">City/District</asp:label><asp:textbox
id="txtaarea" style="Z-INDEX: 153; LEFT: 600px; POSITION: absolute; TOP: 592px"
Width="108px"></asp:textbox><asp:button id="Button2" style="Z-INDEX: 152; LEFT: 72px;
runat="server" Width="160px" Text="Save& Continue"
BackColor="#E0E0E0" BorderColor="Maroon" BorderStyle="Outset" BorderWidth="3px"
onclick="Button2_Click"></asp:button><asp:textbox id="txtanat" style="Z-INDEX: 151; LEFT:
600px; POSITION: absolute; TOP: 560px" tabIndex="28"
runat="server" Width="108px"></asp:textbox><asp:textbox
id="txtastr" style="Z-INDEX: 150; LEFT: 392px; POSITION: absolute; TOP: 592px" tabIndex="30"
id="txthno" style="Z-INDEX: 149; LEFT: 160px; POSITION: absolute; TOP: 592px" tabIndex="29"
runat="server" Width="108px"></asp:textbox><asp:label
id="Label74" style="Z-INDEX: 148; LEFT: 504px; POSITION: absolute; TOP: 592px" runat="server"
ForeColor="Maroon">Area/Mondal</asp:label><asp:label
ForeColor="Maroon">Street/Village</asp:label><asp:label
ForeColor="Maroon">H.No</asp:label><asp:textbox id="txtacat"
style="Z-INDEX: 145; LEFT: 600px; POSITION: absolute; TOP: 528px" tabIndex="25"
id="txtaage" style="Z-INDEX: 144; LEFT: 392px; POSITION: absolute; TOP: 560px" tabIndex="27"
id="txtagender" style="Z-INDEX: 143; LEFT: 160px; POSITION: absolute; TOP: 560px"
Width="108px"></asp:textbox><asp:textbox id="txtafname" style="Z-INDEX: 142; LEFT: 600px;
POSITION: absolute; TOP: 496px"
Width="108px"></asp:textbox><asp:textbox id="txtacaste" style="Z-INDEX: 141; LEFT: 392px;
ForeColor="Maroon">nationality</asp:label><asp:label
ForeColor="Maroon">Age</asp:label><asp:label id="Label69"
style="Z-INDEX: 138; LEFT: 80px; POSITION: absolute; TOP: 560px" runat="server"
ForeColor="Maroon">Gendor</asp:label><asp:label id="Label68"
ForeColor="Maroon">Category</asp:label><asp:label
ForeColor="Maroon">Caste</asp:label><asp:textbox id="txtaocc"
style="Z-INDEX: 135; LEFT: 160px; POSITION: absolute; TOP: 528px" tabIndex="23"
id="txtaname" style="Z-INDEX: 134; LEFT: 392px; POSITION: absolute; TOP: 496px"
Width="108px"></asp:textbox><asp:textbox id="txtano" style="Z-INDEX: 133; LEFT: 160px;
id="txtcstate" style="Z-INDEX: 132; LEFT: 392px; POSITION: absolute; TOP: 416px"
ForeColor="#804000"></asp:textbox><asp:textbox id="txtccity" style="Z-INDEX: 131; LEFT:
ForeColor="#804000"></asp:textbox><asp:textbox id="txtcarea" style="Z-INDEX: 130; LEFT:

System
ForeColor="#804000"></asp:textbox><asp:textbox id="txtcvil" style="Z-INDEX: 129; LEFT: 168px;
ForeColor="#804000"></asp:textbox><asp:label id="Label33" style="Z-INDEX: 128; LEFT: 64px;
Font-Bold="True" ForeColor="Black">Accused Person Details
:</asp:label><asp:label id="Label65" style="Z-INDEX: 127; LEFT: 80px; POSITION: absolute; TOP:
528px" runat="server"
ForeColor="Maroon">Occupation</asp:label><asp:label
ForeColor="Maroon">Father's Name</asp:label><asp:label
ForeColor="Maroon">Name</asp:label><asp:label id="Label62"
ForeColor="Maroon">Serial No:</asp:label><asp:label
ForeColor="#804000">State</asp:label><asp:label id="Label59"
ForeColor="#804000">City/Dist</asp:label><asp:label
ForeColor="#804000">Area/Mondal</asp:label><asp:label
ForeColor="#804000">Street/Village</asp:label><asp:textbox
id="txtstate" style="Z-INDEX: 119; LEFT: 512px; POSITION: absolute; TOP: 280px"
tabIndex="14" runat="server" Width="109"
ForeColor="#804000"></asp:textbox><asp:textbox id="txtdis" style="Z-INDEX: 118; LEFT: 328px;
ForeColor="#804000"></asp:textbox><asp:textbox id="txtmon" style="Z-INDEX: 117; LEFT: 144px;
runat="server" Width="109"
ForeColor="#804000"></asp:textbox><asp:textbox id="txtvil" style="Z-INDEX: 116; LEFT: 512px;
runat="server" Width="109"
ForeColor="#804000"></asp:textbox><asp:textbox id="txtstr" style="Z-INDEX: 115; LEFT: 328px;
ForeColor="#804000"></asp:textbox><asp:textbox id="txtplace" style="Z-INDEX: 114; LEFT:
tabIndex="9" runat="server" Width="109"
Width="56px" ForeColor="#804000">State</asp:label><asp:label
Width="56px"
ForeColor="#804000">Distrct</asp:label><asp:label id="Label42" style="Z-INDEX: 111; LEFT:
Width="48" ForeColor="#804000">Mandal</asp:label><asp:label
Width="56px"
ForeColor="#804000">Village</asp:label><asp:label id="Label40" style="Z-INDEX: 109; LEFT:
Width="56px" ForeColor="#804000">Street</asp:label><asp:label
Width="48px"
ForeColor="#804000">Place</asp:label><asp:textbox id="txtcname" style="Z-INDEX: 107; LEFT:

System
ForeColor="#804000">Name of The Court if
Surrendered</asp:label><asp:label id="Label11" style="Z-INDEX: 105; LEFT: 64px; POSITION:
Font-Bold="True" ForeColor="Black"> Place, date&Time of
arrest</asp:label><asp:label id="Label6" style="Z-INDEX: 104; LEFT: 64px; POSITION: absolute;
TOP: 128px" runat="server"
ForeColor="#804000"> Police Station</asp:label><asp:label
Width="32px" Height="16px" ForeColor="#804000">
Dist</asp:label><asp:label id="Label4" style="Z-INDEX: 102; LEFT: 288px; POSITION: absolute;
TOP: 208px" runat="server"
Font-Bold="True"
ForeColor="#804000">Time</asp:label><asp:label id="Label3" style="Z-INDEX: 101; LEFT: 80px;
Font-Bold="True"
ForeColor="#804000">Date</asp:label></form>
</body>
</HTML>

System
CODE FOR VIEWING FULL DETAILS
<%@ Page language="c#" Inherits="WebApplication4.Reports.fulldetails"

CodeFile="fulldetails.aspx.cs" %>
<HTML>
<HEAD>
<title>fulldetails</title>
</HEAD>
<body bgColor="papayawhip">
<asp:linkbutton id="lbpropsiezed" style="Z-INDEX: 111; LEFT: 32px;
onclick="lbpropsiezed_Click">Property Seezed</asp:linkbutton>
<asp:Label id="Label1" style="Z-INDEX: 117; LEFT: 248px; POSITION:
Font-Size="Large" Font-Bold="True" ForeColor="#804040" Font-
Italic="True">FULL DETAILS OF CASE</asp:Label>
<asp:linkbutton id="lbfir" style="Z-INDEX: 116; LEFT: 32px; POSITION:
Height="20px" Width="145px" onclick="lbfir_Click">First
Information</asp:linkbutton>
<asp:Image id="Image1" style="Z-INDEX: 115; LEFT: 648px; POSITION:
Height="120px" Width="121px"
ImageUrl="file:///C:\Inetpub\wwwroot\WebApplication4\d.jpg"></asp:Image>
<asp:Button id="Button2" style="Z-INDEX: 114; LEFT: 200px;
Width="144px" Text="Main Page" BackColor="#E0E0E0"
BorderColor="#804000" BorderStyle="Outset"
BorderWidth="3px" onclick="Button2_Click"></asp:Button>
<asp:Button id="Button1" style="Z-INDEX: 113; LEFT: 200px;
Width="144px" Text="Back" BackColor="#E0E0E0"
BorderColor="#804000" BorderStyle="Outset"
BorderWidth="3px" onclick="Button1_Click"></asp:Button>
<asp:Label id="lbldis" style="Z-INDEX: 112; LEFT: 352px; POSITION:
BackColor="Transparent" ForeColor="Red" Font-Bold="True"
Font-Size="Medium"></asp:Label><asp:linkbutton id="lbcompdet" style="Z-INDEX: 110; LEFT:
onclick="lbcompdet_Click">Complainant</asp:linkbutton><asp:linkbutton id="lboofoffence"
onclick="lboofoffence_Click">Occurence of Offence</asp:linkbutton><asp:linkbutton
id="lbrofappeal" style="Z-INDEX: 108; LEFT: 32px; POSITION: absolute; TOP: 360px"
onclick="lbrofappeal_Click">Result of Appeal</asp:linkbutton><asp:linkbutton id="lbproperty"

System
onclick="lbproperty_Click">Property</asp:linkbutton><asp:linkbutton id="lbcrtdis" style="Z-INDEX:
106; LEFT: 32px; POSITION: absolute; TOP: 200px" runat="server"
Width="145px" Height="20px" onclick="lbcrtdis_Click">Court
Disposal</asp:linkbutton><asp:linkbutton id="lbcrimedet" style="Z-INDEX: 105; LEFT: 32px;
onclick="lbcrimedet_Click">Crime Details</asp:linkbutton><asp:linkbutton id="lbarr_suren"
onclick="lbarr_suren_Click">Arrest/Surrendered</asp:linkbutton><asp:linkbutton id="lbact_sec"
onclick="lbact_sec_Click">Act&Section</asp:linkbutton><asp:linkbutton id="lbaccusedperson"
onclick="lbaccusedperson_Click">Accused Person</asp:linkbutton>
<asp:DataGrid id="DataGrid1" style="Z-INDEX: 101; LEFT: 200px;
BackColor="Thistle"></asp:DataGrid>
</form>
</body>
</HTML>

System
LIST OF TABLES
Accused details table:
Act Section:

System
Arrest Surrender:
Complain Details:

System
Court disposal details
Crime Details

System
Occurrence Details
Property Details
Property seized details

System
Result of appeal
Section Act
New login table

System
CODING

System
Code For New User Login
using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using System.Configuration;
namespace WebApplication4.forms
{
public partial class newloginpage : System.Web.UI.Page

{
protected void Page_Load(object sender, System.EventArgs e)

{
Session["position"]=ddlpos.SelectedItem.Text;
}
#region Web Form Designer generated code

override protected void OnInit(EventArgs e)
{
InitializeComponent();
base.OnInit(e);
}
#endregion
SqlConnection con=new
SqlConnection("server=.;uid=sa;database=crpt");
protected void Button1_Click(object sender, System.EventArgs e)
{
con.Open();
SqlDataReader rd;
string cmdl="select * from new_login where userid='
txtuid.Text.Trim() + "' and password='"+txtpass.Text.Trim()+
"'and user_position='" +ddlpos.SelectedItem.Text.Trim()+ "'";
SqlCommand cmd=new SqlCommand(cmdl,con);
rd=cmd.ExecuteReader();
if(rd.Read())
{
Response.Redirect("new_user_option.aspx");

System
}
else
{
lbl.Visible=true;
}
}

{
Response.Redirect("loginmain.aspx");
}
}
}
CODE FOR ENTERING DETAILS
using System;
using System.Data;
using System.Web;
namespace WebApplication4.forms
{
public partial class WebForm7 : System.Web.UI.Page
{
protected System.Web.UI.WebControls.DropDownList
DropDownList3;
protected System.Web.UI.WebControls.DropDownList
DropDownList4;

{
base.OnInit(e);
}
private void InitializeComponent()

{

System
this.DataGrid1.ItemCommand += new
System.Web.UI.WebControls.DataGridCommandEventHandler(this.DataGrid1_Item
Command);
}
#endregion
SqlConnection(ConfigurationSettings.AppSettings["con"]);
int j=0;
int cnt=0;
DataSet ds;
public string section;
public string act;
public string grave;
public string punishable;
{
if(!IsPostBack)
{
txtfirno.Text=Session["Firno"].ToString().Trim();
lbldisdate.Text=DateTime.Now.ToString();
ds=new DataSet();
SqlDataAdapter adp=new SqlDataAdapter("select *
from sections_acts",con);
adp.Fill(ds);
Session["dss"]=ds;
cnt=ds.Tables[0].Rows.Count;
for(j=0;j<cnt;j++)
{
ddlact.Items.Add(ds.Tables[0].Rows[j].ItemArray[1].ToString());
ddlsection.Items.Add(ds.Tables[0].Rows[j].ItemArray[3].ToString());
}
}
}
protected void ddlsection_SelectedIndexChanged(object sender,

System.EventArgs e)
{
int a=ddlsection.SelectedIndex;
DataSet ds1=(DataSet)Session["dss"];
section=ds1.Tables[0].Rows[a].ItemArray[4].ToString();
txtsectiondesc.Text =section;
act=ds1.Tables[0].Rows[a].ItemArray[2].ToString();
txtactdesc.Text =act;
grave=ds1.Tables[0].Rows[a].ItemArray[5].ToString();
txtgrave.Text=grave;

System
punishable=ds1.Tables[0].Rows[a].ItemArray[6].ToString();
txtpunishable.Text=punishable;
}
protected void btnadd_Click(object sender, System.EventArgs e)

{
if(con.State==ConnectionState.Closed)
con.Open();
SqlDataReader rd;
SqlCommand cmd=new SqlCommand("insert into
temp_acts_sections values('"+txtfirno.Text.Trim()
+"','"+lbldisdate.Text+"','"+ddldist.SelectedItem.Text+"','"+ddlps.SelectedItem.Text+"
','"+ddlact.SelectedItem.Text+"','"+txtactdesc.Text+"','"+ddlsection.SelectedItem.Text
+"','"+txtsectiondesc.Text+"','" +(txtgrave.Text.Trim())+ "','" +
(txtpunishable.Text.Trim())+"') ",con);
rd=cmd.ExecuteReader(CommandBehavior.CloseConnection);
rd.Close();
con.Open();
SqlDataAdapter adp=new SqlDataAdapter("select * from
temp_acts_sections",con);
DataSet ds=new DataSet();
adp.Fill(ds);
DataGrid1.DataSource=ds;
DataGrid1.DataBind();
}
protected void btnsave_Click(object sender, System.EventArgs e)

{
try
{
con.Open();
SqlCommand cmd=new SqlCommand("insert into
act_section select * from temp_acts_sections",con);
cmd.ExecuteNonQuery();
}
catch(SqlException ex)
{
Response.Write(ex.ToString());
}
con.Open();
SqlDataReader rd1;
SqlCommand cmd1=new SqlCommand("delete from
rd1=cmd1.ExecuteReader(CommandBehavior.CloseConnection);

System
rd1.Close();
Response.Redirect("complainant_details.aspx");
}
private void DataGrid1_ItemCommand(object source,

System.Web.UI.WebControls.DataGridCommandEventArgs e)
{
con.Open();
string secno=e.Item.Cells[2].Text;
Response.Write(secno.ToString());
SqlCommand cmd=new SqlCommand("delete from
temp_acts_sections where sec='"+secno.Trim()+"'",con);
cmd.ExecuteNonQuery();
SqlDataReader rd;
SqlCommand cmd1=new SqlCommand("select * from
rd=cmd1.ExecuteReader();
DataGrid1.DataSource=rd;
con.Close();
}
}
}
CODE FOR VIEWING FULL DETAILS
using System;

System
using System.Data;
using System.Web;
namespace WebApplication4.Reports
{
public partial class fulldetails : System.Web.UI.Page
{
SqlConnection(ConfigurationSettings.AppSettings["con"]);
string fir;
SqlDataAdapter adp;
DataSet ds=new DataSet();
{
fir=Session["Firno"].ToString();
}

{
base.OnInit(e);
}
private void InitializeComponent()

{
}
#endregion
protected void lbaccusedperson_Click(object sender,

System.EventArgs e)
{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from accused_details where
firno='" +fir+"'",con);

System
adp.Fill(ds);
if(ds.Tables[0].Rows.Count==0)
{
lbldis.Text="No Records Found";
DataGrid1.Visible=false;
}
else
{
DataGrid1.Visible=true;
}
ds.Reset();
}
protected void lbact_sec_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from act_section where
firno='"+fir+"'",con);
adp.Fill(ds);
{
}
else
{
}
ds.Reset();
}
protected void lbarr_suren_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from
arrest_surrendered_details where firno='"+fir+"'",con);
adp.Fill(ds);
{

System
}
else
{
}
ds.Reset();
}
protected void lbcompdet_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from complainant_details
where firno='"+fir+"'",con);
adp.Fill(ds);
{
}
else
{
}
ds.Reset();
}
protected void lbcrtdis_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from courtdisposal_details
where firno='"+fir+"'",con);
adp.Fill(ds);
{
}
else
{

System
}
ds.Reset();
}
protected void lbcrimedet_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from crime_details where
adp.Fill(ds);
{
}
else
{
}
ds.Reset();
}
protected void lboofoffence_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from occurancedetails where
adp.Fill(ds);
{
}
else
{
}

System
ds.Reset();
}
protected void lbproperty_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from property_details where firno='"+fir+"'",con);
adp.Fill(ds);
{
}
else
{
}
ds.Reset();
}
protected void lbpropsiezed_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from property_seezed_details where
adp.Fill(ds);
{
}
else
{
}
ds.Reset();
}

System
protected void lbrofappeal_Click(object sender, System.EventArgs e)
{
lbldis.Text="";
ds.Reset();
con.Open();
adp=new SqlDataAdapter("select * from resultof_appeal where
adp.Fill(ds);
{
}
else
{
}
ds.Reset();
}

{
Response.Redirect("reports.aspx");
}

{
Response.Redirect("../forms/new_user_option.aspx");
}
protected void lbfir_Click(object sender, System.EventArgs e)

{
lbldis.Text="";
ds.Reset();
con.Open()
adp=new SqlDataAdapter("select * from fir_information where firno='"
+fir+"'",con);
adp.Fill(ds);
{
}
else
{

System
}
ds.Reset();
}
}
}

System
TESTING
TESTING

System
Software testing is critical element of Software Quality Assurance and
represents the ultimate review of the specifications, design and coding. Testing is a
process of executing a program with the intent of finding an error.
Objectives:
The main objective of testing is to uncover a host of errors, systematically and

with minimum amount of efforts and time. A successful test is one that covers an
undiscovered error. A good test case is one that has a high probability of finding error,
if it exists.
Unit Testing:
In this testing each module of the project is tested to provide its correctness,
validity and also determines any missing operation and to verify whether the
objectives have been met. Errors are noted down and corrected immediately.
Each and every unit is subjected to through unit testing and once it is found error free,
it is taken to the next stage, which is integration to other units.
Integration testing:
The integration testing is performed because; it need not be the case, the software
whose modules when run individually and showing perfect results, will also show
perfect results when run as a whole. This is basically a systematic technique for
constructing the program structure and conducting tests to uncover errors associated
with interfacing. The objective is to take unit-tested modules and to build a program
structure that has been dictated by design.
After the integration is completed system testing is performed. A system plan is

prepared which provides a summary of the approaches to be used for system testing
including the features that have to be tested, how the testing has to be organized, the
tasks that have to be organized.
Top-down Integration:

System
Top down integrations is an incremental approach for construction of program
structure. Modules are integrated by moving downward through the control
hierarchy, beginning with the main control program. Modules subordinate to the
main program are incorporated in the structure either in the breath-first or depth-first
manner.
Bottom-up Integration:
This method as the name suggests, begins construction and testing with atomic
modules i.e., modules at the lowest level. Because the modules are integrated in the
bottom up manner the processing required for the modules subordinate to a given
level is always available and the need for stubs is eliminated.
Validation Testing:
At the end of integration testing software is completely assembled as a

package. Validation testing is the next stage, which can be defined as successful
when the software functions in the manner reasonably expected by the customer.
Reasonable expectations are those defined in the software requirements specifications.
Information contained in those sections form a basis for validation testing approach.
System Testing:
System testing is actually a series of different tests whose primary purpose is

to fully exercise the computer-based system. Although each test has a different
purpose, all work to verify that all system elements have been properly integrated to
perform allocated functions.
Security Testing:
Attempts to verify the protection mechanisms built into the system.
Performance Testing:
This method is designed to test runtime performance of software within the

context of an integrated system.
IMPLEMENTATION

System
Softwares required for running crime record system application are
1) Microsoft .Net 2008

2) SQL Server 2000
 To install microsoft .net 2008
1) Insert the Microsoft .Net2008 cd in the cd rom.

2) A welcome window appears, after loading of the page click next.
3) Enter the product key which is written on the cd cover.
4) From the Software License Agreement window, read the agreement, and click
yes if you agree with the terms.
5) A new dialog box appears, here select the directory location where you want
to install the software, and select the type of installation you want to install
select Full which installs all features of the porduct.
Click install.
6) The installatioon starts, after completion click finish
 To install Microsoft SQL Server 2000 Enterprise Edition, follow these steps on
the database server and the history server.
1) Insert the Microsoft SQL Server 2000 Enterprise Edition CD and click SQL
Server 2000 Components.
2) Click Install Database Server.
The Microsoft SQL Server 2000 Enterprise Edition setup begins. Click Next.
3) From the Welcome window, click Next.
4) From the Computer Name window, click Local Computer and Next.
5) From the Installation Selection window, click Create a new instance of SQL
Server or Install Client Tools. Click Next.
6) From the User Information window, type your name and company. Click
Next.
7) From the Software License Agreement window, read the agreement, and click
yes if you agree with the terms.
From the Installation Definition window, click Server and Client Tools. Click
Next.
8) From the Instance Name window, make sure the Default check box is selected
and click Next.

System
9) From the Setup Type window, click Custom, click both Browse buttons and
use C:\ as the destination directory for the program files and data files. This
causes your SQL Server 2000 program files and data files to be placed in the
C:\MSSQL directory. Click Next.
10) From the Select Components window, accept all the default components and
subcomponents. Click Next.
11) From the Services Accounts window, keep the default value Use the same
account for each service.
For Service Settings, click Use a Domain User account. Type the username,
password and domain information for a user that has administrative rights
across all Tivoli Business Systems Manager servers.Click Next.
12) From the Authentication Mode window, click Mixed Mode (Windows
Authentication and SQL Authentication) and type the SQL sa password.
13) From the Collation Settings window, click Collation designator and click
Latin1_General. Select Binary as the Sort Order. (You must click Binary as
the sort order for Tivoli Business Systems Manager to function correctly.)
Click Next.
14) From the Network Libraries window, accept the default values for Named
Pipes and Named Pipe name and TCP/IP Sockets. Select both Multi-Protocol
and Enable Multi-Protocol encryption. Click Next.
15) When the Start Copying Files window opens, click Next to continue with the
installation. If you want to change any parameters, click Back.
When you click Back, selections reset back to their default values. If you click
Back at any time during the installation, make sure you reselect the values you
wanted before clicking Next.
16) From the Choose Licensing Mode window, click Processor License for. Type
the number of processors you need for your machine. Click Continue.
17) From the Setup Complete window, click Finish.
After installing the softwares follow these steps.

System
 From the webapplication 4 folder select the database folder then copy the .mdf
files and paste it in the SQL server folder, if its installed in the C drive then paste
it in the following folder.
C:\Program Files\Microsoft SQL Server\MSSQL\Data
 Click start, programs, microsoft SQL server then click enterprise manager.
Here, right click the database and attach the file which was pasted in the above
folder. Close the sql server.
 To run the application on the system follow these steps:
1) Click start, programs, microsoft visual studio 2008, click microsoft visual
studio 2008.
2) Click flie, open, wesite, selcet the webapplication4 folder from the
computer.
3) The website is opened in the solution explorer.
4) In the solution explorer right click the login.aspx and set as start page and
click F5 or click debug.
5) This will start the application.

System
SCREENS

System

System

System

System

System

System

System

System

System

System

System

System

System

System
REPORTS

System

System

System

System

System

System

System

System
UPDATES

System

System

System

System

System

System

System

System

System

System

System
CONCLUSION
 The project has been appreciated by all the users in the organization.

System
 It is easy to use, since it uses the GUI provided in the user dialog.
 User friendly screens are provided.
 The usage of software increases the efficiency, decreases the effort.
 It has been efficiently employed as a Task management mechanism.
 It has been thoroughly tested and implemented.

System
BIBILOGRAPHY
SOFTWARE ENGINEERING
By Mr.HariNath
Professional ASP.NET 1.1
By Wrox
MSDN 2002
By Microsoft
WEB SITES
www.msdn.com
www.w3schools.com

Project Report Crime Record System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Report Crime Record System

Uploaded by

Copyright:

Available Formats

Project Report Crime Record

1.1 Introduction To The Project 3

2.1 Purpose of The System 6

2.2 Objectives of the Project 6

3.1 Existing And Problems In Existing System 8

3.2 Proposed System 9

3.3 Benefits To The Organization 10

3.5 System Requirement Specification 13

3.6 Feasibility Study 14

3.7 Technical Specification 16

4.1 UML Diagrams 35

4.2 GUI Design 51

4.3 Database Tables 60

10. BIBILOGRAPHY 120

Computer Science Department Page 1

Computer Science Department Page 2

Some of the basic users (police) perspectives of our project are:

Here we have three positions,

Computer Science Department Page 3

Computer Science Department Page 4

Computer Science Department Page 5

The purpose of this application “CRIME RECORD SYSTEM” is to improve the

The objectives of the CRIME RECORD SYSTEM are:

 To study similarities in the Modus Operandi of criminals and on its basis

Computer Science Department Page 6

Computer Science Department Page 7

PROBLEMS IN THE EXISTING SYSTEM

 Difficult to identify the records

 Tracing errors is impossible

Computer Science Department Page 8

This application envisages information sharing within the organization and

3. Property Search & Seizure

6. Court Disposal (adult, juvenile, punishment)

7. Result of Appeals

Effective coordination among different departments / entities in criminal justice

Computer Science Department Page 9

Benefits to the Organization:

Computer Science Department Page 10

 There is a need to create a comprehensive categorization for the entities of

 The system needs to provide for a Comprehensive Querying mechanism which

 What is the current status of Case X?

 Status of Completion of evidence gathering

 Status of Completion of questioning of suspects

 Modus operandi established

Computer Science Department Page 11

 Does Suspect A have a previous criminal record?

 What crimes have been committed by Suspect B?

 Give a listing of crimes committed with Modus Operandi O.

Computer Science Department Page 12

SYSTEM REQUIREMENT SPECIFICATIONS

Processor speed: 600 MHz

Operating systems: windows 2000server

Frame work : 2.0 and above

Front end : ASP.net

Back end : SQL server 2000

Computer Science Department Page 13

A feasibility analysis usually involves a through assessment of the financial

A system development project may be regarded as technically feasible or

Organization s will need to make this assessment based on:

 Knowledge of the current and emerging technological solutions.

Computer Science Department Page 14

A system development project is likely to be operationally feasible if it meets

Computer Science Department Page 15