You are on page 1of 43

Mechanization Of Police Transfer System

1. INTRODUCTION
1.1 SYSTEM OVERVIEW
Police Service is one of the most defence renowned services all over the
world. There are various modules in this service like transfers, promotions and many
more.
This project exactly concentrates on this aspect----automation of police
transfers as transfers done generally in a tedious process, thus over coming various
aspects and difficulties in general transfers and making the transfers very simpler,
easier and quicker by using this automation process.
This automation of police transfers mainly concentrates on hierarchy of areas
like divisions, circles and stations. The stations are again classified as two types. Plain
station and Agency Station come under one type of stations and General station and
Women station come under the other type of stations.

Objectives:
The main objectives of this project are:

Maintaining details about employees and their transfers

Maintaining details about vacancies

Maintaining details of stations

Advantages:
Reduction of manual work
Minimizing the time and work
The work can be done faster

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
Currently, the transfer of police is done manually. It is not functionally good
and also not flexible enough to get all the details of a particular employee and his
work history and the information about transfers and vacancies and also about the
information of about any station like to which circle or division it belongs.

Bottlenecks:
The Bottlenecks of the existing system are:

It is difficult to maintain the records of all employees which includes


their details and work history.

It is time consuming as it takes much time to notify the employees


about their transfers.

The main thing is thing is that it will become difficult to decide when
to issue transfer orders to a particular employee.

It is also difficult to maintain the information about various types of


stations like general, women, agency etc.

If we have to verify whether sufficient vacancies are there or not, we


have to check the total number of posts and number of working
employees which is very difficult, time consuming and even it may
lead to errors.

2.2 PROPOSED SYSTEM


The proposed system Mechanization Of Police Transfer System developed
using Java is one that eliminates all the drawbacks of the existing system.
Advantages:

Reduction of manual work

Minimizing the time and work

The work can be done faster

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Interactiveness with the system

2.3. FEASIBILITY STUDY


The existing system is clearly understood. The next step is to conduct the
feasibility study, which is a high level capsule version of the entire System Analysis
and Design process. The objective is to determine whether the proposed system is
feasible. The three tests of feasibility have been carried out:
Technical Feasibility
Economical Feasibility
Operational Feasibility

2.3.1 Technical Feasibility:


In technical feasibility study, one has to test whether the proposed system can
be developed using existing technology or not. It is planned to implement the
proposed system using Windows XP, Java and Apache Tomcat Server. The
Organization already possesses Windows XP Operating System. It is evident that the
necessary hardware and software are available for the development and
implementation of the proposed system. Hence the solution is technically feasible.

2.3.2 Economical Feasibility:


As part of this, the costs and benefits associated with the proposed system are
to be compared and the project is economically feasible only if benefits outweigh
costs. It need not to invest for the internet connection and also the organization
initiated to use Open Source in project development, hence there is 0 additional cost
incurred for the tools that will be used.

2.3.2 Operational Feasibility:


This test of feasibility checks if the system works with least difficulties when
it is developed and installed. The technical staff has sufficient knowledge of the
tools being used and the users need just to know how to access and run the
programs. Hence it is concluded that the system is operationally feasible.

2.4 SOFTWARE AND HARDWARE REQUIREMENTS


Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Software Requirements:
Front End
Back End

:
:

Java
SQL

Operating System
Web Server

:
:

Windows XP/2000/2003
Apache Tomcat

:
:
:

PENTIUM IV
256MB
20GB

Hardware Requirements:
Processor
Ram
Hard Disk

2.5 DATAFLOW DIAGRAMS


The DFD takes an input-process-output view of a system i.e. data objects flow
into the software, are transformed by processing elements, and resultant data objects
flow out of the software.
Data objects represented by labeled arrows and transformation are represented
by circles also called as bubbles. DFD is presented in a hierarchical fashion i.e. the
first data flow model represents the system as a whole. Subsequent DFD refine the
context diagram (level 0 DFD), providing increasing details with each subsequent
level.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


The DFD enables the software engineer to develop models of the information
domain & functional domain at the same time. As the DFD is refined into greater
levels of details, the analyst performs an implicit functional decomposition of the
system. At the same time, the DFD refinement results in a corresponding refinement
of the data as it moves through the processes that embody the applications.
A context-level DFD for the system the primary external entities produce
information for use by the system and consume information generated by the system.
The labeled arrow represents data objects or object hierarchy.
A DFD identifies all inputs and outputs and reads left to right and top to
bottom. It indicates external sources and destinations of data with Squares. It indicates
each process internal to the system with rounded Circles. There must be no unnamed
process. It identifies all data flows for each process step, except simple Record
retrievals and labels data flow on each arrow.

DFD for Database:

Automatic
Registration

Police Transfer
Automation System

Tp=5yrs
in plain
or
Tp=3yrs
in
agency
station

Yes Generating
Transfers

No
Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Database

Not eligible for


transfer.

DFD for Employee:

Employee login

Update
personal
details

Search for
vacancies

Department of CSE, MITS, Madanapalle

Employee
details

Request
for
transfers

View
details

Page |

Mechanization Of Police Transfer System

DFD for Stations:


Station
Type of stations

Add
categories

Add
employees

Department of CSE, MITS, Madanapalle

details

Search for
particular
employee

View
details

Page |

Mechanization Of Police Transfer System

3. SYSTEM DESIGN
3.1 Design Objectives:
Design is the first step in moving from problem domain to the solution
domain. Design is essentially the bridge between requirements specification and the
final solution.
The goal of design process is to produce a model or representation of a
system, which can be used later to build that system. The produced model is called the
Design of the system. It is a plan for a solution for the system.

3.2 UNIFIED MODELLING LANGUAGE (UML):


Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

An Overview of UML:
The UML is a language for
Visualizing
Specifying
Constructing
Documentation
These are the artifacts of a software-intensive system.

A conceptual model of UML:


The three major elements of UML are
The UMLs basic building blocks.
The rules that dictate how those building blocks may be put together.
Some common mechanisms that apply throughout the UML.

Basic building blocks of the UML:


The vocabulary of UML encompasses three kinds of building blocks:
Things
Relationships
Diagrams
Things are the abstractions that are first-class citizens in a model.
Relationships tie these things together.
Diagrams group the interesting collection of things.
Things in UML: There are four kinds of things in the UML
1. Structural things
2. Behavioral things
3. Grouping things
4. Annotational things

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


These things are the basic object oriented building blocks of the UML. They
are used to write well-formed models.

STRUCTURAL THINGS
Structural things are the nouns of the UML models. These are mostly static
parts of the model, representing elements that are either conceptual or physical. In all,
there are seven kinds of Structural things.

Class:
A class is a description of a set of objects that share the same attributes,
operations, relationships, and semantics. A class implements one or more interfaces.
Graphically a class is rendered as a rectangle, usually including its name,
attributes and operations, as shown below.

Window
origin
Size
Open()
Close()
Display()

Interface:
An Interface is a collection of operation that specifies a service of a class or
component. An interface describes the externally visible behavior of that element.
Graphically, the interface is rendered as a circle together with its name.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

ISpelling

Use case:
Use case is a description of a set of sequence of actions that a system performs
that yields an observable result of value to a particular things in a model.
Graphically, Use case is rendered as an ellipse with dashed lines, usually
including only its name as shown below.

Chain of

Place Order

Responsibility

Component:
Component is a physical and replaceable part o a system that conforms to and
provides the realization of a set of interfaces.
Graphically, a component is rendered as a rectangle with tabs, usually including only
its name, as shown below.

orderform.java

Node:
Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


A Node is a physical element that exists at run time and represents a
computational resource, generally having at least some memory and often, processing
capability.
Graphically, a node is rendered as a cube, usually including only its name, as
shown below.

server

BEHAVIORAL THINGS
Behavioral Things are the dynamic parts of UML models. These are the verbs
of a model, representing behavior over time and space.
Interaction:
An interaction is a behavior that comprises a set of messages exchanged
among set objects within a particular context to accomplish a specific purpose.
Graphically, a message is rendered as a direct line, almost always including
the name of its operation, as shown below.
Display
State Machine:
A state machine is a behavior that specifies the sequence of states an object or
an interaction goes through during its lifetime on response to events, together with its
responses to those events.
Graphically, a state is rendered as a rounded rectangle usually including its
name and its sub-states, if any, as shown below.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Waiting

GROUPING THINGS
Grouping things are the organizational parts of the UML models. These are the
boxes into which a model can be decomposed.

Package:
A package is a general-purpose mechanism for organizing elements into
groups.

Business Rules

ANNOTATIONAL THINGS
Annotational things are the explanatory parts of the UML models. It doesnt
correspond to any object but serves as comment.

Note:
A note is simply a symbol for rendering constraints and comments attached to
an element or a collection of elements.
Graphically a note is rendered with dog-eared corner together, with a textual
or graphical comment.

RELATIONSHIPS IN THE UML


Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

There are four kinds of relationships in the UML:


1. Dependency
2. Association
3. Generalization
4. Realization

CLASS DIAGRAMS
Class diagrams are the most common diagrams found in modeling objectoriented systems. A class diagrams shows a set of classes, interfaces, and
collaborations and their relationships. Graphically, a class diagram is a collection of
vertices and arcs.

Contents:
Class Diagrams commonly contain the following things:
Classes
Interfaces
Collaborations
Dependency, generalization and association relationships

USE CASE DIAGRAMS


Use case diagrams are one of the five diagrams in the UML for modeling the
dynamic aspects of systems (activity diagrams, sequence diagrams, state chart
diagrams and collaboration diagrams are the four other kinds of diagrams in the UML
for modeling the dynamic aspects of systems). Use case diagrams are central to
modeling the behavior of the system, a sub-system, or a class. Each one shows a set of
use cases and actors and relationship.
Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Common Properties:
A Use case diagram is just a special kind of diagram and shares the same
common properties, as do all other diagrams- a name and graphical contents that are a
projection into the model.
Use case diagrams can be used during analysis to capture the system
requirements and to understand how the system works. During the design phase, the
use case diagrams are used to specify the behavior of the system as implemented.
What distinguishes a use case diagram from all other kinds of diagrams is its
particular content.
Contents:
Use case diagrams commonly contain:
Use case
Actors
Dependency, generalization, and association relationships
USE CASES are the system boundaries identifying what system should do
ACTORS are the things outside the system
Like all other diagrams, use case diagrams may contain notes and constraints.
Use case diagrams may also contain packages, which are used to group
elements of your model into larger chunks. Occasionally, you will want to place
instances of use cases in your diagrams, as well, especially when you want to
visualize a specific executing system.

INTERACTION DIAGRAMS
An Interaction diagram shows an interaction, consisting of a set of objects and
their relationships, including the messages that may be dispatched among them.
Interaction diagrams are used for modeling the dynamic aspects of the system.
A sequence diagram is an interaction diagram that emphasizes the time
ordering of the messages. Graphically, a sequence diagram is a table that shows

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


objects arranged along the X-axis and messages, ordered in increasing time, along the
Y-axis and messages, ordered in increasing time, along the Y-axis.
Sequence diagrams establish the role of objects and provide essential
information to determine class responsibilities and interfaces.
Contents:
Interaction diagrams commonly contain:
Objects
Links
Messages
Like all other diagrams, Interaction diagrams may contain Notes and
constraints.

SEQUENCE DIAGRAMS
A Sequence diagrams is an interaction diagram that emphasizes the time
ordering of the messages.
Graphically, a sequence diagram is a table that shows objects arranged along
the X-axis and messages, ordered in increasing time, along the Y-axis.
Typically you place the object that indicates the interaction at the left, and
increasingly more sub-routing objects to the right. Next, you place the messages that
these objects send and receive along the Y-axis, in order of increasing time from top
to the bottom.
This gives the reader a clear visual cue to the flow of control over time.

ACTIVITY DIAGRAMS
An Activity diagrams essentially a flow chart showing flow of control from
Activity to Activity. They are used to model the dynamic aspects of as system. They
can also be used to model the flow of an object as it moves from State to State of
different points in the flow of control.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


Contents:
Activity diagrams commonly contain
Activities
Decisions
States
Objects
Swim lanes
Transitions
Activity diagrams are closely related to state chart diagrams. The main
difference between the two diagrams is that state chart diagrams are state centric
where as activity diagrams are activity centric. Once the activity is completed, the
flow of control moves to next activity or state through a transition.
An activity is a behavioural diagram which is used for modeling the dynamic
aspects of the system. An activity diagram is mainly used to focus the flow of control
between activities.we need to specify various activities with respect to each business
aspects.

STATE CHART DIAGRAMS


A State chart diagram shows a state machine. State chart diagrams are used to
model the dynamic aspects of the system. For the most part, this involves modeling
the behavior of the reactive objects. A reactive object is on whose behaviors is best
characterized by its response to events dispatched from outside its context. A reactive
object has a clear life line whose current behavior is affected by its past.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


A state chart diagram typically consists of one start state and multiple end
states. Transitions connect the various states in the diagram. Each state represents a
named condition during the life of an object which it satisfies some condition or waits
for an event to occur. State chart diagrams are closely related to

Work history

activity diagrams. The main difference between the two

Eid:string
Sid: number
From_date:date
To_date:date
Maintain()
Modify()

diagrams is that state chart diagrams are state centric where as


activity diagrams are activity centric.
Graphically, a state chart diagram is a collection of
vertices and arcs. State chart diagrams commonly contain:
Simple states and composite states.
Transactions, including events and actions.

CLASS DIAGRAM
The following class diagram for Constables Transfer Automation System
consists

of

classes

like

employee,work_history,

stations,

type

of

stations,circles,transfers,priorities and vacancies.

Generalization relationship exists between stations and type of stations.

Association relationship exists between employee and stations.

Aggregation relationship exists between employee and work_history,


employee and priorities.

Dependency relationship exists between transfers and priorities, transfers and


vacancies.

Employee
Eid:string
Name: string
Dob: number
Qualification:string
Department of CSE, MITS, Madanapalle
Gender: string
Working()
Designation()
Salary()

Page |

Mechanization Of Police Transfer System

Priorities
Eid:string
Pno:number
Sid: number

Works
Dependency
Stations
Sid: number
cid:number
div_id:number
Records()
verify()

Aggregation

Circles
Cid:number
Div_id:number
maintain()
modify()

Transfers
Generalization
Dependency

Type2
general sid:number
women sid:number
records()
verify()

Eid:string
Sid: number
transferring()
modify()

Vacancies
Sid :num
Sanc_posts :num
Modify()

USECASE DIAGRAM

PLAIN or AGENCY

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

GENERAL or WOMEN

Stations
CIRCLES

VACANCIES

Transfers
PRIORITIES

Employee

WORK_HISTORY

MAINTAIN DATABASE

System
MODIFY DATABASE

SEQUENCE DIAGRAM

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

home page

system
database

System
requirements

Employee
Request
Home page
Send request

Validate
Information of validation

Request for vacancies


Response to employee
Request for view details
Form with data

3.3 DATABASE TABLES


Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


TABLE NAME: CIRCLES

Column Name
Type

Size

CID

NUMBER

10

DIV_ID

NUMBER

10

DESCRIPTION

VARCHAR

20

Column Name

Type

Size

SID

NUMBER

10

CID

NUMBER

10

TYPE 1
TYPE 2
DESCRIPTION

VARCHAR
VARCHAR
VARCHAR

20
20
20

TABLE NAME: STATIONS

TABLE NAME: TRANSFERS


Column Name

Type

Size

EID

VARCHAR

20

SID

NUMBER

10

TABLE NAME: EMPLOYEE DETAILS

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Column Name

Type

Size

EID

VARCHAR

20

ENAME

VARCHAR

20

DOB

DATE

10

DATEAPPOINTED

DATE

10

QUALIFICATION

VARCHAR

20

NATIVE PLACE

NUMBER

10

CASTE

VARCHAR

20

NO.OF.REWARDS

NUMBER

10

NO.OF.DEFAULTS

NUMBER

10

ANS_POSTING

NUMBER

10

SEX

VARCHAR

20

MARITAL_STATUS

VARCHAR

20

P_W_N STN

NUMBER

20

SINCE_WORKING

DATE

10

TABLE NAME: WORK_HISTORY

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Column Name
EID

Type
VARCHAR

Size
20

SID

NUMBER

10

FROM_DATE

DATE

10

TO_DATE

DATE

10

TABLE NAME: PRIORITIES

TABLE NAME: VACANCIES

Column Name

4.

Type
Type

SizeSize

EID
SID

VARCHAR
NUMBER

20
10

PNO
SANC_POSTS

NUMBER
NUMBER

10
10

SID
EXISTING_POSTS

NUMBER
NUMBER

10
10

IMPLEMENTATION
4.1. Introducton
During the implementation stage, the system is physically created. Necessary
programs are coded, debugged and documented. The test plan is established for
checking each and every component of the system.
The choice of a programming language for a specific project must take into
account both engineering and physical characteristics.
Java is a secured language. It is platform independent as it doesnt depend
on configuration or OS of a particular system but it should have Java Virtual Machine
(JVM). Byte code verification takes place at the end of the compilation process to
make sure that is all accurate and correct. So byte code verification is integral to the
compiling and executing of Java code.
Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


It helps the programmer to create full featured GUI and OOPS based
applications. It acts as FRONT END tool for databases like SQL, MS- Access, Oracle,
Sybase etc.
Since present applications require storing the large data and we have to
manipulate on that data, it is fully database application. For managing
Corporate database we can choose SQL acts as the BACKEND tool.

4.2. Modules Used:


Employee:
This module is used to get the data regarding the employee like his id, name,
date of birth, date of appointment, qualification, gender etc. All these data is saved in
the database. Whenever we want to retrieve the data from the database, it gives the
details in the format like Year-Month-Date, Description, and Qualification. This
module is also used for getting an employees work history.
Stations:
This module is used to get the data regarding the stations like to which circle
or division the station belongs. All the data is saved in the database. Whenever we
want to retrieve the data from the database, it gives the details in the format like

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


stationID-circleID-Description. This module is also used to retrieve what type of
station it is whether plain or agency, general or woman station.
Circles:
This module gives the data regarding the stations like to which circle or
division the station belongs. All the data is saved in the database. Whenever we want
to retrieve the data from the database, it gives the details in the format like CircleIDStationID-Description.
Priorities:
This module gives the important data regarding the employee which is the
priority data. Transfers are generated to the employees based on their priorities. All
the data is saved in the database. Whenever we want to retrieve the data from the
database, it gives the details in the format like EmployeeID-Priority-StationID.
Work history:
This module gives the work history of the employee which includes his work
experience. All the data is saved in the database. Whenever we want to retrieve the
data from the database, it gives the details in the format like StationID-EmployeeIDFrom_date, To_date.

Transfers:
It is a module which is used to get all the data regarding both employees and
stations. This module defines on what basis transfers are done and also gives
information about vacancies after transfers. All the data is automatically updated
about employees and stations after transfers are done.
Vacancies:
This module is used to get the details about vacant posts which are the existing
posts after filling the available posts. All the data is saved in the database. Whenever
we want to retrieve the data from the database, it gives the details in the format like
StationID-Sanctioned posts-Existing posts.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

5. TESTING
Software testing is a critical element of software quality assurance and represents
the ultimate review of specification, design and coding. In fact, testing is the one step in
the software engineering process that could be viewed as destructive rather than
constructive.
A strategy for software testing integrates software test case design methods into a wellplanned series of steps that result in the successful construction of software. Testing is
the set of activities that can be planned in advance and conducted systematically. The
underlying motivation of program testing is to affirm software quality with methods
that can economically and effectively apply to both strategic to both large and smallscale systems.

5.1 Testing fundamentals:


The software engineering process can be viewed as a spiral. Initially system
engineering defines the role of software and leads to software requirement analysis
UNIT TESTING

where the information domain, functions, behavior, performance, constraints and


validation criteria for software are established. Moving inward along the spiral, we
MODULE
come to design and finally to coding.
To develop computer software we spiral in along
TESTING

streamlines that decrease the level of abstraction on each turn.


SUB-SYSTEM
TESING

Component

Testing

SYSTEM TESTING
Integration Testing

Department of CSE, MITS, Madanapalle

Page |
ACCEPTANCE
TESTING

UserTesting

Mechanization Of Police Transfer System

A strategy for software testing may also be viewed in the context of the
spiral. Unit testing begins at the vertex of the spiral and concentrates on each unit of
the software as implemented in source code. Testing progress by moving outward
along the spiral to integration testing, where the focus is on the design and the
construction of the software architecture. Talking another turn on outward on the
spiral we encounter validation testing where requirements established as part of
software requirements analysis are validated against the software that has been
constructed. Finally we arrive at system testing, where the software and other system
elements are tested as a whole.
Testing is a process, which reveals errors in the program. It is the major
quality measure employed during software development. The testing method varies
from project to project depending on the nature and complexity of the system,
working environment etc. During testing the program is executed with a set of test
cases and the output of the program for the test cases is evaluated to determine if the
program is performing as it is expected to.
There are several levels in testing phase. These are unit testing, integration
testing, system testing and acceptance testing. Initially the tests are focused on each
module individually to test whether it is functioning as a unit.
In conventional applications, unit-testing focuses on the smallest combinable
program unit the sub program (e.g. module, sub routine, procedure, and component).
After testing them individually, it is integrated into a program structure and does the
remaining testing.

Unit Testing:
The first level of testing is unit testing. When object-oriented software is
considered the concept of unit changes. Rather than testing an individual module,
the smallest testable unit is the encapsulated class or object. Class testing for objectoriented software is the equivalent of unit testing for conventional software. Unlike
unit testing of conventional software, which tends to focus on the algorithmic detail
Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


of a module and the data that flow across the module interface, class testing for
object oriented software is driven by the operations encapsulated by the class and
state behavior of the class.

Integration Testing:
This testing is second level in testing process. After completion of unit
testing, which confirms the modules functionality, we integrated modules to form
sub systems. These subsystems are tested under this integration testing. It checks
whether data lost or preserved between interface calls. In this module whether data
flowed properly across the procedures is tested. Modules are integrated by moving
downward through the control hierarchy beginning from the main control module.
The following are the types of Integration Testing:
5.1.2.1 Top-Down Integration
This method is an incremental approach to the construction of program
structure. Modules are integrated by moving downward through the control
hierarchy, beginning with the main program module. The module subordinates to the
main program module are incorporated into the structure in either a depth first of
breadth-first manner.
5.1.2.2 Bottom Up Integration
This method begins the construction and testing with the modules at the
lowest level in the program structure. Since the modules are integrated from the
bottom up, processing required for modules subordinate to a given level is always
available and the need for stubs is elimination. The bottom-up integration strategy
may be implemented with the following steps:
The low-level modules are combined into clusters that perform a specific

software
Sub-function.
A drive (i.e.,), the control program for testing is written to co-ordinate test case

input and Output.


The cluster is tested.
Drivers are removed and clusters are combined moving upward in the program
structure.

5.1.3 Validation Testing


At the end of the Integration Testing, software is completely assembled as a
package, interfacing errors have been uncovered and correction testing begun. The
Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


system has been tested and implemented successfully and thus ensured that all the
requirements as listed in the software requirements specification are completely
fulfilled. In case of erroneous input corresponding error messages are displayed.
5.1.3.1 Compiling Test
It was a good idea to do our stress testing early on, because it gave us time to
fix some of the unexpected deadlocks and stability problems that only occurred
when components were exposed to very high transaction volumes.
5.1.3.2 Execution Test
This program was successfully loaded and executed. Because of good
programming there were no execution error found.
5.1.3.3 Output Test
The successful output screens are placed in the output screens section above.
5.1.3.4 Validation Test Criteria:
Software testing and validation is achieved trough serried of black box tests
that demonstrate conformity with the requirements. A test plan outlines the classes
of tests to be conducted and a test procedure defines specific test cases that will be
used to demonstrate conformity with requirements. Both, the plan and the procedure
are designed to ensure that all functional requirements are achieved, documentation
is correct and other requirements are met.
System testing:
System testing is responsible to ensure total software is worked as per
requirements specified in requirement documents. The main reference for this level
of testing is requirement document. This goal of this testing is to see, whether
system meets its requirements or not.
Acceptance testing:
Acceptance testing was top level testing which tests with some realistic
data of the client to demonstrate that the software is working satisfactory. Testing
here focuses on the external behavior of the system.

5.2. White Box Testing


This strategy examines the logic of the program. To follow this method we
developed some test data that resulted in executing every instruction in the program
and module i.e. every path is tested. Systems are not designed as entire nor are they
tested as single systems. To ensure that the coding is perfect two types of testing is
performed or for that matter is performed or that matter is performed or for that
matter is performed on all systems.
Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


In this the test cases are generated on the logic of each module by drawing flow
graphs of that module and logical decisions are tested on all the cases.
It has been uses to generate the test cases in the following cases:
Guarantee that all independent paths have been executed.
Execute all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds.
Execute internal data structures to ensure their validity.
This is a unit testing method where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors. I tested step
wise every piece of code, taking care that every statement in the code is executed at
least once. The white box testing is also called Glass Box Testing.

5.3. Black Box Testing


In this strategy some test cases are generated as input conditions that
fully execute all functional requirements for the program. This testing has been uses
to find errors in the following categories:
1. Incorrect or missing functions
2. Interface errors
3. Errors in data structure or external database access
4. Performance errors
5. Initialization and termination errors.
In this testing only the output is checked for correctness. The logical flow
of the data is not checked.
This testing method considers a module as a single unit and checks the
unit at interface and communication with other modules rather getting into details at
statement level. Here the module will be treated as a block box that will take some
input and generate output. Output for a given set of input combinations are
forwarded to other modules.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System


This test involves the manual evaluation of the flow from one module to
the other and check accordingly for the process flow. This process of testing is with
the following criteria:
Criteria Satisfied by Test Cases:
1. Test cases that reduced by a count that is greater than one, the number of
additional test cases that much be designed to achieve reasonable testing.
2. Test cases that tell us something about the presence or absence of classes of
errors, rather than an error associated only with the specific test at hand.

6. SCREEN SHOTS

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

7. CONCLUSION
The Mechanization of Police Transfer System in the present study is effective
and efficient. It maintains the data that are generated out of various activities (like
transfers and vacancies) thus minimizing the effort.

It maintains the details of vacancies after filling all the available posts. It is
portable and flexible for future enhancements. It provides valuable data information
for decision making of when to perform transfer of employees which would improve
the effectiveness and efficiency of the system.
The screens are designed in a simple way such that even a person with poor
computer knowledge can also use it. This application is implemented using Java ,with
web browser Apache Tomcat on Windows. The package is user friendly. The system is
easy to use and requires little effort to understand and operate.
Thus this project is very efficient, easier, quicker, simpler automated process
which reduces manual work of keeping records about each and every employee and
do needful in transfer process.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

SCOPE FOR EXPANSION


This project entitled Police Transfer Automation System has a good scope
for expansion. Actually, this project may be used by any organization where transfers
are possible like postal department, teachers etc.
However, this project can also be used to find out vacancies in any
organization. The intention behind developing this project is the computerization
which is going to help for faster notices of transfers.

This project helps quite good for each and every category in the department
of police as it is purely an automated process with which an employee in the
department can know easily through his login, updating his details and request for
transfer and can view the details easily.

Department of CSE, MITS, Madanapalle

Page |

Mechanization Of Police Transfer System

8. APPENDIX
8.1 BIBILOGRAPHY
The following books were referred during the analysis and execution phase of
the project
ORACLE 8I THE COMPLETE REFERENCE
By Oracle Press
SOFTWARE ENGINEERING
By Roger S. Pressman
UNIFIED MODELING LANGUAGE
By Gradi Booch, Ivar Jacobson, James Rambaugh
COMPLETE REFERENCE JAVA
By Herbert Schildt
The following links were searched and exploited extensively for the project
development and implementation.

http://www.java.sun.com/products\java

http://www.jakarta.apache.org

http://www.javaworld.com/

http://www.java2s.com/

http://www.wikipedia.com

Department of CSE, MITS, Madanapalle

Page |

You might also like