Professional Documents
Culture Documents
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:
Advantages:
Reduction of manual work
Minimizing the time and work
The work can be done faster
Page |
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:
The main thing is thing is that it will become difficult to decide when
to issue transfer orders to a particular employee.
Page |
Page |
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
Page |
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 |
Database
Employee login
Update
personal
details
Search for
vacancies
Employee
details
Request
for
transfers
View
details
Page |
Add
categories
Add
employees
details
Search for
particular
employee
View
details
Page |
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.
Page |
An Overview of UML:
The UML is a language for
Visualizing
Specifying
Constructing
Documentation
These are the artifacts of a software-intensive system.
Page |
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.
Page |
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 |
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.
Page |
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.
Page |
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
Page |
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
Page |
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.
Page |
Page |
Work history
Eid:string
Sid: number
From_date:date
To_date:date
Maintain()
Modify()
CLASS DIAGRAM
The following class diagram for Constables Transfer Automation System
consists
of
classes
like
employee,work_history,
stations,
type
of
Employee
Eid:string
Name: string
Dob: number
Qualification:string
Department of CSE, MITS, Madanapalle
Gender: string
Working()
Designation()
Salary()
Page |
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
Page |
GENERAL or WOMEN
Stations
CIRCLES
VACANCIES
Transfers
PRIORITIES
Employee
WORK_HISTORY
MAINTAIN DATABASE
System
MODIFY DATABASE
SEQUENCE DIAGRAM
Page |
home page
system
database
System
requirements
Employee
Request
Home page
Send request
Validate
Information of validation
Page |
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
Type
Size
EID
VARCHAR
20
SID
NUMBER
10
Page |
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
Page |
Column Name
EID
Type
VARCHAR
Size
20
SID
NUMBER
10
FROM_DATE
DATE
10
TO_DATE
DATE
10
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 |
Page |
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.
Page |
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.
Component
Testing
SYSTEM TESTING
Integration Testing
Page |
ACCEPTANCE
TESTING
UserTesting
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 |
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
Page |
Page |
Page |
6. SCREEN SHOTS
Page |
Page |
Page |
Page |
Page |
Page |
Page |
Page |
Page |
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.
Page |
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.
Page |
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
Page |