ACKNOWLEDGEMENT

At the very outset, I would like to give the first honours to god who gave the wisdom and
knowledge to complete this project.
First of all I thank The Lord, Almighty for his immense grace at every stage of this
project.
I wish to extend my sincere gratitude to Prof. Raju K John, Principal and Mrs. Sheba
Eldho, Head of the Department for having given me the opportunity to complete this project successfully. I
am indeed indebted to Mr.Shaju Varghese, our course coordinator for his timely advices.
I wish to extend my sincere thanks to my guide Mrs. Dhanya Job, Lecturer,Dept of
Computer Science B P C College Piravom, for his valuable guidance and support . I think him for the
timely suggestions and constants encouragement that boosted up my morale and led to the accomplishment
of this project.
It is my privilege to submit my heartfelt thanks to management of Logic Software
Solutions for providing me an opportunity to do the project.
My deep sense of gratitude to Mr. Byju P.Y and Mr.Jijo of Logic Software Solutions for
their kind co-operation and help they extended in the completion of this project.
I finally thank my parents, my friends and all my well wishers, who had supported me
directly and indirectly, during my project.
 CRIME STOPPER CELL

ABSTRACT

Criminal histories are maintained by law enforcement agencies on all levels of

government. Local police departments and specialty police agencies may maintain their
own internal databases. On the state level, state police, troopers, highway patrol,
correctional agencies, and other law enforcement agencies also maintain separate
databases. Law enforcement agencies often share this information with other similar
enforcement agencies but this information is rarely available to the public. Getting
information regarding an issue is a tedious job in the existing system.
The “Crime Stopper Cell” is a web site which handles a centralized dynamic
database about different crimes and criminals and exposes the different ways that a
criminal adopted for different crimes. This database helps the police and other authorities
to find out and publish information for the public. Also, the public have their own way to
enter the other details about crimes. The site administrator can verify these details and if
found to be valid, can add them to the web site. The most important feature of this site is
the opportunity to give critical information about a crime to the police directly through
this web site. The information is passed as an encoded form and thus provides maximum
security.
This site contains complete information about criminal activities reported and
provides detailed reports of the status of each case. The administrator reviews all
information sent by different users from various locations and adds only the genuine ones
to the site. Administrator conducts a primary investigation about the information
received to ensure that it is a genuine case.
All genuine cases registered in the site are forwarded to the concerned authorities.

The concerned authorities are assigned unique ids and passwords through which they can

monitor various criminal cases registered under their area of control. The cases registered

are managed on a case to case basis and the status is updated online.
 This site provides information of all registered criminal cases to the public. The

users visiting this site can search for any information based on various criteria such as

location, incident, dates etc. Users have an option of adding their comments or any

additional information for any specific case. These can be useful to the investigating

officers for cracking a case.

The Public General Service module is basically a module for Public Awareness. It

is used for displaying alerts for the General Public regarding various social problems.

Users can visit this section to find information related to a particular area or occasion, and

problems that are anticipated in certain situations. This section lists areas where acts of

violence have been reported and can be used to raise alarms regarding proposed Bandhs

or Hartals. These can be very helpful to persons planning to visit different places.

Apart from this, there a separate cells for addressing Women’s Grievance and to

register complaints about Anti-Corruption activities. This site also provides information

about the authorities who handle cases in each area with telephone numbers and

designation.

Modules:
The different modules in the system are :-

1. Administration Module

2. Crime Management Module

3. Public Information Module

4. Public General Service Module

5. Women Grievance Cell

6. Anti Corruption Bureau

7. Directory Information
CONTENTS

1. INTRODUCTION
1.1ORGANIZATION PROFILE
2. SYSTEM ANALYSIS
2.1 SYSTEM STUDY
2.1.1 EXISTING SYSTEM
2.1.2 NEED FOR COMPUTERIZATION
2.1.3 PROPOSED SYSTEM
2.2 FEASIBILITY STUDY
2.2.1 ECONOMIC FEASIBILITY
2.2.2 TECHNICAL FEASIBILITY
2.2.3 OPERATIONAL FEASIBILITY
2.3 SYSTEMSPECIFICATION
2.3.1 HARDWARE CONFIGURATION
2.3.2 SOFTWARE CONFIGURATION
2.3.2.1 SOFTWARE FEATURES
3. SYSTEM DESIGN
3.1 DATABASE DESIGN
3.2 SCREEN DESIGN
3.3 PROCEDURE DESIGN
3.4 INPUT DESIGN
3.5 OUTPUT DESIGN
4. SYSTEM IMPLEMENTATION
4.1 SYSTEM TESTING
4.2 TRAINING
5. MAINTENANCE
5.1 POST IMPLEMENTATION REVIEW
6. FUTURE ENHANCEMENT
7. CONCLUSION
8. APPENDICES
SCREEN LAYPUT
REPORTS
9. BIBLIOGRAPHY
1.INTRODUCTION

1.1ORGANIZATION PROFILE

Microweb was born in Cochin, India, in 1996 with the burning desire of a simple
logic to provide Competitive and World class quality-maintained service in God’s own
Country. Microweb Solutions Pvt.Ltd. consists of four divisions such as, Software
development, Education & Training, H.R Consultancy and Authorized Testing Centre.
Over these years our committed and well focused Management has led to the blossoming
of Microweb as Pioneer in Kerala’s Information Technology Industry. Presently
Microweb operates with our four Direct Centers at Key locations in Kerala. Microweb’s
Regional Head office situated in Cochin town at Microweb Tower.

Software Development Wing:

Starts with a simple logic i.e. to be a complete solution provider for Software
Industry in the God’s own Country, and is become the basis of our official name as
‘MICROWEB SOFTWARE SOLUTION Pvt. Ltd, with five years of proven successful
track records in developing, deploying software with delightful customers. In this IT
booming stage Microweb comes in the first row among the best software developing &
training providers in Kerala, imparting advanced development and training in the
products from Microsoft, Cisco Systems, Sun Microsystems, Checkpoint, IBM, Lotus
Corporation, Oracle Corporation etc. Out service infrastructure is the best in the industry
backed up with the Engineers certified in MCP, MCAD, MCSD, MCSA, MCSE, CCNA,
CCNP, OCP,SCSA etc….Logic Software Solution’s Engineers are very keen in meeting
our customers necessities and maintaining them fully satisfied always. The entire
 development process passes through our Quality Standard which has been developed by
our ‘Quality Maintenance Wing’ to ensure systematic process from beginning till the
sharp delivery of the product.

2.REQUIREMENT ANALYSIS

2.1 Hardware Specification

CPU ~ Pentium® IV 1.6 GHz

RAM ~ 512MB RAM
Hard Disk ~ 20GB
Monitor ~ 15” Color Monitor
Input Devices ~ Mouse, Keyboard

Software Specification

Operating System ~ Windows 2003/XP/2005 series

Client Side Technologies ~ Java Script, HTML
Programming Language ~ Java
Framework ~ Struts 1.2
Web Technologies ~ JSP, Servlets, Java Beans
Application Server ~ My Eclipse Tomcat
Database ~ Microsoft SQL Server 2005
Software ~ JDK 1.6, My Eclipse 6.0, Apache Tomcat 6.0

2.2 Software Overview

2.3.1 My Eclipse 6.0

Genuitec has announced the release of the commercial

My Eclipse 6.0, offering advanced features and integration for Spring and Java Persistence
Architecture (JPA) development. This Eclipse plug-in set allows users to create entity
managers and transaction manager beans, generate entities and DOA and much more
through the cross-capabilities bridge created by My Eclipse. My Eclipse 6.0 includes the
following enhancements over previous releases:

• Platform and Installation Support

• Eclipse 3.3/Europa 1.0 compatible
• Java 5 & Java 6 support
• Windows (XP, Vista), Linux, Mac
• Java EE 5 & Spring Feature Improvements
• EJB3 improved project flexibility, bean generation from DB schema
• Project actions to generate Entities and DAOs from DB schema
• Automatically maintains entity classes in persistence.xml
• Improved JPA project capabilities configuration
• Improved documentation and examples
• Spring 2.0 upgrade with enhanced configuration and management
• Hibernate upgrade

2.3.2 Struts Frame Work 1.2

2.3.2.1 MVC Architecture

The main aim of the MVC architecture is to separate the business logic and
application data from the presentation data to the user. Here are the reasons why we should
use the MVC design pattern. They are reusable . When the problems recurs, there is no
need to invent a new solution, we just have to follow the pattern and adapt it as necessary.
They are expressive: By using the MVC design pattern our application becomes more
expressive.

1). Model: The model object knows about all the data that need to be displayed. It is
model who is aware about all the operations that can be applied to transform that object. It
only represents the data of an application. The model represents enterprise data and the
business rules that govern access to and updates of this data. Model is not aware about the
presentation data and how that data will be displayed to the browser.

2). View: The view represents the presentation of the application. The view object
refers to the model. It uses the query methods of the model to obtain the contents and
renders it. The view is not dependent on the application logic. It remains same if there is
any modification in the business logic. In other words, we can say that it is the
responsibility of the view’s to maintain the consistency in its presentation when the model
changes.

3). Controller: Whenever the user sends a request for something then it always go
through the controller. The controller is responsible for intercepting the requests from view
and passes it to the model for the appropriate action. After the action has been taken on the
data, the controller is responsible for directing the appropriate view to the user. In GUIs,
the views and the controllers often work very closely together.

Features of MVC1:

• Html or jsp files are used to code the presentation. To retrieve the data Java Bean
can be used.
• In mvc1 architecture all the view, control elements are implemented using Servlets
or Jsp.
• In MVC1 there is tight coupling between page and model as data access is usually
done using Custom tag or through java bean call.

Features of MVC2:

• The MVC2 architecture removes the page centric property of MVC1 architecture
by separating Presentation, control logic and the application state.
• In MVC2 architecture there is only one controller which receives the entire request
for the application and is responsible for taking appropriate action in response to
each request.
2.3.2.2 Struts 1.2

An MVC Framework: Struts provides a unified framework for deploying servlet

and JSP applications that use the MVC architecture.
A Collection of Utilities:– Struts provides utility classes to handle many of the most
common tasks in Web application development.

A Set of JSP Custom Tag Libraries: Struts provides custom tag libraries for
outputting bean properties, generating HTML forms, iterating over various types of data
structures, and conditionall youtputting HTML. The proper way to view Struts :depends
on what you are going to use it for,but the MVC framework is the most common way of
looking at Struts.

Advantages of Struts 1.2

• Centralized file-based configuration

Rather then hard-coding information into Java programs, many Struts values are
represented in XML or property files. This loose coupling means that many changes can
be made without modifying or recompiling Java code, and that wholesale changes can be
made by editing a single file. This approach also lets Java and Web developers focus on
their specific tasks (implementing business logic, presenting certain values to clients,
etc.) without needing to know about the overall system layout.

• Form beans

In JSP, you can use property=\'*\' with jsp:setProperty to automatically populate a

Java Bean component based on incoming request parameters. Apache Struts extends this
capability to Java code and adds in several useful utilities, all of which serve to greatly
simplify the processing of request parameters.

• Bean tags

Apache Struts provides a set of custom JSP tags (bean: write, in particular) that let
you easily output the properties of JavaBeans components. Basically, these are concise
and powerful variations of the standard jsp:useBean and jsp:getProperty tags.

2.3.2.3 JEE 5.0

 With the Java TM Platform, Enterprise Edition (Java EE), development of Java
enterprise applications has never been easier or faster. The aim of the Java EE 5 platform is
to provide developers a powerful set of APIs while reducing development time, reducing
application complexity, and improving application performance. The Java EE 5 platform
introduces a simplified programming model. With Java EE 5 technology, XML deployment
descriptors are now optional. Instead, a developer can simply enter the information as an
annotation directly into a Java source file, and the Java EE server will configure the
component at deployment and runtime. These annotations are generally used to embed in a
program data that would otherwise be furnished in a deployment descriptor. With
annotations, the specification information is put directly in your code next to the program
element that it affects.

In the Java EE platform, dependency injection can be applied to all resources

that a component needs, effectively hiding the creation and lookup of resources from
application code. Dependency injection can be used in EJB containers, web containers, and
application clients. Dependency injection allows the Java EE container to automatically
insert references to other required components or resources using annotations.

The Java Persistence API is new to the Java EE 5 platform. The Java
Persistence API provides an object/relational mapping for managing relational data in
enterprise beans, web components, and application clients. It can also be used in Java SE
applications, outside of the Java EE environment.

This tutorial uses examples to describe the features and functionalities

available in the Java EE 5 platform for developing enterprise applications. Whether you are
a new or experienced Enterprise developer, you should find the examples and
accompanying text a valuable and accessible knowledge base for creating your own
solutions.

2.3.2.4 Apache Tomcat Server

 Apache Tomcat is an implementation of the Java Servlet
and Java Server Pages technologies. The Java Servlet and Java Server Pages specifications
are developed under the Java Community Process.

Apache Tomcat is developed in an open and participatory

environment and released under the Apache Software License. Apache Tomcat is intended
to be a collaboration of the best-of-breed developers from around the world.
Apache Tomcat powers numerous large-scale, mission-critical web applications across a
diverse range of industries and organizations

2.3.2.5 Java Script

JavaScript is a simple programming language that can be written directly into

HTML documents to allow for increased interactivity with the user. JavaScript is an easy-
to-use programming language that can be embedded in the header of your web pages. It can
enhance the dynamics and interactive features of your page by allowing you to perform
calculations, check forms, write interactive games, add special effects, customize graphics
selections, create security passwords and more.

Difference between JavaScript and Java

Actually, the 2 languages have almost nothing in common except for the name.
Although Java is technically an interpreted programming language, it is coded in a similar
fashion to C++, with separate header and class files, compiled together prior to execution.
It is powerful enough to write major applications and insert them in a web page as a special
object called an "applet." Java has been generating a lot of excitement because of its unique
ability to run the same program on IBM, Mac, and UNIX computers. Java is not considered
an easy-to-use language for non-programmers. JavaScript is much simpler to use than Java.
With JavaScript, if I want check a form for errors; I just type an if-then statement at the top
of my page. No compiling, no applets, just a simple sequence.

2.3.2.6 Microsoft SQL Server 2005

 SQL Server 2005 is a set of components that work together to meet the data storage
and analysis needs of the largest Web sites and enterprise data processing systems.
Features of SQL Server 2005
Microsoft SQL Server 2005 features include:
1. Internet Integration.
The SQL Server 2005 database engine includes integrated XML support. It also has
the scalability, availability, and security features required to operate as the data storage
component of the largest Web sites

2. Scalability and Availability.

The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows 98 through large, multiprocessor servers running
Microsoft Windows 2005 Data Center Edition. SQL Server 2005 Enterprise Edition
supports features such as federated servers, indexed views, and large memory support that
allow it to scale to the performance levels required by the largest Web sites.
3.Enterprise-Level Database Features
The SQL Server 2005 relational database engine supports the features required to
support demanding data processing environments. The database engine protects data
integrity while minimizing the overhead of managing thousands of users concurrently
modifying the database.
4.Ease of installation, deployment, and use
SQL Server 2005 includes a set of administrative and development tools that
improve upon the process of installing, deploying, managing, and using SQL Server across
several sites. SQL Server 2005 also supports a standards-based programming model
integrated with the Windows DNA, making the use of SQL Server databases and data
warehouses a seamless part of building powerful and scalable systems.
5.Data warehousing
SQL Server 2005 includes tools for extracting and analyzing summary data for
online analytical processing. SQL Server also includes tools for visually designing
databases and analyzing data using English-based questions.
 6 .Database Architecture
Microsoft SQL Server 2005 data is stored in databases. The data in a database is
organized into the logical components visible to users. A database is also physically
implemented as two or more files on disk. Each instance of Sql Server has four system
databases (master, model, tempdb, and msdb) and one or more user databases. When using
a database, you work primarily with the logical components such as tables, views,
procedures, and users. The physical implementation of files is largely transparent.
Typically, only the database administrator needs to work with the physical implementation.

Some organizations have only one user database, containing all the data for their
organization. Some organizations have different databases for each group in their
organization, and sometimes a database used by a single application. For example, an
organization could have one database for sales, one for payroll, one for a document
management application, and so on. Sometimes an application uses only one database;
other applications may access several databases.
It is not necessary to run multiple copies of the SQL Server database engine to allow
multiple users to access the databases on a server. An instance of the SQL Server Standard
or Enterprise Edition is capable of handling thousands of users working in multiple
databases at the same time. Each instance of SQL Server makes all databases in the
instance available to all users that connect to the instance, subject to the defined security
permissions.
When connecting to an instance of SQL Server, your connection is associated with a
particular database on the server. This database is called the current database. You are
usually connected to a database defined as your default database by the system
administrator, although you can use connection options in the database APIs to specify
another database. You can switch from one database to another using either the Transact-
SQL USE database_name statement, or an API function that changes your current database
context.
SQL Server 2005 allows you to detach databases from an instance of SQL Server,
then reattach them to another instance, or even attach the database back to the same
instance. If you have a SQL Server database file, you can tell SQL Server when you
connect to attach that database file with a specific database name.

Parts of a Database
A database in Microsoft® SQL Server™ 2005 consists of a collection of tables that
stores a specific set of structured data. A table contains a collection of rows (referred to as
records or tuples) and columns (referred to as attributes). Each column in the table is
designed to store a certain type of information (for example, dates, names, dollar amounts,
or numbers). Tables have several types of controls (constraints, rules, triggers, defaults, and
customized user data types) that ensure the validity of the data. Tables can have indexes
similar to those in books that allow rows to be found quickly. Declarative referential
integrity (DRI) constraints can be added to the tables to ensure that interrelated data in
different tables remains consistent. A database can also store procedures that use Transact-
SQL programming code to perform operations with the data in the database, such as storing
views that provide customized access to table data.
Relational Database Components
The database component of Microsoft® SQL Server™ 2005 is a Structured Query
Language (SQL)–based, scalable, relational database with integrated Extensible Markup
Language (XML) support for Internet applications. Each of the following terms describes a
fundamental part of the architecture of the SQL Server 2005 database component:
Database
A database is similar to a data file in that it is a storage place for data. Like a data
file, a database does not present information directly to a user; the user runs an application
that accesses data from the database and presents it to the user in an understandable format.
Database systems are more powerful than data files in that data is more highly
organized. In a well-designed database, there are no duplicate pieces of data that the user or
application must update at the same time. Related pieces of data are grouped together in a
single structure or record, and relationships can be defined between these structures and
records.
When working with data files, an application must be coded to work with the
specific structure of each data file. In contrast, a database contains a catalog that
applications use to determine how data is organized. Generic database applications can use
the catalog to present users with data from different databases dynamically, without being
tied to a specific data format.
A database typically has two main parts: first, the files holding the physical
database and second, the database management system (DBMS) software that applications
use to access data. The DBMS is responsible for enforcing the database structure,
including:
• Maintaining relationships between data in the database.
• Ensuring that data is stored correctly, and that the rules defining data relationships
are not violated.

Relational Database
Although there are different ways to organize data in a database, relational
databases are one of the most effective. Relational database systems are an application of
mathematical set theory to the problem of effectively organizing data. In a relational
database, data is collected into tables (called relations in relational theory).
A table represents some class of objects that are important to an organization. For
example, a company may have a database with a table for employees, another table for
customers, and another for stores. Each table is built of columns and rows (called attributes
and tuples in relational theory). Each column represents some attribute of the object
represented by the table. For example, an Employee table would typically have columns for
attributes such as first name, last name, employee ID, department, pay grade, and job title.
When organizing data into tables, you can usually find many different ways to
define tables. Relational database theory defines a process called normalization, which
ensures that the set of tables you define will organize your data effectively.
Scalable
SQL Server 2005 supports having a wide range of users access it at the same time.
An instance of SQL Server 2005 includes the files that make up a set of databases and a
copy of the DBMS software. Applications running on separate computers use a SQL Server
2005 communications component to transmit commands over a network to the SQL Server
2005 instance. When an application connects to an instance of SQL Server 2005, it can
reference any of the databases in that instance that the user is authorized to access. The
communication component also allows communication between an instance of SQL Server
2005 and an application running on the same computer. You can run multiple instances of
SQL Server 2005 on a single computer.
SQL Server 2005 is designed to support the traffic of the largest Web sites or
enterprise data processing systems. Instances of SQL Server 2005 running on large,
multiprocessor servers are capable of supporting connections to thousands of users at the
same time. The data in SQL Server tables can be partitioned across multiple servers, so that
several multiprocessor computers can cooperate to support the database processing
requirements of extremely large systems. These groups of database servers are called
federations.
Although SQL Server 2005 is designed to work as the data storage engine for
thousands of concurrent users who connect over a network, it is also capable of working as
a stand-alone database directly on the same computer as an application. The scalability and
ease-of-use features of SQL Server 2005 allow it to work efficiently on a single computer
without consuming too many resources or requiring administrative work by the stand-alone
user. The same features allow SQL Server 2005 to dynamically acquire the resources
required to support thousands of users, while minimizing database administration and
tuning. The SQL Server 2005 relational database engine dynamically tunes itself to acquire
or free the appropriate computer resources required to support a varying load of users
accessing an instance of SQL Server 2005 at any specific time. The SQL Server 2005
relational database engine has features to prevent the logical problems that occur if a user
tries to read or modify data currently used by others.
Structured Query Language

To work with data in a database, you have to use a set of commands and statements
(language) defined by the DBMS software. Several different languages can be used with
relational databases; the most common is SQL. The American National Standards Institute
(ANSI) and the International Standards Organization (ISO) define software standards,
including standards for the SQL language. SQL Server 2005 supports the Entry Level of
SQL-92, the SQL standard published by ANSI and ISO in 1992. The dialect of SQL
supported by Microsoft SQL Server is called Transact-SQL (T-SQL).

3. EXISTING SYSTEM

Existing system is purely manual one. The projects are handled by number of files. The
main drawback of existing system is that it takes lot of time for Project Manager. Each user has to
go through a number of files, which is tedious and time consuming. Apart from that there are
chances of inaccurate data entry and that would lead to chains of problems. Also there are
security problems like authorized data view and access. Files consume lot of space and it is a time
consuming process to locate the corresponding files.
Limitations

• Lack of accuracy of data: As the existing system is done manually, it lacks accuracy of
data.
• Lack of security of data: Existing system lack security of data. Since all the information
is kept in files, unauthorized persons may get access to them.
• More time consumption: Maintaining information in files and handling files is time
consuming.
• More storage area due to redundancy of data.
• Consumes more volume of paperwork
• Access of information is difficult.
• Lack of validation

4. PROPOSED SYSTEM

The proposed application is mainly classified in to two levels User Level and
Administrator Level. User level contains the information about Agent’s and consignees. Also
Manifestation details, customs checking, storage details, warehouse rent collection and landing
charge collection. Handle the collection details of rent for air landing charge and storage rent
separately.
Advantages of Proposed System
 1. Set securities base User level.
2. Intelligent Package Handling.
3. Optimal Resource Usage.
4. To centralize the firm.
5. Produce relevant Reports.
6. Import and Export details.

5.MODULE DESCRIPTION

1. Administration Module

Administrator has the overall control of the site. The following are his duties :-

 View all cases registered in the site.

 Approve new cases added by users.

 Investigate and Validate each case.

 Forward the case to the authorized person.

2. Crime Management Module

 Registration for specific posts.

 View specific cases on the basis of area of operation

 Update Action taken for each case.

3. Public Information Module

 View new registered criminal cases.

 Lookup a case based on criteria.

 Feedback Entry

4. Public General Service Module

 View information

 Upload information

 Feedback Entry
 5. Women Grievance Cell

 Register Complaints

 View Pending Complaints

 Update Complaint Status

6. Anti Corruption Bureau

 Report Anti Corruption Activities

 Update Status of Complaint

 View All Registered Cases.

7. Directory Information

 Enter List of Authorities area-wise

 View Directory of Police Authorities

 Update/Delete Directory Entries

SYSTEM TESTING
6.1 Introduction
System testing is an expensive, but critical process that may take as much
as 50 percent of the budget for program development. Testing performs a very critical
role for quality assurance and for ensuring the reliability of software. In a software
development project, errors can be injected at any stage during development. Testing is
the phase where the errors remaining from the earlier phases also must be detected. The
common view of testing is that it is performed to prove that there are no errors in the
program. But this is quite difficult since the analyst cannot prove that software is free
from all sorts of errors. Therefore, the most useful and practical approach is with the
understanding that testing is the process of executing program with the explicit intention
of finding errors that is to make the program fail. A successful test can be therefore, one
that finds an error.
6.2 Testing Strategies
The philosophy behind testing is find errors. Test cases are devised with this
purpose in mind. A test case is a set of data that the system will process as normal input.
However, the data is created with the express intent of determining whether the system will
process it correctly. Each test case is designed with the intent of finding errors in the way the
system will process it. There are two general strategies for testing software, code testing and
specification testing.

6.3 CODE TESTING

The code testing strategy examines the logic of the program. To follow
this testing method, the analyst develops test cases that result in executing every
instruction in the program or module; that is, path through the program is tested. A path is
a specific combination of conditions that is handled by the program. On the surface, code
testing seems to be an ideal method for testing software. However, even if code testing
can be performed in its entirety, it does not guarantee against software failures. This
testing strategy does not indicate whether the code meets its specifications nor does it
determine whether all aspects are even implemented. Code testing also does not check the
range of data that the program will accept, even though, when software failures occur in
actual case, it is frequently because users submitted data outside of expected ranges.

6.3 Specification Testing

To perform specification testing, the analyst examines the specifications
stating what the program should do, and how it should perform under various conditions.
Then test cases are developed for each condition or combination of conditions and
submitted for processing. By examining the results, the analyst can determine whether the
program performs according to its specified requirements.

6.4 LEVELS OF TESTING

Systems are not designed as entire systems nor are they tested as single
systems. The analyst must perform both unit and system testing.
6.4.1 UNIT TESTING
Unit testing comprises a set of tasks performed by an individual prior to
integration of the unit into a larger system. A program unit is usually small enough that
programmers who developed it can test it in great details and certainly in greater details
then will be possible when the unit is integrated into an evolving software product.
Modules are tested in isolation from one another in an artificial environment, which
consists of driver programs and data necessary to exercise the modules.
All the units that make up the system were tested independently to ensure
that they were required

6.4.2 SYSTEM TESTING

System Testing involves two kinds of activities:-
 Integration Testing
 Acceptance Testing

6.4.2.1. Integration Testing

Bottom up integration is the traditional strategy used to integrate the
component of a software system into a functioning whole. This integration consists of
unit testing, followed by sub system testing, followed by testing the entire system. A
subsystem consists of several modules that can communicate with each other through
well defined interfaces. The primary concern here is the compatibility of individual
modules. Though each module works independently they should work after linking them
together.

6.4.2.2. Acceptance Testing

Acceptance Tests involve planning and execution of functional tests and in
order to demonstrate that the implemented software satisfies its requirements. This
software is feasible enough that it can accommodate the future needs existing in the
system. So maintenance becomes easy using software.
 SYSTEM IMPLEMENTATION

7.1 Implementation Phase

It involves careful planning, investigation of the current system and its constraints
on implementation, design of methods to achieve the change over, an evaluation, of change
over methods. Apart from planning major task of preparing the implementation are
education and training of users. The more complex system being implemented, the more
involved will be the system analysis and the design effort required just for implementation.
An implementation coordinating committed based on policies of individual organization
has been appointed. The implementation process begins with preparing a plan for
implementation of system. According to this plan, activities are to be carried out,
discussions made regarding the equipment and resources and additional equipment has to
be acquired to implement the new system.
Implementation is final and important phase. The most critical stage in achieving
a successful new system and in giving the users confidence that the system will work and
be effective. The system can be implemented only after thorough testing is done and if it
found to working according to the specification. This method also offers the greatest
security since the old system can take over if the errors are found or inability to handle
certain type of transactions while using the new system.
At the beginning of the development phase a preliminary plan is created to
schedule and manage the many different activities that must be integrated into plan. The
implementation plan is updated throughout the development phase, culminating in
changeover for the operation phase. The major elements of implementation plan are test
plan, equipment installation plan and a conversion plan.
7.2 SYSTEM SECURITY
The security features are considered while developing the system, so as to avoid
he errors and omissions that may lead to serious problems. The system may have to face
the unwanted events called threats. Computer system is secure against a particular threat if
counter measures have been taken to reduce an acceptability low level amount of loss that
threat may be expected to cause over a given period of time.
 7.3 EDUCATION AND TRAINING
For the successful implementation and cooperation of new systems the users must
be selected, educated and trained. Unless the users are not trained, the system will become
complex and it will feel as a burden for them. The selection of staff must take place at an
early stage. The estimate of the numbers and the types of the people required has been
submitted to the management for approval. The people who will be affected are given a
high priority in training and they are told at the earliest stage why the changes are
necessary and how they will be affected. This communication was taken place through
their respective managers.
For running the project, trained users are needed when the implementation starts.
For the client section there is no need to give training for the users. Because most of the
users are familiar with browsing. In the administrator section trained persons are needed.
Since data validation methods are applied they can easily learn the data entry operation.
After the system is implemented successfully, training of the user is one of the
most important subtasks of the developer. For this purpose user manuals are prepared and
handled over to the user to operate the developed system. Thus the users are trained to
operate the developed system. Both the hardware and software securities are made to run
the developed systems successfully in future. In order to put new application system into
use, the following activities were taken care of:
 Preparation of user and system documentation.
 Conducting user training with demo and hands on.
 Test run for some period to ensure smooth switching over the system
The users are trained to use the newly developed functions. User manuals
describing the procedures for using the functions listed on menu and circulated to all the
users. It is confirmed that the system is implemented up to users need and expectations.

6. FUTURE ENHANCEMENT

The software is developed in JAVA which make the system more reliable
and compatible with the other environments. The application proves better extensibility
and flexibility for future enhancements. Any further requirement application is possible
with the same features guaranteed. The design of this software is in such a way that the
addition of any new module if necessary is possible without affecting the integrity of the
present system.

Some suggestions to improve the functioning of the system

1. The provision to remember the username and password for the user incase confusion
arises.
2. Online help (FAQ) can be attached to the system to make the system more user-
friendly.

7. CONCLUSION

Anything can not be ended in a single step. It is the fact that nothing is
permanent in this world. So this utility also has some future enhancements in the
evergreen and booming IT industry. Change is inevitable. Almost every project is
subjected to change depending on the client’s requirements. The system and the
architecture of the proposed system is a compatible one, so addition of new modules can
be done without much difficulty. Since this module has its unique properties it can extend
further to make this system a complete one.
The software was implemented and tested with real data and were found to be
error free.Also,the system is protected from any unauthorized access .All the necessary
validations are carried out on this project, so that any kind of users can make use of this
software and necessary messages makes them conscious of the error they have made.
1. Table :USERREGISTRATION
Purpose: To store new user details

2. Table : COMPLAINTS
Purpose : To store the general complaints by the user.
3. Table: WOMENCOMPLAINTS
Purpose : To store the complaints by the women.

4. Table : CORRUPTIONDETAILS
Purpose : To store the corruption complaints.

5. Table : INFORMATIONMASTER
Purpose : To store the information about the different crimes.

6. Table : CRIMINALMASTER
Purpose : To store the details of the criminals.
7. Table : UPDATEDETAILS
Purpose : To store the status of the general complaints.

8. Table : WOMENUPDATEDETAILS
Purpose : To store the status of women’s complaints.

9. Table : CORRUPTIONUPDATEDETAILS
Purpose : To store the status of corruption complaints.
10. Table : AUTHORITYDETAILS
Purpose : To store the authority details.

11. Table : FEEDBACK

Purpose : To store the feedbacks by the users.