Ecops report1.doc
-
Upload
taran-jeet -
Category
Documents
-
view
111 -
download
1
description
Transcript of Ecops report1.doc
1.1 OBJECTIVE
As we step into the 21st century, it is imperative to keep in mind a Vision. The impact of
IT and Communications in every aspect of our lives is phenomenal. Information is the
life of any police organization. Quick access to data is essential for effective prevention,
control and detection of crime and many other decision making and decision support
processes involved in police work.
The concept of e-governance has made its way into the state with Andhra Pradesh leading
the country in the field of technological advances. As part of the VISION 2020, the
state’s focus on modernization of law & order and crime takes the shape of eCOPS (e-
Computerized Operations for Police Services).
1.2 PROBLEM DESCRIPTION
1.2.1 What is the Problem?
The police act as agents attempting to stabilize a society affected by disorder and
lawlessness. The internal security represents the strength and health potential of the state
which needs to be protected against violent onslaughts so that the psychological
immunities get nurtured by natural healing.
India today faces a series of problems related to crime control and order maintenance.
The Indian police play a crucial role in confronting problems affecting the social and
internal security of the nation. Curtailing the attempts of hostile forces whose main aim is
to disrupt and destabilize the nation’speace, unity and integrity.
However, the police constantly face denunciation from various strata of society who are
not entirely aware of the professional, structural and moral dilemma of the police.
Unfortunately even the educated sections of society have an unclear, imprecise and hazy
1
knowledge of both the police and the criminal justice system.
Regretfully, even after so many years there remains a big wall of misunderstanding and
miscommunication between the police and the public which is a direct outcome of
various factors over which the police has no control. Development has been
conceptualized as a phenomenon characterizing change and growth but this change has to
be meaningful and the growthneeds to be purposive.
The ECOPS site is an attempt to build a working partnership between the police and the
community thus promoting harmony and the spirit of oneness amongst various segments
of society transcending through religious, social and linguistic diversities. Let us together
work in unison and provide a safer environment for qualitative living.
1.3 EXISTING SYSTEM
In the Police stations lot of things were done manually. In the stations for the ECOPS, the
records for the accidents Detail, arrests Detail and other records regarding any tragedy
any important information regarding normal public were kept in cabinet files and
organized manually. In the manual system there is problem, a problem of data
inconsistency serious flaws have been detected. The existing system work manually. The
existing system has got lot of intricacies within itself and need lot of human effort and
paper works. All above the data need to be maintained on ledgers and maintaining this is
a tedious and risky process. As the transactions increases, so the data too. So the task of
maintaining them increases exponentially. To view a data may need lot of paper to be
searched. Other limitations are inaccuracy, inefficiency, delays, and improper record
maintenance and also some basic technical problems faced by manual system for the
ECOPS system Some of them are described below:
1. Not GUI based: - The existing system is not GUI based. It is handled manually.
Because of this reasons it is non-interactive and time consuming and also non-user
friendly.
2
2. Inconsistency: - Presently system is not aware of duplication and replication of data.
They are maintaining the records manually which results in the total being in excess of
what it should be.
In such a situation, the data is said to be inconsistence, which supply incorrectly
information.
3. Improper Record Maintenance: - In the existing system, since every thing is
maintain on paper, so it is very inconvenient to modify data, in case of manual error, if
the number of mistake is abnormally high, then the whole set of records may have to be
written again, to avoid any possible errors occurring thereof.
5. Data Redundancy: - In the existing system all the data is maintainable in different
files and registers. This often leads to considerable data duplication and redundancy in
the stored thus leading to wastage of storage of storage space.
6. Problem of updating: - In the existing system since every thing is stored in the
number of files. It is quite difficult and time consuming to update all of them. The major
problems encountered is modification, which must be reflected in all the entries, and
summaries also need to be updated.
7. Time and Receiving Problems: - Retrieval of information is the quite time
consuming process because of large volume of data. Thus if it required to trace a
particular account or record a large number of registers need to be scanned
8. Expenditure:-It is high. Manual system needs added manpower
3
2.1 ABOUT SOFTWARE TECHNOLOGIES
This section introduces the selection and related motivation of technologies and tools
used in this project .it also introduces certain aspects of development methodology.
Technology and tools are strongly related to the approach of software development.
While selection of a particular methodology may imply use of certain tools, the tools
themselves often leave significant room for developers to choose how to use them.
The selection has therefore been based mainly on the objective of the project, while
the methodologies were selected after the tools were selected, due to the fact that
technologies and tools poses certain restrictions of how development can be done.
Creating a system to fulfil the basic business requirements of the objective would
allow large freedom in selecting technologies, since almost any language or paradigm
could be used for supporting these simple tasks on a local machine.
Given the challenges a developer faces, he also has to decide which key technologies
and products and architectural platform to use in order to meet these challenges. The
problem is there are simply too many of them and it is hard to come up with your own
architecture or framework where everything is in a well integrated and cohesive form.
At present we have many technology options and have various frameworks 7 patterns
for design, implementation and maintenance.
The java server pages as one of the part of java tm 2 platforms, enterprise edition
immediately came to mind as the best solution for this project, due to the extensive
support from the java camp e.g. Sun, IBM and others. Based on the above
considerations the following technologies and tools were used in the implementation
of this project.
4
TECHNOLOGIES USED
1) JAVA TM 2 Platform(as front end)
Java server pages technology (JSP)
Java database connectivity (JDBC)
2) M-Access (as back end)
3) Microsoft windows(as operating system)
2.1.1JAVA TM2 Platform (as front end)
The java TM2 Platform is a set of coordinated specification and practices that
together enable solutions for developing, deploying, and managing multi-tier server
centric applications. Building on the JAVA 2 platforms, standard edition (J2SE)
provides the necessities to provide a complete, stable, secure and fast platform.
OVERVIEW
There are three flavours of JAVA –Mobile Edition (J2ME), Standard edition (J2SE),
and Enterprise Edition (J2EE). These three flavours of JAVA represent three distinct
target market segments each of which has unique issues and requirements that need to
be addressed somewhat differently.
Mobile Edition addresses of market segment of small devices such as cell phones
and set top boxes, which are typically constrained in terms of memory space and
processing power.
Standard Edition represents the JAVA that we all know, a JAVA for desktop and
workgroup server environments that require a full feature functionalities including
rich graphical user interface.
5
Enterprise Edition covers the java platform for developing and deploying enterprise
quality applications, which are typically transactional, reliable and secure.
J2EE describes the runtime environment for a j2EE application. This environment
includes application components, containers, and resource manager drivers. The
elements of this environment communicate with a specified set of standard services.
The J2EE API’s/Technology that are used in this project are
JAVA Servlet Technology
JAVA Server pages technology
Java Database Connectivity(JDBC) API
2.1.2 JAVA SERVER PAGES (JSP) TECHNOLOGY
The Sun Microsystems Java Server Pages technology allows you to rapidly develop
and easily maintain information rich, dynamic web pages. As part of java family, JSP
enables development of web base application that are platform independent.. The web
applications build using the JSP technology works with a wide variety of web servers,
application servers, browsers and development tools.. The logic that generates the
content is encapsulated in tags and JavaBeans components and tied together in
scripts, all of which are executed on the server side. If the core logic is encapsulated
in tags and Beans, then other individuals, such as web masters and page designers can
edit and work with the JSP page without affecting the generation of the content. Thus
the JSP technology separates the user interface from the content generation.
Most web applications produce primarily dynamic html pages that, when served,
change only in data values and not in basic structure. For example, web pages in a
typical web application may have identical structure and differ only in technology
exists for producing such content.
6
FEATURES OF JSP:
JSP gives an ideal platform for creating web application easily and quickly. There are
various features supported by JSP which makes this possible. JSP provides an
attractive alternative to other dynamic scripting languages. These features are
described below.
1. Platform and server Independence:
The JSP technology follows the ‘Write Once, Run Anywhere’. Rule which is the basis
of the Java language. JSP technology can run on various web servers including
Apache, J2EE, Web logic etc.
2. Enhanced performance:
The compilation process in JSP is automatically thus produce faster results and
outputs.
3. Environment:
JSP uses pure Java and takes full advantages of its objects-oriented nature. JSP
technology lets you separates contents generation from layout by accessing
components from the page. JSP provides components based on JavaBeans technology
or JSP tags.
4. Separation of logic from display:
The use of JSP permits the HTML-specific dynamic content to be placed in separate
files.
5. Extensible JSP tags:
JSP uses a combination of tags and scripting to create dynamic web pages. It allows
you to extend the JSP tags available. JSP developers can create custom tag libraries,
so that more functionally can be extracted using XML-like tags and this leads to less
use of scripting in JSP pages.
7
6. Reusability across platforms:
The JSP pages components like Enterprise JavaBeans, JavaBeans or custom JSP tags
which are usable. This gives the JSP reusability capabilities. These reusable
components help the pages to keep simple and run faster.
7. Ease of Administration:
The use of JSP eliminates the need for high-level technical expertise, thereby helping
web developers, designers, content creators, and content managers to work together
and develop java applications in less time and with less effort.
8. Ease of Use:
All JSP applications run on major web servers and operating systems, including
Microsoft IIS, Netscape Enterprise Server, and Apache Web Servers.
9. Easier Maintenance:
Applications made using JSP technology are easier to maintain. This is explained
using the following points.
1. Scripting language work well with small applications but can not manage
large and complex applications. The JSP being based on structured Java
language is easier to build and maintain. Moreover, since JSP pages are
compiled to servlets, JSP pages have all the benefits of java technology,
including robust memory management and security.
2. Because JSP technology emphasize on component over scripting, it is easier to
revise contents without affecting logic, or revise logic without changing
content.
3. Because JSP is platform independent,. Web servers, platforms, and other
components can be easily upgraded or switched without affecting JSP-based
applications.
8
JSP ARCHTECTURE
JSPs are built on top of Sun’s servlet technology. JSPs are essential an HTML page
with special JSP tags embedded. These JSP tags can contain Java code. The JSP file
extension is .jsp rather than .htm or .html. The JSP engine parses the .jsp and creates
a Java servlet source file. It then compiles the source file into a class file; this is
done for the first time and this why the JSP is probably slower the first time it is
accessed. Any time after this the special compiled servlet is executed and is
therefore returns faster.
JSP Architecture
Steps required for a JSP request:
1. The user visits a web site made using JSP. He goes to a JSP page (ending
with .jsp). The web browser makes the request via the Internet.
2. The JSP request gets sent to the Web server.
9
3. The Web server recognizes that the file required is special (.jsp), therefore passes
the JSP file to the JSP Servlet Engine.
4. If the JSP file has been called for the first time, the JSP file is parsed, otherwise
go to step 7.
5. The next step is to generate a special Servlet from the JSP file. The entire HTML
required is converted to println statements.
6. The Servlet source code is compiled into a class.
7. The Servlet is instantiated, calling the init and service methods.
8. HTML from the Servlet output is sent via the Internet.
9. HTML results are displayed on the user’s web browser.
Java Server Page Request Model in Intranet
Web Server with JSP engine
Introduction to JSP Tags
In JSP tags can be divided into 4 different types. These are:
Directives
In the directives we can import packages, define error handling pages or the session
information of the JSP page.
JSP directives are always enclosed within
<%@……… %>
10
The two primary directives are
Page
Include.
Page Directive
It is found at top of almost all of the JSP pages.
Include Directive
This directive can be used to include the contents of the indicated file at any
location within the JSP page
Declarations
This tag is used for defining the functions and variables to be used in the JSP.
Scriplets
In this tag we can insert any amount of valid java code and these codes are placed in
jspService() method by the JSP engine.
<% @ page attributes %>attributes language, import
<%@ include file =”filename.html” %>
<%!……….%>
11
Expressions
We can use this tag to output any data on the generated page. These data are
automatically converted to string and printed on the output stream.
2.1.3 The Apache Tomcat 3.2.1 Web Server
Apache Tomcat is an open source, Java-based Web application that runs servlet and
JSP web applications. Tomcat is supported and maintained under the Apache-
Jakarta subproject by volunteers from the open source java community. Tomcat
server is the reference implementation for the servlet and JSP specifications, so it’s
probably safe to say that Tomcat Server implements the Apache-Jakarta
specifications as well or better than most commercial application server.
Tomcat is a servlet container and Java Server Pages (TM) implementation. It may
be used stand alone or in conjunction with several popular Web Servers.
2.1.4 Hyper Text Mark-Up Language (HTML)
HTML = HyperText Mark-up Language.
Universal, non-proprietary, structured, text mark-up language.
Used to publish documents on the World Wide Web.
Used to define the structure of documents and links between documents.
An application of Standard Generalized Mark-up Language.
SGML is a meta-language, used to describe a mark-up language.
Latest SGML-based version of HTML is 4.01 that supports
<%
//java codes
%>
<%="Any thing" %>
12
Scripting.
Accessibility.
HTML Basics
Strictly speaking, HTML documents have a well defined structure.
Legal structure, elements, and attributes are defined in an SGML Document
Type Definition (DTD).
Documents are structured using units called elements. Most elements are tag
pairs, a start tag and an end tag.
A few elements have single tags and some have optional end tags.
Tags look like this: <ELEMENT> or <ELEMENT> ... </ELEMENT>
Element names in HTML are not case-sensitive, but should be used consistently.
Elements can have attributes: <ELEMENT attribute_name="value">
Attributes are parameters to elements and Attribute values should be quoted.
Nearly all elements have the attributes id, class, style, and title.
The text data between start and end tags is the marked-up content. User should
User be consistent with formatting style.
XML and XHTML are case-sensitive and use lower-case lettering for element
names.
Unrecognized elements and attributes are simply ignored by HTML browsers.
HTML TAGS:
o <HTML>
Must have a <HTML> start tag at the beginning and a </HTML> end tag at the end
of the document.
<HTML>Document</HTML>
13
o <HEAD>
Is actually optional but should be used to at least define the document title
using the <TITLE> element
o <BODY>
The contents of the document go between <BODY> and </BODY>
In HTML 4.01 Transitional, the <BODY> element has a number of optional
attributes that can be used to modify the color of the document's background, links
and text (bgcolor, text, alink, vlink)
These attributes should be used carefully (if at all) and can be used to ensure
that the page renders nicely in older HTML browsers
o Headings
Six header levels available <H1>, <H2>, <H3>, <H4>, <H5>, <H6>
Graphical browsers display headings in decreasing size
o Divisions
The <DIV> tag can be used to define divisions.
Used to structure a HTML document into logical sections.
<HEAD>Document</HEAD>
<BODY>Document</BODY>
14
In HTML 4.01 Transitional, the contents of the division can be aligned left, right
or center using the align attribute, <CENTER> was supported in older versions of
HTML, but the preferred method is to use the align attribute of a <DIV> or <P>
instead.
o Images
Use the <IMG> element to include an image in a document.
Attributes of <IMG> include src and alt. src is the URL of the image and alt
should be used to provide text that describes the image.
Height and width specify the dimensions of the image.
border specifies a border around an image
align sets horizontal alignment and valign sets vertical alignment
2.1.5 BASIC DATABASE CONCEPTS
What is a database?
It is a coherent collection of data with some inherent meaning, designed, built and
populated with data for a specific purpose. A database stores data that is useful to us.
To be able to successfully design and maintain database we have to do the following:
1) Identify which part of the world’s data is of interest to us.
2) Identify what specific objects in that part of the world’s data of interest to us.
3) Identify a relationship between the objects.
<DIV align="center"> Centers all text within the division
<IMG src="picture.jpg" alt="My picture" width="200" height="150">
15
Hence, the objects, their attributes and the relationship between them that are of
interest to us are stored in the database that is designed, build and populated with data
for a specific purpose. Software houses took up the challenge of designing a system
that would help users in managing data in a database. The systems were called
Database Management Systems (DBMS).
2.1.6 JDBC-ODBC Connectivity
The JDBC-ODBC Connectivity is a JDBC driver that implements JDBC
operations by translating them into ODBC operations.
To ODBC it appears as a normal application program.
The Connectivity implements JDBC for any database for which an ODBC driver
is available.
The Connectivity is implemented as the sun.jdbc.odbc Java package and
contains a native library used to access ODBC.
JDBC Components
Driver Manager: Loads database drivers, and manages the connection between
application & driver
.
Connection: A session between an application and a driver.
Try { Class.forName (“odbc: jdbc: JdbcOdbcDriver”): } Catch (Exception e) { out.println (“Error in Loading”): }
Connection conn=driverManager.getConnection (Oracle9iUrl, userName, Password);
16
Statement: A SQL statement to perform a query or an update operation.
Execute Query: Executes a Query and returns the result the data in the table.
Process the Result:
Close the Connection
Statement st = conn.createStatement();
String query = “select * from Tablename”;
ResultSet rs = st.executeQuery(query):
While (rs.next()){ Retrieve the Value from the Table
}
Conn.Close();
17
3.1 Software Analysis And Specification
The requirement Analysis and Specification phase is undertaken once the feasibility
study phase is complete and the project is technically and financially feasible.
Analysis is a detailed study of the various operations performed by system and their
relationships within and outside of the System. Key question is “What must be done
to solve the problem?” It defines the boundaries of the system and determining
whether or not a candidate system should consider other related systems. During
analysis, data are collected on the available files, decision points and transactions
handled by present system. Data Flow Diagrams, interviews and questionnaires are
tools used for analysis. Once analysis is completed, the analyst has a firm
understanding of what is to be done.
This phase consists of two things i.e.
Requirement Analysis
Requirement Specification
3.1.1 Requirement Analysis:
It involves obtaining a clear and thorough understanding of the product to be
developed i.e. what is the problem? Why is it important to solve the problem? What
are the solutions? Etc.
It includes two things.
1. Requirement Gathering:
This involves interviewing the end-users and customers to collect all possible
information regarding the system. We followed the method of Questionnaire to
get the requirements of the Fashion online System. The Requirements that we got
from them are following.
18
The new system should require minimum amount of data entry.
The new system should be user friendly.
The System should be efficient and fast.
Only authorized user may access the system and make transactions.
The system should have current information related to fashion agency and
modelling as carrier & information should be updated easily.
2. Analysis of Gathered Requirements:
The main purpose of analysis of the collected information is to clearly understand the
exact requirements of the models as well as clients and resolve anomalies, conflicts,
and inconsistencies in the gathered requirements.
The system should give the appropriate error message if there is some wrong
thing done by user.
The unique user_id should be assigned to each user.
3.1.2 REQUIREMENT SPECIFICATION:
It includes SRS document i.e. Software Requirement Specification.
An SRS document should clearly include the following:
Functional requirements of the system
Non functional requirements of the system
Constraints on the system.
19
3.2 Proposed System
The proposed system is a computerized one. This has greater accuracy and
efficiency. This takes only limited time for calculation.
The proposed system can be used to maintain efficiently the large data of any police
station of any country. At that time also the proposed system is useful and helpful.
ECOPS is very useful site for all country to easily record all the data regarding the
criminals or any tragedy. with this site, it will easy to record all the information
regarding any tragedy..
The system includes two users.
1) Database Administrator
2) General User
Database administrator has all the SYSDBA privileges. The user gets into the system
using user name and a unique password. Each user has his own accessibility
permission to accomplish his task flawlessly.
Advantages of the proposed system are
1) ECOPS provides the facility for easy access to the data
2) The new system is more users friendly, reliable and flexible.
3) Pop-up menus to carry out transactions for a new user, and for
other alert messages.
4) ECOPS helpful in timely Report generation
.
20
3.3 SYSTEM REQUIREMENTS
Minimum hardware requirements:
128 MB RAM
A PC with any processor III/IV
Mouse
101/102 keys Keyboard
Hard Disk 40GB
Internet Connection
Mouse
Minimum software requirements:
OS : Windows XP
Languages used : JSP (JAVA SERVER PAGES)
Database : ORACLE 9i/MS-ACCESS
Mark-up language : HTML
Server : Apache Tomcat 4.0
Browser : Internet Explorer
21
3.4 THE PROJECT LIFE CYCLE
The development life cycle of a project usually involves three phases:
Project Initiation
Project Execution
Project Completion
In the project initiation phase, the development team prepares the project plan and
finalizes the outcome of each phase. In this phase, the team also prepares a
comprehensive list of tasks involved in this phase, and the project manager assigns
responsibilities to the team members, depending on their skills.
In the project execution phase, the team develops the product. In the case of this
application development team, they will develop the file transfer and chat application.
This phase consists of the following stages:
Requirements analysis
High-level design
Low-level design
Construction
Testing
Acceptance
All of these stages are discussed in detail, later on.
The Requirement Analysis phase
During the requirements analysis phase, the development team analyzes the
requirements to be fulfilled by the file transfer and chat application and identifies the
probable approach for meeting these requirements. To identify the requirements of the
application, the team decides to study the existing applications at various sites and
conduct extensive interviews among the customers.
22
In this phase we gathered all the requirements about the project .For this phase to be
undertaken we analyze “Modelguru.com” a popular modelling agency site on the
internet to have full knowledge of desired input and output requirements of the
project.
The High-Level Design Phase
In this phase, the team decides how the application will function. The formats of data
input and output are finalized in this stage. The functional specifications
documentation of their application is presented in a language that can be understood
by all. The finalized project design is executed only on the project manager’s
approval. The development team designs all the interfaces and screens for the
application. During this phase the design of the database is also finalized.
In this phase the input requirements collected from the above phase is refined. We
decided to use Front Page as our HTML editor.
The Low-Level Design Phase
In this phase, a detailed design of software modules, based on the high-level design is
created. In addition the team creates specifications for the various software modules
of an application. The functionality of the file transfer and chat application and the
interaction between the various interfaces in the application is shown in the
flowchart / data flow diagrams.
In this phase modules were decided on as well as work has been divided
among the team members involved in the project.
The Construction Phase
In the construction phase, the software components are built. This phase uses the
output of the low-level design to produce software items. During the construction
23
phase, the development team divides the responsibilities among its team members.
Some team members are assigned the task of designing the interface, whereas others
take the job of writing the code to develop the application.
In this phase designing of web pages as well as incorporation of jsp tags takes place.
Firstly the web pages that are static content were developed and then jsp code that
makes application dynamic is added.
The Testing Phase
Software modules are tested for their functionality as per the requirements identified
during the requirements analysis phase. To test the functionality of the file transfer
and chat application, a Quality Assurance (QA) team is formed. The requirements
identified during the requirements analysis phase are submitted to the QA team. In
this phase the QA team tests the application for these requirements. The development
team submits a test case report to the QA team so that the application can be tested in
the various possible scenarios.
In this phase the addition of flash objects to provide a great graphical user interface to
the clients. The testing involve is unit testing and integration testing. Each and every
web page is tested against the unusual values.
The Acceptance Phase
In this phase, based on the predefined acceptance criteria, the marketing team
conducts testing for client projects. In the case of the file transfer and chat application,
the acceptance criteria are the fulfilment of all the requirements identified during the
requirements analysis phase.Finally in this phase the project is fully tested and is
presented before the project guide for acceptance.The Software development model
used in this project is iterative waterfall model.
24
SYSTEM DEVELOPMENT LIFE CYCLE OF ECOPS.COM
25
3.5 SYSTEM DESIGN
System Design aims to identify the modules that should be in the system, the
specification of these modules and how they interact with each other to produce the
desired result.
System design provides the understandings and procedural details necessary for
implementing the system recommended in the system study. Emphasis is on the
translating the performance requirements into design specifications. The design phase
is a transition from a user-oriented document (System proposal) to a document
oriented to the programmers or database personnel
System design goes through two phases of development:
1) Logical Design
2) Physical Design
A data flow diagram shows the logical flow of the system. For a system it describes
the input (source), output (destination), database (data stores) and procedures (data
flows) all in a format that meets the user’s requirement. When analysis prepare the
logical system design, they specify the user needs at a level of detail that virtually
determines the information flow into an out of the system and the required data
resources. The logical design also specifies input forms and screen layouts.
The activities following logical design are the procedure followed in the physical
design e.g., producing programs, software, file and a working system. Design
specifications instruct the user about what the system should do.
26
Logical and Output Design:
The logical design of an information system is analogous to an engineering blue print
of an automobile. It shows the major features and how they are related to one another.
The detailed specification for the new system was drawn on the bases of user’s
requirement data. The outputs inputs and databases are designed in this phase.
Output design is one of the most important features of the information system. When
the outputs is not of good quality the users will be averse to use the newly designed
system and may not use the system. There are many types of output, all of which can
be either highly useful or can be critical to the users, depending on the manner and
degree to which they are used.
Outputs from computer system are required primarily to communicate the results of
processing to users, They are also used to provide a permanent hard copy of these
results for later consultation. Various types of outputs required can be listed as
below:
External Outputs, whose destination is outside the organization.
Internal outputs, whose destination is with the organization.
Operational outputs, whose use is purely with in the computer
department e.g., program-listing etc.
Interactive outputs, which involve the user is communicating directly
with the computer, It is particularly important to consider human factor
when designing computer outputs. End user must find outputs easy to use
and useful to their jobs, without quality output, user may find the entire
system unnecessary and avoid using it. The term “Output” in any
information system may apply to either printer or displayed information.
During the designing the output for this system, it was taken into
consideration, whether the information to be presented in the form of
query of report or to create documents etc.
27
Other important factors that were taken into consideration
are:
The end user who will use the output.
The actual usage of the planned information.
The information that is necessary for presentation
When and how often output and their format is needed. While designing
output for project based Attendance Compilation System, the following
aspects of outputs designing were taken into consideration.
The outputs (i.e., well formatted table outputs in the screen itself)
designed are simple to read and interpret.
Format of each output was another important point taken into
consideration. Output media, for each output appropriate media is
decided whether it will be displayed on screen or will be taken to printer
or both.
Other output design related specifications, i.e., how frequently the
outputs will be generated, how many pages or sheets approximately it
will keep up, what is its planned use and output distribution to users are
also taken into account.
These were a few major designing issues, which were taken into consideration, while
deciding the output specifications for the system. As direct beneficiary of reports is
the user community, they were consulted constantly at every level. Formats and
screen design for various reports were identified, taking into account the user
requirements. Before finalizing these were given to users for any improvement and
suggestions. End users issues taken into consideration were Readability, Relevance
and Acceptability.
28
Output Sources:
Output contents originate from these sources:
Retrieval from a data source.
Transmission from a process or system activity.
Directly from an input source.
The information produced in an output can be presented as
Tabular contents
Graphic format
Using Icons
Output Definition:
The output should be defined in terms of:
Types of outputs:
Content-headings, numeric, alphanumeric, etc.,
Format-hardcopy,screen,microfilm,etc.,
Location-local, remote, transmitted, etc.,
Frequency-daily, weekly, hourly, etc.,
Response-immediate with in a period, etc.,
Input Design:
The input design is the link that ties the information system into the user’s world.
Input specifications describe the manner in which data enters the system for
processing. Input design features can ensure the reliability of the system and produce
results from accurate data, or they can result in the production of erroneous
information.
29
Input Design consists of
Developing specifications and procedures for data preparation
Steps necessary to put data into a usable form for processing.
Data entry, the activity of putting data into the computer processing.
Objectives of Input design
Five objectives of design input focus on:
Controlling the amount of input required
Avoid delay
Avoiding errors in data
Avoiding extra steps.
Keeping the process simple.
Input designs are aimed at reducing the chances of mistakes of errors. As the human
beings are prone to errors there is always a possibility of occurrence of chance of
errors. Adequate validation checks are incorporated to ensure error free data storage.
Some of the data validation checks applied are as following:
Redundancy of data is checked. It means the records of primary key do
not occur twice.
Primary key field of any table must not be left blank.
Wherever items are coded, input code is checked for it’s validly with
respect to several checks.
Utmost care has been taken to incorporate the validation at each stage of the system.
E.g. when entering records into employee information table for employee, it is
checked that whether the corresponding employee exists in the employee information
table etc.
30
Enough messages and dialogue boxes are provided while design screen, which does
guide user at the time of any errors, or at time of entry. This feature provides a user-
friendly interface to native users.Design is the process by which an application
developer, working within the web’s specifications, makes decisions about how web
components will accomplish the web’s objectives. The web’s purpose and audience
are taken into account during the design phase. The aim is to find out how to achieve
the effects called for in the most flexible, efficient, and elegant way.
The following points were considered:
To create consistent look and feel for web.
Information to be separated into manageable page-sized
Chunks.
Cues to be provided for the reader about the web’s information structure and
contents, context, and navigation.
Links to be used to connect pages along the routs of use and user thinking.
3.6 DATA FLOW DIAGRAMS
Data Flow Diagramming is a means of representing a system at any level of detail
with a graphic network of symbols showing data flows, data stores, data processes,
and data sources/destination.
The data flow diagram is analogous to a road map. It is a network model of all
possibilities with different detail shown on different hierarchical levels. This
processes of representing different details level is called “leveling” or “partitioning”
by some data flow diagram advocates. Like a road map, there is no starting point or
stop point, no time or timing, or steps to get somewhere. We just know that the data
path must exist because at some point it will be needed. A road map shows all
existing or planned roads because the road is needed.
31
Details that is not shown on the different levels of the data flow diagram such as
volumes, timing, frequency, etc. is shown on supplementary diagrams or in the data
dictionary. For example, data store contents may be shown in the data dictionary.
Data Flow Diagram (DFD) uses a number of symbols to represent the systems. Data
Flow Diagram also known as ‘Bubble Chart’ is used to clarify system requirements
and identifying the major transformations that will become programs in system
design. So it is the starting point of the design phase that functionally decomposes the
requirements specifications down to the level of details.
Terms used in DFD
Process
A process transforms data values. The lowest level processes are pure functions
without side effects. An entire data flow graphics high-level process.
Data flows
A data flow connects the output of an object or process to input of another
object or process. It represents the intermediate data value within a
computation. It is represented by an arrow and labeled with a description of
data, usually its name or type.
Graphical Representation:
Graphical Representation:
32
Actors
An actor is active object that drives the data flow graph by producing or
consuming values.
Data store
A data store is a passive object with in a data flow diagram that stores data for
later access.
External Entity
A rectangle represents an external entity such as a librarian, a library member.
Output Symbol
This box represented data production during human computer interaction
Graphical Representation:
Graphical Representation:
Graphical Representation:
33
Client/Server framework:
ClientWorld Wide
Web Server
34
P O L I C E
I N F O R M A T I O N
S Y S T E M
DBA PAGE
INFORMATIONPAGE
ADD USER
DELETE USER
UPDATE USER
SHOW STATUS
INFORMATION PAGE
Arrests
CASES
CELLS
EVIDENCES
JAILS
MISSING PERSONS
MISSINGVEHICLES
ACCIDENTS
login
login
login
login
Login
accidents
arrests
cases
cells
evidences
jails
Missingpersons
Missing vehicle
35
3.7 SYSTEM TESTING
During system testing, the system is used experimentally to ensure that the software
does not fail i.e. it will run accordingly to specifications and in the way users expects.
Special test data are input for the processing and the result examined. A limited
number of users may be allowed to use the system so that analyst can see whether
they use it in unforeseen ways. It is preferable to discover any surprise before the
organisation implements the systems and encounters them later on. This type of
testing which allows only a few, selected users to work on the system is known as
beta testing. On the other hand the testing done by the developer(s), they are known as
alpha testing.
Persons other than who write the original programs to ensure complete and unbiased
and more reliable software generally testing.
The norms followed during the testing phase were thoroughly tested by me, the
developer; I was required to release the source code. The source code was copied into
the area of the testers from the area of the developers. Here all the further testing was
done. If some changes were desired in the program, I was suitable informed and was
required to make the necessary modification.
3.7.1 OBJECTIVES OF TESTING
Testing is vital to the success of a system. Testing is done at different stages within
the development phase. System testing makes a logical assumption that if all parts of
the system are correct, the goals will be successfully achieved. Inadequate testing
leads to errors that may not appear until months later when correction will be
extremely difficult. Another objective of testing its utility as user oriented vehicle
before implementation.
36
3.7.2 TESTING PROCEDURES
Following testing procedures were used:-
UNIT TESTING
Unit testing is the testing of a single program module in an isolated environment. The
testing of the processing procedure is the main focus. In this, regard, the entire
module was separately tested first as isolated and complete entities. This help a lot in
discovering problems related to single module and rectifying them in the context of
the module itself, rather than considering module-related problems in a global
context.
INTEGRATION TESTING
Integration testing is the process of the testing the interfaces among system modules,
such testing ensure that data moves between systems are intended. In the regard of
integration testing, it was seen that all the data was expected to be the output of a
particular module was obtained in the correct format, so that the next module could
accept it appropriately. This could be done
Either after the entire system was developed, or in stages after more than one module
was developed.
SUB SYSTEM TESTING
In this many unit-tested modules are combined into subsystems, which are then tested
again. The goal here was to see that if the modules can be integrated properly.
SYSTEM TESTING
System testing is the testing of the system against its initial objectives. Such testing is
done either in a simulated environment or in a live environment.
37
In the case system, which I developed, the testing was done in a pseudo- real
environment. The work I was involved dealt with insertion, updating and in the tables,
all the work was developed in the ‘development’ area. I call the environment pseudo-
real since all data which is being used for online transaction can be copied into the
tables of the ‘development’ and live data can be worked on. Thus, whatever would be
the output on the ‘client’ is reflected exactly on the ‘development’ also.
Thus, discovery of the errors become simpler in that the errors, which would occur in
the real-time environment, were exactly duplicated in the ‘development’ environment.
All the above types of testing were carried out and various extreme cases were also
introduced to check for whether the system responded as expected. The various forms,
database packages, procedures, functions, modules and the events were tested to
discover.
They behaved in the manner expected of them and gave the accurate results.
However, the factor, which helped most in the modification and rectification of the
system, was the user response. The user after using the system would invariable come
up with some idea to improve the system. Such ideas, if feasible were incorporated
into the system. Thus leading to an improvement in the overall efficiency of the
system.
38
4.1 RESULT
As we step into the 21st century, it is imperative to keep in mind a Vision. The
impact of IT and Communications in every aspect of our lives is phenomenal.
Information is the life of any police organization. Quick access to data is essential for
effective prevention, control and detection of crime and many other decision making
and decision support processes involved in police work.
The concept of e-governance has made its way into the state with Andhra Pradesh
leading the country in the field of technological advances. As part of the VISION
2020, the state’s focus on modernization of law & order and crime takes the shape of
eCOPS (e-Computerized Operations for Police Services).
4.2 ADVANTAGES OF SYSTEM
There are lots of benefits acquired from this system. And these benefits are:
Efficiency:
Time saving
Considerable manpower – every work is done computerized.
Computer do its job very accurately.
Data processing is too much fast as compare to manual system.
Data storage capacity and processing is very high of this system.
Information retrieval:
Data retrieval process is very fast so helpful in further processing.
Presentation:
Multiple copies can be generated at a time, so time is saved.
Results can be easily understand because everything is done in very
procedural and in simple way.
39
Data is tabular so easy to understand.
4.3 LIMITATIONS OF SYSTEM
FEW LIMITATIONS OF ECOPS SYSTEM ARE AS FOLLOWS:
A) Complex hardware is needed to make system efficient.
B) Labour should be skilled for better output.
C) DSN facility is necessary for its functionality.
4.4 PROPOSED SYSTEM:
To make a system efficient in which all the work performed manually become
computerized. All data about any tragedy like accidents are generated automatically.
And its will easiest to generate large amount of records and by making it
computerized efficient output can be obtained.
40
5.1 CONCLUSION
The police act as agents attempting to stabilize a society affected by disorder and
lawlessness. The internal security represents the strength and health potential of the
state which needs to be protected against violent onslaughts so that the psychological
immunities get nurtured by natural healing.
India today faces a series of problems related to crime control and order maintenance.
The Indian police play a crucial role in confronting problems affecting the social and
internal security of the nation. Curtailing the attempts of hostile forces whose main
aim is to disrupt and destabilize the nation’s peace, unity and integrity.
However, the police constantly face denunciation from various strata of society who
are not entirely aware of the professional, structural and moral dilemma of the police.
Unfortunately even the educated sections of society have an unclear, imprecise and
hazy knowledge of both the police and the criminal justice system.
Regretfully, even after so many years there remains a big wall of misunderstanding
and miscommunication between the police and the public which is a direct outcome
of various factors over which the police has no control. Development has been
conceptualized as a phenomenon characterizing change and growth but this change
has to be meaningful and the growth needs to be purposive.
The ECOPS site is an attempt to build a working partnership between the police and
the community thus promoting harmony and the spirit of oneness amongst various
segments of society transcending through religious, social and linguistic diversities.
Let us together work in unison and provide a safer environment for qualitative living.
41
5.2. FUTURE SCOPE OF PROJECT
An earnest attempt to bridge the gap between YOU-The public & US-The Police.It is
the Citizen who is benefited a lot through eCOPS. In the manual System, registration
of FIR was not done 100% accurately for various reasons. Certain mandatory
information needed was also not collected either the complainant furnished vague
information or much thought was not given to the importance of the information
which would have helped later in speeding up the investigation process. The System’s
insistence for certain mandatory information at the time of registration of complaint
automatically improved the responsiveness of the Police and in turn is building up
sensitivity. Once a complaint is registered, it is electronically transferred to the higher
authorities. Consequently, the scope for delinquencies such as non-acceptance of a
complaint, loss of track of case, etc are totally eliminated.
The transparency in the system helps in enhancing public interface and confidence. It
is assisting in expediting the progress of investigating process culminating in
dispensing timely justice and ultimately bringing the criminal activity under control.
Scope For Future
The future of eCOPS lies in developing new technologies to fight crime and improve
criminal justice. These include:
Development of new methods of crime prevention and reduction of crime
and delinquency
Development of dual-use technologies to support national defense and local
law enforcement needs
Apart from the above, eCOPS will also be used for the following:
field reporting and warrants
42
gang activity analysis and mobile data enquiries , traffic management etc
5.3 MAINTENANCE
Maintenance of a typical software product requires much more effort than the effort
necessary to develop the product itself. Many studies carried out in the past conform
this and indicate that the relative effort of development of the typical software
product to its maintenance effort is roughly in the 40:60 ratios.
Maintenance is generally of three types:
1. Corrective maintenance.
2. Adaptive maintenance
3. Perfective maintenance.
Corrective maintenance:
Corrective maintenance means repairing processing or performance failures or
making changes because of previously uncorrected problems or false assumptions.
Adaptive maintenance:
Adaptive maintenance means changing the program function according to new
enhancement in surroundings like make it flexible on new operating system.
Perfective maintenance:
Perfective maintenance means enhancing the performance or modifying the
program(s) to respond to the user’s additional or changing needs.
43
44
TEXT REFFERENCES
JAVA 2 COMPLETE REFFERENCE
JAVA SERVER PAGES IN 21 DAYS BY SAMS
ORACLE 9i COMPLETE REFFERENCE
SOFTWARE ENGINEERING BY Pressman
COMPLETE REFFERNCE HTML & DHTML
WEB REFFERENCES
Sun java homepage
http://www.java.sun.com
JSP tutorial
http://www.api.jhu.edu/-hall/java/servlet/tutorial
45
(A) CODING
adduser.jsp
<%@ page language="java"%><%@ page import="java.sql.*"%>
<HTML>
<HEAD> <TITLE>Add User Information</TITLE></HEAD><body bgcolor="#CCCCFF" text="#000000">
<% Connection con=null; Statement state=null; ResultSet result=null; String query=null; String user_id=null; String password=null; String dba=null; String status=null; try { Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); con=DriverManager.getConnection("Jdbc:Odbc:ecops"); state=con.createStatement(); user_id=request.getParameter("user_id"); password=request.getParameter("password"); status=request.getParameter("status"); dba=request.getParameter("dba"); if((user_id.length()==0) || (password.length()==0)) {%> <html> <title>Failed</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta http-equiv="refresh" content="0;URL=http://localhost:8080/ecops/pageAddUser.jsp"> </head> <body><% } else { query="select * from login where user_id='"+user_id+"' and password='"+password+"'";
46
result=state.executeQuery(query); if(result.next()) {%>
<p align="center"><font size="6" face="Verdana, Arial, Helvetica, sans-serif">User Information<br></font><font size="4" face="Verdana, Arial, Helvetica, sans-serif" color="RED">User Already Exixts.Enter another user Id.</font></p><form name="form1" method="post" action="http://localhost:8080/ecops/addUser.jsp"> <table width="58%"> <tr> <td width="40%">User Id </td> <td width="60%"> <input type="text" name="user_id"> <font color="red">*</font> </td> </tr> <tr> <td width="40%">Password </td> <td width="60%"> <input type="password" name="password"> <font color="red">*</font> </td> </tr> <tr> <td width="40%">Status </td> <td width="60%"> <select name="status"> <option value="sp">sp</option> <option value="jailor">jailor</option> <option value="dsp">dsp</option> </select> </td> </tr> <tr> <td width="40%"> </td> <td width="60%"> <input type="checkbox" name="dba" value="dba"> Make DBA user </td> </tr> <tr> <td width="40%"> </td> <td width="60%"> </td> </tr> <tr> <td width="40%"> <input type="submit" name="Submit" value="Craete User"> </td> <td width="60%"> <input type="reset" name="Submit2" value="Clear Information"> </td>
47
</tr> </table> </form><b><i> <font color="Black">Fields Marked by <font color="red">* </font>are Mandatory</font></b></i><% } else { if(dba==null) { query="insert into login values('"+user_id+"','"+password+"','"+status+"','false')"; } else { query="insert into login values('"+user_id+"','"+password+"','"+status+"','true')"; }
int i=state.executeUpdate(query);%><html><head><title></title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><meta http-equiv="refresh" content="4;URL=http://localhost:8080/ecops/pageAddUser.jsp"></head>
<body bgcolor="#CCCCFF" text="#000000"><p><font size="4">New User has been created successfully.</font></p><p> </p></body></html><% } } } catch(Exception e) { out.println("Error : "+e.getMessage()); } finally { con.close(); }%></BODY></HTML>
48
dpaOpt.jsp<%@ page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#FFFFFF" text="#000000" background="http://localhost:8080/ecops/BG.JPG"><p><a href="http://localhost:8080/ecops/pageAddUser.jsp" target="mainFrame"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Add User</font></a>
<font face="Verdana, Arial, Helvetica, sans-serif" size="2"><br> <a href="http://localhost:8080/ecops/pageDelUser.jsp" target="mainFrame">Delete User</a> <br> <a href="http://localhost:8080/ecops/pageUpdateUser.jsp" target="mainFrame">Update User</a> <br> <a href="http://localhost:8080/ecops/pageShowStatus.jsp" target="mainFrame">Show Status</a> <br> <a href="http://localhost:8080/ecops/userLogInfo.jsp" target="mainFrame">Login Information</a> <br> <a href="http://localhost:8080/ecops/pageOpt.jsp" target="_top">Goto Options Page</a><br>
<br> </font> </p><p> </p></body></html>delUser.jsp
<%@ page language="java"%><%@ page import="java.sql.*"%>
<HTML><HEAD> <TITLE></TITLE></HEAD><body bgcolor="#CCCCFF" text="#000000"><% Connection con=null; Statement state=null; ResultSet result=null; String query=null; String user_id=null; String password=null; try
49
{ Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); con=DriverManager.getConnection("Jdbc:Odbc:ecops"); state=con.createStatement(); user_id=request.getParameter("user_id"); password=request.getParameter("password"); if((user_id.length()==0) || (password.length()==0)) {%><html><head><title></title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><meta http-equiv="refresh" content="0;URL=http://localhost:8080/ecops/pageDelUser.jsp"></head>
<body bgcolor="#CCCCFF" text="#000000"></body></html><% } else { query="select * from login where user_id='"+user_id+"' and password='"+password+"'"; result=state.executeQuery(query);
if(result.next())
{ query="delete from login where user_id='"+user_id+"' and password='"+password+"'"; int i=state.executeUpdate(query);%><html><head><title></title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><meta http-equiv="refresh" content="4;URL=http://localhost:8080/ecops/pageDelUser.jsp"></head>
<body bgcolor="#CCCCFF" text="#000000"><p><font size="4">User has been removed successfully.</font></p><p> </p></body></html>
<%
50
} else {%> <p align="center"><font size="6" face="Verdana, Arial, Helvetica, sans-serif">User Information</font><br><font size="4" face="Verdana, Arial, Helvetica, sans-serif" color="RED">Wrong Information.User Does not Exist.</font></p><form name="form1" method="post" action="http://localhost:8080/ecops/delUser.jsp"> <table width="58%"> <tr> <td width="40%">User Id </td> <td width="60%"> <input type="text" name="user_id"><font color="RED"> *</font> </td> </tr> <tr> <td width="40%">Password </td> <td width="60%"> <input type="password" name="password"><font color="RED"> *</font> </td> </tr> <tr> <td width="40%"> </td> <td width="60%"> </td> </tr> <tr> <td width="40%"> <input type="submit" name="Submit" value="Delete User"> </td> <td width="60%"> <input type="reset" name="Submit2" value="Clear Information"> </td> </tr> </table> </form><b><i>Fields Marked by <font color="red"> *</font> are Mandatory</b></i><% } } } catch(Exception e) { out.println("Error : "+e.getMessage()); } finally { con.close(); }
51
%></BODY></HTML>framedesc.jsp<%@page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#FFFFFF" text="#000000">
</body></html>frameDescOpt.jsp<html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="#000000" background="http://localhost:8080/ecops/BG.JPG"><p align="left"><b><font size="4">DBA Page : <br> </font></b> This Page provides the following Options : </p> 1)Add a User<br> 2)Delete a User<br> 3)Update a User<br> 4)Show Status<br> 5)Login Information<p align="left"><font size="4"><b>Information Page : <br> </b></font>Selecting this option you can search or insert information.</p><p align="left"><b><font size="4"> </font></b></p><p> </p></body></html>frameHead.jsp<html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#FFFFFF" text="#000000" background="TOP.JPG"></body></html><%@page language="java"%>
52
<html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="00000"> <font color="00000" size="4"><p align="center">Sign In : </p></font><form name="form1" method="post" action="http://localhost:8080/ecops/respLogin.jsp" target="_top"> <p align="center"><font color="#00000"><br> </font><font color="#00000">User ID : </font><font color="#00000"><br> </font><font color="#00000"> <input type="text" name="user_id" size="20"> <font color="#00000"><br> <font color="#00000">Password :</font></font> </font> <br> <input type="password" name="password" size="20'"><br><br> <input type="checkbox" name="dba" value="dba"><font color="#00000">DBA USER </font><br><br> <input type=submit value="Sign In">
</form>
</body></html><%@page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="#000000" background="http://localhost:8080/ecops/BG.JPG"><font face="vardana" size="1"><p> Accidents <a href="http://localhost:8080/ecops/pageAccidents.jsp" target="mainFrame">Insert</a> <a href="http://localhost:8080/ecops/pageSearchAccidents.jsp" target="mainFrame"> Search</a><br> Arrests <a href="http://localhost:8080/ecops/pageArrests.jsp" target="mainFrame">Insert </a><a href="http://localhost:8080/ecops/pageSearchArrests.jsp" target="mainFrame"> Search</a><br> Cases <a href="http://localhost:8080/ecops/pageCases.jsp" target="mainFrame">Insert</a> <a href="http://localhost:8080/ecops/pageSearchCases.jsp" target="mainFrame"> Search</a><br> Cells <a href="http://localhost:8080/ecops/pageCells.jsp" target="mainFrame">Insert</a> <a
53
href="http://localhost:8080/ecops/pageSearchCells.jsp" target="mainFrame"> Search</a><br> Crime Classes <a href="http://localhost:8080/ecops/pageCrimeClasses.jsp" target="mainFrame">Insert</a> <a href="http://localhost:8080/ecops/pageSearchCrimeClasses.jsp" target="mainFrame"> Search</a><br> Evidences <a href="http://localhost:8080/ecops/pageEvidences.jsp" target="mainFrame">Insert</a> <a href="http://localhost:8080/ecops/pageSearchEvidences.jsp" target="mainFrame"> Search</a><br>
Incident Crime Solvability <a href="http://localhost:8080/ecops/pageInciCrimeSolv.jsp" target="mainFrame">Insert</a> <a href="http://localhost:8080/ecops/pageSearchInciCrimeSolv.jsp" target="mainFrame"> Search</a><br>
Incident Modus Operandi <a href="http://localhost:8080/ecops/pageInciModOper.jsp" target="mainFrame">Insert <a href="http://localhost:8080/ecops/pageSearchInciModusOper.jsp" target="mainFrame"> Search</a></a><br>
Incident Persons <a href="http://localhost:8080/ecops/pageInciPersons.jsp" target="mainFrame">Insert <a href="http://localhost:8080/ecops/pageSearchInciPersons.jsp" target="mainFrame"> Search</a></a><br> Incident Vehicles <a href="http://localhost:8080/ecops/pageInciVehicles.jsp" target="mainFrame">Insert</a> <a href="http://localhost:8080/ecops/pageSearchInciVehicles.jsp" target="mainFrame"> Search</a><br>
Jails <a href="http://localhost:8080/ecops/pageJails.jsp" target="mainFrame">Insert <a href="http://localhost:8080/ecops/pageSearchJails.jsp" target="mainFrame"> Search</a></a><br> Missing Persons <a href="http://localhost:8080/ecops/pageMissPersons.jsp" target="mainFrame">Insert <a href="http://localhost:8080/ecops/pageSearchMissPersons.jsp" target="mainFrame"> Search</a></a><br> Missing Vehicles <a href="http://localhost:8080/ecops/pageMissVehicles.jsp" target="mainFrame">Insert <a href="http://localhost:8080/ecops/pageSearchMissVehicles.jsp" target="mainFrame"> Search</a></a><br> Stations <a href="http://localhost:8080/ecops/pageStations.jsp" target="mainFrame">Insert</a><a href="http://localhost:8080/ecops/pageSearchStations.jsp" target="mainFrame"> Search</a><br><% String dba=null; dba=request.getParameter("dba"); if(dba.equals("true")) {%> <a href="http://localhost:8080/ecops/pageOpt.jsp" target="_top">Goto Option Page</a><br>
54
<% }%> </p>
<p> </p></font></body></html><%@ page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="#000000"></body></html><%@page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="BLACK"><B>
</body></html><%@page language="java"%>
<html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head><frameset rows="95,*" frameborder="NO" border="0" framespacing="0" cols="*"> <frame name="topFrame" scrolling="NO" noresize src="/ecops/frameHead.jsp" > <frameset cols="530,*" frameborder="NO" border="0" framespacing="0" rows="*"> <frame name="leftFrame" scrolling="NO" noresize src="/ecops/framedesc.jsp"> <frame name="mainFrame" src="/ecops/frameLogin.jsp"> </frameset></frameset><noframes><body bgcolor="#FFFFFF" text="#000000"></body></noframes></html>
55
<html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<frameset rows="80,*" frameborder="NO" border="0" framespacing="0"> <frame name="topFrame" scrolling="NO" noresize src="frameHead.jsp" > <frameset cols="273,*" frameborder="NO" border="0" framespacing="0" rows="*"> <frame name="leftFrame" scrolling="NO" noresize src="frameOpt.jsp"> <frame name="mainFrame" src="frameSelect.jsp"> </frameset></frameset><noframes><body bgcolor="#CCCCFF" text="#000000">
</body></noframes></html><%@ page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="#000000"><a href="http://localhost:8080/ecops/showDba.jsp" target="_top">Dba Page</a><br><a href="http://localhost:8080/ecops/showInformation.jsp" target="_top">Information Page</a></body></html><%@ page language="java" %><%@ page import="java.sql.*"%>
<HTML><HEAD><TITLE>Accident Data Entry</TITLE></HEAD>
<body bgcolor="#CCCCFF" text="BLACK"><B><CENTER> <DIV align=left><b> <p align="center"><font face="Verdana, Arial, Helvetica, sans-serif" size="4"> ACCIDENT DATA ENTRY</font></b> <FORM NAME="LOGIN" ACTION="http://localhost:8080/ecops/respAccidents.jsp" METHOD="post"> <table width="75%" align="center"> <tr> <td width="58%">Accident Number</td> <td width="42%"> <input type="text" name="ACCIDENT_NUMBER" size="10"> <font color="#FF0000">*</font><font color="#000000"> </font> </td>
56
</tr> <tr> <td width="58%">Incident Number</td> <td width="42%"> <p> <input type="text" name="INCIDENT_NUMBER" value="" size="5"> <font color="#FF0000">*</font></p> </td> </tr> <tr> <td width="58%">Date</td> <td width="42%"> <input type="text" name="DATE" value="" size="12"> <font color="#FF0000">*</font> </td> </tr> <tr> <td width="58%">Time</td> <td width="42%"> <input type="text" name="TIME" value="" size="10"> </td> </tr> <tr> <td width="58%">Reporting officer Id</td> <td width="42%"> <input type="text" name="REPORTING_OFFICER_ID" value="" size="8"> <font color="#FF0000">*</font> </td> </tr> <tr> <td width="58%">Agency</td> <td width="42%"> <input type="text" name="AGENCY" value="" size="8"> </td> </tr> <tr> <td width="58%">Location</td> <td width="42%"><b> <input type="text" name="LOCATION" value="" size="20"> </b></td> </tr> <tr> <td width="58%">Address<b> </b></td> <td width="42%"><b> <input type="text" name="ADDRESS" value="" size="30"> </b></td> </tr> <tr> <td width="58%">Zip Code<b></b></td> <td width="42%"><b> <input type="text" name="ZIP_CODE" value="" size="10"> </b></td>
57
</tr> <tr> <td width="58%">Staion Id<b> </b></td> <td width="42%"><b> <input type="text" name="STATION_ID" value="" size="20"> <font color="#FF0000">*</font><b> </b></b></td> </tr> <tr> <td width="58%">Crime Id<b> </b></td> <td width="42%"><b> <input type="text" name="CRIME_ID" value="" size="15"> <font color="#FF0000">*</font></b></td> </tr> <tr> <td width="58%">Number Of Injured</td> <td width="42%"><b> <input type="text" name="NUMBER_OF_INJURED" value="" size="5"> </b></td> </tr> <tr> <td width="58%">Number of Fatal</td> <td width="42%"><b> <input type="text" name="NUMBER_OF_FATAL" value="" size="5"> </b></td> </tr> <tr> <td width="58%"> </td> <td width="42%"> <input type="submit" name="Submit" value="Submit Information"> </td> </tr> </table> <p><i><font size="2">FIELDS MARKED BY <b><font color="#FF0000">*</font></b> ARE MANDATORY</font></i></p> <p> </p> </FORM> </DIV></center></BODY></HTML><%@ page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="#000000"><p align="center"><font size="6" face="Verdana, Arial, Helvetica, sans-serif">User Information</font></p>
58
<form name="form1" method="post" action="http://localhost:8080/ecops/addUser.jsp"> <table width="58%"> <tr> <td width="40%">User Id </td> <td width="60%"> <input type="text" name="user_id"><font color="RED"> *</font> </td> </tr> <tr> <td width="40%">Password </td> <td width="60%"> <input type="password" name="password"><font color="RED"> *</font> </td> </tr> <tr> <td width="40%">Status </td> <td width="60%"> <select name="status"> <option value="sp">sp</option> <option value="jailor">jailor</option> <option value="dsp">dsp</option> </select> </td> </tr> <tr> <td width="40%"> </td> <td width="60%"> <input type="checkbox" name="dba" value="dba"> Make DBA user </td> </tr> <tr> <td width="40%"> </td> <td width="60%"> </td> </tr> <tr> <td width="40%"> <input type="submit" name="Submit" value="Create User"> </td> <td width="60%"> <input type="reset" name="Submit2" value="Clear Information"> </td> </tr> </table> </form><b><i> Fields marked by <font color="RED">* </font> are Mandatory.</i></b></body></html><%@ page language="java"%><%@ page import="java.sql.*"%>
59
<HTML><HEAD><TITLE>INSERT INTO ARRESTS</TITLE></HEAD>
<body bgcolor="#CCCCFF" text="BLACK"><B><CENTER> <DIV align=left><b><p align="center"><font face="Verdana, Arial, Helvetica, sans-serif" size="4" color="#003333">ARRESTS DATA ENTRY</font></b> <FORM NAME="LOGIN"ACTION="http://localhost:8080/ecops/respArrests.jsp" METHOD="post"> <table width="75%" align="center"> <tr> <td>Station Id</td> <td><font color="#000000"> <input type="text" name="STATION_ID" size="10"> <font color="#FF0000">*</font></font></td> </tr> <tr> <td>Crime Id</td> <td> <input type="text" name="CRIME_ID" value="" size="10"> <font color="#FF0000">*</font> </td> </tr> <tr> <td>Name</td> <td> <input type="text" name="NAME" value="" size="20"> <font color="#FF0000">*</font> </td> </tr> <tr> <td>Father's Name</td> <td> <input type="text" name="FATHERS_NAME" value="" size="20"> </td> </tr> <tr> <td>Address</td> <td> <input type="text" name="ADDRESS" value="" size="30"> </td> </tr> <tr> <td>Date Of Arrest(mm/dd/yyyy)</td> <td><b> <input type="text" name="DATE_OF_ARREST" value="" size="15"> </b> <font color="#FF0000">*</font></td> </tr> <tr> <td>Place Of Arrest</td>
60
<td><b> <input type="text" name="PLACE_OF_ARREST" value="" size="20"> </b></td> </tr> <tr> <td>Relative Name</td> <td><b> <input type="text" name="RELATIVE_NAME" value="" size="25"> </b></td> </tr> <tr> <td>Relative Address</td> <td><b> <input type="text" name="RELATIVE_ADDRESS" value="" size="30"> </b></td> </tr> <tr> <td>Relation</td> <td><b> <input type="text" name="RELATION" value="" size="20"> </b></td> </tr> <tr> <td>Finger Print Number</td> <td><b> <input type="text" name="FINGER_PRINT_NUMBER" value="" size="10"> </b></td> </tr> <tr> <td>Other Identifications</td> <td><b> <input type="text" name="OTHER_IDENTIFICATIONS" value="" size="30"> </b></td> </tr> <tr> <td> </td> <td> <input type="submit" name="Submit" value="Submit Information"> </td> </tr> </table> <p><i><font size="2">FIELDS MARKED BY <b><font color="#FF0000">*</font></b> ARE MANDATORY</font></i></p> <p> </p> </FORM> </DIV></center></BODY></HTML>
61
<%@page language="java"%><HTML><HEAD><TITLE>INSERT INTO CASES</TITLE></HEAD>
<body bgcolor="#CCCCFF" text="BLACK"><B><div align="center"><b> <font face="Verdana, Arial, Helvetica, sans-serif" size="4" color="#003333"> CASES DATA ENTRY</font></b> </div><FORM NAME="LOGIN"ACTION="http://localhost:8080/ecops/respCases.jsp" METHOD="post"> <table width="75%" align="center"> <tr> <td><font color="#000000">Station Id</font></td> <td><font color="#000000"> <input type="text" name="STATION_ID" size="10"> </font><font color="#FF0000">*</font><font color="#000000"> </font> </td> </tr> <tr> <td>FIR Number</td> <td> <input type="text" name="FIR_NUMBER" value="" size="5"> <font color="#FF0000">*</font> </td> </tr> <tr> <td>FIR Description</td> <td> <input type="text" name="FIR_DESCRIPTION" value="" size="12"> </td> </tr> <tr> <td>FIR Date</td> <td> <input type="text" name="FIR_DATE" value="" size="10"> <font color="#FF0000">*</font> </td> </tr> <tr> <td height="21"> <p>Complaint Name</p> </td> <td height="21"> <input type="text" name="COMPLAINT_NAME" value="" size="8"> </td> </tr> <tr> <td>Address</td> <td><b> <input type="text" name="ADDRESS" value="" size="20"> </b></td> </tr> <tr>
62
<td>Act Sections</td> <td><b> <input type="text" name="ACT" value="" size="20"> </b></td> </tr> <tr> <td>Accused Details</td> <td><b> <input type="text" name="ACCUSED_DETAILS" value="" size="30"> </b></td> </tr> <tr> <td>Disposal</td> <td><b> <input type="text" name="DISPOSAL" value="" size="10"> </b></td> </tr> <tr> <td>Judgement</td> <td><b> <input type="text" name="JUDGEMENT" value="" size="20"> </b></td> </tr> <tr> <td>Punishment Details<b> </b></td> <td><b> <input type="text" name="PUNISHMENT_DETAILS" value="" size="15"> </b></td> </tr> <tr> <td>Property Lost<b> </b></td> <td><b> <input type="text" name="PROPERTY_LOST" value="" size="19"> </b></td> </tr> <tr> <td>Property Received<b></b></td> <td><b> <input type="text" name="PROPERTY_RECIEVED" value="" size="18"> </b></td> </tr> <tr> <td> </td> <td> <input type="submit" name="Submit" value="Submit Information"> </td> </tr> </table> <p><i><font size="2"><b>FIELDS MARKED BY <font color="#FF0000">*</font> ARE
63
MANDATORY</b></font></i></p></FORM> </BODY></HTML><%@ page language="java"%>
<HTML><HEAD><TITLE>INSERT INTO CELLS</TITLE></HEAD>
<body bgcolor="#CCCCFF" text="BLACK"><B><div align="center"><b><font face="Verdana, Arial, Helvetica, sans-serif" size="4" color="#003333">CELLS DATA ENTRY</font></b> </div><FORM NAME="LOGIN"ACTION="http://localhost:8080/ecops/respCells.jsp" METHOD="post"> <table width="75%" align="center"> <tr> <td>Cell Id</td> <td><b> <input name="CELL_ID" size="10"> <font color="#CC0000">*</font></b></td> </tr> <tr> <td height="33">Cell Description</td> <td height="33"> <input size=30 name=CELL_DESCRIPTION> </td> </tr> <tr> <td> </td> <td><b><font size=2> <input type="submit" name="btnSubmit"
value="Submit Information"> </font></b></td> </tr> </table> <p> <FONT SIZE=2><i><b>FIELDS MARKED BY <font size=2><font color="#CC0000">*</font></font>ARE MANDATORY </b></i></font></p></FORM></BODY></HTML><%@ page language="java"%><HTML><HEAD><TITLE>INSERT INTO CRIME CLASSES</TITLE></HEAD>
<body bgcolor="#CCCCFF" text="BLACK"><B><div align="center"><b><font face="Verdana, Arial, Helvetica, sans-serif" size="4" color="#003333">CRIME CLASSES DATA ENTRY</font></b> </div>
64
<FORM NAME="LOGIN"ACTION="http://localhost:8080/ecops/respCrimeClasses.jsp" METHOD="post">
<table width="75%" align="center"> <tr> <td> Crime Id</td> <td> <input name="CRIMEID" size="10"> <font color="#CC0000">* </font></td> </tr> <tr> <td>Description</td> <td> <input size=30 name=DESCRIPTION> </td> </tr> <tr> <td> </td> <td><b><font size=2> <input type="Submit" name="btnSubmit"
value="Submit Information"> </font></b></td> </tr> </table> <p><FONT SIZE=2><i><b>FIELDS MARKED BY <font size=2><font color="#CC0000">*</font></font>ARE MANDATORY </b></i></font> </p></FORM></BODY></HTML><%@ page language="java"%><html><head><title>Untitled Document</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body bgcolor="#CCCCFF" text="#000000"><p align="center"><font size="6" face="Verdana, Arial, Helvetica, sans-serif">User Information</font></p><form name="form1" method="post" action="http://localhost:8080/ecops/delUser.jsp"> <table width="58%"> <tr> <td width="40%">User Id </td> <td width="60%"> <input type="text" name="user_id"><font color="RED"> *</font> </td> </tr> <tr>
65
<td width="40%">Password </td> <td width="60%"> <input type="password" name="password"><font color="RED"> *</font> </td> </tr> <tr> <td width="40%"> </td> <td width="60%"> </td> </tr> <tr> <td width="40%"> <input type="submit" name="Submit" value="Delete User"> </td> <td width="60%"> <input type="reset" name="Submit2" value="Clear Information"> </td> </tr> </table> </form><b><i> Fields marked by <font color="RED">* </font> are Mandatory.</i></b></body></html>
66
(B) SCREENSHOTS
Ecops Home Page
67
Login Page
68
DBA page
69
Form to add user
70
Information Page
71
Page to search Accident Information
72
Result of search information about Accidents
73
Form for Arrest Data Entry
74
Form for searching Arrest data
75
Form to search any cell information
76
Form to insert incident persons data
77
Form to search jails information
78
Form to show status
79
Form to show status of All Users
80
Resultant page of above form
81
Form for missing person data entry
82
Form for user updation
83
Form for Evidences data entry
84
Form to search
85
Resultant page
86