1.

INTRODUCTION

We are developing a WEBSITE ON E-POLICE AND INFORMATION. This includes missing citizen search, secure registration and profile management facilities for detectives and security agencies, Facilitate users with the help of Discussion/forum/mail/Online FIR, etc. This system also contains information about all judiciary acts. With so many branches and roots of the Indian Judicial System, it became very important to have a more organized, systematic and an engineered Indian Judiciary, which could make the functioning of the justice system smooth, convenient and fast for a common man.

Users of the system:

Citizens: Interact with the portal. They can use forum\acts\mailing\online FIR facility. And can view missing persons details, online FIRs, forum question answers, mails, etc. Indirect Users: Benefits from the results or reports produced by these systems but do not directly interact with the hardware or software. These users may be managers of business functions using the system. End-Users: Are not alike. Some are intermittent users. The end-user can also be a competitor, not a part of the system. Senior Manager Users (Admin): Are fourth types of users and is talking increased responsibility for the maintenance and development of information systems.

3.1 PROBLEM DEFINITION

Basically the system offers the user to get more reliable services. E-POLICE and information deals with several modules such as missing person search, computerized and online FIR, forum, information of various Acts and sections, mailing, etc. The system being online is not subjected to small group of people. It facilitates user to perform various activities online which in turn save time, money and power; the constraint that the user must have valid user name and password. User gets login-id with the process of signup.

Requirement Analysis:
Requirement Analysis is done to determine the requirement for the new system from user. Requirement analysis is one of the most important parts of the designing process. It consists of gathering requirement for new system. After understanding problem domain requirement analysis can be carried out. To develop user friendly system, requirement analysis determines the output needed, inputs required to obtain these outputs, resources to be used etc. The method for collecting data is called fact-finding techniques. Various fact finding techniques used in system were: Interviews: Unstructured interview method was used which included questionanswer format to acquire information about new system, the respondent being users of proposed system, facts about actual requirements and expected results etc. were gathered. Observation: An observation was made of how actually various activities are conducted, which helped to understand over all flow of the system. And thus, gave idea of which all process must be included in new system.

3.2

EXISTING SYSTEM

The existing system is manual and is a very slow process, due to which there are some drawbacks in the existing system:1. The Existing system engages many people for collecting the data of different departments. 2. The Process of analyzing and searching the data is complex and time consuming. 3. All information needs to be kept in the form of paper documents, which leads to loss of accuracy. 4. There is big chance of manual mistakes. 5. Wrong data may lead to wrong decision making.

3.3

NEED FOR THE NEW SYSTEM/PROPOSED SYSTEM

In order to quantify the benefits of your e-POLICE portal, you first have to know what to look for. E-POLICE AND INFORMATION can help you in different ways. Here are some of the areas to look for benefits in implementing a portal:

Paper Reduction:
E-POLICE AND INFORMATION can reduce the cost associated with creating and distributing paper requirements and resumes. Cost savings result from: Direct savings from reduced paper, printing, and distribution costs Indirect savings from time spent handling paper documents

Paperwork Transfer:
A big expense with a manually maintaining records and requirement system is that of transferring of records from one person to another. For example, the file works is no not been done by hands but is done online, reducing the communication expenses.

Improved Data Quality:

Manual records must be then entered into a computer in order to be processed for further process or may be maintained into database for future requirement. Whenever data is keyed into a computer from a hand-written document, errors will be made. These errors can cost you in many direct and indirect ways: Incorrect selection may take place. When wrong justification is done due to manual errors and adjustment is costly for system. Without accurate information, you lose the ability to perform useful decision support. You should have accurate information about the background of the case as well as the crime, departments worked in, areas the organization is working in etc. for your decision support.

Transparency:
The work of judicial system is not transparent these days. This is an initiative to make the progress transparent.

Fewer Inquiries :
A good automated system will provide useful information to the citizens, Detectives and Defense officials online, that they traditionally request from the store departments. By making this information available online, your store departments will spend less time answering questions from citizens and officials.

3.4

PROPOSED SYSTEM

We are developing a WEBSITE ON E-POLICE AND INFORMATION. This includes missing citizen search, online FIR filing, secure registration and profile management facilities for detectives and security agencies; facilitate users with the help of Discussion/forum/mail/etc. This system also contains information about all judiciary acts. With so many branches and roots of the Indian Judicial System, it became very important to have a more organized, systematic and an engineered Indian Judiciary, which could make the functioning of the justice system smooth, convenient a fast for a common man.

Users of the system:

Citizens: Interact with the portal. They can use forum\acts\mailing\online FIR facility. And can view missing persons details, online FIRs, forum question answers, mails, etc. Indirect Users: Benefits from the results or reports produced by these systems but do not directly interact with the hardware or software. These users may be managers of business functions using the system. End-Users: Are not alike. Some are intermittent users. The end-user can also be a competitor, not a part of the system. Senior Manager Users (Admin): Are fourth types of users and is talking increased responsibility for the maintenance and development of information systems.

3.5

SCOPE OF THE SYSTEM

Admin will manage all the information. It is the super user of the system. Admin have all the privileges to do anything in the system and maintain the database.

User can create his own account and he can also modify his account. After creating account user get the facility of forum, mail, online FIR, missing person search, so on.

Following facility is provided to user with the help of forum: User can ask the questions View other user questions Update his questions Can reply the questions Delete the answer.

The system contains information of all Judiciary Acts. Users can access this information and can gain knowledge of different types of crimes and their respective punishments.

Users can send and receive mails from different users. Contain details of missing person and their contact information. Users can also see their filed FIR online.

3.6

FEASIBILITY STUDY

Feasibility Study of the system is done to ensure that the proposed system is consistent with the objective of the organization before it can be approved for development. A complete feasibility study highlights both, the benefits of the system to the organization and the inherent risks in the development and implementation of the proposed system.

A preliminary investigation was done to determine whether the proposed system would have the features expected by end-user and would be providing something extra and useful than the current system which would make the system simpler for the end user to use.

Efforts that are made to study the benefits gained from the system could be defined in terms of: Economical Feasibility. Technical Feasibility. Operational Feasibility.

ECONOMICAL FEASIBILITY:
This is done to verify whether the new system, which is to be developed is good investment for the organization. For the customer, the benefits obtained should be substantially greater than the cost of development of the system. Presentation software system was developed using the existing resources with little additional resources. Hence the system is Economically Feasible.

TECHNICAL FEASIBILITY:
This basically deals with the technological aspects of the system. In this phase the reliability, technology, performance, maintainability is studied. Investigation of adequate available technology, hardware, software, operating time and support facility was conducted in order to achieve technical feasibility. The system is designed to exploit the resources in an efficient and effective and hence technically there is no problem other than having a PC anticipated. Hence the system is Technically Feasible.

OPERATIONAL FEASIBILITY:
This test of feasibility determines if the system will perform well after it has been installed at users site and will fulfill the user requirements. This feasibility is proved by customizing the product as per users requirements and suggestions.

3.7

HARDWARE AND SOFTWARE CONFIGURATIONS

Hardware Specification
For this system the minimum hardware requirement is as mentioned bellow: Processor : Pentium 4 RAM : 1 GB or above

Hard Disk : 20 GB

Software Specification
For this system the minimum software requirement is as mentioned bellow: Platform Front End Back End : Windows XP or Windows server 2003 : ASP.NET 3.0 using C# : MS SQL Server 2005

Web Browser : Mozilla Firefox or Internet Explorer (Used Softwares: Microsoft Visual Studio 2008, IIS, SQL Server 2005, Windows service pack2, .NET Frame work 3.0)

INTRODUCTION TO .NET FRAMEWORK

The Microsoft .NET Framework is a software framework that can be installed on computers running Microsoft Windows operating systems. It includes a large library of coded solutions to common programming problems and a virtual machine that manages the execution of programs written specifically for the framework. The .NET framework supports multiple programming languages in a manner that allows language interoperability, whereby each language can utilize code written in other languages; in particular, the .NET library is available to all the programming languages that .NET encompasses. The .NET Framework is a Microsoft offering and is intended to be used by most new applications created for the Windows platform. The framework's Base Class Library provides a large range of features including user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. The class library is used by programmers, who combine it with their own code to produce applications. Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. Also part of the .NET Framework, this runtime environment is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine so that programmers need not consider the capabilities of the specific CPU that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together constitute the .NET Framework. Interoperability Because interaction between new and older applications is commonly required, the .NET Framework provides means to access functionality that is implemented in programs that execute outside the .NET environment. Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices

namespaces of the framework; access to other functionality is provided using the P/Invoke feature. Common Runtime Engine The Common Language Runtime (CLR) is the virtual machine component of the .NET framework. All .NET programs execute under the supervision of the CLR, guaranteeing certain properties and behaviors in the areas of memory management, security, and exception handling. Language Independence The .NET Framework introduces a Common Type System, or CTS. The CTS specification defines all possible data types and programming constructs supported by the CLR and how they may or may not interact with each other conforming to the Common Language Infrastructure (CLI) specification. Because of this feature, the .NET Framework supports the exchange of types and object instances between libraries and applications written using any conforming .NET language. Base Class Library The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of functionality available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction, XML document manipulation and so on. Simplified Deployment The .NET framework includes design features and tools that help manage the installation of computer software to ensure that it does not interfere with previously installed software, and that it conforms to security requirements. Security The design is meant to address some of the vulnerabilities, such as buffer overflows, that have been exploited by malicious software. Additionally, .NET provides a common security model for all applications. Portability

The design of the .NET Framework allows it to theoretically be platform agnostic, and thus cross-platform compatible. That is, a program written to use the framework should run without change on any type of system for which the framework is implemented. While Microsoft has never implemented the full framework on any system except Microsoft Windows, the framework is engineered to be platform agnostic, and cross-platform implementations are available for other operating systems. Microsoft submitted the specifications for the Common Language Infrastructure (which includes the core class libraries, Common Type System, and the Common Intermediate Language), the C# language,and the C+ +/CLI language to both ECMA and the ISO, making them available as open standards. This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms.

Architecture
Common Language Infrastructure (CLI) The purpose of the Common Language Infrastructure, or CLI, is to provide a language-neutral platform for application development and execution, including functions for exception handling, garbage collection, security, and interoperability. By implementing the core aspects of the .NET Framework within the scope of the CLR, this functionality will not be tied to a single language but will be available across the many languages supported by the framework. Microsoft's implementation of the CLI is called the Common Language Runtime, or CLR.

Visual overview of the Common Language Infrastructure (CLI)

Metadata All CIL is self-describing through .NET metadata. The CLR checks the metadata to ensure that the correct method is called. Metadata is usually generated by language compilers but developers can create their own metadata through custom attributes. Metadata contains information about the assembly, and is also used to implement the reflective programming capabilities of .NET Framework. Security .NET has its own security mechanism with two general features: Code Access Security (CAS), and validation and verification. Code Access Security is based on evidence that is associated with a specific assembly. Typically the evidence is the source of the assembly (whether it is installed on the local machine or has been downloaded from the intranet or Internet). Code Access Security uses evidence to determine the permissions granted to the code. Other code can demand that calling code is granted a specified permission. The demand causes the CLR to perform a call stack walk: every assembly of each method in the call stack is checked for the

required permission; if any assembly is not granted the permission a security exception is thrown. When an assembly is loaded the CLR performs various tests. Two such tests are validation and verification. During validation the CLR checks that the assembly contains valid metadata and CIL, and whether the internal tables are correct. Verification is not so exact. The verification mechanism checks to see if the code does anything that is 'unsafe'. The algorithm used is quite conservative; hence occasionally code that is 'safe' does not pass. Unsafe code will only be executed if the assembly has the 'skip verification' permission, which generally means code that is installed on the local machine. .NET Framework uses AppDomains as a mechanism for isolating code running in a process. AppDomains can be created and code loaded into or unloaded from them independent of other AppDomains. This helps increase the fault tolerance of the application, as faults or crashes in one AppDomains do not affect rest of the application. AppDomains can also be configured independently with different security privileges. This can help increase the security of the application by isolating potentially unsafe code. The developer, however, has to split the application into subdomains; it is not done by the CLR. Class library The .NET Framework includes a set of standard class libraries. The class library is organized in a hierarchy of namespaces. Most of the built in APIs are part of either System.* or Microsoft.* namespaces. These class libraries implement a large number of common functions, such as file reading and writing, graphic rendering, database interaction, and XML document manipulation, among others. The .NET class libraries are available to all CLI compliant languages. The .NET Framework class library is divided into two parts: the Base Class Library and the Framework Class Library. The Base Class Library (BCL) includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime. The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL. The BCL classes are

available in both .NET Framework as well as its alternative implementations including .NET Compact Framework, Microsoft Silverlight and Mono. The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire class library that ships with .NET Framework. It includes an expanded set of libraries, including Windows Forms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows Communication Foundation among others. The FCL is much larger in scope than standard libraries for languages like C++, and comparable in scope to the standard libraries of Java. Memory management The .NET Framework CLR frees the developer from the burden of managing memory (allocating and freeing up when done); instead it does the memory management itself. To this end, the memory allocated to instantiations of .NET types (objects) is done contiguously from the managed heap, a pool of memory managed by the CLR. As long as there exists a reference to an object, which might be either a direct reference to an object or via a graph of objects, the object is considered to be in use by the CLR. When there is no reference to an object, and it cannot be reached or used, it becomes garbage. However, it still holds on to the memory allocated to it. .NET Framework includes a garbage collector which runs periodically, on a separate thread from the application's thread, that enumerates all the unusable objects and reclaims the memory allocated to them. The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-andsweep garbage collector. The GC runs only when a certain amount of memory has been used or there is enough pressure for memory on the system. Since it is not guaranteed when the conditions to reclaim memory are reached, the GC runs are non-deterministic. Each .NET application has a set of roots, which are pointers to objects on the managed heap (managed objects). These include references to static objects and objects defined as local variables or method parameters currently in scope, as well as objects referred to by CPU registers. When the GC runs, it pauses the application, and for each object referred to in the root, it recursively enumerates all the objects reachable from the root objects and marks them as reachable. It uses .NET metadata and reflection to discover the objects encapsulated by an object, and then recursively walk them. It then enumerates all the objects on the

heap (which were initially allocated contiguously) using reflection. All objects not marked as reachable are garbage. This is the mark phase. Since the memory held by garbage is not of any consequence, it is considered free space. However, this leaves chunks of free space between objects which were initially contiguous. The objects are then compacted together to make used memory contiguous again. Any reference to an object invalidated by moving the object is updated to reflect the new location by the GC. The application is resumed after the garbage collection is over. The GC used by .NET Framework is actually generational. Objects are assigned a generation; newly created objects belong to Generation 0. The objects that survive a garbage collection are tagged as Generation 1, and the Generation 1 objects that survive another collection are Generation 2 objects. The .NET Framework uses up to Generation 2 objects. Higher generation objects are garbage collected less frequently than lower generation objects. This helps increase the efficiency of garbage collection, as older objects tend to have a larger lifetime than newer objects. Thus, by removing older (and thus more likely to survive a collection) objects from the scope of a collection run, fewer objects need to be checked and compacted.

ABOUT SQL SERVER 2005

The code base for MS SQL Server (prior to version 7.0) originated in Sybase SQL Server, and was Microsoft's entry to the enterprise-level database market, competing against Oracle, IBM, and, later, Sybase. Microsoft, Sybase and AshtonTateoriginally teamed up to create and market the first version named SQL Server 1.0 for OS/2 (about 1989) which was essentially the same as Sybase SQL Server 3.0 on Unix, VMS, etc. Microsoft SQL Server 4.2 was shipped around 1992 (available bundled with Microsoft OS/2 version 1.3). Later Microsoft SQL Server 4.21 for Windows NT was released at the same time as Windows NT 3.1. Microsoft SQL Server v6.0 was the first version designed for NT, and did not include any direction from Sybase. About the time Windows NT was released, Sybase and Microsoft parted ways and each pursued their own design and marketing schemes. Microsoft negotiated exclusive rights to all versions of SQL Server written for Microsoft operating systems. Later, Sybase changed the name of its product to Adaptive Server Enterprise to avoid confusion with Microsoft SQL Server. Until 1994, Microsoft's SQL Server carried three Sybase copyright notices as an indication of its origin.

Since parting ways, several revisions have been done independently. SQL Server 7.0 was a rewrite from the legacy Sybase code. It was succeeded by SQL Server 2000, which was the first edition to be launched in a variant for the IA64 architecture. In the eight years since release of Microsoft's previous SQL Server product (SQL Server 2000), advancements have been made in performance, the client IDE tools, and several complementary systems that are packaged with SQL Server 2005. These include: an ETL tool (SQL Server Integration Services or SSIS), a Reporting Server, an OLAP and data mining server (Analysis Services), and several messaging technologies, specifically Service Broker and Notification Services.

SQL Server 2005

SQL Server 2005 (codenamed Yukon), released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational data. For this purpose, it defined an xml data type that could be used either as a data type in database columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using XQuery ;CLR Integration was the main features with this edition where one could write SQL code as Managed Code these are those code which are being executed by CLR(Common Language Runtime). SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery queries in T-SQL. In addition, it also defines a new extension to XQuery, called XML DML, that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over web services using TDS packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML. For relational data, T-SQL has been augmented with error handling features (try/catch) and support for recursive queries (Common Table Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms and better error recovery systems. Data pages are checksummed for better error resiliency, and

optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a cluster is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework. SQL Server 2005 introduced "MARS" (Multiple Active Results Sets), a method of allowing usage of database connections for multiple purposes.

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, serverside 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 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. ACTIVE SERVER PAGES.NET ASP.NET is a programming framework built on the common language runtime that can be used on a server to build powerful Web applications. ASP.NET offers several important advantages over previous Web development models: Enhanced Performance. ASP.NET is compiled common language runtime code running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding, just-intime compilation, native optimization, and caching services right out of the box. This amounts to dramatically better performance before you ever write a line of code.

World-Class Tool Support. The ASP.NET framework is complemented by a rich toolbox and designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-and drop server controls, and automatic deployment are just a few of the features this powerful tool provides. Power and Flexibility. Because ASRNET is based on the common language runtime, the power and flexibility of that entire platform is available to Web application developers. The NET Framework class library, Messaging, and Data Access solutions are all seamlessly accessible from the Web. ASRNET is also language-independent, so you can choose the language that best applies to your application or partition your application across many languages. Further, common language runtime interoperability guarantees that your existing investment in COM-based development is preserved when migrating to ASP.NET. Simplicity. ASRNET makes it easy to perform common tasks, from simple form submission and client authentication to deployment and site configuration. For example, the ASRNET page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, Visual Basic - like forms processing model. Additionally, the common language runtime simplifies development, with managed code services such as automatic reference counting and garbage collection. Manageability. ASRNET employs a text-based, hierarchical configuration system, which simplifies applying settings to your server environment and Web applications. Because configuration information is stored as plain text, new settings may be applied without the aid of local administration tools. This "zero local administration" philosophy extends to deploying ASRNET Framework applications as well. An ASRNET Framework application is deployed to a server simply by copying the necessary files to the server. No server restart is required, even to deploy or replace running compiled code. Scalability and Availability. ASRNET has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and multiprocessor environments. Further, processes are closely monitored and

managed by the ASRNET runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep your application constantly available to handle requests. Customizability and Extensibility. ASRNET delivers a well-factored architecture that allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend or replace any subcomponent of the ASRNET runtime with your own custom-written component. Implementing custom authentication or state services has never been easier. Security With built in Windows authentication and per-application configuration, you can be assured that your applications are secure LANGUAGE SUPPORT The Microsoft NET Platform currently offers built-in support for three languages: C#, Visual Basic, and Jscript

C#.Net
C# is an object-oriented programming language developed by Microsoft as part of the NET initiative and later approved as a standard by ECMA and ISO. Anders Hejlsberg leads development of the C# language, which has a procedural, objectoriented syntax based on C++ and includes aspects of several other programming languages (most notably Delphi and Java) with a particular emphasis on simplification. Design goals The ECMA standard lists these design goals for C#: C# is intended to be a simple, modern, general-purpose, object-oriented programming language. Because software robustness, durability and programmer productivity are important, the language should include strong type checking, array bounds checking, detection of attempts to use un initialized variables, source code portability, and automatic garbage collection. The language is intended for use in developing software components that can take advantage of distributed environments.

Programmer portability is very important, especially for those programmers already familiar with C and C++. Support for internationalization is very important. C# is intended to be suitable for writing applications for both hosted and embedded systems, ranging from the very large that use sophisticated operating systems, down to the very small having dedicated functions. Although C# applications are intended to be economical with regards to memory and processing power requirements, the language was not intended to compete directly on performance and size with C or assembly language. Features The following description is based on the language standard and other documents listed in the External links section. By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of C#'s intrinsic types correspond to value-types implemented by the CLI framework. However, the C# language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime (CLR), or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or FORTRAN; in practice, all existing C# implementations target CLI. C# differs from C and C++ in many ways, including: There are no global variables or functions. All methods and members must be declared within classes. Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts. C# supports a strict boolean type, bool. Statements that take conditions, such as while and if, require an expression of a Boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or a

pointer. C# disallows this "integer meaning true or false" approach on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of programming mistakes such as if (a = b) (use of = instead of ==). In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe references, which cannot be made invalid. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is not marked as unsafe can still store and manipulate pointers through the System.IntPtr type, but cannot dereference them. Managed memory cannot be explicitly freed, but is automatically garbage collected. Garbage collection addresses memory leaks. C# also provides direct support for deterministic finalization with the using statement (supporting the Resource Acquisition Is Initialization idiom). Multiple inheritance is not supported, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication, avoid dependency hell and simplify architectural requirements throughout CLI. C# is more typesafe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers and conversion from a derived type to a base type. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions between booleans and integers and between enumeration members and integers (except 0, which can be implicitly converted to an enumerated type), and any userdefined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors (which are implicit by default) and conversion operators (which are always implicit). Enumeration members are placed in their own namespace. Accessors called properties can be used to modify an object with syntax that resembles C++ member field access. In C++, declaring a member public enables both reading and writing to that member, and accessor methods must be used if more fine-grained control is needed. In C#, properties allow control over member access and data validation.

4.1 Data Dictionary

Table:-Admin Login Information

Table:-User Login Information

Table:-User Information

Table:-Forum Question

Table:-Forum Answer

Table:-Section Details

Table:-Missing Person Details

Table:-Missing Person Image Details

Table:-Send Mail

Table:-Receive Mail

Table:-Draft Mail

Table:-FIR Details

4.2 Entity-Relationship Diagram

Passwor d Id Ph. No.

Manage s

Name

Administrator
Date Place DOB

Passwor d
ID

Ph. No. NNNo.

Manage s
Can Send Receive Can View

Missing Person

Mail

Name

User Account

Ha s

User

Address

Can View\p ost

Can View

Section

Forum

Questio n Answer Punishmen t

Number

Date U_Nam e

4.3 Data Flow Diagram

A graphical tool used to describe and analyze the moment of data through a system manual or automated including the process, stores of data, and delays in the system. The DFD is also know as a data flow graph or a bubble chart. DFDs are the model of the proposed system. They clearly should show the requirements on which the new system should be built. The Basic Notation used to create a DFDs are as follows: 1. Dataflow: Data move in a specific direction from an origin to a destination.

2. Process: People, procedures, or devices that use or produce (Transform) Data. The physical component is not identified.

3. Source: External sources or destination of data, which may be People, programs, organizations or other entities.

4. Data Store: Here data are stored or referenced by a process in the System.

DFD of 0 Level

Crime Database DB Info Details

Mail Registered User Forum Act Search Update Account Info

0.0
Mail E-POLICE System

FIR

Forum Add,Update Missing Deatails

Admin

Sing Forum Up

Act Search

Unregistered User

First Level DFD For Admin

Correct Password Allow To Login

Admin table

Checking In Database Verifying Admin Password

ADMIN

Login Process

Verification Of Password

Wrong Password

FIR

MAIL

Forum

Missing Person Details

DFD of LEVEL I : For Client

Update database

Correct Password Allow To Login

User table

Checking In Database Verifying User Password

USER

Login Process

Verification Of Password

Wrong Password

Update Account

FIR

MAIL

Forum

Missing Person Details

Act Search

4.4 UML DIAGRAMS

Use Case Diagram (For Admin):

Organize Accounts Add Missing Person Info. Update Missing Person Info. Delete Missing Person Info. Admi Search Missing Person Info. Post/Reply to User Question Send/Receive Mail Suspend Illegal Users Add, Update, Edit Acts\ Section Info.

Use Case Diagram ( For User)

<<includes>>

Login

Ask/Reply Question/Answer

Modify Question

View Acts and Section Information User Send/Receive Mail

View Missing Person details

Activity Diagrams: Registration Diagram:

[E nter R egis tration D etails

G t th D ta e e e ils [s b it um ]

V lid te D ta a a e ils

N o

R je te e c d

Ys e

Ac p d c e te [S c e sF llyR g te d uc s u e is re ]

Login Activity Diagram:

[Enter User Name and Password

G Details et Error

[Submit ]
Validate Data

Rejected

No

yes

Accepted

Sequence Diagram (For Admin):

Process

Master Screen

Administrator

Server

Add Missing Person Update Missing Person Validate Missing Person

Search Missing Person Validate User Reply To User

Request for Appropriate Screen For MP Generate Response from Server

Request for User

Display ( ) Suspend Users

Send Response

Sequence Diagram (For User):

Process

User Screen

Server

Ask Question
Validate User Question

Reply

Validate User Answer

Save Question

View Section Information Send Mail

Validate User For Mail Display ()

Save Answer

View Missing Person Info.

Generate Response for Request

Component Diagram:

D Database Server

LAN

TCP/IP Client Machine Web Browser

Web Server Services

Deployment Diagram:

Server

Internet

Client: C1

Client: C2

Client: Cn

5. MODULE SPECIFICATION
Password Module: In this module, user enters a password and the portal checks its validity. If the password is valid then he is allowed to enter, otherwise Invalid User/Password message is displayed. Search: In Search section, authorized user and admin will search for missing people details and can also seek information of different acts and section, etc. Contact of concerned authority: Contact details of the area official who is managing things. Secure registration and profile management facilities for detectives and security agencies. Validation of Data Entered by the User and Error Handlin: In this module, the validity of data entered by the user during the various processes is checked through various validation checks. For example, there shouldnt be any characters entered in the numeric fields, likewise if there is any error occurs that it should handle that particular error and give the required messages. Setting: User can change its account information if he wants to, after creating his account. Acts and Section: All detailed information regarding different acts and sections is available on a single button click. Users can use this information.

Forum: One can post questions if he has some queries and can also answer the questions posted by other users of the system if he knows the answer. Missing Person: Admin has the only right to enter the details of a missing citizen and post on the web according to the valid information provided by the user to do so. Admin can add/edit/delete this information as required. End Users themselves cannot alter this information. Mail: Users and admin can send\receive mails on their authorised accounts. Online FIR: FIR can be seen online once it is filed by the admin on the demand of the user. The admin can add, update and delete FIR as per requirements.

6.

SCREENS

6.1 USER INTERFACE User Login Form:

This is Login form User can login using his/her ID and Password

After Login Page:

User can Perform Different Tasks

Forum Page
User can Perform Different task such as Ask Question, Modify question

Ask Question Page:

User can Ask Question

My Question Page
User can only see his/her Question which is ask

All Question Page

User can see Question Ask by all users

View Answer of Question Page:

User can View Answers of The Question

Modify Question Page:

User can only Modify Question ask by him/her

Answer Question Page:

User can Post Answer To the Question

Enter Missing Person Details Page:

User Enter Person Name or Number To View Details

View Missing Person Details Page:

User can View Missing Person Details

Select Fir Page:

User can view FIR

View Fir Page

User can View Fir According To FIR Number

View Fir Page

User can View FIR According To Selected Topic

Check While Update Account Information:

Checking of User ID and Password To Edit Account Information

View account Information

User can View Account Information

Section Search Page

User can Only Get Information about Acts

About Us page

Contact Us Page

Create Account Page

User able to Create his/her Account using which user able to can access The Site

Receive Mail Page (Inbox)

Compose Mail Page

Display Inbox Data Page

Sent Mail Page

Draft Mail Page

6.2 ADMIN USER INTERFACE Admin Log In Page

After Log In Page

Missing Person Page

Add Record Of Missing Person Page

View Missing Person Details Page

View Details Of Missing Person Page

Update Missing Person Information Page

Edit Information Page

FIR Page

Add FIR Page

Update FIR Page

Update FIR According To FIR Number Page

View Fir Page

View FIR According To FIR Number Page

View FIR According To FIR Topic Page

Receive Mail For ADMIN Page (Inbox)

Display Inbox Matter Page

Section Search For ADMIN Page

7. TESTING STRATEGIES
Software testing is one of the traditional methods for testing software quality. It is a process of executing a program with objectives of finding errors. It was very useful in developing error free system, as during testing various cases of accident were taken and checked whether system generated desired output. Various testing techniques used for testing system are: White Box Testing (Code testing): In this strategy, internal logic of program was tested. Various test cases were developed such that they result in execution of every instruction in program, so all path of program were tested. Black Box Testing (Specification testing): In this strategy, system was tested for some set of input, verifying whether it generates desired output in all various conditions. Using various test cases, black box testing was done successfully.

8. CONCLUSION
Today in this world of modernization, we are faced with opportunities unprecedented in history. With technological advancement everything can be replicated and duplicated but manpower is one unique asset that be duplicated hence utmost importance is given toward making once work as possible. This project has helped me great depth to learn new concepts of web, .NET, Frameworks, SQL, etc. I have tried to make software user friendly and simple to understand as far as possible so as to bring efficiency in the work. At last, I am thankful to the University of Pune to include this project work as part of M.Sc. academic syllabus. This project work really gave chance to me to do something apart from typical reference book.

9. LIMITATION
Site can be only used for the Indian Laws and Acts. Cannot Registered Online FIR and Information About Missing Person. Mail can only use in IntraDomain not InterDomain

10. BIBLIOGRAPHY
www.w3schools.com www.sql-tutorial.net Unified Modeling Languages: Grady Booch Online ASP.NET and MYSQL manuals.