ACKNOWLEDGEMENT

It gives us immense pleasure in submitting the project report on ECOPS for the partial fulfillment of the course BCA from Falcon Infosys (Institute of IT & Management). First of all we are thankful to PUNJAB TECHINICAL UNIVERSITY, JALANDHAR for giving the opportunity to work on this project and for allowing us to work on this project. We are also thankful to Falcon Infosys for providing all the privileges. We are highly grateful to us guide in this project Ms. Aparna Srivastava, working as IT Faculty in Falcon Infosys (Institute of IT & Management), for her encouragement, guidance and valuable suggestions, which we incorporated in our project. And last but not the least we thank our parents and all our friends who not only encouraged us but also helped us in the process of making this project.

Thanking All, Alka Mishra Roll No. : - 820654075 Abhimanyu Kr. Rawat Roll No. : - 820654070 Kailash Chandra Joshi Roll No. : - 820654097

Contents Preface Project plan Introduction Objective Project planning and Scheduling Software Requirement Hardware Requirement Software Requirement Specification System Analysis Requirement Analysis Description of Tool Used Software Engineering Paradigm Number of modules Process logic of each module DFD Description Data Flow Diagram E-R Diagram System Design Data Structures (Tables) Coding Testing Test Cases Gantt chart Form Layout Form Coding Reports Cost Benefit Analysis Security Mechanism Future Scope Bibliography

PREFACE
We are on the thresh hold of a new information era and future generations may view our era as the time when people developed tools to amplify human intelligence. Use of computer has grown immensely over the past few decades. Computers are being used in every sphere of modern life to make better use of time and space as they form the base of almost every third organization the computer and/or industry department. has seen With some the radical requirements and ease of use increasing every day, improvements in software development tools. For a software developer, the starting step is to properly understand the overall problem. Every individual has different needs and it is very difficult to develop common software to solve general problems. So we need to develop various soft wares to meet their individual needs so as to provide exactly what they want. In this era of evolution, there are good software which are easy to use and work with, and they do not need much learning.

This software is a step forward to attain this goal. It aims of providing the accurate and complete information about what the Ecops is all about? PROJECT PLAN Sno Phase
1. 2. 3. 4. 5. 6. Problem Identification Analysis Designing Coding Testing & Debugging Total Time Involved

Time of Completion
15 15 20 30 20 90 days days days days days days (3 months)

PROJECT INTRODUCTION
The project titled as Enterprise Case and Occurrence Processing System is a web based application. This software provides facility for reporting online crimes, complaints, fir detail and giving feedback to the user. The E-COPS PreQualification Program offered by Public Safety Solutions is the first of its kind to offer potential public safety employees full range of services that will assist them in obtaining the public safety position they desire. E-COPS Pre-Qualification Program provides a complete applicant assistance program that includes in-depth assessment personal counseling and coaching throughout the process, complete background investigation, and matching of your interests and capabilities to the job and agency that will provide you with the best opportunity for success. We even mentor you in your quest for future Advancement opportunities. This document is meant to describe the features of ECOPS, so as to Serve as a guide to the developers on one hand and a software validation Document for the prospective client on the other. This project is help to

the citizen which can easily fill the complaint against a criminal in a Very fast manner and police would giving a quick response against a Criminal.

OBJECTIVE
The main objective of this project as a whole is to provide the managing each criminal fir detail which is fill by the police officer which is highly successful.

Ecops is to make use of information technology for COPS to serve the society quickly, capture the criminals by instant messaging and communications between different police station. Specific Objective of the Site: Administrator has the rights to create new Branch and can able the change the existing details of other branches it also have the task of appointing new police officers and register the new officers to the requiring police stations. Administrator can also change the place of the police officers from one place to another place to continue their jobs are known as transfer of police officers. Police should have areas of control which can be modified at later time. When a complaint is made it undergoes various processes like FIR, Complaint all these activities are performed by a ps. Maintaining the criminal information state wise/city wise/area wise is mandatory.
The magistrate should be able to access the case details

and provide the arrest warrant.

PROJECT PLANNING AND SCHEDULING

Planning is an ongoing function that provides the framework for operational activity and decision-making. A plan is a predetermined course of action. It represents goals and activities necessary to achieve these goals. Planning is very important in every aspect of development work. Good managers carefully monitor developments at various phases. Improper planning leads to failure of the project. Software project plan can be viewed as the following1. Within the organization - how the project is to be implemented? What are various constraints (time, cost, and staff)? What is market strategy? 2. With respect to the customer weekly or timely meetings with the customer with presentation on status report. Customer feedback is also taken and further modification and developments are done. Project milestones are deliverables are also presented to the customer. 3. For a successful software project, the following steps can be followed. 4. Select a project. 5. Identifying projects aims and objectives. 6. Understanding requirements and specification. 7. Methods of analysis, design, and implementation. 8. Testing techniques. 9. Documentation

PROJECT MILESTONES AND DELIVERABLES

1. 2. 3. 4. 5. 6. 7. Budget allocation Exceeding limits within control Project estimates Cost & time Size of code Duration Resource allocation

8. Hardware & Software 9. Previous relevant project information 10. Digital library 11. Risk management, risk avoidance & risk detection 12. Risk control & risk recover 13. Scheduling techniques 14. Work breakdown structure 15. Team management 16. Customer interaction The proposed software system should be able to: 1. Read the structure data available in the access files and store it in a database system. 2. Validate data of the database on the basis of predefined business rules. 3. Prepare reports on data that is found to be in error during validation, and 4. Prepare MIS reports from the validated data. 5. Delivery deadlines.

PROJECT PLAN OBJECTIVES:The objective of the system can be defined here as: 1. The proposed system should be able to read the data from access files and store validated data in the database. 2. Easy to manage large amount of data. 3. Data can be managed effectively.

ACTIVITIES AND MILESTONES:The activities in the system, after including the provisions for security are: 1. Verification of software. 2. Migration of the software. 3. Validation of the migrated data.

SCHEDULING:-

Scheduling of a software project can be correlated to prioritizing various tasks (jobs) with respect to their cost, time, and duration. Scheduling can be done with resource constraint or time constraint in mind. Depending upon the project, scheduling methods can be static or dynamic in implementation.

SCHEDULING TECHNIQUES:There are various types of scheduling techniques in software engineering:-

WORK BREAKDOWN STRUCTURE:The project is scheduled in various phases following a top-down approach. A tree like structure is followed without any loops. At each phase or step, milestones and deliverables are mentioned with respect to requirements. The work breakdown structure shows the overall breakup flow of the project and does not indicate any parallel flow. Work breakdown structure of the Hotel Management Project is given below:

WORK BREAKDOWN STRUCTURE OF THE PROJECT:Here the project is split into Analysis, Design, Coding and Testing phase. Further analysis is divided into Feasibility Report, Cost Estimation, and Project Planning and Scheduling, and software requirement specification; design is divided into procedural design, user interface design, and architecture design; coding is divided into comments and description, standardization of coding, error handling and security; testing is divided into black box testing and white box testing.

SOFTWARE (SQL PROJECT GENERATO R)

ANAL YSIS

DESI GN

COD ING

TEST ING

FEASI REP BLE ORT

SOFT REQUIRE WARE SPECIFIC MENT ATION

SECU RITY

PROJECT PLANNING AND SCHEDULI NG

COMM ENT& DESCRI PTION STANDARI OF SATION CODIN G

ERR HAND OR LING

WHI BTE TEST O ING X

BLACK TEST BOX ING

PRO US DE ER INTER CED SI SI D FACE E GN

ARCHITE DESI CTURE GN

SOFTWARE REQUIREMENT SPECIFICATION This document is generated as output of requirement analysis. The requirement analysis involves obtaining a clear and throughout understanding of the product to be developed. Thus SRS should be consistent, correct unambiguous and complete document. The developer of the system can prepare SRS after detail communication with the customer. An SRS can clearly define the following: INTRODUCTION-

1.1 Purpose
This document describes the software requirements for the Automated Ecops System named ECOP for the Public Welfare.

1.2 Scope
The deep study of the working of the existing Hotel system and the problems faced by them results in a proposal to build a prototype of an Automated Ecops System for their current system. This new Ecops needs to be scalable enough so that it can accommodate the increase in Police Station usage caused by increasing importance of welfare and its fast and timely access. The system will be designed to provide an electronic version of the Inter Ecops tool. The system will have a userfriendly graphical interface and will be more cost effective compared to the current non-electronic version of the hotel management system. The objectives of this development effort are:1. To provide existing staff a new environment in which time and amount calculation for hotel users can be done. 2. To regain control of the system securities to avoid data loss, information leakage and inconvenience of the users. 3. To implement prototype of a scaled down version of the final system to test the solution and further develop requirements.

4. To collect statistics in a more efficient manner for future project development and construction. 5. To increase efficiency of Police Department.

1.3. Definitions, Acronyms and Abbreviation

ECOP-Enterprise case and occurrence processing system. CASE- Computer Aided Software Engineering SDD- Software Design Description SRS- Software Requirement Specification SDS- Software Design Specification GUI- Graphical User Interface UML- Unified Modeling Language

1.4

Products And Its Functions

The final product that will be received is an error free and robust automated System to manage a police station. It consists of database. Database handles data storage, retrieval and updating of data. The E-COPS Program offered by Public Safety Solutions is the first of its kind to offer potential public safety employees a full range of services that will assist them in obtaining the public safety position they desire. E-COPS Program provides a complete applicant assistance program that includes in-depth assessment, personal counseling and coaching throughout the process, complete background investigation, and matching of your interests and capabilities to the job and agency that will provide you with the best opportunity for success. We even mentor you in your quest for future advancement opportunities.

1.5

Benefits And Goals

Following are some of the benefits of the software: No need of register record. Easily maintains the record of several years. Easy time & mount calculation. It can search out the total time and total amount by the date, month or year. Goals of the project are as follows: To achieve the highest order of security and protection.

To supply a fully computerized and robust system foe the management of hotel. To avoid the inconvenience of the uses caused due to the manual data entry.

Overall Descriptions This section describes the general factors that affect the product and its requirement. This section consists of five subsections that follow. This section does not state specific requirements. Each of the subsections makes those requirements easier to understand; it does not specify design or express specific requirements. Specific Requirements

1.1 Interface Requirements

This should specify:1) The characteristics that the software must support for each human interface to the software product. For example, if the user of the system operates through a display terminal, the following should be specified:(a)Required screen formats (b)Page layout and content of any reports or menus (c)Relative timing of inputs and outputs (d)Availability of some form of programmable function 2) All the aspects of optimizing the interface with the person who must use the system. This may simply comprise a list of dos and donts on how the system will appear to the user.

1.2 User Requirements

Analysis of the users requirements is made in many ways. As the staff of the concerned Organization was to be affected by the system therefore their needs and wish list were listed so as to do the requirement Analysis. Objective was to ask the following questions: Who? What? Why? Where? When? Only the people who actually are in the system could answer these questions. Therefore the questions were asked to some of the staff the concerned organization.

1.3 Hardware Requirements

Processor RAM HDD FDDMonitorPrinter MouseKeyboard 1.2 GHz or above 512 MB 40 GB 1.44MB 14SVGA Dot Matrix /Inkjet /Laser Printer Normal Normal

1.4 Software Requirements

Front-end Tool: - Microsoft C#.Net User friendly Low Cost Solution GUI feature Better designing aspect Back-end Tool: - SQL Server 2000 Platform/ Operating System Windows Platform like: Windows XP service pack 2 or 3 Others Virus scan program etc.

1.5 Logical Database Requirement

Certain requirements may, due to the nature of the software, the user organization, etc., be placed in separate. This could specify the requirements for any database that is to be developed as part of the product. This might include: (1) Types of information (2) Frequency of use (3) Accessing capabilities (4) Data element and file description

(5) Relationship of data elements, record and files (6) Static and dynamic organization (7) Retention requirements for data

ECOP
System Analysis
System Analysis is the first and basic step in the development of software. This is the backbone for the software development. This refers to a systematic investigation of a real or planned system to determine the functions of the system and how they relate to each other and to any system. It is performed to develop a proper design of software to be developed and to fulfill the needs of the firm or customer. System Analysis includes requirement analysis, which plays an important role in identifying what are the expectations of a firm from the proposed system. The task of requirement analysis is a process of discovery, refinement, modeling and specification. After requirement analysis, an analysis model is built which gives information about the data required in the system and also specifies the functions and behavior of the system. The main purpose of conducting system analysis is to study the various processes and to find out its requirements. These may include ways of capturing or processing data, producing information, controlling a business activity or supporting management. The determination of Requirements entails studying the existing details about it to find out what these Requirements are. System Analysis is conducted with the following objectives in mind: Identify needs of the customer Evaluate the system concept for feasibility. Perform economic and technical analysis. Allocate functions to system elements like hardware, software, people, database and others. Establish cost and schedule constraints. Create a system definition that forms the foundation for all subsequent engineering work. Analysis was performed to accomplish the objectives mentioned under the

title objectives. The necessary details required in the analysis of project were collected from the record registers, staff of the police station and the record of criminals. During the analysis phase of this project following set of principles were considered: The information domain of a problem must be represented and understood. The functions that the software is to perform must be defined. The behavior of the software must be represented. The modules that depict information function and behavior must be partitioned in a manner that uncovers details in a layered fashion. The analysis process should move from essential information toward implementation details.

The following steps were taken during analysis.

PROBLEM DEFINITION
As per the norms of system development lifecycle is concerned. The very first Step in designing a system is defining the problem. A system is collection of entities, which work together in synergy to achieve a predefined goal and objectives. The definition phase of the system answers the question, what does the need and wants from the new system? The definition phase can be called the requirement analysis or logical design phase. We can never skip the definition phase. New system are always be evaluated, first and foremost, on whether or not it fulfilled the business requirement regardless of how impressive the technological solution be. The initial activity of definition phase is to outline the business requirements. The foundation of this activity was established in the study phase when the system improvement objectives were identified. This activity translates those objectives into inputs, outputs, and process that will be specified in greater deal during subsequent activities. The problem produced a need to change the existing system. Some of these shortcomings are being discussed below:-

Problems Faced With Existing System

The manual system to be time consuming and less efficient with respect to the following procedures: Maintenance of customer record is very typical. Maintenance of a large amount of data is a tedious job. To obtain details regarding the time and amount of particular node at any time involves a lot of hard work. Searching data by given particular time is a cumbersome job. In this section we shall discuss the limitation and drawback of the existing system that forced us to take up this project. Some of these shortcomings are as follows:-

Low Functionality: With the existing system, the biggest problem was the low functionality. The problem faced hampered the work. For small task like adding any new node to server or deleting a node or keeping daily record we have to appoint minimum two or three employees.

Erroneous Input And Output: In the existing system, humans performed all the tasks. As in the human tendency, error is also a possibility. Therefore, the inputs entered by the person who is working in the Hotel, in the registers may not be absolutely foolproof and may be erroneous. As a result of wrong input, the output report etc will also be wrong which would in turn affect the performance.

Portability: System that existed previously was manual. As a result, the system was less portable. One has to carry the loads of many registers to take the data from one place to another. A big problem was that the system was less flexible and if we wanted to calculate yearly or monthly income then it was a big headache.

Security: Security concerns were also one of the motives of the Hotel for the need of software. In the registers, the data is not secure as anybody can tamper with the data written in the registers. While in this software, just a password makes it absolutely secure from the reach of unauthorized users.

Data Redundancy: In the case of manual system, the registers are maintained in which, a lot of data is written. Each time a new customer gets connected to a node the node number is to be written repeatedly which may cause confusion while tallying the allotted time of different nodes.

Processing Speed:In manual system maintaining a register and performing the necessary calculation has proved to be a troublesome job, which takes a lot of time and may affect the performance of the organization or Hotel. But with this software we can have the entire task performed in a fraction of second by a single-click thus making the troublesome job much easier.

Manual Errors: When a number of tough tasks are prepared by the humans like preparation of reports, performing long calculation then some human error is obvious due to a number of factors like mental strain, tiredness etc. But as we all knows that computer never get tired irrespective of the amount of work it has to do. So this software can nullify the probability of manual error that improve the performance.

Complexity In Work: In manual system whenever a record is to be updated or to be deleted a lot of cutting and overwriting needs to be done on the registers that are

concerned that are deleted or updated record, which makes the work very complex.

REQUIREMENT SPECIFICATION
After collecting the requirements, requirement specification is created which specifies the need of the computer. It helps the developer and customer to access quality once software is built. If customer changes his requirements, the developer can demand for more time or additional cost or both. The requirement specification software is as follows: for the proposed

Because of the needs specified above, it is necessary to build user friendly software, which would provide integrated billing, management and security features. It must prevent unauthorized use of the Computer. It should provide powerful security features to give the user complete control over the Hotel and minimizes system maintenance time. It should business performance & help in maintaining the data. It would facilitate a better service experience to the users and builds an image for the Ecops, thus helping the Hotel in getting ahead of the competitors around within the area. This software will help in above defined problems. User can easily do all taskdefined above.

PRELIMINARY INVESTIGATION
Very often when the customer put his demand for any system, the definition of problem or requirement remains incomplete. To collect the complete requirements so as to build a system according to the need of the customer, preliminary investigation is conducted. During investigation questions are asked to managers, person who will use the system. All the necessary details required in the analysis of project are collected from the record registers, customers. Following questions are asked to the user to find out the major heading that he wants to give on the software:a) Which type of information he wants to display? b) What facilities he wants?

c) In which format he wants to display information? d) What are the expectations from the software? e) What is the information he wants to be viewed only by administrator and restricts to others? f) What facilities he wants to give to registered to user and what to daily users? The following fact-finding techniques are also used for preliminary investigation. 1. Existing documentation, forms, file and records 2. Observation of the work environment 3. Interviews and group work sessions

FEASIBILITY STUDY
The feasibility study is conducted to check whether the candidate system is feasible. The system which is selected to be the best against the criteria, is thereafter designed and developed. The feasibility study takes in to consideration, the risks involved in the project development beforehand. Therefore in this phase we have to do feasibility study which is the test of the Ecops Project according to its workability, impact on the organization, ability to meet user need and effective use of resources. We do the feasibility study for Hotel Management Project to analyze the risks, costs and benefits relating to economics, technology and user organization. There are several types of feasibility depending on the aspect they cover. Import of these includes:

TECHNICAL FEASIBILITY
In this phase alternatives for hardware, software and general design approach of Ecops is determined. Here we must consider the following points: Does the necessary technology for the project exist? Does the proposed equipment have the technical capacity to hold the data required to use the project?

 Can this system be expanded, if developed? Are there technical guarantees of accuracy, reliability, easy of access and data security?

OPERATIONAL FEASIBILITY
Operational feasibility is a measure of how people are able to work with the software. This type of feasibility demands if the system will work if developed and installed. Here following points must be considered: Is the sufficient support for the Hotel Management Project from the management and the users? Have the users been involved in the planning and development of Hotel Management Project? Will this system cause any harm? The following questions are related to this point? Will loss of control result in any area? Will accessibility of information be lost? Will customer be affected in an undesirable way? Will its slow performance in any area?

ECONOMIC FEASIBILITY
Here we analyze the costs of specific software, hardware, personnel office space and so forth for each implementation alternatives for Hotel Management Project. Each costs and benefits estimates can be analyzed to determine how rapidly costs are recovered by benefits, to calculate both the absolute and interest adjustment amount of excess benefits and to establish the ratio of benefits of costs for the software. More commonly known as cost- benefits analysis; procedure is to determine the benefits and savings that are expected from a proposed system and compared them with costs. Costs and benefits can be classified as follows:

TANGIBLE BENEFITS

OR

INTANGIBLE

COSTS

AND

An outlay of cash for any specific item or activity is referred to as tangible costs. In this project expenses on cost of space to install computers, n/w connection and furniture, light and air conditioning are tangible cost. Cost that are known to exist but their financial value can not be exactly measured that referred to as intangible cost. The estimate is only an approximation. It is difficult to fixed exact intangible costs. For example the intangible cost for this project is the cost to conduct a full system investigation, the

cost of hardware and software for class of application being considered.

DIRECT OR INDIRECT COST

Direct cost are those which are directly associated with the system. For example- the purchase of floppy box and cds are direct cost for this project. Indirect Cost is not directly associated with a specific activity in the system. They are often referred as overhead expenses.

FIXED OR VARIABLE COSTA AND BENEFITS

Some costs and benefits remains constant, regardless of how a system is used, such type of cost is called a Fixed Cost. Fro example- The purchase of equipment for Hotel is called as fixed cost as it remains constant whether equipment is being used or not. Similarly insurance is also a fixed cost. In contrast Variable costs are incurred on regular basis.

REQUIREMENTS ANALYSIS
Requirement analysis involves:
1. Determining

the operational requirement (user needs and Recruiter Expectations). E.g. the instructor must be able to vary the road conditions in a Driving System Simulator.

2. Translating the operational requirement into technical specifications of the system that will satisfy the operational requirements. E.g. the coefficient of friction between tires and road must be variable between 0.5 and 1.0

Requirements engineering for web SOFTWARE Systems

REQUIREMENTS ENGINEERING

Develop Software Architectur e Specify Hardware Requirement s Define Operational Requirement s User Needs Customer Expectations Acquirer Constraints

Determine Software Requirements Develop Softwar e Design Software Validation Obtain Software Compone nts Integrate Software Components

Start Here

Operational Validation

End Here

WHY ARE (GOOD) REQUIREMENTS IMPORTANT? These people Customers/users Developers Managers Testers -Depend on requirements to -Specify their needs -Establish design parameters -Determine cost and schedule - Specify validation criteria

Configuration Managers Everyone

- Establish a functional -Baseline -Guide their efforts

DESCRIPTION OF TOOLS USED

HTML (Hypertext Markup Language) HTML is creating documents that could be displayed consistently on computers of between and operating System.HTML is used to construct formatted pages for the web known as WebPages. Structure of html documents
The skeleton of HTML document is: <HTML> <HEAD> . </HEAD> <BODY> . . </BODY> </HTML>

.NET FRAMEWORK 2.0

.NET Framework is a development and execution that allows developers to create Windows and Web Based applications. .NET Framework provides an integrated development environment in which programmers can develop applications in different programming languages such as C# and VB.NET. .Net Framework primarily consists of two main components: - Common Language Runtime(CLR)- This is a language independent runtime environment of .NET framework that manages the code code at execution time. Irrespective of what language we chose to develop out application,CLR manages the code for all. - Framework Class Libraries (FCL) - This is a repository of built in classes and interfaces that correspond to the specific functionality. ASP (Active Server Pages).NET 2.0 ASP.NET 2.0 supports some brilliant new features that enable faster development of Web application with lesser code. Master Page concept of ASP.Net 2.0, Web developer just needs to define the layout once and for all.All the other web pages follow this template web pages layout and the only thing that needs to be done is the insertion of page-specific content. DEVELOPER PRODUCTIVITY Developer productivity is one of the key features of ASP.NET 2.0. Developers can build Web sites faster than ever before and the obvious reason for this fast development of Web sites is lesser code.ASP.NET 2.0 improves the functionality of the existing controls and adds a bunch of entirely new controls to its control repository. Generally the requests are made from a web client, and the response is a generated HTML document that gets sent back to the web client. Because Active pages are server side application, they have access the resources on the server.

All controls support adaptive rendering to render a Web application as per the requesting Web browser. ASP.NET 2.0 allows the Validator controls to be grouped so that a developer can enable validation for a specific set of controls. Rolls play By XML Data tagging for shared fields. A common database data format. If we ever expect to share code. We will need some way to share the meaning of the data elements in channels. XML makes that possible. XML allow developer to make their own styles and documents which makes developer in easy mode to develop the website. XML are very important for designing part. WORKING with ADO.NET ADO.NET is the main data access system and protocol that ASP.NET 2.0 uses. It uses a disconnected data architecture where the data we work wit is just a copy of the data in the actual database. ADO.NET Objects
- Data Connection Objects: To start working a database, we must

have a data connection. A data adapter needs a connection to a data source to read and write data .
- Data Adapters: Data adapters are a very important part of

ADO.Net. We use to communicate between a data source and a dataset.

- Command Objects: Data adapters can read, add, update and delete

records in a data source. To allow to specify how each of these operations work, a data adapter contains command objects for each of them.

- Datasets Objects: Datasets store data in a disconnected cache. The

structure of a dataset is similar to that of a relational database. It gives us access to an object model of tables, rows, and columns and it contains constraints and relationships defined for the dataset.
- Data Row Objects: Data Row objects correspond to a particular

row in a data table. We can get particular field in the row with Data Row properties.

The process involved in a ASP.NET using ADO.NET to access a database

User Browses

Browser

Invokes ASP.NET Query/update SQL

HTML

Rows

Result set

ADO.NET

Database

Application server for ASP.NET i.e. IIS Server Are application servers required? Context management engines (an app that collects analyses and distributes personalization and customization information)? Integration brokers (middleware that enables applications to share data)? These all are part of a comprehensive portal system. For a portal that includes customization and personalization, all of these components, at least functionally, will be required. It is a server and sends response to the user on demand. This is the top-level entry point of the documentation bundle for the ASP.NET framework. It includes many additional features that make it a useful platform for developing and deploying web applications and web services.

SOFTWARE ENGINEERING PARADIGM

In this project, Spiral model is used for the development. Spiral model has features of prototyping and linear sequential model. It helps to develop incremental versions of the software rapidly. Because software evolves as the process progresses, the developer and customer better understand and react to risks at each evolutionary level. This

is a very powerful model to develop large-scale system and software.

This model is divided into a number of task regions. Each of the regions is populated by a set of work tasks called a task set that are done according to the requirement of the project to be developed. For small projects the number of tasks and their formality is low. Conversely, for large projects the reverse is true. These task regions of spiral model are:

Customer Communication:- The task is basically done

to establish effective communication between developer and customer. In this task region customers are asked about their requirements from the system, through a dialog between developer and the customer.

Planning: - This task is basically done to define resources,

time lines and other project related information. In this task region resource, timelines and other project related information are considered and appropriate decision taken.

Risk Analysis: - This task is basically done to access both

technical and management risks. In this region technical and management risks are identified and suitable measures taken wherever feasible.

Engineering: - This task is basically done to build one or

more representations of the application. In this region one or more representations of application are built.

Construction and Release: - This task is basically

done to construct, test, install and provide user support (e.g.,

documentation and training). In this region, application is constructed, tested, installed and user support is provided.

Customer Evaluation: - This task is basically done to

obtain customer feedback based on the evaluation of the software representation created during the engineering stage and implemented during the install stage in this region, feedback is taken from the customer about the overall performance of the application built during the engineering and implemented during installation stage. This evolutionary process begin at the centre position and moves in a clockwise direction. Each traversal of the spiral typically results in a deliverable. For example, the first and second spiral traversals may result in the production of a product specification and a prototype, respectively. In this way a more stochastic version of the software is produced after some subsequent traversal. A key difference between the spiral model and other software model is that risk analysis is performed in former and not in later.

Advantages of the Spiral Model

The spiral model is very good approach to develop largescale software because of its evolutionary approach to develop software. Besides this both customer and developer can identify and remove the risks that can occur during the software development. Prototyping is used to reduce the risk as it can be developed at any stage of the evolutionary level. Due to its demand of considering technical risks at all stage, it reduces risks that may become a big problem in future. It combines iterative and linear feature which helps in developing better software.

Thus according to the steps of spiral model first of all following steps are performed for the proposed project: The requirements are collected and partial software is developed fulfilling basic requirements of the users (based on the requirement collected). As the information, the user wants to put on the software and the manner in which he wants to give the information has already been discussed, the technical and managerial risks were reduced. After designing and creation of some pages of project, a feedback is asked from the users. According to the

given feedback, further refinement to the software was made, wherever required. This procedure was followed until the whole software was completely developed. Thus the complete software was developed in an iterative and sequential way to the entire satisfaction of the users.

No. of modules: Since the project is web based, it includes number static as well as dynamic pages. All these pages fall under various categories as per the type of information or operation carried by them. Hence entire project can be divided into following four modules as under:1) Information Handling process 2) Administrator Handling Process 3) Magistrate Handling Process 4) Police Officer Handling Process 5) Message Handling Process

Information Handling Process:In this module all the pages provide some information to the user in either static or dynamic form. The dynamic pages take their information from database. The module is responsible to provide information like: Complaint Details: - This module allows user to enter the complaint in complaint details form. Complaint Status: - This module allows user to see the complaint status of the complaint.

Administrator Handling Process:-

This module is concerned with administrative line of work like updating information to be displayed on website for people as well as other related tasks. Therefore there are following sub-modules to perform above-mentioned jobs. Adding Process: This module allows the

administrator to Add State, Add City, Add Area, Add Branch, Add Department and Add Police Officer. Viewing ProcessThrough this module the

administrator to View Branch Details, View Police Officer Details, View Complaint Details, View Complaint Status, View FIR Details. Deleting Process:- This module allows administrator to Delete Branch and Police Officer Details. Administrator Login Process: - This module allows administrator to login and get some options related with his work.

Message Handling Process:- This module is divided into sub-modules: Feedback/Query Handling Process: - This module allows the users to send either their Query or their feedback in a format provided by the website. Enquiry Handling Process: - This module allows citizen for enquiry of complaint status.

Magistrate Handling Process: - This module is concerned with magistrate related work such as view FIR details and

release/reject arrest warrant. The following sub modules are: View FIR Details: - This module allows magistrate to view the FIR details and according to crime type release/reject arrest warrant.

Police Officer Handling Process: - This module allows Police Officer to view complaint details entered by user and fill FIR form. There are some sub-modules: View Complaint Details: - This module allows viewing complaint details which are entered by citizens in complaint details form. Fill FIR Details: - This module allows the police Officer to fill FIR details according to complaint details for helping the citizens.

COMPLAINT REPORTING
Description and Priority Whenever any crime occurs the citizen can report it online to the police station. It is the necessary requirement so must be implemented. Stimulus/Response Sequences Victim will visit website. Click on complaint detail form. Form appears. He/she will fill the form step wise. Finally submit. Get confirmation and complain number for future reference.

Functional Requirements REQ1: Validate user input. REQ2: Search the nearest police station. REQ3: Message it the query.

REQ4: REQ5: FIR as REQ6:

The Admin will check it. If query convincible/really matters then he will prepare per the complain report form. Check the available police officer and forward it.

CASE STATUS
Description and Priority Citizen can view the status of his/her complain/case. Stimulus/Response Sequences Citizen will visit website. Click on case statuses. Form appears to input the case/complain number. He/she will fill the form. Finally submit. Get the case status. Functional Requirements REQ1: Validate user input. REQ2: Search for the case. REQ3: find different attribute like who is handling the case, different dates and reports of FIR, Charge Sheet, etc. REQ4: Generate report dynamically of the specific layout. REQ5: Display to the user.

ADD POLICE OFFICER

Description and Priority Add Police Officer will enable each police station to maintain his staff account on the server. It will provide facility to add police officers record at respective police station. Stimulus/Response Sequences Each Police Inspector (PI) will get username and password for his police station by central administrator. Police Inspector (PI) will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open.

 He can insert police officers records. Click on Submit button. Functional Requirements REQ1: Validate username and password input. REQ2: Create online account of police officers whenever new police officer record is entered. REQ3: Message police officer its username and password.

FIR DETAILS
Description and Priority Police officers account helps him to keep track of all cases he is/was handling from FIR to Convince Report. Also provide communication facility. Stimulus/Response Sequences Each Police Inspector (PO) will get username and password from his police station by PI via message. Police officer (PO) will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. Receive crime report of citizen. Generate FIR. He can insert and delete case records under his investigation. He has only view authority for cases, police and criminal record of other police station. Functional Requirements REQ1: Validate username and password input. REQ2: Create different reports in printable format. REQ3: Check authority when accessing case, police or criminal records. REQ4: Communication between different police officers and police stations.

ADD BRANCH
Description and Priority Add Branch will enable to maintain the record of branch. Stimulus/Response Sequences Admin will visit website.

Click on log in. Form appears. He/she will enter username and password. Account gets open. He can insert branch records. Click on Submit button.

Functional Requirements REQ1: Validate username and password input. REQ2: Create online account of branch whenever new branch record is entered.

ADD STATE
Description and Priority Add State will enables the admin to add the state for adding branch and police officers registration. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can insert State records. Click on Add button. Functional Requirements REQ1: Validate username and password input. REQ2: Create online account of state whenever new state record is entered.

ADD CITY
Description and Priority Add City will enable the admin to add the city for adding branch and police officers registration. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can insert City records. Click on Add button. Functional Requirements REQ1: Validate username and password input.

REQ2: Create online account of city whenever new city record is entered.

ADD AREA
Description and Priority Add Area will enable the admin to add the area for adding branch and police officers registration. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can insert City records. Click on Add button. Functional Requirements REQ1: Validate username and password input. REQ2: Create online account of city whenever new city record is entered.

DELETE BRANCH RECORDS

Description and Priority Delete Branch will enable the admin to delete the branch. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can delete branch records. Click on delete button. Functional Requirements REQ1: Validate username and password input. REQ2: Delete online account of branch.

DELETE POLICE OFFICER RECORDS

Description and Priority Delete Police Officer will enable the admin to delete the police officer records.

Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can delete police officer records. Click on delete button. Functional Requirements REQ1: Validate username and password input. REQ2: Delete online account of police officer.

WARRANT RELEASE/REJECT
Description and Priority Magistrate will view the FIR details and according to crime type accept/reject the warrant. Stimulus/Response Sequences Magistrate will visit website. Click on log in. Form appears. He/She will enter username and password. Account gets open. Receive FIR Details. Matching criteria of crime for releasing/rejecting warrant. If criteria match click on Accept button. Else click on Reject button. Functional Requirements REQ1: Validate user input. REQ2: Generate report dynamically of the specific layout. REQ3: Display to the user.

VIEW POLICE OFFICER RECORDS

Description and Priority View Police Officer records will enable the admin to view the police officer records. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears.

 He/she will enter username and password. Account gets open. He can view police officer records by selecting state, city and area. Click on show button. Functional Requirements REQ1: Validate username and password input. REQ2: View online account of police officer.

VIEW BRANCH RECORDS

Description and Priority View Branch records will enable the admin to view the branch records. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can view branch records by selecting state, city and area. Click on show button. Functional Requirements REQ1: Validate username and password input. REQ2: View online account of branch.

VIEW FIR RECORDS

Description and Priority View FIR records will enable the admin to view the FIR records. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears.

 He/she will enter username and password. Account gets open. He can view FIR records. Functional Requirements REQ1: Validate username and password input. REQ2: View online account of FIR reports.

VIEW COMPLAINT RECORDS

Description and Priority View Complaint records will enable the admin to view the Complaint records. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can view Complaint records. Functional Requirements REQ1: Validate username and password input. REQ2: View online account of Complaint reports.

VIEW COMPLAINT STATUS

Description and Priority View Complaint status will enable the admin to view the Complaint Status. Stimulus/Response Sequences Admin will visit website. Click on log in. Form appears. He/she will enter username and password. Account gets open. He can view Complaint Status. Functional Requirements REQ1: Validate username and password input. REQ2: View online account of Complaint Status reports.

The Data Flow Diagram

The first step is to draw a data flow diagram (DFD). The DFD was first developed by Larry Constantine as a way of expressing system requirements in a graphical form this led to a modular design. A DFD , also known as Bubble Chart, has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design phase that functionality decomposes the requirements specifications down to the lowest level of detail. A DFD consist of a series of bubbles joined by lines. The bubbles represent data transformation and the lines represent data flows in the system. DFD Symbols: In the DFD, there are four symbols ,as shown in figure: 1. A square defines a source or destination of system data. 2. An arrow identifies data flow-diagram in motion. It is a pipeline through which information flows. 3. A circle or a bubble ( some people use an oval bubble) represents a Process that transforms incoming data flows(s) into outgoing data flow(s). 4. An open rectangle is a data store-data at rest, or a temporary repository of data. FIGURES Basic Symbols Symbols Meaning

Source or destination of data Data flow Process that transforms data Data Store

DATA-FLOW-DIAGRAM CONTEXT-DIAGRAM
Magistrate Respon se Vie w Respon se Vie w Users Vie w Online Police Service s Vie w Respon se

Admin

Police Officer

Respon se

Admin

Level -1 DFD-Administrator Datab

Updat e record s Online Police Servic es FIR ase

LoginAuthen ticate

User

State City

Level -2 DFD-Administrator Re
gist er rea Bran ch Police Officer Branch Details Police Officer Complaint Details Details FIR Details Complaint Status Admin

LoginAuthe nticate

Online Police Service s

Vie w

Del ete

Branch Details Police Officer Details

Repor t Gener ation

Reports Add Reports

Repo rts User

Level -1 DFD-Police Officer

Police Officer View Complaint Details

Username, Password

Complain t

Login Auth entica te

Onli ne Polic e Servi ces FIR Fill FIR Details

User

Fee dbac k

 Level-2 DFD-Police Officer

Complaint Details Police Officer View Comp laint Username, Password Complaint

LoginAuthen ticate FIR Details Fill FIR FIR

Feedb ack

User

FIR No. Details

 Level-1DFDMagistrate
Magistrate Username, Password View FIR

FIR Details

FIR

LoginAuthen ticate Warra nt

Warrant Release Accept

Reject Warrant Rejected

 Level-1 DFD -Citizen

View

Branch Details

Police Officer Details Citizen Complaint Details Compl aint Registr ation Complai nt Id Compl aint Status Complaint Status Complaint

E-R DIAGRAM
MESS AGE

ADMIN

MAGISTR ATE

LOGI N

POLICE OFFICER

SET COMPL AINT STATUS

ECOPS

VIEWCOM PLAINT DETAILS ANFILL FIR DETAILS

REGISTERC OMPLAINT & VIEW COMPLAIN T STAUS

USER

SYSTEM DESIGN
The design of the system is most critical factor affecting the quality of the software; it has major impact on the phases particularly testing and maintenance. This document is similar to blueprint or plan for the solution. The design activity is often divided into three phases: System Design Detailed Design Database Design

System Design: modules there

System design aims to identify the

Should be in the system, the specification of these modules and how they interact with each other to produce the desired result. At the end of system design all the major data structure, file formats and the major modules in the system and their specifications are decided.

Detailed Design: logic of each of

During detailed design, the internal

the modules specified in the system design are decided. During this phase further of the data structures and the algorithm design of the module is specification. The logic of a module is usually speciation in a high-level design description language, which is independent of the language in which the software will eventually be implemented.

Database Design: - A database may be thought of a set

of related files. Related files means that records in another file. The conventional file based system emphasized that the application and the files were built round it. The database environment emphasizes the independently of application that the use the data. The application is allowed evolve around the database design such that it can adopt the changing needs. Data becomes the central resources in the database environment.

Information system is built around this central resource to give flexible access to data. Special software called Database Management System often referred the database operations. TABLES: LOGIN 1 Field Name user_name password user_type Table: Data Type Varchar Varchar Varchar Size 20 20 20 Description User Name Unique Password Account Type Table: Description Unique State Id State Name Table: Size Description 20 20 20 State Id Unique City Id City Name Table: 4 Description State Id City Id Unique Area Id Area Name

STATE (Details of State) 2 Field Name state_id Data Type Varchar Size 20 20

state_name Varchar CITY (Details Of City) 3 Field Name state_id city_id city_name

Data Type Varchar Varchar Varchar

AREA (Details of Area) Field Name state_id city_id area_id area_name Data Size Type Varchar 20 Varchar 20 Varchar 20 Varchar 20

DEPARTMENT (Details of Department) Table: 5 Field Name Data Size Description Type department_id Varchar 20 20 Unique Department Id Department Name department_name Varchar

CRIME (Details of Act, Crime, Article) Table: 6 Field Name act crime article Data Size Description Type Varchar 20 Act Name Varchar Varchar 20 20 Crime Name Unique Article No. Table:

Add Branch (Details of Branch) 7 Field Name Data Size Description Type branch_id Varchar 20 Unique Branch Id branch_name Varchar 20 Branch Name state Varchar 20 State Name city Varchar 20 City Name area Varchar 20 Area Name pincode Varchar 10 Area Pincode phoneno Varchar 10 Branch Phone No

Police Officer Registration (Details of Police Officer) Table: 8 Field Name reg_no police_name address age dob Data Type Varchar Varchar Varchar Varchar Varchar Size Description 20 20 40 20 20 Unique Registration No. PoliceOfficer Name PoliceOfficer Address PoliceOfficer Age PoliceOfficer DOB

qualification applied_dist department posting

Varchar Varchar Varchar Varchar

40 20 20 20

Qualification Applied District Department Posting

COMPLAINT DETAILS (Details of Complaint) Table: 9 Field Name Data Size Description type complaint_id Varchar 20 Unique Complaint Id complaint_date Varchar name gender state city area pincode phoneno email_id crime_date crime_type crime_info FIR DETAILS 10 Field Name complaint_id name state city area crime_type crime_date criminal_name Data type Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Size 20 20 20 20 20 20 20 20 Description Unique Complaint Id Mulzim Name State City Area Crime Type Crime Date Criminal Name Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar 20 20 20 20 20 20 10 10 20 20 40 60 Complaint Date Mulzim Name Gender State City Area Pincode Phoneno Email Id Crime Date Crime Type Crime Information Table:

cstate ccity address age phoneno crime_info article

Varchar Varchar Varchar Varchar Varchar Varchar Varchar

20 20 40 20 20 40 20

State City Address Age PhoneNo Crime Information Article

Temprily(Details of Warrant) 10 Field Name complaint_id name state city area crime_type crime_date Data type Size Varchar Varchar Varchar Varchar Varchar Varchar Varchar 20 20 30 30 30 60 20 30 30 30 30 30 10 60 20 20 20 Description

Table:

Unique Complaint Id Mulzim Name State City Area Crime Type Crime Date Criminal Name State City Address Age PhoneNo Crime Information Article Warrant Release Warrant Rejected

criminal_name Varchar cstate ccity address age phoneno crime_info article accept reject Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varcha Varchar

FEEDBACK(Details of Messaging) Table: 11 Field Name Data Size Description Type to_rec Varchar 25 Message Reciever EmailId from_sen Varchar 25 Message Sender EmailId Subject Body Varchar Varchar 15 70 Message Topic Message Content

CODING
The main activity of the coding phase is to translate design in to code. In this phase We have to code the design document of Hotel Management System project. The coding phase affects both the testing and maintenance process. The time spent in coding is the smallest percentage of the total software cost, while testing and maintenance consume the major percentage. This phase transform the software design document into a high level language code. Currently, major software companies adhere to some well specified and standard style of coding called Coding Standards. Good code standards improve the understanding of the code. Once the module is developed, a check is carried out to ensure that coding standards are followed. Coding standards generally give guidelines -- -name of modules. -internal and external documentation of source code. -modification history & uniform appearance of code. CODING CONVENTIONS There are some basic coding conventions that are generally followed while writing programs. COMMENTING

Comments are an integral part of any system. Likewise any high quality, properly developed and maintained system, this system too has sufficient comments and description of processes, functions, classes and data structure. PROGRAMMING STYLE Programmers have their own style of writing code. Good programming style makes the code easy to understand. Programming style is important for the following aim reason -to simplify software maintenance -to avoid problems -to achieve simplicity and readability

TESTING
Once source code has been generated, software must be tested to uncover and correct as many errors as possible before delivery to customer. Testing is conducted to uncover errors in internal logic of software components, and in program function, behavior and performance. It is working according to specification, if its behavioral and performance requirements appear to have been met. It improves the reliability and thus quality of the software. Testing of the software starts with small components of it. After completion of the software, it is tested as a whole. The testing that has been performed for this project are WHITE-BOX TESTING,
BLACK-BOX TESTING. TESTING, ALPHA TESTING AND BETA

WHITE-BOX TESTING: - White-box testing of software is predicted on close examination of procedural detail. Logical paths through the software are tested by test cases that exercise specific sets of conditions and/or loops. The status of the program

may be examined at various points to determine if the expected or asserted status corresponds to the actual status. White-box testing can be described as testing in the small that is testing of modules or small groups of modules. Since white-box testing of a small program requires large amount of test cases, it is difficult to test large software. But due to this reason it should not be declared as impractical. A limited number of important paths can be selected and tested. BLACK-BOX TESTING: - Black-box testing is also called Behavioral Testing. It is used to demonstrate that software functions are operational, that input is properly accepted and output is correctly produced and that the integrity of external information is maintained. A black-box text examines some fundamental aspects of a system with little regard for the internal logic of structure of the software. It is a complementary approach to white-box testing. It attempts to find errors in the following categories:1. Incorrect or missing functions 2. Interface errors 3. Errors in data structure or external base access 4. Behavior or performance errors 5. Initialization and terminations errors It is performed during the later stages of testing. After performing white-box and black-box by testing most developer, of but the it errors is are removed the virtually

impossible for him to foresee how the customer will actually use a program. Instructions for use may be misinterpreted; strange combination of data may be regularly used, output that seemed clear to the tester may be unintelligible to a user in the field.

Alpha and beta testing is performed when there are many users of the software to ensure that the users/customers are fully satisfied. A customer conducts alpha test at the developers site. Developer note down the errors encountered during the use of the software. Alpha tests are conducted in a controlled environment. Beta-test is conducted at one or more customer site by the end user of the software. Unlike alpha testing, the developer is not present. In this project, We performed the unit testing after development of a component, here a page. Unit test includes testing of interface, local data structure, boundary condition, independent paths and error handing paths. Unit testing makes heavy use of white box testing techniques, exercising specific paths in a modules control structure to ensure complete coverage and maximum error detection. After completion of development of all the web pages We performed black box testing to confirm that none of the categories of errors mentioned earlier while discussing Black box testing, exists in the developed software/website. After this alpha and beta testing have been conducted.

The validation checks that have been applied to all the entry forms are tested if they are working or not by the following test cases.

ADD STATE FORM: Field Name Input State Name ADD CITY FORM: Field Name City Name ADD AREA FORM: Field Name Area Name If blank

Message Enter the State Name

Input If blank

Message Enter the City Name

Input If blank

Message Enter the Area Name

ADD BRANCH FORM:Field Name Input Branch Id Branch Name Pin code If blank If blank If blank Only numeric values are allowed Limit is given If blank Only numeric values are allowed Limit is given

Message Enter the Branch Id Enter the Branch Name Enter the Pin code Enter in nos Only 6 digits Enter the Phone No Enter in nos Only 10 digits

Phone No

ADD POLICE OFFICER FORM:

Field Name Police Officer Name Age Qualification

Input If blank If blank Only numeric values are allowed If blank

Message Enter the name Enter the age Enter in nos Enter the qualification

COMPLAINT DETAIL FORM Field Name Input Name Pin code If blank If blank Only numeric values are allowed Limit is given If blank Only numeric values are allowed Limit is given Check for valid mail ids Eg. 1 @ , 1 dot(.) operator only and must If blank

Message Enter the Name Enter the Pin code Enter in nos Only 6 digits Enter the Phone No Enter in nos Only 10 digits Enter the valid Email

Phone No

Email Id

Crime Information

Enter Crime Information

FIR DETAIL FORM: Field Name Input Criminal Name Age Address Phone No If blank If blank If blank If blank Only numeric values are allowed Limit is given

Message Enter the Criminal Name Enter the Age Enter the Address . Enter the Phone No Enter in nos Only 10 digits

FEEDBACK FORM:

Field Name To From Subject Body

Input If blank If blank If blank If blank

Message Enter the Email Id Enter the Email Id Enter the Enter the Receiver Sender Topic Matter

CODING
The main activity of the coding phase is to translate design in to code. In this phase We have to code the design document of Hotel Management System project. The coding phase affects both the testing and maintenance process. The time spent in coding is the smallest percentage of the total software cost, while testing and maintenance consume the major percentage. This phase transform the software design document into a high level language code. Currently, major software companies adhere to some well specified and standard style of coding called Coding Standards. Good code standards improve the understanding of the code. Once the module is developed, a check is carried out to ensure that coding standards are followed. Coding standards generally give guidelines -- -name of modules. -internal and external documentation of source code. -modification history & uniform appearance of code. CODING CONVENTIONS There are some basic coding conventions that are generally followed while writing programs. COMMENTING Comments are an integral part of any system. Likewise any high quality, properly developed and maintained system, this system too has sufficient comments and description of processes, functions, classes and data structure. PROGRAMMING STYLE Programmers have their own style of writing code. Good programming style makes the code easy to understand. Programming style is important for the following aim reason -to simplify software maintenance -to avoid problems -to achieve simplicity and readability

TESTING
Once source code has been generated, software must be tested to uncover and correct as many errors as possible before delivery to customer. Testing is conducted to uncover errors in internal logic of software components, and in program function, behavior and performance. It is working according to specification, if its behavioral and performance requirements appear to have been met. It improves the reliability and thus quality of the software. Testing of the software starts with small components of it. After completion of the software, it is tested as a whole. The testing that has been performed for this project are WHITE-BOX TESTING,
BLACK-BOX TESTING. TESTING, ALPHA TESTING AND BETA

WHITE-BOX TESTING: - White-box testing of software is predicted on close examination of procedural detail. Logical paths through the software are tested by test cases that exercise specific sets of conditions and/or loops. The status of the program may be examined at various points to determine if the expected or asserted status corresponds to the actual status. White-box testing can be described as testing in the small that is testing of modules or small groups of modules. Since white-box testing of a small program requires large amount of test cases, it is difficult to test large software. But due to this reason it should not be declared as impractical. A limited number of important paths can be selected and tested. BLACK-BOX TESTING: - Black-box testing is also called Behavioral Testing. It is used to demonstrate that software functions are operational, that input is properly accepted and output is correctly produced

and that the integrity of external information is maintained. A black-box text examines some fundamental aspects of a system with little regard for the internal logic of structure of the software. It is a complementary approach to white-box testing. It attempts to find errors in the following categories:1. Incorrect or missing functions 2. Interface errors 3. Errors in data structure or external base access 4. Behavior or performance errors 5. Initialization and terminations errors It is performed during the later stages of testing. After performing white-box and black-box by testing most developer, of but the it errors is are removed the virtually

impossible for him to foresee how the customer will actually use a program. Instructions for use may be misinterpreted; strange combination of data may be regularly used, output that seemed clear to the tester may be unintelligible to a user in the field. Alpha and beta testing is performed when there are many users of the software to ensure that the users/customers are fully satisfied. A customer conducts alpha test at the developers site. Developer note down the errors encountered during the use of the software. Alpha tests are conducted in a controlled environment. Beta-test is conducted at one or more customer site by the end user of the software. Unlike alpha testing, the developer is not present.

In this project, We performed the unit testing after development of a component, here a page. Unit test includes testing of interface, local data structure, boundary condition, independent paths and error handing paths. Unit testing makes heavy use of white box testing techniques, exercising specific paths in a modules control structure to ensure complete coverage and maximum error detection. After completion of development of all the web pages We performed black box testing to confirm that none of the categories of errors mentioned earlier while discussing Black box testing, exists in the developed software/website. After this alpha and beta testing have been conducted. The validation checks that have been applied to all the entry forms are tested if they are working or not by the following test cases.

TEST CASES: ADD STATE FORM: Field Name Input State Name ADD CITY FORM: Field Name City Name ADD AREA FORM: Field Name Area Name If blank Message Enter the State Name

Input If blank

Message Enter the City Name

Input If blank

Message Enter the Area Name

ADD BRANCH FORM:Field Name Input Branch Id Branch Name Pin code If blank If blank If blank Only numeric values are allowed Limit is given If blank Only numeric values are allowed Limit is given

Message Enter the Branch Id Enter the Branch Name Enter the Pin code Enter in nos Only 6 digits Enter the Phone No Enter in nos Only 10 digits

Phone No

ADD POLICE OFFICER FORM: Field Name Input Police Officer Name Age If blank If blank Only numeric

Message Enter the name Enter the age Enter in nos

Qualification

values are allowed If blank

Enter the qualification

COMPLAINT DETAIL FORM Field Name Input Name Pin code If blank If blank Only numeric values are allowed Limit is given If blank Only numeric values are allowed Limit is given Check for valid mail ids Eg. 1 @ , 1 dot(.) operator only and must If blank

Message Enter the Name Enter the Pin code Enter in nos Only 6 digits Enter the Phone No Enter in nos Only 10 digits Enter the valid Email

Phone No

Email Id

Crime Information

Enter Crime Information

FIR DETAIL FORM: Field Name Input Criminal Name Age Address Phone No If blank If blank If blank If blank Only numeric values are allowed Limit is given

Message Enter the Criminal Name Enter the Age Enter the Address . Enter the Phone No Enter in nos Only 10 digits

FEEDBACK FORM: Field Name Input To From If blank If blank

Message Enter the Receiver Email Id Enter the Sender Email Id

Subject Body

If blank If blank

Enter the Topic Enter the Matter

GANTT CHART

Gantt chart is also known as Time Line Charts. A Gantt chart can be developed for the entire project or a separate chart can be developed for each function. A tabular form is maintained where rows indicate the tasks with milestones and columns indicate duration (weeks/months). The horizontal bars that spans across columns indicate duration of the task.
April Requirement Gathering Design Test Cases Coding Testing Build June July August

SCREEN SHOTS:HOME-PAGE:

ADMIN-LOGIN:

WELCOME TO ADMIN:

ADMIN REGISTRATION MENU:

ADD BRANCH: ADD POLICEOFFICER:

ADD STATE: ADD CITY: ADD AREA:

ADD POLICEOFFICER:

ADD STATE:

ADD AREA:

ADMIN VIEW:

VIEW BRANCH DETAIL:

VIEW POLICEOFFICER DETAIL:

ADMIN DELETE:

DELETE BRANCH:

DELETE POLICEOFFICER:

MAGISTRATE LOGIN:

WELCOME TO MAGISTRATE:

VIEW FIR:

VIEW FIR DETAIL:

FIR ACCEPT:

ADMIN POLICEOFFICER:

WELCOME TO POLICEOFFICER:

VIEW COMPLAINT DETAIL:

FIR REGISTERED:

FEEDBACK FORM :

REPORTS: BRANCH DETAIL:

POLICEOFFICER:

FIR DETAIL:

COMPLAINT-DETAIL:

COMPLAINT STATUS:

CODE PAGE: Login.aspx.cs

using using using using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Xml.Linq; System.Data.SqlClient;

public partial class MasterPage : System.Web.UI.MasterPage { Class1 obj = new Class1(); protected void Page_Load(object sender, EventArgs e) { obj.connect(); } protected void btnLogin_Click1(object sender, EventArgs e) { if (lstUserType.SelectedIndex == 1) { obj.cmd.CommandText = "select * from login where user_name='" + txtUserName.Text + "'and password='" + txtPassword.Text + "'"; obj.adp.Fill(obj.ds, "login"); if (obj.ds.Tables["login"].Rows.Count == 0) { lblMsg.Text = "Wrong Entry"; txtPassword.Text = ""; } else { Session.Add("l1", txtUserName.Text); Response.Redirect("Admin.aspx"); } } else if(lstUserType.SelectedIndex == 2) { obj.cmd.CommandText="select * from login where user_name='"+txtUserName.Text+"' and password='"+txtPassword.Text+ "'"; obj.adp.Fill(obj.ds,"login"); if (obj.ds.Tables["login"].Rows.Count == 0) { lblMsg.Text = "Wrong Entry";

} else { }

txtPassword.Text = "";

Session.Add("l1", txtUserName.Text); Response.Redirect("Magistrate.aspx"); } else if(lstUserType.SelectedIndex == 3) { obj.cmd.CommandText="select * from login where user_name='"+txtUserName.Text+"' and password='"+txtPassword.Text+"'"; obj.adp.Fill(obj.ds,"login"); if (obj.ds.Tables["login"].Rows.Count == 0) { lblMsg.Text = "Wrong Entry"; txtPassword.Text = ""; } else { Session.Add("l1", txtUserName.Text); Response.Redirect("PoliceOfficer.aspx"); } } } protected void chkRem_CheckedChanged(object sender, EventArgs e) { } }

CODE PAGE: Addstate.aspx.cs

public partial class AddState : System.Web.UI.Page { Class1 obj = new Class1(); int a; protected void Page_Load(object sender, EventArgs e) { obj.connect(); txtStateid.Enabled = false; obj.con.Open(); obj.cmd.CommandText = "select max(state_id) from state"; obj.adp.Fill(obj.ds, "state"); object app = obj.cmd.ExecuteScalar(); obj.con.Close();

if (app is DBNull) else a = 1001;

a = Convert.ToInt32(app) + 1; txtStateid.Text = Convert.ToString(a); } protected void btnAdd_Click1(object sender, EventArgs e) { obj.cmd.CommandText = "Select * from state"; obj.adp.Fill(obj.ds, "state"); obj.dr = obj.ds.Tables["state"].NewRow(); obj.dr["state_id"] = txtStateid.Text; obj.dr["state_name"] = txtStatename.Text; obj.ds.Tables["state"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from state"; obj.adp.Fill(obj.ds, "state"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["state"]); lblInfo.Text = ("Added Successfully..."); obj.con.Open(); obj.cmd.CommandText = "select max(state_id) from state"; obj.adp.Fill(obj.ds, "state"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) a = 1001; else a = Convert.ToInt32(app) + 1; txtStateid.Text = Convert.ToString(a); txtStatename.Text = " "; } }

CODE PAGE: AddCity.aspx.cs

public partial class AddCity : System.Web.UI.Page { int a; Class1 obj = new Class1(); protected void Page_Load(object sender, EventArgs e) { obj.connect(); if (!Page.IsPostBack) { obj.cmd.CommandText = "select * from state"; obj.adp.Fill(obj.ds, "state"); //lstStateName.DataValueField = "state_id"; lstStateName.DataTextField = "state_name"; lstStateName.DataSource = obj.ds.Tables["state"]; lstStateName.DataBind(); } txtCityId.Enabled = false;

obj.con.Open(); obj.cmd.CommandText = "select max(city_id) from city"; obj.adp.Fill(obj.ds, "city"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) a = 2001; else a = Convert.ToInt32(app) + 1; txtCityId.Text = Convert.ToString(a);

} protected void btnAdd_Click(object sender, EventArgs e) { obj.cmd.CommandText = "select * from city"; obj.adp.Fill(obj.ds, "city"); obj.dr = obj.ds.Tables["city"].NewRow(); obj.dr["state_id"] = lstStateName.Text; obj.dr["city_id"] = txtCityId.Text; obj.dr["city_name"] = txtCityName.Text; obj.ds.Tables["city"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from city"; obj.adp.Fill(obj.ds, "city"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["city"]); lblInfo.Text = ("Added Successfully..."); obj.con.Open(); obj.cmd.CommandText = "select max(city_id) from city"; obj.adp.Fill(obj.ds, "city"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) a = 2001; else a = Convert.ToInt32(app) + 1; txtCityId.Text = Convert.ToString(a); txtCityName.Text = " "; } }

CODE PAGE: AddArea.aspx.cs

public partial class AddArea : System.Web.UI.Page { Class1 obj = new Class1(); int a; protected void Page_Load(object sender, EventArgs e) { obj.connect(); if (!Page.IsPostBack) { obj.cmd.CommandText = "select * from state"; obj.adp.Fill(obj.ds,"state"); lstStateName.DataTextField = "State_name"; lstStateName.DataValueField = "State_id"; lstStateName.DataSource=obj.ds.Tables["state"];

lstStateName.DataBind(); obj.cmd.CommandText = "select * from city"; obj.adp.Fill(obj.ds, "city"); lstCityName.DataTextField = "city_name"; lstCityName.DataValueField = "city_id"; lstCityName.DataSource = obj.ds.Tables["city"]; lstCityName.DataBind();

txtAreaId.Enabled = false; obj.con.Open(); obj.cmd.CommandText = "select max(area_id) from area"; obj.adp.Fill(obj.ds, "area"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) a = 3001; else } a = Convert.ToInt32(app) + 1; txtAreaId.Text = Convert.ToString(a);

protected void Button1_Click1(object sender, EventArgs e) { obj.cmd.CommandText = "select * from area"; obj.adp.Fill(obj.ds, "area"); obj.dr = obj.ds.Tables["area"].NewRow(); obj.dr["State_id"] = lstStateName.Text; obj.dr["city_id"] = lstCityName.Text; obj.dr["area_id"] = txtAreaId.Text; obj.dr["area_name"] = txtAreaName.Text; obj.ds.Tables["area"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from area"; obj.adp.Fill(obj.ds, "area"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["area"]); lblInfo.Text = ("Added Successfully..."); obj.con.Open(); obj.cmd.CommandText = "select max(area_id) from area"; obj.adp.Fill(obj.ds, "area"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) a = 3001; else a = Convert.ToInt32(app) + 1; txtAreaId.Text = Convert.ToString(a); txtAreaName.Text = ""; } }

CODE PAGE: AddBranch.aspx.cs

public partial class AddBranch : System.Web.UI.Page

Class1 obj = new Class1(); protected void Page_Load(object sender, EventArgs e) { obj.connect(); if (!Page.IsPostBack) { obj.cmd.CommandText = "Select * from state"; obj.adp.Fill(obj.ds, "state"); lstState.DataSource = obj.ds.Tables["state"]; lstState.DataTextField = "state_name"; lstState.DataBind(); obj.cmd.CommandText = "select * from city"; obj.adp.Fill(obj.ds, "city"); lstCity.DataSource = obj.ds.Tables["city"]; lstCity.DataTextField = "city_name"; lstCity.DataBind(); obj.cmd.CommandText = "select * from area"; obj.adp.Fill(obj.ds, "area"); lstArea.DataSource = obj.ds.Tables["area"]; lstArea.DataTextField = "area_name"; lstArea.DataBind(); } } protected void Button1_Click(object sender, EventArgs e) { obj.cmd.CommandText = "select * from addbranch"; obj.adp.Fill(obj.ds, "addbch"); obj.dr = obj.ds.Tables["addbch"].NewRow(); obj.dr["branch_id"] = txtBranchId.Text; obj.dr["branch_name"] = txtBranchName.Text; obj.dr["state"] = lstState.Text; obj.dr["city"] = lstCity.Text; obj.dr["area"] = lstArea.Text; obj.dr["pincode"] = txtPincode.Text; obj.dr["phoneno"] = txtPhoneNo.Text; obj.ds.Tables["addbch"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from addbranch"; obj.adp.Fill(obj.ds, "addbch"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["addbch"]); lblInfo.Text = ("Branch added successfully....."); } protected void btnClear_Click(object sender, EventArgs e) { txtBranchId.Text = ""; txtBranchName.Text = ""; txtPhoneNo.Text = ""; txtPincode.Text = ""; }

CODE PAGE: AddPoliceOfficer.aspx.cs

public partial class AddPoliceOfficer : System.Web.UI.Page { Class1 obj = new Class1(); int a; protected void Page_Load(object sender, EventArgs e) { obj.connect(); txtRegId.Enabled=false; obj.con.Open(); obj.cmd.CommandText = "select max(reg_no) from addpoliceofficer"; obj.adp.Fill(obj.ds, "addpol"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) else a = 1;

a = Convert.ToInt32(app) + 1; txtRegId.Text=Convert.ToString(a); if (!Page.IsPostBack) { obj.cmd.CommandText = "select * from city"; obj.adp.Fill(obj.ds, "city"); //lstCity.Items.Add("Select Type"); lstCity.DataSource = obj.ds.Tables["city"]; lstCity.DataTextField = "city_name"; lstCity.DataBind(); obj.cmd.CommandText = "select * from department"; obj.adp.Fill(obj.ds, "department"); //lstDepartment.Items.Add("Select Type"); lstDepartment.DataSource = obj.ds.Tables["department"]; lstDepartment.DataTextField = "department_name"; lstDepartment.DataBind(); obj.cmd.CommandText = "select * from area"; obj.adp.Fill(obj.ds, "area"); //lstArea.Items.Add("Select Type"); lstArea.DataSource = obj.ds.Tables["area"]; lstArea.DataTextField = "area_name"; lstArea.DataBind(); } lstDate.Items.Add("Select Type"); for (int i = 1; i <= 31; i++) { lstDate.Items.Add(i.ToString()); } lstMonth.Items.Add("Select Type"); lstMonth.Items.Add("Jan"); lstMonth.Items.Add("Feb"); lstMonth.Items.Add("Mar"); lstMonth.Items.Add("Apr"); lstMonth.Items.Add("May"); lstMonth.Items.Add("Jun"); lstMonth.Items.Add("July"); lstMonth.Items.Add("Aug"); lstMonth.Items.Add("Sep"); lstMonth.Items.Add("Oct"); lstMonth.Items.Add("Nov"); lstMonth.Items.Add("Dec"); lstYear.Items.Add("Select Type");

for (int i = 1950; i <= 2012; i++) { lstYear.Items.Add(i.ToString()); } } protected void Button1_Click(object sender, EventArgs e) { string s; s = lstDate.Text + "-" + lstMonth.Text + "-" + lstYear.Text; obj.cmd.CommandText = "select * from addpoliceofficer"; obj.adp.Fill(obj.ds, "addpol"); obj.dr = obj.ds.Tables["addpol"].NewRow(); obj.dr["reg_no"] = txtRegId.Text; obj.dr["police_name"] = txtName.Text; obj.dr["address"] = txtAddress.Text; obj.dr["age"] = txtAge.Text; obj.dr["dob"] = s; obj.dr["qualification"] = txtQualification.Text; obj.dr["applied_dist"] = lstCity.Text; obj.dr["department"] = lstDepartment.Text; obj.dr["posting"] = lstArea.Text; obj.ds.Tables["addpol"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from addpoliceofficer"; obj.adp.Fill(obj.ds, "addpol"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["addpol"]); lblInfo.Text = ("Registration complete successfully....."); } protected void btnClear_Click(object sender, EventArgs e) { txtRegId.Text = ""; txtName.Text = ""; txtAddress.Text = ""; txtAge.Text = ""; lstDate.Text = "Select Type"; lstMonth.Text = "Select Type"; lstYear.Text = "Select Type"; txtQualification.Text = ""; //lstCity.Text = "Select Type"; //lstDepartment.Text = "Select Type"; //lstArea.Text = "Select Type"; obj.con.Open(); obj.cmd.CommandText = "select max(reg_no) from addpoliceofficer"; obj.adp.Fill(obj.ds, "addpol"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) else } a = 1;

a = Convert.ToInt32(app) + 1; txtRegId.Text = Convert.ToString(a);

CODE PAGE: AdminViewBranchDetail.aspx.cs

public partial class AddViewBranchDetail: System.Web.UI.Page { Class1 obj = new Class1(); protected void page_load(object sender,EventArgs e) { obj.connect(); if (!Page.IsPostBack) { obj.cmd.CommandText = "select * from state"; obj.adp.Fill(obj.ds, "state"); lstState.DataSource = obj.ds.Tables["state"]; lstState.DataTextField = "state_name"; lstState.DataBind(); obj.cmd.CommandText = "select * from city"; obj.adp.Fill(obj.ds, "city"); lstCity.DataSource = obj.ds.Tables["city"]; lstCity.DataTextField = "city_name"; lstCity.DataBind(); obj.cmd.CommandText = "select * from area"; obj.adp.Fill(obj.ds, "area"); lstArea.DataSource = obj.ds.Tables["area"]; lstArea.DataTextField = "area_name"; lstArea.DataBind(); } } protected void btnShow_Click(object sender, EventArgs e) { obj.cmd.CommandText = "select * from addbranch where state='" + lstState.Text + "' and city='" + lstCity.Text + "' and area='" + lstArea.Text + "'"; obj.adp.Fill(obj.ds, "branch"); if (obj.ds.Tables["branch"].Rows.Count == 0) { lblMsg.Text = ("No Record Found"); } else { GridView2.DataSource = obj.ds.Tables["branch"]; GridView2.DataBind(); } } }

CODE PAGE: AdminViewPoliceOfficerDetails.aspx.cs

public partial class AdminViewPoliceOfficerDetails : System.Web.UI.Page { Class1 obj = new Class1(); protected void Page_Load(object sender, EventArgs e) {

obj.connect(); if (!Page.IsPostBack) { obj.cmd.CommandText = "select * from addpoliceofficer"; obj.adp.Fill(obj.ds, "pol"); lstState.DataSource = obj.ds.Tables["pol"]; lstState.DataTextField = "applied_dist"; lstState.DataBind(); obj.cmd.CommandText = "select department_name from department"; obj.adp.Fill(obj.ds, "city"); lstDepartment.DataSource = obj.ds.Tables["city"]; lstDepartment.DataTextField = "department_name"; lstDepartment.DataBind(); obj.cmd.CommandText = "select * from area"; obj.adp.Fill(obj.ds, "area"); lstArea.DataSource = obj.ds.Tables["area"]; lstArea.DataTextField = "area_name"; lstArea.DataBind(); } } protected void btnShow_Click(object sender, EventArgs e) { obj.cmd.CommandText = "select * from addpoliceofficer where applied_dist='" + lstState.Text + "' and department='" + lstDepartment.Text + "' and posting='" + lstArea.Text + "'"; obj.adp.Fill(obj.ds, "pol"); if (obj.ds.Tables["pol"].Rows.Count == 0) { lblMsg.Text = ("No Record Found"); } else { lblMsg.Text = ""; GridView2.DataSource = obj.ds.Tables["pol"]; GridView2.DataBind(); } } protected void btnReciept_Click(object sender, EventArgs e) { Response.Redirect("ReportPoliceOfficer.aspx"); } }

CODE PAGE: ComplaintDetails.aspx.cs

public partial class ComplaintDetails : System.Web.UI.Page { Class1 obj = new Class1(); int a; protected void Page_Load(object sender, EventArgs e) { obj.connect(); txtComplaintId.Enabled = false;

obj.con.Open(); obj.cmd.CommandText = "select max(complaint_id) from complaintdetail"; obj.adp.Fill(obj.ds, "comd"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) else a = 1;

a = Convert.ToInt32(app) + 1; txtComplaintId.Text = Convert.ToString(a); if (!Page.IsPostBack) { obj.cmd.CommandText = "select * from crime"; obj.adp.Fill(obj.ds, "crime"); lstCrimeType.DataSource = obj.ds.Tables["crime"]; lstCrimeType.DataTextField = "crime_type"; lstCrimeType.DataBind(); obj.cmd.CommandText = "select * from state"; obj.adp.Fill(obj.ds, "state"); lstState.DataSource = obj.ds.Tables["state"]; lstState.DataTextField = "state_name"; lstState.DataBind(); obj.cmd.CommandText = "select * from city "; obj.adp.Fill(obj.ds, "city"); lstCity.DataSource = obj.ds.Tables["city"]; lstCity.DataTextField = "city_name"; lstCity.DataBind(); obj.cmd.CommandText = "select * from area"; obj.adp.Fill(obj.ds, "area"); lstArea.DataSource = obj.ds.Tables["area"]; lstArea.DataTextField = "area_name"; lstArea.DataBind(); lstDate.Items.Add("Select Type"); for (int i = 1; i <= 31; i++) { lstDate.Items.Add(i.ToString()); } lstMonth.Items.Add("Select Type"); lstMonth.Items.Add("Jan"); lstMonth.Items.Add("Feb"); lstMonth.Items.Add("Mar"); lstMonth.Items.Add("Apr"); lstMonth.Items.Add("May"); lstMonth.Items.Add("Jun"); lstMonth.Items.Add("July"); lstMonth.Items.Add("Aug"); lstMonth.Items.Add("Sep"); lstMonth.Items.Add("Oct"); lstMonth.Items.Add("Nov"); lstMonth.Items.Add("Dec"); lstYear.Items.Add("Select Type"); for (int i = 1950; i <= 2012; i++) {

} }

lstYear.Items.Add(i.ToString());

} protected void btnClear_Click(object sender, EventArgs e) { txtComplaintDate.Text = ""; txtName.Text = ""; rdbFemale.Checked = false; rdbMale.Checked = false; txtPhoneNo.Text = ""; txtPincode.Text = ""; txtEmailId.Text = ""; txtCrimeInfo.Text = ""; lstDate.SelectedIndex=0; lstMonth.SelectedIndex=0; lstYear.SelectedIndex=0; obj.con.Open(); obj.cmd.CommandText = "select max(complaint_id) from complaintdetail"; obj.adp.Fill(obj.ds, "complaintdetail"); object app = obj.cmd.ExecuteScalar(); obj.con.Close(); if (app is DBNull) else a = 1;

a = Convert.ToInt32(app) + 1; txtComplaintId.Text = Convert.ToString(a); } protected void btnSubmit_Click(object sender, EventArgs e) { string s; s = lstDate.Text + "-" + lstMonth.Text + "-" + lstYear.Text; obj.cmd.CommandText = "select * from complaintdetail"; obj.adp.Fill(obj.ds, "comd"); obj.dr = obj.ds.Tables["comd"].NewRow(); obj.dr["complaint_id"] = txtComplaintId.Text; obj.dr["complaint_date"] = txtComplaintDate.Text; obj.dr["name"] = txtName.Text; if (rdbMale.Checked == true) { obj.dr["gender"] = rdbMale.Text; } else { obj.dr["gender"] = rdbFemale.Text; } obj.dr["state"] = lstState.Text; obj.dr["city"] = lstCity.Text; obj.dr["area"] = lstArea.Text; obj.dr["pincode"] = txtPincode.Text; obj.dr["phoneno"] = txtPhoneNo.Text; obj.dr["email_id"] = txtEmailId.Text; obj.dr["crime_date"] = s;

obj.dr["crime_type"] = lstCrimeType.Text; obj.dr["crime_info"] = txtCrimeInfo.Text; obj.ds.Tables["comd"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from complaintdetail"; obj.adp.Fill(obj.ds, "comd"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["comd"]); lblInfo.Text = ("Complaint Registered successfully"); } }

CODE PAGE: FIRDetail.aspx.cs

public partial class FIRDetail : System.Web.UI.Page { Class1 obj = new Class1(); protected void Page_Load(object sender, EventArgs e) { obj.connect(); if (!Page.IsPostBack) { obj.cmd.CommandText = "select * from crime"; obj.adp.Fill(obj.ds, "crime"); lstArticle.DataSource = obj.ds.Tables["crime"]; lstArticle.DataTextField = "article"; lstArticle.DataBind(); obj.cmd.CommandText = "Select * from state"; obj.adp.Fill(obj.ds, "state"); lstState.DataSource = obj.ds.Tables["state"]; lstState.DataTextField = "state_name"; lstState.DataBind(); obj.cmd.CommandText = "select * from city"; obj.adp.Fill(obj.ds, "city"); lstCity.DataSource = obj.ds.Tables["city"]; lstCity.DataTextField = "city_name"; lstCity.DataBind(); obj.cmd.CommandText = "select * from complaintdetail"; obj.adp.Fill(obj.ds, "comd"); lstComplaintId.DataSource = obj.ds.Tables["comd"]; lstComplaintId.DataTextField = "complaint_id"; lstComplaintId.DataBind(); } } protected void btnSubmit_Click1(object sender, EventArgs e) { obj.cmd.CommandText = "select * from firdetail"; obj.adp.Fill(obj.ds, "fir"); obj.dr = obj.ds.Tables["fir"].NewRow(); obj.dr["complaint_id"] = lstComplaintId.Text;

obj.dr["name"] = lblName.Text; obj.dr["state"] = lblState.Text; obj.dr["city"] = lblCity.Text; obj.dr["area"] = lblArea.Text; obj.dr["crime_type"] = lblCrimeType.Text; obj.dr["crime_date"] = lblCrimeDate.Text; obj.dr["criminal_name"] = txtName.Text; obj.dr["cstate"] = lstState.Text; obj.dr["ccity"] = lstCity.Text; obj.dr["address"] = txtAddress.Text; obj.dr["age"] = txtAge.Text; obj.dr["phoneno"] = txtPhoneNo.Text; obj.dr["crime_info"] = lblCrimeInfo.Text; obj.dr["article"] = lstArticle.Text; obj.ds.Tables["fir"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from firdetail"; obj.adp.Fill(obj.ds,"fir"); obj.cb=new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["fir"]); lblInfo.Text="Record added successfully"; } protected void btnClick_Click(object sender, EventArgs e) { obj.cmd.CommandText = "select name,state,city,area,crime_type,crime_date,crime_info from complaintdetail where complaint_id='" + lstComplaintId.Text+ "'"; obj.adp.Fill(obj.ds, "comd"); lblName.Text = obj.ds.Tables["comd"].Rows[0] [0].ToString(); lblState.Text = obj.ds.Tables["comd"].Rows[0] [1].ToString(); lblCity.Text=obj.ds.Tables["comd"].Rows[0] [2].ToString(); lblArea.Text=obj.ds.Tables["comd"].Rows[0] [3].ToString(); lblCrimeType.Text=obj.ds.Tables["comd"].Rows[0] [4].ToString(); lblCrimeDate.Text=obj.ds.Tables["comd"].Rows[0] [5].ToString(); lblCrimeInfo.Text = obj.ds.Tables["comd"].Rows[0] [6].ToString(); } protected void btnClear_Click(object sender, EventArgs e) { lblName.Text = ""; lblState.Text = ""; lblCity.Text = ""; lblCrimeDate.Text = ""; lblCrimeType.Text=""; txtName.Text = ""; txtPhoneNo.Text = ""; txtAddress.Text = ""; txtAge.Text = ""; lblInfo.Text = ""; lblArea.Text = ""; } }

CODE PAGE: MagistrateViewComplaintDetails.aspx.cs

public partial class MagistrateViewComplaintDetails : System.Web.UI.Page { Class1 obj = new Class1(); protected void Page_Load(object sender, EventArgs e) { obj.connect(); obj.cmd.CommandText = "select * from firdetail"; obj.adp.Fill(obj.ds, "fir"); lstComplaintId.DataSource = obj.ds.Tables["fir"]; lstComplaintId.DataTextField = "complaint_id"; lstComplaintId.DataBind();

} protected void Button1_Click(object sender, EventArgs e) { obj.cmd.CommandText = "Select * from firdetail where complaint_id='" + lstComplaintId.Text + "'"; obj.adp.Fill(obj.ds,"fir"); if (obj.ds.Tables["fir"].Rows.Count == 0) { lblMsg.Text = ("Work in process.............."); } else { { obj.cmd.CommandText = "select * from firdetail"; obj.adp.Fill(obj.ds, "fir"); DetailsView2.DataSource = obj.ds.Tables["fir"]; DetailsView2.DataBind(); } } protected void btnAccept_Click(object sender, EventArgs e) { obj.cmd.CommandText = "select * from temprily"; obj.adp.Fill(obj.ds, "temp"); obj.dr = obj.ds.Tables["temp"].NewRow(); obj.dr["complaint_id"] = obj.ds.Tables["fir"].Rows[0] [0].ToString(); obj.dr["nam"] = obj.ds.Tables["fir"].Rows[0] [1].ToString(); obj.dr["state"] = obj.ds.Tables["fir"].Rows[0] [2].ToString(); obj.dr["city"] = obj.ds.Tables["fir"].Rows[0] [3].ToString(); obj.dr["area"] = obj.ds.Tables["fir"].Rows[0] [4].ToString(); obj.dr["crime_type"] = obj.ds.Tables["fir"].Rows[0] [5].ToString(); obj.dr["crime_date"] = obj.ds.Tables["fir"].Rows[0] [6].ToString();

obj.dr["criminal_name"] = obj.ds.Tables["fir"].Rows[0] [7].ToString(); obj.dr["address"] = obj.ds.Tables["fir"].Rows[0] [10].ToString(); obj.dr["age"] = obj.ds.Tables["fir"].Rows[0] [11].ToString(); obj.dr["cstate"] = obj.ds.Tables["fir"].Rows[0] [8].ToString(); obj.dr["ccity"] = obj.ds.Tables["fir"].Rows[0] [9].ToString(); obj.dr["phone_no"] = obj.ds.Tables["fir"].Rows[0] [12].ToString(); obj.dr["article"] = obj.ds.Tables["fir"].Rows[0] [14].ToString(); obj.dr["crime_info"] = obj.ds.Tables["fir"].Rows[0] [13].ToString(); obj.dr["accept"] = btnAccept.Text; lblInfo.Text = "Warrant Release"; obj.ds.Tables["temp"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from temprily"; obj.adp.Fill(obj.ds, "temp"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["temp"]); } protected void btnReject_Click1(object sender, EventArgs e) { obj.cmd.CommandText = "select * from temprily"; obj.adp.Fill(obj.ds, "temp"); obj.dr = obj.ds.Tables["temp"].NewRow(); obj.dr["complaint_id"] = obj.ds.Tables["fir"].Rows[0] [0].ToString(); obj.dr["nam"] = obj.ds.Tables["fir"].Rows[0] [1].ToString(); obj.dr["state"] = obj.ds.Tables["fir"].Rows[0] [2].ToString(); obj.dr["city"] = obj.ds.Tables["fir"].Rows[0] [3].ToString(); obj.dr["area"] = obj.ds.Tables["fir"].Rows[0] [4].ToString(); obj.dr["crime_type"] = obj.ds.Tables["fir"].Rows[0] [5].ToString(); obj.dr["crime_date"] = obj.ds.Tables["fir"].Rows[0] [6].ToString(); obj.dr["criminal_name"] = obj.ds.Tables["fir"].Rows[0] [7].ToString(); obj.dr["address"] = obj.ds.Tables["fir"].Rows[0] [10].ToString(); obj.dr["age"] = obj.ds.Tables["fir"].Rows[0] [11].ToString(); obj.dr["cstate"] = obj.ds.Tables["fir"].Rows[0] [8].ToString(); obj.dr["ccity"] = obj.ds.Tables["fir"].Rows[0] [9].ToString(); obj.dr["phone_no"] = obj.ds.Tables["fir"].Rows[0] [12].ToString(); obj.dr["article"] = obj.ds.Tables["fir"].Rows[0] [13].ToString(); obj.dr["crime_info"] = obj.ds.Tables["fir"].Rows[0] [14].ToString();

obj.dr["reject"] = btnReject.Text; lblInfo.Text = "Warrant Rejected"; obj.ds.Tables["temp"].Rows.Add(obj.dr); obj.cmd.CommandText = "select * from temprily"; obj.adp.Fill(obj.ds, "temp"); obj.cb = new SqlCommandBuilder(obj.adp); obj.adp.Update(obj.ds.Tables["temp"]); } }

CODE PAGE: DeleteBranch.aspx.cs

public partial class DeleteBranch: System.Web.UI.Page { Class1 obj = new Class1(); CheckBox chk = new CheckBox(); protected void Page_Load(object sender, EventArgs e) { obj.connect(); if (!Page.IsPostBack) { bind(); } } public void bind() { obj.cmd.CommandText = "select * from addbranch"; obj.adp.Fill(obj.ds, "branch"); GD1.DataSource = obj.ds.Tables["branch"]; GD1.DataBind(); } protected void cmdSelectAll_Click(object sender, EventArgs e) { foreach (GridViewRow gd in GD1.Rows) { chk = (CheckBox)gd.FindControl("ch1"); chk.Checked = true; } } protected void cmdDelete_Click(object sender, EventArgs e) { foreach (GridViewRow gd in GD1.Rows) { chk = (CheckBox)gd.FindControl("ch1"); if (chk.Checked == true) { obj.con.Open(); obj.cmd.CommandText = "delete from addbranch where branch_id='" + gd.Cells[1].Text + "'"; obj.cmd.ExecuteNonQuery(); obj.con.Close(); } } bind(); }

CODE PAGE: DeletePoliceOfficer.aspx.cs

public partial class DeletePoliceOfficer : System.Web.UI.Page { Class1 obj = new Class1(); CheckBox chk = new CheckBox(); protected void Page_Load(object sender, EventArgs e) { obj.connect(); if (!Page.IsPostBack) { bind(); } } public void bind() { obj.cmd.CommandText = "select * from addpoliceofficer"; obj.adp.Fill(obj.ds, "police"); GD2.DataSource = obj.ds.Tables["police"]; GD2.DataBind(); } protected void cmdSelectAll_Click(object sender, EventArgs e) { foreach (GridView gd in GD2.Rows) { chk = (CheckBox)gd.FindControl("ch1"); chk.Checked = true; } } protected void cmdDelete_Click(object sender, EventArgs e) { foreach (GridViewRow gd in GD2.Rows) { chk = (CheckBox)gd.FindControl("ch1"); if (chk.Checked == true) { obj.con.Open(); obj.cmd.CommandText = "delete from addpoliceofficer where reg_no='" + gd.Cells[1].Text + "'"; obj.cmd.ExecuteNonQuery(); obj.con.Close(); } } bind(); } }

CODE PAGE: feedback.aspx.cs

public partial class feedback : System.Web.UI.Page

Class1 obj = new Class1(); protected void Page_Load(object sender, EventArgs e) { txtTo.Enabled = false; obj.connect(); } protected void btnSend_Click(object sender, EventArgs e) { String from = txtFrom.Text.ToString(); String to = txtTo.Text.ToString(); String subject = txtSubject.Text.ToString(); String body = txtBody.Text.ToString(); String mserver = "local host"; MailMessage mymsg = new MailMessage(from,to,subject,body); SmtpClient mysmtp = new SmtpClient(mserver); mysmtp.DeliveryMethod = SmtpDeliveryMethod.Network; mysmtp.Send(mymsg); Response.Write("Mail Sent"); MailMessage mailobj = new MailMessage(txtFrom.Text,txtTo.Text,txtSubject.Text,txtBody.Te xt); SmtpClient smtpserver = new SmtpClient("local host"); try {

} }

smtpserver.Send(mailobj); } catch (Exception ex) { Response.Write(ex.ToString()); }

CODE PAGE: ReportViewBranch.aspx.cs

public partial class ReportViewBranch : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { CrystalDecisions.CrystalReports.Engine.ReportDocument myrep = new CrystalDecisions.CrystalReports.Engine.ReportDocument(); CR1.ReportSource = myrep; myrep.Load(Server.MapPath("BranchDetailCrystalReport.rpt")); } }

CODE PAGE:

ReportPoliceOfficer.aspx.cs
public partial class ReportPoliceOfficer : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { CrystalDecisions.CrystalReports.Engine.ReportDocument myrep = new CrystalDecisions.CrystalReports.Engine.ReportDocument(); CR4.ReportSource = myrep; myrep.Load(Server.MapPath("PoliceOfficerCrystalReport.rpt")); } protected void CR4_Init(object sender, EventArgs e) { } }

CODE PAGE: ReportComplaintStatus.aspx.cs

public partial class ReportComplaintStatus : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { CrystalDecisions.CrystalReports.Engine.ReportDocument myrep = new CrystalDecisions.CrystalReports.Engine.ReportDocument(); CR2.ReportSource = myrep; myrep.Load(Server.MapPath("ComplaintStatus.rpt")); } }

CODE PAGE: ReportFir.aspx.cs

public partial class ReportFir : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { CrystalDecisions.CrystalReports.Engine.ReportDocument myrep = new CrystalDecisions.CrystalReports.Engine.ReportDocument(); CR3.ReportSource = myrep; myrep.Load(Server.MapPath("FIRCrystalReport.rpt")); } }

CODE PAGE:

ReportComplaintDetail.aspx.cs
public partial class ReportComplaintDetail : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { CrystalDecisions.CrystalReports.Engine.ReportDocument myrep = new CrystalDecisions.CrystalReports.Engine.ReportDocument(); CR2.ReportSource = myrep; myrep.Load(Server.MapPath("ComplaintDetailCrystalReport.rpt")) ; }

REPORT GENERATION

Branch Details Report: - is used to display the details of branch that are registered by the administrator. Police Officer Details Report: - is used to display the details of police Officer that are registered by the administrator. Complaint Details Report: - is used to display the details of complaint that are filled by the Citizens. Complaint Status Report: - is used to display the details of complaint status that are displayed by the magistrate for the citizens. FIR Details Report: - is used to display the details of FIR that are filled by the Police Officer according to complaint details filled by citizens.

COST-BENEFIT ANALYSIS
Resource Sharing:

The main goal is to make all programs, equipment and data available to anyone on the network without regard to the physical resource and the user. Users need to share resource other files, as well, a common example being printers. Printers are utilized only a small percentage of the time, therefore company doesnt want to invest in a printer for each computer. Network can be use in this situation to allow the entire user to have access any of the available printers. High-Reliability: Goal of computer network is to provide high reliability by having alternative source of supply. For example all files could be replicated on two or three machines, so if one of them is unavailable (due to H/w failure), in other copies could be used. In addition, the presence of multiple CPUs means that if one goes down, the other may be able to take over it works, although at reduced performance. For many applications the ability to continue operating in the face of H/w problems is utmost importance.

Saving-Money: Small computers have much better price/performance ratio than larger ones mainframes are roughly a factor of ten faster than personal computers but they cost a thousand times more. This imbalance Has caused many system designers to built system consisting of personal computers, one per user, with data kept on one are more shared files server machines. In this model, the users are called client and the whole arrangement is called the Clientserver model.

Scalability: The ability to increase the system performance gradually as the work load grows just by adding more processors with centralized mainframes, when a system is full a larger one, usually at great expense and even greater description to the user must replace with

client-server model, new client and new server can be added as needed. Communication-Medium: A computer network can provide a powerful communication medium among widely separated users. Using a computer network it is easy for two or more people who are working on some project and who live for apart to write a report together. When one worker makes a change to an online document, the other can see the change immediately. Instead of waiting several days for a letter. Such a speed up makes cooperation among far-flung groups of people easy where it previously had been impossible. Increase Productivity: Network increases productivity as several people can enter data at the same time, but they can also evaluate and process the shared data. So, one person can handle accounts receivables and someone else processes the profit and loss statements. Since we have seen what factors have to be kept in mind before calculating the cost estimating of the full network setup. The networks would include: Server Hardware: The HP server on windows2000 which cost around RS1.5 lakhs will be best suited for their organization purpose, as it has maximum security and easy to manage with a great looking GUI interface making more manageable.

Server Software: The client machine or the workstation needs to e powerful to lesser the load on the server like the Windows Server 2000 (in which the workstations are not more than interface to the server). A genuine Intel Pentium-3 cost around 32,000. The machine configuration

will be 512MB RAM 40 GB HD, Floppy-Drive, Multimedia-Kit and Monitor. This organization requires 12 number of client machine. Firewall: The company needs ant virus S/w for protection again viruses anti viruses S/w cost about RS10, 000. Besides these the organization needs dot-matrix printers for printing of issue details and other printing operation. There is a need of at least four printers and the 0is its cost around 4,000.

SECURITY MECHANISMS
Security prompting the user for a username and password in our application is a potential security threat. So credential information is transferred from the browser to server are encrypted. Cookies are an easy and useful way to keep user-specific information available. However, because cookies are sent to the browsers computer, they are vulnerable to spoofing or other malicious use. So we follow these guidelines: Do not store any critical information in cookies. For example, do not store a users password in cookies, even temporarily. Avoid permanent cookies if possible. Consider encrypting information in cookies. Set expiration dates on cookies to the shortest practical time we can. Security features are implemented. No unauthorized access to the package as the security is implemented through login and passwords. Only authorized person can view web pages and can access/modify the data store in database. The far most security is provided by the database itself being implemented. It installs with a much higher level of security. In this system there are four types of users Administrator, Police Officer, Magistrate, and Citizen and different types of permissions are given to them according to their rights The Backup and Restore components allow creating a copy of database for protection of data. This copy is stored protected

from the potential failures of the server, the instance of the database server. If any problem occurs the backup copy is used to recreate or restore the database.

Future Scope of the project

Since the System has been generated by using object oriented programming, there are every chances of reusability of the codes in other environment even in different platforms. Also its present features can be enhanced by some simple modification in the codes so as to reuse it in the changing scenario. Because the technology used in this project is providing high flexibility to programmer to reuse the code and enhance its features. This project should provide following facilities: Fast and efficient working. Proper maintenance of records. Provide fast and detailed reports. Facility of quick query.

BIBLIOGRAPHY
Here we would like to present the name of the books used for reference while designing, coding, and testing and implementation of the system. Database System Concept By Henry F. Korth Pankaj jalote Software Engineering Roger S.Pressman Software Engineering A practiceners approach McGraw Hill System Analysis and Design By Elias M. Ewad

WEBSITES http:// www.google.com http:// www.msdn.com http:// www.aspcode.com