Final Print

PROJECT REPORT ON
IT SOLUTIONS FOR INTELLIGENCE BUREAU

Submitted in partial fulfillment of the requirements for the
award of the degree of
BACHELOR OF ENGINEERING
IN
INFORMATION TECHNOLOGY
Developed at:
Developed By:
Joshi Siddhi (ID - 056032)
Under the guidance of

Internal Project Guide External Project Guide
Prof.Harshad Prajati Ms. Jhelam Vohra
Asst. Professor Asst.Software Engineer
Dept. of Information Technology
DDU.
DEPARTMENT OF INFORMATION TECHNOLOGY

FACULTY OF TECHNOLOGY
DHARMSINH DESAI UNIVERSITY
NADIAD, GUJARAT, INDIA
APRIL – 2009
DDU (Faculty of Tech., Dept. of IT)

CANDIDATE’S DECLARATION
I declare that final semester report entitled “IT SOLUTIONS FOR INTELLIGENCE
BUREAU” is our own work conducted under the supervision of the external guide Ms.
Jhelam Vohra from TCS Gandhinagar.
We further declare that to the best of our knowledge the report for B.E. final semester
does not contain part of the work which has been submitted for the award of B.E. Degree
either in this or any other university without proper citation.
Joshi Siddhi
Branch: IT
ID No: 056032
Submitted To:
Prof. Harshad Prajapati
Department of Information Technology,
Faculty of Technology,
Dharmsinh Desai University,
Nadiad,
Gujarat.

DHARMSINH DESAI UNIVERSITY
NADIAD-387001, GUJARAT
CERTIFICATE
This is to certify that the project “IT SOLUTIONS FOR INTELLIGENCE

BUREAU” is a bonafide work carried out by JOSHI SIDDHI, Student ID NO: 056032
Of Department of Information Technology, semester VIII, under the guidance and
supervision for the award of the degree of Bachelor of Engineering at Dharmsinh Desai
University, Gujarat. They were involved in Project training during academic year 2008-
2009.
Prof. Harshad Prajapati

Department of Information Technology,
Dharmsinh Desai University, Nadiad
Date:
Prof. R.S. Chhajed

Head, Department of Information Technology,
Dharmsinh Desai University, Nadiad
Date:

ACKNOWLEDGEMENT
It gives us immense pleasure and satisfaction in presenting this report of System

development Project undertaken during the 8th semester of B.E.
As it is the first step into our Professional Life, we would like to take this opportunity to
express our sincere thanks to several people, without whose help and encouragement, it
would be unfeasible for us to carry out the desired work.
We would like to thank to Mr. Mihir Solanki (Project Leader) and Ms. Jhelam Vohra
(Module Leader) for giving us an opportunity to work with one of the most esteemed
organization of the world. An enviable work culture and an environment that encourages
creativity and innovation have inculcated in us a sense of discipline and perseverance.
We are indebted to Mr. Hardik Shah, Ms. Nikita Shah, Mr.Dharamendra Mahida
and Mr.Tejas Poojara for guiding us throughout the project development and helped us
conceptualize the idea of the project and helped us streamline our work by providing us
with facility required.
From the bottom of our heart, I would like to express my sincere thanks to our Head of
Department Prof. R.S.Chhajed and our internal guide Prof. Harshad Prajapati, who
gave us an opportunity to undertake such a great challenging and innovative work. We
are grateful to them for their guidance, encouragement, understanding and insightful
support in the development process.
Finally, we would like to thank to all TCS employees, all faculty members of our college,
our friends and our family members for providing their support and continuous
encouragement throughout the project.
With sincere regards,

Joshi Siddhi J.
DDU (Faculty of Tech., Dept. of IT) i

ABSTRACT
The Intelligence Bureau is formed to aid the police force. Its main objective is to collect,
collate and analyze intelligence and advance information for taking appropriate
preventive actions to maintain law and order in the state.
To handle the day-to-day affairs and collection and reporting of information, there are
several branches established to look after specific activities.
Requirement gathering of standard procedures, formats, forms, registers, reports and
various other documents and business processes will enable us to understand, analyze and
propose a new computerized system for better efficiency and efficacy. This will enable in
effective and better utilization of manpower, better and improved reporting framework
and processes with reduced repetitive work and faster decision making.
The branches of Intelligence Bureau do the following activities:
 Information Gathering
 Consolidation Activities
 Forecasting (Analysis Activities)
 Record Maintenance Activities
 Reporting Activities
IB is the main coordinating authority regarding security, law and order situation with the
Centre and other states. Hence, the Head office is interlinked with information flow of all
kinds of activities and events related to political, communal, religious, elections, students,
unions, farmers, laborers, foreigners, Pakistan nationals, airport, ports and coastal areas
of the state and security related information through these various support units. Work
allocation for above activities is distributed to the branches situated at the head office of
the Intelligence Bureau.
IB has identified the provision of online and instantaneous access to information. The
proposed solution includes the following
• Building up of Master Data for various applications

• Re-using the data across various applications thereby reducing the data-
redundancy and duplication of work.
The purpose of this project is to mainly computerize the Intelligence Bureau Department.
Hence this project is solely for the work done by the IB. Any other department is not
covered in the scope of this project. Also the project is entirely based on user
requirements as specified by the user and hence it is not possible to add any extra features
apart from those provided by the user. Its scope is limited to the work done by the
Intelligence Bureau Department.
DDU (Faculty of Tech., Dept. of IT) ii

COMPANY PROFILE
Tata Consultancy Services (TCS) is one of the leading information technology companies
in the world. With a workforce of over 94,000 professionals spread across more than 50
global delivery centers, it helps organizations stay ahead with new technology. Its clients
include seven of the top ten corporations in the Fortune 500 list of the largest
corporations in the United States.
TCS products and services help companies in various sectors effectively meet their
business challenges. With technical expertise and employing a flexible approach to client
relationships, TCS offers its clients: consulting, IT services, business process
outsourcing, infrastructure outsourcing, and engineering and industrial services.
Quality – a key business driver
Since its inception, the company has invested in new technologies, processes, and people
in order to help its customers succeed. With inputs from its innovation labs and university
alliances, and drawing on the expertise of key partners, TCS keeps clients up-to-date with
new technology. This has helped the company meet various benchmarks of excellence in
software development - it is the world's first organization to achieve an enterprise-wide
Maturity Level 5 on quality improvement models, CMMI® and P-CMM®, using the
most rigorous assessment methodology, SCAMPISM.
Research and Development
TCS offerings are backed by its investment (over 4% of its revenues) in Research and
Development in cutting edge technology; its software tools foundry at Tata Research
Development and Design Center, Pune is one of the most advanced in the world. TCS
also has research alliances with several world-renowned universities, such as the
University of California at Riverside and San Diego, the Indian Institutes of Technology
(IIT), and the Rotterdam School of Management.
Working with TCS
Being with TCS is all about possibilities, growth, learning, teamwork and leading change.
At TCS, there is much more than just technology and software development. TCS
encourages you to think different, challenge the conventional and innovate. People here
from diverse cultural and educational backgrounds bring in a wealth of knowledge and
experience that gives you an opportunity to learn and expand your horizons.
DDU (Faculty of Tech., Dept. of IT) iii

Location
TCS is headquartered in Mumbai, and operates in more than 50 countries and has more
than 170 offices across the world. The company is listed on the National Stock Exchange
and Bombay Stock Exchange in India.
Areas of business
The following TCS services help customers optimize business processes and create
resilient IT infrastructure, ensuring faster business results:
• Consulting
TCS consulting services help enterprises transform the way of doing business by
helping them to optimize business processes, align IT with business requirements,
support IT operations, and design effective risk management strategies.
• IT services
TCS provides system integration and testing solutions, and application development
and management services that help companies make the most of their IT investments.
• Business process outsourcing
TCS works with enterprises worldwide, helping them focus on their core business
while accelerating outsourced operations and ensuring round-the-clock service
delivery.
• Infrastructure outsourcing
The Company partners with enterprises to make their IT infrastructure flexible,

scalable, and secure, while maximizing performance.
• Engineering and industrial services
DDU (Faculty of Tech., Dept. of IT) iv

Using the best technologies, processes, and competencies, TCS helps businesses to
put into practice their strategies in product development, and management of assets
and production.
Industries
TCS helps clients from various industries solve complex problems, mitigate risks, and
become operationally excellent. Some of the industries it serves are:
• Banking and financial services

• Energy and utilities
• Government
• Healthcare and life sciences
• Hi technology
• Insurance
• Manufacturing
• Retail
• Telecom
• Travel and hospitality
Looking Ahead
Always looking ahead, TCS is working towards being among the global top ten IT
consulting companies in the coming years. Emphasizing its commitment to quality, TCS
intends to achieve SEI CMM level 5 certification for all its development centers. In
retrospection, TCS has grown over the years not merely in size, geographical spread and
revenue. It has evolved into a corporate culture dedicated to client satisfaction, lasting
relationships and social responsibility. It has become an environment where the best
minds from the top universities are instilled with the finest training possible. Its human
skills are ably backed by the latest in hardware, software and telecommunication links
that span the world.
In addition, it would also cater to the ERP projects being executed by the company for
the global clients. TCS is already working with the Gujarat government on several
projects and the in-house unit would also benefit their other operations in the state.
TCS CEO and Managing Director S Ramadorai said in a statement on their plans in
Gujarat: “TCS plans to play an integral role in the further development of the Gujarat
economy by working with corporations and helping train and develop the talent in the
State.”
DDU (Faculty of Tech., Dept. of IT) v

TABLE OF CONTENTS:
Candidate’s Declaration
College Certificate
Acknowledgement i
Abstract ii
Company Profile iii
Table of Contents vi
List of Figures ix
List of Tables xii
Abbreviations vi
1.0 Introduction 1
1.1 Project Details 1
1.2 Purpose 2
DDU (Faculty of Tech., Dept. of IT) vi

1.3 Scope 3
1.4 Objective 3
1.5 Technology and Literature Review 4
2.0 Project Management 15

2.1 Feasibility Study 15
2.1.1 Technical feasibility 16
2.1.2 Operational feasibility 16
2.1.3 Economic Feasibility 16
2.2 Project Planning 17
2.2.1 Project Development Approach and Justification 17
2.2.1 Project Plan 17
2.2.2 Milestones and Deliverables 19
2.2.3 Roles and Responsibilities 19
2.2.4 Group Dependencies 22
2.3 Project Scheduling 23

Project Scheduling chart 23
3.0 System Requirements Study 24

3.1 Study of Current System 24
3.2 Problems and Weaknesses of Current System 25
3.3 User Characteristics 26
3.4 Hardware and Software Requirements 27
3.5 Constraints 28
3.3.1 Hardware Limitations 28
3.3.2 Interfaces to Other Applications 28
3.3.3 Higher Order Language Requirements 29
3.3.4 Reliability Requirements 29
3.3.5 Safety and Security Consideration 29
3.3.6 Criticality of the Application 29
DDU (Faculty of Tech., Dept. of IT) vii

3.6 Assumptions and Dependencies 29
4.0 System Analysis 31

4.1 Requirements of New System (SRS) 31
4.1.1 User Requirements 31
4.1.2 System Requirements 54
4.2 Features Of New System 52
4.3 Navigation Chart 53
4.5 Use case diagram 54
4.6 Data Modeling 55
4.6.1 ER Diagram 55
5.0 System Design 57

5.1 System Architecture Design 58
5.1.1 Class Diagram 58
5.1.2 Sequence Diagrams 59
5.1.3 Deployment Diagram 66
5.2 Database Design/Data Structure Design 67

5.2.1 Database Table and Relationship 67
5.2.2 Table Relationship diagram 76
5.3 Input/Output and Interface Design 78
5.3.1 State Transition Diagram 80
6.0 Implementation Planning 84

6.1 Implementation Environment 84
6.2 Program/Modules Specification 86
6.3 Security Features 88
6.4 Coding Standards 92
7.0 Testing 102

7.1 Testing Plan 102
DDU (Faculty of Tech., Dept. of IT) viii

7.2 Testing Strategy 103
7.3 Testing Methods 104
7.4 Test Cases 105
8.0 User Manual 115
9.0 Limitation and Future Enhancement 132
10.0 Conclusion and Discussion 136

10.1 Conclusions and Future Enhancement 136
10.2 Discussion 136
10.2.1 Self Analysis of Project Viabilities 136
10.2.2 Problem Encountered and Possible Solutions 137
10.2.3 Summary of Project work 137
References 138
Experience 139
LIST OF FIGURES:
Fig 1.5.1 J2EE Technologies 6
Fig 1.5.2 J2EE Multi-tier Distributed Application Model 6
Fig 1.5.3 Hibernate Model 7
Fig 1.5.4 MVC Architecture 9
Fig 1.5.5 MVC 2 Architecture 11
Fig 1.5.6 MVC 2 Architecture 11
DDU (Faculty of Tech., Dept. of IT) ix

Fig 1.5.7 ITSIB SOA Using Spring and Hibernate 13
Fig 1.5.8 ITSIB flow of the process 14
Fig 2.2.2.1 Project Planning and Management Approach 18
Fig 2.2.4.1 Project Team Structure 21
Fig 2.3.1 Time Allotted to Various Activities 23
Fig 3.1.1 Typical Workflow in an organization 26
Fig 4.4.1 Navigation chart 53
Fig 4.5.1 Use Case Diagram 54
Fig 4.6.1 ER Diagram for Border Activities Details 55
Fig 4.6.2 ER Diagram for Border Activities Details 55
Fig 5.1.1 Class Diagram 58
Fig 5.1.2.1 Sequence Diagram for insert data 59
Fig 5.1.2.2 Sequence Diagram for Login 60
Fig 5.1.2.3 Sequence Diagram for Logout 60
Fig 5.1.2.4 Sequence Diagram for update data 61
Fig 5.1.2.5 Sequence Diagram for View data 62
Fig 5.1.2.6 Sequence Diagram for Report Generation 62
Fig 5.1.2.7 Sequence Diagram delete data 63
Fig 5.1.2.8 Sequence Diagram for create correspondence 64
DDU (Faculty of Tech., Dept. of IT) x

Fig 5.1.2.9 Sequence Diagram for forward correspondence 64
Fig 5.1.2.10 Sequence Diagram for approve correspondence 65
Fig 5.1.2.11 Sequence Diagram for Reject correspondence 65
Fig 5.1.3.1 Deployment Diagram 66
Fig 5.2.2.2 Table Relationship Diagram-application 76
Fig 5.2.2.1 Table Relationship Diagram-common 77
Fig 5.3.1 Input/Output and Interface Design- Main Page 78
Fig 5.3.2 Input/Output and Interface Design-Common Form 79
Fig 5.3.3 Input/Output and Interface Design-Report Form 79
Fig 5.3.1.1 State Transition Diagram to insert data 80
Fig 5.3.1.2 State Transition Diagram to update data 81
Fig 5.3.1.3 State Transition Diagram to view data 82
Fig 5.3.1.4 State Transition Diagram for correspondence 83
Fig 7.1.1 Testing Plan 102
Fig 8.1 Main Page 116
Fig 8.2 Personal Details Form 117
Fig 8.3 Address details form 118
Fig 8.4 Physical Description form 119
Fig 8.5 Contact in India details form 120
Fig 8.6 Apprehension details form 121
Fig 8.7 Criminal Antecedents details form 122
Fig 8.8 Release details form 123
Fig 8.9 Edit/Update search details form 124
Fig 8.10 Case search form 125
Fig 8.11 Location details form 126
DDU (Faculty of Tech., Dept. of IT) xi

Fig 8.12 Correspondence 127
Fig 8.13 Ongc details – Report parameter page 128
Fig 8.14 Campaign details – Report parameter page 128
Fig 8.15 Ongc details – Report Generation page 129
Fig 8.16 Campaign details – Report Generation page 130
Fig 8.17 Search Parameter 130
Fig 8.18 Advanced Search Page 131
Fig 8.19 Advanced Search Page-Results 131
Fig 9.1 Connecting District Offices 134
Fig 9.2 Search Component 135
LIST OF TABLES:
Table 2.2.3.1 Milestones and Deliverables 19
DDU (Faculty of Tech., Dept. of IT) xii

Table 3.2.1 Tools and Technology 27
Table 3.2.2 Hardware Requirement 27
Table 3.2.3 Software Requirement 28
Table 4.1 Personal Details Input

32
Table 4.2 Address Details Input 34
Table 4.3 Physical Description Input 39
Table 4.4 Contact in India Input 39
Table 4.5 Apprehension Details Input 42
Table 4.6 Criminal Antecedents Details Input

45
Table 4.7 Criminal Antecedents Details Input 40
Table 5.2.1.1 Person Table 67
Table 5.2.1.2 City Table 68
Table 5.2.1.3 Contact Table 68
Table 5.2.1.4 Country Table 68
Table 5.2.1.5 District Table 68
Table 5.2.1.6 Language Table 69
Table 5.2.1.7 Location Table 69
Table 5.2.1.8 Nationality Table 69
Table 5.2.1.9 State Table 70
Table 5.2.1.10 Occupation Table 70
Table 5.2.1.11 Taluka Table 70
Table 5.2.1.12 Village Table 70
Table 5.2.1.13 Religion Table 70

DDU (Faculty of Tech., Dept. of IT) xiii
Table 5.2.1.14 Action_Flag Table 71
Table 5.2.1.15 Service Table 71
Table 5.2.1.16 Lookup_master table 71
Table 5.2.1.17 Borderactivites_mst 72
Table 5.2.1.18 Bordercustody_dtl 73
Table 5.2.1.19 Border_release_dtl 73
Table 5.2.1.20 Border_lang_mpg 74
Table 5.2.1.21 Border_crmreg_mpg 74
Table 5.2.1.22 Border_contact_dtl 74
Table 5.2.1.23 Reports 74
Table 5.2.1.24 Reports _ parameter 75
Table 5.2.1.25 Reports _ column 75
Table 6.1.1 Prerequisites 85
Table 6.4.1 Naming Convention Table 92
Table 7.4.1 Test Case for Border Activity Details 105
Table 7.4.2 Test Case for ONGC Details – Report 113
Table 7.4.3 Test Case for Campaign Details- Report 113
Abbreviations:
GUI – Graphical User Interface

SQL – Structured Query Language
DDU (Faculty of Tech., Dept. of IT) xiv

CMM – Capability Maturity Model
J2EE – Java 2 Enterprise Edition
HTML – Hypertext Markup Language
XML – Extensible Markup Language
MVC – Model View Controller
HOD – Head of the Department
UML – Unified Modeling Language
IB – Intelligence Bureau
DDU (Faculty of Tech., Dept. of IT) xv

Introduction
1. INTRODUCTION
1.1 PROJECT DETAILS
The functions of Intelligence Bureau broadly include crime detection, crime prevention
and law and order maintenance. All these functions are interlinked to each other, which
depend on the flow of information amongst them.
Departmental hierarchy allows the reporting from bottom to top level with consolidation
of reports at each level. Instructions pass from top to bottom whereas reporting is done
from bottom to top. Crime Units are the places where crime related data is generated and
sent upwards. In the hierarchy as one goes lower, information is more in details.
The Intelligence Bureau is divided in to many sub branches. Each Sub branch gathers
information, investigates and tracks different kinds of crimes.
Currently Intelligence Bureau team works on the Past Experience faced by the senior
officers. So all the decisions are taken by IB are truly according to the Image of the
incident in the officers’ mind. The fact may be different in many cases.
This is so because they don’t have real facts of all the important incidents. They have to
read Related Files for all the incidents and they are running sort of time. Even in many
cases they don’t have related Physical files with them. Due to this they don’t have fact
data with them. So all they can do is to take decisions with the Experience.
In addition to this, there is no scheme with the help of which they can have data reports
generated automatically. This is to be done by hand which is next to impossible.
So these are the main disadvantage of the present system which is being followed by IB
currently.
Another problem is that the superior authority, seating at the head quarter, can never see
the status of the particular file unless he asks the relative local officer or he gets the
Physical file in his hand.
To overcome these problems, IB Department needs an Integrated Automation System

which connects all of the Police Stations where IB team has its representatives.
This System will gather all the data about the important incidents, organizations and
people.
DDU (Faculty of Tech., Dept. of IT) 1

Introduction
The System will generate Reports with the data it has. These reports will be very helpful
in concluding the fact from the data.
The System will be able to take place of Physical files and thus removing the paper work.
Instead of physical file, the system will send the e-file to the authorities and to other
departments when it’s necessary to forward a file in hierarchy.
1.2 PURPOSE
A study has been conducted to understand the current processes being followed by the
Intelligence Bureau, through various standard-interviewing techniques like interviews,
questionnaires, checklist, and role play with each responsible user of the functions of the
main office. The results of this study showed that the current system of management of
Intelligence Bureau requires all the forms, reports etc. to be generated manually. This
requires a lot of hard work to be done by hand and hence a lot of time is also wasted.
The purpose of this project is to propose a new system for the work related to Intelligence
Bureau. This will be the basis for the development and implementation of the
computerized system for better efficiency, effective utilization of manpower, reduced
repetitive processes and reporting systems, and above all, quicker decision making.
Requirement gathering of standard procedures, formats, forms, registers, reports and

various other documents and business processes will enable us to understand, analyze and
propose a new computerized system for better efficiency and efficacy. This will enable in
effective and better utilization of manpower, better and improved reporting framework
and processes with reduced repetitive work and faster decision making.
This project aims at computerizing the work done by the Intelligence Bureau. This
requires development of forms, procedures, reports etc. which are till now maintained
manually.
On completion of this project, the new system for the Intelligence Bureau will help it in
better manpower and cost management and also in reducing repetitive work.
1.3 SCOPE

Introduction
The purpose of this project is to mainly computerize the Intelligence Bureau Department.
Hence this project is solely for the work done by the IB. Any other department is not
covered in the scope of this project. Also the project is entirely based on user
requirements as specified by the user and hence it is not possible to add any extra features
apart from those provided by the user. Its scope is limited to the work done by the
Intelligence Bureau Department.
1.4 OBJECTIVE
The branches of Intelligence Bureau do the following activities:
• Information Gathering
• Consolidation Activities
• Forecasting (Analysis Activities)
• Record Maintenance Activities
• Reporting Activities
IB is the main coordinating authority regarding security, law and order situation with the
Centre and other states. Hence, the Head office is interlinked with information flow of all
kinds of activities and events related to political, communal, religious, elections, students,
unions, farmers, laborers, foreigners, Pakistan nationals, airport, ports and coastal areas
of the state and security related information through these various support units. Work
allocation for above activities is distributed to the branches situated at the head office of
the Intelligence Bureau.
IB has identified the provision of online and instantaneous access to information. The
proposed solution includes the following
•
Building up of Master Data for various applications
• Re-using the data across various applications thereby reducing the data-
redundancy and duplication of work.
1.5TECHNOLOGY AND LITERATURE REVIEW
• Eclipse

Introduction
To build complete enterprise level applications, developers need more than Java.
Oracle believes strongly, and has invested heavily, in the combination of Java,
SQL, and XML. Java is used for programming the business and presentation
logic, SQL for interacting with the database, and XML for passing information
between loosely coupled applications.
- As MVC Architecture was used, Java Developer Eclipse helps developers

build an enterprise level application using Java, XML, HTML, SQL, and PL/SQL
and provides various code editors and visual tools for each of these languages.
- To maximize developer productivity, Eclipse provides a comprehensive
set of integrated tools that support the complete development lifecycle, from
source control, modeling, and coding through debugging, testing, profiling, and
deploying. Eclipse simplifies J2EE development by providing wizards, editors,
visual design tools, and deployment tools to create high-quality, standard J2EE
components including applets, JavaBeans, Java Server Pages (JSP), Servlets, and
Enterprise JavaBeans (EJB).
• MySQL Query Browse
MySQL Query Browser is an Integrated Development Environment that is

specifically targeted at the development of stored program units for Oracle
Databases. Over time more and more business logic and application logic has
moved into the Oracle Server, so that MySQL Query Browser has become a
significant part of the total development process. MySQL Query Browser focuses
on ease of use, code quality and productivity, key advantages during Oracle
application development.
• Tomcat Server 5.0.28

 The Apache Software Foundation provides support for the Apache community of
open-source software projects. The Apache projects are characterized by a
collaborative, consensus based development process, an open and pragmatic
software license, and a desire to create high quality software that leads the way in
its field.
 Apache Tomcat is the servlet container that is used in the official Reference
Implementation for the Java Servlet and Java Server Pages technologies.
 Apache Tomcat is developed in an open and participatory environment and
released under the Apache Software License. Apache Tomcat is intended to be a
collaboration of the best-of-breed developers from around the world.

Introduction
 Apache Tomcat powers numerous large-scale, mission-critical web applications

across a diverse range of industries and organizations.
Advantages of tomcat server:
 Performance optimizations and reduced garbage collection

 Refactored application deployer, with an optional standalone deployer allowing
validation and compilation of a web application before putting it in production
 Complete server monitoring using JMX and the manager web application
 Scalability and reliability enhancements
 Improved Taglibs handling, including advanced pooling and tag plugins
 Improved platform integration, with native Windows and Unix wrappers
 Embedding using (Java Management Extension) JMX
 Enhanced Security Manager support
 Integrated session clustering
• J2EE
As J2EE is a combination of several technologies that offer cohesiveness to bond

together server side systems and services and produce an industrial-strength
scalable environment within which web-centric applications can thrive.
- J2EE simplifies the creation of an enterprise-wide application, because

functionality is encapsulated in components of J2EE.
- This enables designers and programmers to organize the application into
functionality that is distributed across the server-side components built using
J2EE.
- Moreover J2EE contains all the interfaces and libraries that is required for
handling complex programs of multithreading and synchronization.
- J2EE is a Multi-Tier Architecture (to be precise four tier architecture).
These consist of Client Tier, Web Tier, Business Tier, and Enterprise Information
Tier.

Introduction
Fig 1.5.1 J2EE Technologies
- The J2EE platform uses a multi-tiered distributed application model.

Application logic is divided into components according to function, and the
various application components that make up a J2EE application are installed on
different machines depending on the tier in the multi-tiered J2EE environment to
which the application component belongs
• Client-tier components run on the client machine.
• Web-tier components run on the J2EE server.
• Business-tier components run on the J2EE server.
• Enterprise information system (EIS)-tier software runs on the EIS server.
• Hibernate is a powerful, high performance object/relational persistence and
query service.
• Hibernate relieves the developer from 95 percent of common data persistence
related programming tasks, compared to manual coding with SQL.
• Hibernate can map entities and particular properties to SQL expressions.
Fig 1.5.2
J2EE Multi-tier Distributed Application Model
• hibernate
Below are some of the reasons as why hibernate is used extensively:-
 Natural programming model.

 No build-time byte code enhancement.
 Extreme scalability.
 The query options.
 Free/open source.

Introduction
• Hibernate Overview:
Architecture
The System follows a popular MVC-2 (Model-view-Controller) architecture. MVC

architecture calls for a visual application to be broken up into three separate parts:
A model that represents the data for the application.

The view that is the visual representation of that data.
A controller that takes user input on the view and translates that to changes in the
model.
The goal of the MVC-2 design pattern is to separate the application object
(model) from the way it is represented to the user (view) from the way in which the
user controls it (controller).
In the System, the Browser and the JSP pages comprise the View.
 The Front Servlet is the single controller for the system which identifies the
different parameters and transfers the control to the appropriate request handlers.
The Request Handlers, Business Objects and the Data Access Objects comprise
the Model part.
The Request Handlers process the business logic of the requests.
Fig 1.5.3 Hibernate Model
• Spring Framework
 Spring is
essentially a technology dedicated to enabling you to build applications using
Plain Old Java Objects (POJOs).
 It enables you to
develop components as POJOs containing only your business logic, while the

Introduction
framework takes care of the many value adds you need to build enterprise
applications — even in areas that you may not have considered when initially
authoring the application.
 This goal requires
a sophisticated framework, which conceals much complexity from the developer.
Because your business logic is abstracted from infrastructure concerns, it’s also
likely to enjoy a longer life, improving the return on investment of writing it.
 Business logic
should change at the pace of your business; only if it is abstracted from
infrastructure concerns can the impact on your code base of inevitable
infrastructure change (such as choice of application server) be minimized.
• Microsoft Visual Source Safe
Microsoft Visual Source Safe is a version control tool, basically used for proper
and efficient maintenance of the project related documents. All the documents that are
delivered by various vendors at various phases of testing are maintained through this tool.
There is a facility to provide access rights in this tool. So only the team members’
specific to project can access the documents related to their projects. No other person,
other than the team members has access rights to it.
Hence it helps managing the projects, regardless of the file type (text files,
graphics files, binary files, sound files, or video files) by saving them to a database.
When we need to share files between two or more projects, we can share them quickly
and efficiently. When we add a file to VSS, the file is backed up on the database, made
available to other people, and changes that have been made to the file are saved so we can
recover an old version at any time. Members of team can see the latest version of any file,
make changes, and save a new version in the database.
VSS project organization makes team coordination easy and intuitive for more
information on projects.
When a file (or set of files) is ready to deliver to another person, group, Web site,
or any other location, VSS makes it easy to share and secure different versions of the
selected set of files.
Before adding files to the VSS database, there should be a project to place the
files in. When working with VSS, the first thing to do is create one or more projects.
After the project has been created, files or folders can be added to the VSS database
• Coding Architecture
MVC architecture calls for a visual application to be broken up into three separate
parts:

Introduction
• A model that represents the data for the application.

• The view that is the visual representation of that data.
• A controller that takes user input on the view and translates that to
changes in the model.
Fig 1.5.4 MVC Architecture
The solution architecture has three layers:
1) Presentation layer:
This layer enables navigation, manipulation and translation onto the users' desktops.
2) Application layer:
This layer consists of an application server and a web server, both handled by the J2EE
application, and a mail server for messaging and workflow in order to provide a
collaborative environment.
3) Data layer:
This layer consists of structured data in the Oracle RDBMS, and unstructured documents
and textual information in J2EE application.
The MVC architecture has the following benefits:

Introduction
1) Multiple views using the same model:
The separation of model and view allows multiple views to use the same enterprise
model. Consequently, an enterprise application's model components are easier to
implement, test, and maintain, since all access to the model goes through these
components.
2) Easier support for new types of clients:
To support a new type of client, you simply write a view and controller for it and wire
them into the existing enterprise model.
3) Clarity of design:
By glancing at the model's public method list, it should be easy to understand how to
control the model's behavior. When designing the application, this trait makes the entire
program easier to implement and maintain.
4) Efficient modularity:
Modularity of the design allows any of the components to be swapped in and out as the
user or programmer desires - even the model! Changes to one aspect of the program
aren't coupled to other aspects, eliminating many nasty debugging situations. Also,
development of the various components can progress in parallel, once the interface
between the components is clearly defined.
5) Ease of growth:
Controllers and views can grow as the model grows; and older versions of the views
and controllers can still be used as long as a common interface is maintained.
6) Distributable:
With a couple of proxies one can easily distribute any MVC application by only altering
the startup method of the application.

Introduction
Fig 1.5.5 MVC 2 Architecture
Fig 1.5.6 MVC 2 Architecture

• MVC 2 Architecture.
JSP pages in a Model 1 application that use scripting elements, custom tags, or JavaScript
to forward requests should be re-factored to Model 2.
Model 1 architecture is best when the page navigation is simple and fixed, and when a
simple directory structure can represent the structure of the pages in the application. Such
applications usually embed the page flow information in the links between the pages. The

Introduction
presence of forward in a JSP page implies that logic embedded in the page is making a
decision about the next page to display.
Over time, as the application grows and changes, page flow logic accumulates. The
application becomes difficult to maintain because the page flow logic is distributed across
multiple pages. The best time to switch from Model 1 to Model 2 is before this
maintenance problem arises. This is why it's usually best to choose Model 2 from the
outset, basing the application on an existing Web controller framework that best meets
application requirements. Model 1 remains a viable option for simple, static applications.
To build complete enterprise level applications, developers need more than Java. Oracle
believes strongly, and has invested heavily, in the combination of Java, SQL, and XML.
Java is used for programming the business and presentation logic, SQL for interacting
with the database, and XML for passing information between loosely coupled
Applications.
As MVC model 2 Architecture was used, XML, HTML and SQL provide various code
editors.
Also, AJAX, and Hibernate were used in some common functionalities of the project.
Three things are required for the execution of a new service:
• DAO
• Service
• Value Object(VO)
DAO:
• In DAO an interface is made in which all the methods will be declared.

• DAOImpl is created which is an implementation of the declared interface, in
which all the methods that are declared in DAO are present.
• The HQL query is made in this implementation file only.
Service:
• In service, an instance of DAOImpl is made with the help of which the

appropriate method of DAOImpl is called.
Value Object:
• The Value Object has a map which contains the mapping between the values
that come from JSP page and the values are forwarded to the service.

Introduction
Execution of a New Service:
• Initially the JSP page will set the action flag and it will transfer the control to
the Controller.
• If action flag refers to a method of service then the Controller will fetch the
data related to that action flag from the database and will call the VOGEN or Service
based on sequence of execution.
• The service will call the DAOImpl associated with that service and in turn
DAOImpl will call the ValueObject which in turn refers to the appropriate table of the
database.
• In reverse order when data is retrieved from the database, VO will return the
data to the DAOImpl which in turn will pass the data to the service which will pass
the data to the appropriate JSP Page.
• All the data which is to be passed from one file to another should be passed in
Map only.
• For captions in the jsp file, a properties file is created, which contains all the
captions present in the jsp file. Separate properties file is created for each language.
Each properties file has the actual caption in that particular language, stored against a
common caption id.
IITSIB SOA using Spring and Hibernate

Introduction
Fig 1.5.7 ITSIB SOA Using Spring and Hibernate
Fig 1.5.8 ITSIB flow of the process

Project Management
2. PROJECT MANAGEMENT
2.1 FEASIBILITY STUDY
• Does the system contribute to the overall objectives of the organization?
This system would contribute to the overall objectives of the organization as

under
 Create an Office Automation System

 Enhance Productivity
 Enable Prioritization of work.
 Use IT as an enabler to help in daily work
 Design an efficient workplace
 Enable Business Rules based Processing
 Access Controls at all levels.
 Efficient & Transparent administration
 Generation of Report
 Generation of Standard Reports
 Analyzing and monitoring of data
• Can the system be implemented using the current technology and

within the given cost and schedule constraints?
The part of the system can be implemented using the current technology although
some modifications have to be done at various places. Some alterations with the
prototypes and functionalities would be done in order to work out the cost
constraints and to cope with the scheduling constraints.
• Can the system be integrated with other systems which are already in
place?
Intelligence Bureau provides Document management, Workflow, Collaboration

environment and Knowledge Management in an integrated fashion and delivers as
Electronic Workplace that will result in productivity improvement in an
Organization. Hence, this Application can be integrated with other systems which
are already in place.

Project Management
Various types of Feasibility study are identified as under:
2.1.1 Technical Feasibility
The technical Feasibility test involves questions like

• Is the current Computer’s configuration adequate for Usage?
• Is the selected technique sufficient for future enhancements?
• Is the skill set available with proper manpower for development and
maintenance?
Also as this system is going to be used by a large organization, it is likely to deal with
a large number of data. Security of data is also another important requirement. So,
Oracle 10g is more suitable at back-end.
2.1.2 Operational Feasibility
The users of the client organization should be able to operate the software easily, for
whom the software is developed, to gain the advantages of the software. This
demands good user interface. During the software development process prototypes of
the application are developed initially and are shown to client, so the client can give
some additional changes as per their requirements in the operating software. As the
software is developed and modified as per the comments of the users, there is very
little possibility that there will be resistance from end users.
Users may not be highly adept at the technical aspect of computer skills so will
required some training sessions. After that they are expected to be familiarized with
the application. System has been developed considering user characteristics to make it
user-friendly.
2.1.3 Economic Feasibility
The questions put forward in economic feasibility are:
• Are there sufficient cost benefits in creating the system?

• Are the costs of implementation of current system so great that the task of
project development is required?

Project Management
This feasibility study measures the cost effectiveness of project. It takes into
consideration cost and benefit.
• Hardware-Software Cost
This feasibility is of paramount importance in development of any software for

any particular company. TCS is having license versions of software required for
the development of Intelligence Bureau. (PLSQL Developer, Microsoft Visual
SourceSafe, Oracle 10g). Hardware cost includes the cost of the four servers
required for running the application.
• Maintenance Cost
This includes application and database maintenance cost.
Conclusion: It is economically feasible to develop and implement Intelligence

Bureau.
2.2 PROJECT PLANNING
2.2.1 Project Development Approach and Justification
The Requirements provided by the users are converted into Users Requirement
Specification as described above. The URS documents are then revised, validated,
authorized and approved by the users. The development commences after the approval
phase i.e. after the signing off of the URS documents. Thus, the URS is concerned to be
the most important document from user and developer prospective. The Developer will
try to adhere to the requirements specified in the URS documents in order to develop the
required application.
2.2.2 Project Plan
TCS has a very long-standing relationship at client side, having logged over 4,500
people. It has provided its expertise to various agencies all over the world, working with
numerous hardware and software technologies, to improve its overall image and provide
better services to its constituents. TCS will bring its vast domain expertise, knowledge of
the best practices and lessons learnt in various implementations at client side to this
project. For this specific requirement analysis, TCS consultants with the help of
designated personnel from CLIENT would familiarize themselves with the overall
Project Management
structure of the office and it’s inter-linkages with other departments/systems. They will
understand the broad working of the office and the other related departments, its
functions, manpower employed, processes etc.
TCS consultants shall meet the representative personnel and document the detailed gaps
between the current system and the proposed solution based on the understanding of the
activities and processes, as they are currently being carried out in the office.
The gaps would be documented and analyzed, and if required and possible reengineering
of process in concurrence with CLIENT to leverage the benefits of the product would be
suggested.
Other areas, which would be considered during the planning and analysis, would be:
• Ensure that the information flow is process driven.

• Reduce the manual efforts to the maximum extent for all activities.
• Ensure on-line validation and feedback of data.
• Act as an effective tool in decision support.
• Provide audit control check points.
Fig 2.2.2.1 Project Planning and Management Approach
Internal Training

Project Management
TCS will conduct necessary training for the TCS’ project team to carry out the
proposed project. This will be in addition to the regular extensive training
program that is conducted by TCS for its staff and trainees.
2.2.3 Milestones and Deliverables
Milestones are identified in order to complete the entire project in the time
duration. Milestones are identified for every module of Integrated Workflow Document
Management System.
Table 2.2.3.1 Milestones and Deliverables
PHASE DELIVERABLES PURPOSE
System • Requirement Gathering and It gives exact

Requirement and analysis. understanding of the
Analysis • Functional Specifications user’s requirements.
Non Functional Specifications
System Design • E-R Diagram It gives the logical
• Database Design structure that describes the
• Class diagram system.
• Sequence Diagram
• Use Case Diagram
• Form layouts
Implementation The output obtained for the required It gives the required
and Testing functionality after implementing and module
doing various types of testing
2.2.4 Roles and Responsibilities
TCS proposes the following Project Management structure for the successful
development/customization, implementation and maintenance of the Intelligence
Bureau system.
The following is the recommended Project Management structure for the execution of
the project.
Project Team Structure

Project Management
TCS proposes the following team structure for the successful implementation of
the project. The TCS team will be headed by a Project Manager and will be supported
by Project Leaders/Module Leaders and Team Members and Trainees.
TCS proposes a multi-disciplinary team for the project. TCS would draw in
knowledge from its pool of resources with expertise ranging from business domain to
the systems administration, systems architect, and Networking and Internet
technology. These experts will act as consultants to the TCS Intelligence Bureau
project team. Other enabling groups within TCS such as Quality Assurance,
Manpower Allocation Task Committee, Operations and Training have important role
in the successful execution of the project.
• Project Manager
The responsibilities of the Project Manager are:
 Overall management and functioning of the Intelligence Bureau project

 Project Planning
 Monitoring the progress & status of the project on a regular basis
 Managing the TCS-CLIENT project resources and resource allocation
 Managing the flow of work
 Co-ordinate with Project Manager (PM for Intelligence Bureau) of
CLIENT for acceptance for various deliverables
 Co-ordinate with Project Manager (PM for Intelligence Bureau) of
CLIENT for the approvals required at various stages of the project,
including signing off of the gap analysis document, Acceptance of the
product/solution etc.
 Change Management: Identifying and evaluating the changes to the scope
and content of work during the project, which may impact the original
budget and schedule.
 Reporting status on a Monthly basis to Project Manager (PM for
Intelligence Bureau) of CLIENT and TCS Management
 Ensuring the quality of the deliverables
• Project Leader
The responsibilities of the Project Leader are:
 Planning the application customization/development work in the

Intelligence Bureau Project.
 Monitoring the day-to-day status of application
development/customization activities in the Intelligence Bureau project.

Project Management
 Planning and scheduling of enhancement to Intelligence Bureau system in

co-ordination with Project Manager (CLIENT) and Project Manager
(TCS).
 Liaison with various Intelligence Bureau functionality champions and
Project Manager (PM for Intelligence Bureau) of CLIENT, for the gap
analysis study.
 Ensuring the quality of the deliverables.
 Obtain clarifications necessary from the Project Management team
regarding Functionality, GUI design etc over telephone (teleconference) or
e-mail.
 Manage the flow of work within his/her team and allocate work to team
members.
 Monitor the Quality of the deliverables being created.
 Change Management: Maintain a clarification document and ensure that
any change or clarification is reflected in the design documents.
 Reporting status to the Project Manager on a weekly basis.
Fig 2.2.4.1 Project Team Structure
• Module Leader
The responsibilities of a Module Leader include:
 Responsible for the work related to his/her group

 Allocate work to his module members
 Participate in Gap Analysis, Creation of SRS, Creation of the Design
Document and provide required support to the project team in the
development of the system
 Co-ordinate testing

Project Management
 Perform Defect analysis and take corrective actions

 Ensure all the documentation with respect to the module is complete and
up to date
 Change Management
 Report on a weekly basis the status of the module to the Project leader
• Team member
The responsibilities of a team member include:
 Carrying out the work allocated

 Report on a weekly basis to Module Leader
2.2.5 Group Dependencies
Module Leaders will report the progress of work in their respective modules to
the Project Leader on a weekly basis. The Project Leaders will in turn submit
weekly status reports to the concerned Project Managers. The status report will
contain:
 Activities completed since last report

 Activities planned until the next report
 Progress against plan
 Deliverables to CLIENT since last report
 Deliverables due to CLIENT in the next reporting period
 Outstanding issues
The Project Manager will monitor the progress of the activities against the plan
and prepare a consolidated Monthly Report to Project Manager (PM) of CLIENT.
This report will cover the project status and deviations against plan.

Project Management
2.3 PROJECT SCHEDULING
2.3.1 Time Allotted to Various Activities
D e2c0 0 8 J a 2n 0 0 9 F e 2b 0 0 9 M a2 r0 0 9
ID T a sk N a m e S ta r t F in is h D u r a t io n
2 1/1 22 8/1 2 4/1 1 1/1 1 8/1 2 5/1 1/2 8/2 1 5/2 2 2/2 1/3 8/3 1 5/3 2 2/3 2 9/3
1 U n d e r s t a n d in g o f t h e 1 p/21r /5o2 je0 0c 8t 1 /21 /92 0 0 8 1w
2 S t u d y o f t h e F r a m e w 1o /2r2 k/22 0 0 8 1 /22 /62 0 0 8 1w
S tu d y o f th e u s e r a n d s y s te m
3 1 /22 /92 0 0 8 1/2/2 0 0 9 1w
R e q u ir e m e n t s
4 S y s t e m A& Dn ae lys igs isn in g 1/5/2 0 0 9 1/2 /02 0 0 9 2w
5 C o d in g o f t h e A p p lic a 1/1
t io /9n2 0 0 9 2/2 /72 0 0 9 6w
6 T e s t in g 3/2/2 0 0 9 3/6/2 0 0 9 1w
7 B u g r e s o lu t io n 3/9/2 0 0 9 3/2 /72 0 0 9 3w
8 F in a l t e s t in g 3/3 /02 0 0 9 4/3/2 0 0 9 1w
Fig 2.3.1 Time Allotted to Various Activities

System Requirement Study
3. SYSTEM REQUIREMENT STUDY
After initial discussions with the HR head and preliminary investigation, the requirement
study of the project was done. A pre-Requirement of investigation was prepared which
revealed the exact amount of efforts required in people-person months, the cost that
would be incurred, the risks and the mitigating factors.
Different parameters were taken into consideration while considering the cost factor
incurred in the project:
Consultancy cost: This cost is based on the staffing of the project and its location.
Hardware cost: This cost is based on the cost incurred on the hardware utilized per
person month like computer, tapes etc.
Software cost: This cost includes the cost incurred on the licensing of tools and software
used in the project e.g. Oracle, Microsoft Office etc.
Systems analysis & requirements definition
After doing a preliminary investigation the following functional and non-functional

requirements were found and a SRS (System Requirements Specification) was prepared.
Based on the SRS we decided to follow the Evolutionary prototyping model for our
system development.
A software process model is a simplified description/abstract representation of a software

process which is presented from a particular perspective. A process model for software
engineering is chosen based on the nature of the project and application, the methods and
tools to be used, and the controls and deliverables that are required.
All software development can be characterized as a problem solving loop in which four
distinct stages are encountered:
• Status quo
• Problem definition
• Technical development
• Solution integration
 Status Quo represents the current state of affairs.
 Problem Definition identifies the specific problem to be solved.
 Technical Development solves the problem through the
application of some technology.

 Solution Integration delivers the results (e.g. documents,

programs, data, and new product) to those who requested the
solution in the first place.
3.1 STUDY OF CURRENT SYSTEM
The current system is completely manual operations oriented. The system in

government sector at this stage of time involves lot human resources to maintain
the functional working.
The present system has certain major disadvantages. A few to be listed can be
excessive paperwork, time consuming process flow, laborious work environment
for employees, difficulty to access historical data and all these problems lead to
inefficient working of government sector causing dissatisfaction in the general
public.
The system being developed has the main objective of automation and
computerization a lot of tasks being carried out so basically there is a huge
amount of historical data that will be finally fed into the system that will be
developed. Our module was concerned with the customized system development
for the Intelligence bureau employees.
3.2 PROBLEMS AND WEAKNESSES OF CURRENT SYSTEM
• The present system has certain major disadvantages. A few to be listed can be
excessive paperwork, time consuming process flow, laborious work environment
for employees, difficulty to access historical data and all these problems lead to
inefficient working of government sector causing dissatisfaction in the general
public.
• Apart from the above stated problems there is lack of transparency in the existing
system. This being one of the major drawbacks in the system needs special
attention.
• The problem stated above have certain deep rooted problems like time consuming
process flow for which the government may need to change the structure of the
process flow in certain cases so that the system output can become faster.
• The following listed are the problems or weaknesses of the current system:
 Information is scattered among the various branches.
 There is no synchronization between the different HOD’s.
 Searching & tracking is difficult.

 Manual entry of the same has to be done in multiple registers

 Searching related precedents is very difficult
 Overall an inefficient system
 So much manpower is consumed in handling existing system
 So much time consume in preparing registers which is having replicated data
 It is difficult to prepare report for decision making.
3.3 USER CHARACTERISTICS
The majority of the functionality performed by the staff in the organization involves a
flow of information along predefined hierarchy of users. The flow consists of information
along with hierarchy or outside the system. It involves reviewing, commenting and
approving along various officers in the hierarchy like Level 0 Officer, Level 1 Officer,
Level 2 Officer, Level 3 Officer, Level 4 Officer, Level 5 Officer, Level 6 Officer and
Level 7 Officer.
START
Accept Request
LEVEL-1 EMPLOYEE
Create the case
Approved Case
LEVEL-2 EMLOYEE LEVEL-3 EMPLOYEE
To collect relevant Information /
Send back for Correction. Send for approval
Send for approval
Approved Case
Send for approval
Approved Case CIRCULATING BETW EEN
ASST. LEVEL-2 LEVEL- 4 TO 6
EMPLOYEE
Approved Case Send for approval
END
HIGHEST LEVEL
EMPLOYEE
Fig 3.1.1 Typical Workflow in an organization

3.4 HARDWARE AND SOFTWARE REQUIREMENTS

Table 3.4.1 Tools and Technology
Development technologies Java , J2EE , Hibernate , Spring MVC2 Architecture

Development tools Eclipse
Application server Apache Tomcat 5.0
Database MySQL
Operating system Windows XP Profession Edition, Windows Vista Enterprise
Edition
Web browser Internet Explorer 6.0 and above
Hardware P-IV 2.4, 1 GB RAM, 80 GB HDD
Hardware Requirements
Table 3.4.2 Hardware Requirement
Client Configuration
 Pentium IV, 750 MHz, 20GB HDD

 Operating System: Windows XP/2000
 RAM: 256 MB minimum
 400MB Minimum Free Space on Drive
 Microsoft Office
Server Configuration
2 Servers, each with following configuration
 2 CPU
 Operating System: WinNT
 RAM: 512MB Minimum
 40GB Minimum Free Space on Drive
 750MHz
One Server with Oracle 10g Application Server
Other Server with Oracle 10g Database Server
Software Requirements

Table 3.4.3 Software Requirement
System Software
Oracle 10g Application Server

Oracle 10g Database Server
Oracle 9iAs JDeveloper
Microsoft Office
Adobe Acrobat Reader
3.5 CONSTRAINTS
3.2.1 Hardware Limitations
• There is no hardware limitations to the system as such because once the complete
system is developed after integration of modules exclusive care would be taken
that at the site of deployment of the web portal necessary hardware requirements
are pre-requisitely met.
• There is no hardware configuration heterogeneity in this case of the module or
the complete system being developed.
3.2.2 Interface to Other Application
• The system we are going to develop should integrate to already existing

applications too. The module thus developed will be integrated into the apex
system i.e. web portal.
• There are no cases of problems of integration with an external system because the
system designed is very compact in architecture in spite of the voluminous
amount of modules it comprises. Thus only constraint is the interface
compatibility within the system.
3.2.3 Higher Order Language Requirement
• There aren’t any high order language requirements that can be considered as a
constraint. All such language requirements are accurately met in such elite
technical organizations.

3.2.4 Reliability Requirements
• Reliability requirements of the system are one of the prime ones in the list.
The system needed to be highly reliable in terms of performance but at this stage
where the complete system is far from completion we cannot gauge its reliability
all we could do is to make the individual module we have developed to be as
reliable as possible.
3.2.5 Safety And Security Considerations
• Safety and security too are other major concerns of any client. In this case too
there are certain issues related to the security and safety of the system but as
mentioned earlier this stage is not about those concerns.
• Actually another team of experts in security features will provide necessary
standards of security and safety at later stage when the system would have got
into shape after the integration of individual modules.
3.2.6 Criticality of Applications
• Criticality of the module was one of the concerned constraints. The system
was being developed for the users who were mainly employees of the government
sector. They had certain rigid aspects which were to be taken care during
development. Any change in pattern of their workflow would lead to extremely
critical conditions. Thus this was a matter of concern and served as one of the
deep rooted constraints.
3.6 ASSUMPTIONS AND DEPENDENCIES
• There were very few assumptions made while developing this module of the
system i.e. HDIITS (all modules). They can be listed as below:
a) The users would be well familiar with computer basics.

b) Certain technical aspects related to the workflow of government
processes like file transfer and other such details that were not clearly states in
requirements were assumed.
c) Another assumption was that the roles of specific posts in positional
hierarchies of the offices were well defined and clear.

• There are internal dependencies on different modules of the system HDIITS.

For example the license division module in certain specific cases is dependent on
Traffic module and a few others.
• The development phase of the HDIITS - Traffic is dependent on the

information and resources provided by the government employees so we depend
on their valuable inputs at all stages.
• The system has a large number of minute specifications which need to be

clarified at the stages of development as they are encountered so one needs to
make sure that they co-operate at all stages to the development of effective
system.
• Other than these there are no external dependencies which can cause any
hampering to the system development.

System Analysis
4. SYSTEM ANALYSIS
4.1 REQUIREMENTS OF NEW SYSTEM
Study has been conducted to understand the current processes being followed by
the Crime Branch. The study has been conducted through various standard-
interviewing techniques like interviews, questionnaires, checklist, and role play
with each responsible user of the functions of the main office.
Requirement gathering of standard procedures, formats, registers and reports of

the current business processes will enable us to analyze and propose a new
system. This will be the basis for the development and implementation of the
computerized system for better efficiency, effective utilization of manpower,
reduce repetitive processes and reporting systems, quicker decision making to
improved law and order situation of the state.
4.1.1 User Requirements
Border Activity Details
Overview of Application
Application captures detailed information of the Border activities in Gujarat. These

include Infiltration, Spying, Espionage and Terrorist Activities. Application covers the
Personal Details of the person, Address and Contact Details, Property Seizure Details,
Criminal Antecedents, Deportation/ Repatriation Details, Release Details etc.
The user shall login to the system and go to Border Activity Details Application and fill
the details. Once he clicks “Submit” button these are saved in the system.
Process Flow Description

This functionality covers the following process flow:

System Analysis
• Border activities Details information are gathered from respective regions of

personality and information is sent to respective branch of ib head quarters
• Branch AIO or IO enter the Border activities Details received from region offices
in the prescribed format
• Border activities Details Infiltration, Spying, Espionage and Terrorist Activities.
Application covers the Personal Details of the person, Address and Contact
Details, Property Seizure Details, Criminal Antecedents, Deportation/
Repatriation Details, Release Details are entered into application
• Once the information are entered in the prescribed format data is saved ‘
• As and when required reports are generated from the data saved for analysis and
forecasting
1.1. Personal Details

This functionality covers Personal details of the person
Table 4.1 Personal Details Input

Sr Field Name Description M/O/C/D Remarks
.
No
Personal Details
1. Crime is Whether the M Radio Button to select India or
committed in? crime is country to which he belongs
committed in
India or the
country to
which the
person belongs
2. Type/Category Type/Category M List Box. Values can be Infiltration,

Fisherman, Espionage, Person
apprehended for notified/
/Restricted/Prohibited/Border/Defence
area, person associated with
ISI/Espionage/Terrorist activity.
3. First Name First Name of M Text Box

the person
4. Father/Husband Father/Husband M Text Box

Name Name of the
person
5. Surname Surname of the M Text Box

person

System Analysis

.
No
6. Age Age of the M Text Box
person
7. Sex Sex of the M List Box. Values can be Male or

person Female
8. Photo Photo of the O Text Box

person
9. Religion Religion of the M List Box. Values can be Hindu,

person Muslim, Sikh etc.
10. Caste Caste of the M List Box. Values can be Brahmin,

person Jain, Others etc.
11. Sub Caste Sub Caste of O Text Box

the person
12. Whether If Nationality M Radio Button to select Yes or No

Nationality of the person is
confirmed? confirmed or
not
13. Nationality Name of the M List Box. Values can be Indian,

country to American, Australian, Pakistani etc.
which the
person belongs.
14. Date of Birth Date of Birth of M Date Field

the person
15. Place of Birth Place of Birth M Text Box

of the person
16. Material Status Material Status M List Box. Values can be Married or
of the person Unmarried
17. Occupation Occupation of O Text Box

the person
18. Educational Educational O Multi Line Text Box

Qualification Qualification of
the person
Document Found
19. Type of Type of M List Box Values can be Passport,

System Analysis

.
No
Document Document CDC, Seamen Card, etc.
found with that
person
20. Document No. Document No. M Text Box
21. Date of issue Date of issue M Date Field
22. Valid Up to Valid Up to M Date Field
23. Place Place M Multi Line Text Box
If “Fisherman” is selected in type/category of Personal Details
24. Type of Type of C List box. Values can be Indian

Fisherman Fisherman Fisherman apprehended by PAK
marine security agencies, Pakistan/
Other foreign fisherman apprehended
by Indian security agencies
25. Name of Boat Name of boat C Text box
26. Name of Boat Name of Boat C Text box

owner owner
27. Registration Registration C Text Box

No. of Boat number of boat
28. Type of Type of boat C List Box. Values can be Fisherman,

Boat/vessels Country craft, Hobbies
1.2. Address Details

This functionality covers Address details of the person. Details like Present address,
Permanent address, Contact details etc. are captured.
Table 4.2 Address Details Input

Sr. Field Name Description M/O/C/D Remarks
No
Address Details

System Analysis

No
Present Address
1. Address Whether the person M Radio button to

belongs to City/town select City/town
or in the village or Village
If “City/town” is selected
2. House Name/No Number or name the O Text Box for

house entering the
name or number
of house
3. Society/building Name of society or O Text Box for

name building for the house entering the
name or number name of the
society or
building
4. Street Name of the Street for O Text Box for

the society or the entering the
building Street name
5. Area Name of the Area O Text Box for

entering the
Area
6. City Name of the city C Combo Box for

selecting the
City
7. Other Details Other Details(if any) O Text Box for

entering the
other details
8. Important Land Important Land O Combo Box for

Mark Mark(if any) selecting the
Land Mark
9. Pin code Pin code for the area O Text Box for
entering the pin
code
If “Village” is selected

house entering the

System Analysis

No
name or number
of house
11. Faliyu Name of the “Faliyu” O Combo Box for

selecting the
Faliyu
12. Village Name of the village M Combo Box for

selecting the
Village
13. Taluka Name of the Taluka M Combo Box for

for the Village selecting the
Taluka
14. District Name of the district M Combo Box for

selecting the
District

entering the
other details

Land Mark
entering the pin
code
Contact Details
18. Telephone No(O) Office Telephone No O Text Box

of the person
19. Telephone No(R) Residence Telephone O Text Box

No of the person
20. Mobile No Mobile No of the O Text Box

person
21. E-mail E-mail Id of the O Text Box

person

System Analysis

No
Permanent Address
22. Address Whether the person M Radio button to

belongs to City/town select City/town
or in the village or Village

house entering the
name or number
of house

society or
building


entering the
Area
27. City Name of the city M Combo Box for

selecting the
City

entering the
other details

Land Mark
30. Pin code Pin code for the area O Text Box

house entering the
name or number

System Analysis

No
of house

selecting the
Faliyu

selecting the
Village

Taluka

selecting the
District

entering the
other details

Land Mark
entering the pin
code
Contact Details

of the person

No of the person

person

person

System Analysis
1.3. Physical Description

This functionality covers details about Physical description of the person. Details like
height, weight built and body mark etc. is captured.
Table 4.3 Physical Description Input

No
Physical Description
1. Height Height of the person O Text Box
2. Weight Weight of the person O Text Box
3. Built Built O Text Box
4. Mark on Body Mark on Body O Text Box
5. Other details Other details Multi line text

area for entering
other details
1.4. Contacts in India

This functionality covers Contact details of the person in India.
Table 4.4 Contact in India Input

No
Contact In India
1. First Name First Name of the M Text Box
person
2. Father/Husband Father/Husband Name M Text Box

Name of the person
3. Surname Surname of the person M Text Box
6. Type of Relationship Type of Relationship M List Box
7. Address Whether the person O Radio button to

belongs to City/town select Inside
or in the village Gujarat or
Outside Gujarat

System Analysis

No
If “Inside Gujarat” is selected

house entering the
name or number
of house

society or
building


entering the
Area
12. City Name of the city M Combo Box for

selecting the
City

entering the
other details

Land Mark
entering the pin
code

house entering the
name or number
of house

System Analysis

No
selecting the
Faliyu

selecting the
Village

Taluka

selecting the
District

entering the
other details

Land Mark
entering the pin
code
If “Outside Gujarat” is selected
24. Details Details O Multi Line Text

Box for entering
details
Contact Details

of the person

No of the person

person

System Analysis

No
person
1.5. Apprehension Details

This functionality covers Apprehension details of the person. Details like Date and Time
of Apprehension, Apprehension by, Place, Name of Apprehension agency and custody
details etc. are captured.
Table 4.5 Apprehension Details Input

No
Apprehension Details
1. Date of Date of Apprehension M Date Field
Apprehension
2. Time of Time of Apprehension Text Box

Apprehension
3. Apprehension By Apprehension By M List Box Values

can be Local
Police, State
Police, etc.
4. Place of Place of Apprehension M Text Box

Apprehension
5. Name of Name of M Text Box

Apprehensive Apprehensive Agency
Agency
6. During Detention During Detention M Radio Button to

whether any whether any select Yes or No
information asked information asked
about Indian security about Indian security
agencies or Indian agencies or Indian
Geography Geography
If “Yes” is selected

for entering
details
8. Whether any price Whether any price M Radio Button to

System Analysis

No
offered by Pakistan offered by Pakistan select Yes or No
Marine Marine Agency/
Agency/Military/Jail/ Military/Jail/ ISI/ Any
ISI/ Any Terrorist Terrorist group to
group to become become informer for
informer for them them
If “Yes” is selected

for entering
details.
Custody Details
10. Date of Custody Date of Custody M Date Field
11. Time of Custody Time of Custody M Text Box
12. Place of Custody Place of Custody M Text Box
13. Date of Handing Date of Handing over M Date Field

over to police to police
14. Details of handing Details of handing M Multi Line Text

over to police over to police Box
15. Motive for Motive for Infiltration O Text Box

Infiltration
If “Infiltration” is selected in type/category of Personal Details
Route for Infiltration
16. By Route of the C List box. Values

Infiltration can be By Road,
By Air, By Sea
17. Description Brief Description if C Multi Line Text

any Box
18. Hidden places and Hidden places and C Text box

route route of Infiltration
If “Fisherman” is selected in type/category of Personal Details

System Analysis

No
19. Trace from Indian Indian sea territory C Text Box
sea territory
20. Illegal entry by sea Illegal entry by sea C Text Box

routes routes
If “Person apprehended for Notified area / Restricted area / Prohibited area

/ Border area / Defence area” is selected
21. Medical Opinion Medical Opinion C Text Box
22. Restriction Centre Restriction Centre C Multi Line Text

Details Details Box
23. Whether suffering Whether suffering C Radio Button to

from mental disorder from mental disorder select Yes or No
If “yes” is selected
24. Details Details C Multi Line Text
1.6. Criminal Antecedents

This functionality covers details of Criminal Antecedents. Details like District, Police
station, FIR No, Date, Brief description of FIR etc. are captured.

No
Criminal Antecedents
1. District District M List Box to
select the
District
2. Police Station Police Station M List Box to

select the Police
Station
3. FIR No FIR Number M Text Box
4. Date Date M Date Field
5. Brief Description of Brief Description of M Multi Line Text

FIR FIR Box for entering

System Analysis

No
the brief
description of
FIR
1.7. Release Details

This functionality covers details of Release of the fisherman if any captured.

No
Release Details
1. Date of Release Date of Release of the M Date Field
person
2. Time Time of release M Text Box
3. Whether release with If release with boat M Radio Button to

boat? select Yes or No
ONGC Security Details

Introduction
The application accounts for storing the details of the security of the ONGC units.
Functionalities of this module are:
• Basic Details
• Security Details
• Oil Theft Details
Sr. No Field Name

1. Unit Name Input
2. Location parameters
3. Name of the Oil field
4. Name of the Pumping station
5. Name of the village pipeline passing through
DDU (Faculty of Tech.,
6. Dept.
whether of IT)provided by agency
security 45
7. whether declared prohibited
8. Mode of oil theft
9. Full name of suspect
System Analysis
Output
Basic Details
Unit Location Nearest Name No. Name of Oil sent Oil sent Name Nearest
Name Police of Oil of the to the from the of the police
Station Field Oil Pumping pumping pumping village station
Field Station station station pipeline
from to passing
to
1 2 3 4 5 6 7 8 9 10
Basic Details Security Details

Distance Other Whether Security Whether Designation Strength Whether Declared
of details any provided armed declared by
pipeline security by prohibited whom
between provided agency
two
villages
11 12 13 14 15 16 17 18 19
Security Details
Order Order From If not Whether If sent outward pending If not
No Date Date declared proposal outward date at office sent then
prohibited, sent or no. reason
then not
reason

System Analysis
20 21 22 23 24 25 26 27 28
Oil Theft Details

If FIR registered, Details of Suspect
Mode Whether FIR Date Police District First Father/Husband's Surname Suspect
of FIR No. of Station Name Name Address
Theft registered FIR
29 30 31 32 33 34 35 36 37 38
Campaign Details
Introduction
The application accounts for storing and maintenance of details of Campaign of
the Nominee Candidate and generation of Campaign Details reports.
Functionalities of this module are:
• Candidate Details
• Other Details
Input Parameters
Sr. No Field Name

1. Candidate Name
2. Date
3. District
4. Start Time
5. End Time
6. Party Leader
7. Name of Organization
8. Name of important Campaigner
9. Type of Campaign
10. Incharge Name
Output
Candidate Details
House Candidate Date District Place Start End Party Name of
Field
Name/No. Name Time Time Leader Organization
name
1 2 3 4 5 6 7 8 9

System Analysis
Candidate Details
Name of Type of No. of No. of Place Evens Male Female Total Male(If
important Campaign Vehicles Participants(if Crowd Crowd “Public
Campaigner Rally Meeting”
Selected) is
selected)
10 11 12 13 14 15 16 17 18 19
Candidate Details Other Details

Female(If Total(If Public Speech Issues/Promises/ Audio Opposition Law and
“Public “Public Response Details Manifestos video party order
Meeting” Meeting”is given recording Demo arrangement
is selected) done problems
selected)
20 21 22 23 24 25 26 27
Other Details
Security Whether District(If Police FIR Date Brief Incharge Address
arrangement crime Yes Station No(If Description Name
for VIP registered Selected) (If Yes Yes of FIR
against Selected) Selected)
candidate?
28 29 30 31 32 33 34 35 36
R1: Login
Description: The Login page is displayed and user is required to enter his username and
password.
Pre Condition: Nil
Input: The user enters his username and password according to his/her designation.
Output: The home page is displayed to the user according to his designation, after
verification of password.
Processing:
Main Scenario:
1. Start the application. User prompted for login and password.
2. User gives the login and password.
3. System does authentication.

System Analysis
4. Main screen is displayed according to user’s designation.
Alternate Scenario :
4(a). Authorization fails.
4(a) 1. Prompt the user that he typed the wrong password
4(a) 2. Allow him to re-enter the password.
R2: Change Password

Description:In case the user wishes to change his old password and username
Pre Condition: User logged in
Input: Enter old password and new password
Output: Old password would be changed after verification and new password would be
saved.
Processing:
Main Scenario :
1. User initiates the password change command.
2. User is prompted for old password, new password and confirm new password.
3. User gives the old password, new password and confirm new password.
4. System does authentication.
5. New password is registered with the system.
Alternate Scenario :
4(a). Authorization fails
4(a)1. Prompt the user that he typed the wrong password
4(a)2. Allow him to re-enter the password.
4(b). New password and confirm new password do not match.
4(b)1. Allow him to re-enter the attributes.
R3: New entry of data

Description: The home page displays all the applications. The user has to select the
Investigation application and new entry functionality and then User fills the form.
.
Pre Condition: User logged in to the page of new entry in Investigation schedule
application.
R3.1: Successful entry of data

Description: User fills the form with some mandatory fields.
Input: Fill all the mandatory fields in the form.
Output: A message, saying Data Entered Successfully is displayed and home page
is displayed again.
R3.2: Entry of only some of the fields.
Description: User enters only some of the fields in the form and some mandatory
fields are left out.
Input: Some, not all, mandatory fields are entered.
Output: A message, saying Please Enter <Field name> is displayed and focus is
shifted on that field.
Processing:

System Analysis
Main Scenario:
1. User initiates the “Investigation application”.
2. System asks the user for the Letter No.
3. User enters the Letter No.
4. New Investigation schedule for entered Letter No. is created with all the
entered details & transferred to particular Investigation Officer.
Alternate Scenario:
4(a). Investigation schedule with the same Letter No exists.
4(a)1. System asks the user for a different Letter No.
4(a)2. User enters a different Letter No.
4(a)3. New Investigation schedule for entered Letter No. is created with all the
details & transferred to particular Investigation Officer
R4: Editing some data.

Description: User can edit data, which has been entered successfully.
Precondition: Data for the particular entry which user is trying to edit should be inserted.
Input: User opens the application and the record which he wishes to edit.
Output: The form for the application, with the details of the record filled up in all fields is
displayed.
R5: Successful updating of data

Description: User updates the form which he has opened for editing.
Precondition: Data for the particular entry which user is trying to update should be
opened in edit functionality mode.
Input: User changes some, all or none of the fields of the form.
Output: A message saying Updated successfully is displayed.
R6: View the existing Cases.

Pre-Condition: User logged in to the view functionality mode.
Input: User enters the CASE NO OR FIR NO. of required Investigation schedule.
Output: Show the Invertigation report for the entered CASE NO.or FIR NO and other
related information
Processing:
Main Scenario :
1. User clicks on “View ” option.
2. System asks for the CASE.No.
3. User enters the C.R.No & click on View Button.
4. .System shows the details of case for entered C.R.No.
Alternate Scenario:
4(a). Entered C.R.No. does not exist.
4(a)1. View Case functionality fails, the error message is displayed.
4(b). System asks for new C.R.No.
R7:Create correspondence.
Pre-Condition: User logged in to the new entry functionality mode.
Input: User enters at least the mandatory entries.

System Analysis
Output: Particular details saved in the INBOX of the WORKLIST.

Processing:
Main Scenario :
1. User clicks on “Create Correspondence” option.
2. Details stored in inbox of the worklist.
3. User at lower level can forward these details to higher level and viseversa.
Alternate Scenario:
4(a). System asks for mandatory fields’ entry if not done.
4(b). System shows message “Cant create correspondence” if particular
correspondence is not responded( Approved) by higher level user
R8:Forward correspondence.
Pre-Condition: Worklist is displayed on the screen.
Input: In workluist there is a created correspondence is there with update option.
Output: Particular details saved in the INBOX of the WORKLIST.
Processing:
Main Scenario :
1. User clicks on “Forward” option.
2. Details stored in inbox of the worklist.
3. User at lower level can forward these details to higher level and viseversa.
4. Details shifted to OUTBOX of the user.
Alternate Scenario:
4(a). System asks for mandatory fields’ entry if not done.
4(b). System shows message “Cant create correspondence” if particular
correspondence is not responded( Approved) by higher level user
4(c). user can update the details and then can forward details.
R9:Approve correspondence.
Pre-Condition: Worklist is displayed on the screen.
Input: In workluist there is a forwarded correspondence is there.
Output: Particular details saved in the INBOX of the WORKLIST or at some other place
where user wants to store.
Processing:
Main Scenario :
1. User clicks on “Approve” option.
2. Details stored in inbox of the work list or at some other place where user wants
to store.
3. User at lower level can forward these details to higher level and vise versa.
4. Acceptance message is mailed to lower level user who has forwarded those
details.
Alternate Scenario:
4(a). User can reject the forwarded correspondence.
R10:Reject correspondence.
Pre-Condition: Work list is displayed on the screen.
Input: In work list there is a forwarded correspondence is there.

System Analysis
Output: Particular details are rejected.

Processing:
Main Scenario :
1. User clicks on “Reject” option.
2. Details not stored.
3. Acceptance message is mailed to lower level user who has forwarded those
details.
Alternate Scenario:
4(a). User can Approve the forwarded correspondence.
4.1.2 System Requirements

System Requirements can be briefly listed as:
• Application Procedures i.e. filing of new Application, renewal and

cancellation procedures
• File Movement between various officials
• Facility for attachments
• Facility to provide notifications about various procedures in hierarchies
• Report generation i.e. both Executive reports and individual detailed
reports should be generated
• Records Maintenance
4.2 FEATURES OF NEW SYSTEM
In current, there is no any software developed related to Crime Branch so time is wasted
to enter data into registers manually. By this project user’s manual work is reduced and
also time is saved. This project also contains workflow which is used to send urgent data
to any higher authority so that delay of work is reduced. And any higher authority can
send any decision to the lower authority so further action will be taken by lower authority
so pending work is very less.
The features to be specially highlighted in the new system being developed are:
• Automation of a huge number of tasks.

• Digitalization of manual artifacts.
• Transparency to citizens.
• Reduction in burden of preserving hard copies of records.
• Time consumption in the process flow is considerably reduced.
• The system should be rigid to enforce discipline and accountability in
implementing various schemes and policy initiatives and at the same time

System Analysis
flexible enough to accommodate evolving public policies and to divert from the
regular routing.
• The establishment work should be taken care by the system and allow the
staff concentrate more on policy making issues etc.
• The document opening should pass through the ACID test as discussed
above.
• The system should allow a new document to be open only if it satisfies a
series of ACID tests like whether the subject relates to an infeasible request,
whether the subject falls within the original jurisdiction of the Office etc.
• The system should exploit the power of network computing like workflow
automation in selected work areas within the office departments etc.
4.4 NAVIGATION CHART
Fig 4.4.1 Navigation chart
4.5 USE CASE DIAGRAM

System Analysis
Fig 4.5.1 Use Case Diagram
4.6 DATA MODELING

System Analysis
4.6.1 ER Diagram
Fig 4.6.1 ER Diagram for Border Activities Details

System Analysis
Fig 4.6.2 ER Diagram for Border Activities Details

System Design
5. SYSTEM DESIGN
This presents the logical data model that defines entities required for Intelligence Bureau
application tables.
Overview
The entities in the logical data model have been logically grouped for ease of
understanding. Explanation is not needed for each entity and its attribute of that entity.
Standards and Techniques

In order to create the diagrams the Oracle and the Designer 2000 standards established by
TCS have been followed. Some additional standards and techniques explained below
have also been used to ensure consistency in the design.
Conventions
The entities and attributes have been named as per the SGV standard conventions.

System Design
5.1 SYSTEM ARCHITECTURE DESIGN
5.1.1 Class Diagram
Fig 5.1.1 Class Diagram

System Design
5.1.2 Sequence Diagrams
Fig 5.1.2.1 Sequence Diagram for insert data

System Design
Fig 5.1.2.2 Sequence Diagram for Login
Fig 5.1.2.3 Sequence Diagram for Logout

System Design
Fig 5.1.2.4 Sequence Diagram for update data

System Design
Fig 5.1.2.5 Sequence Diagram for View data
Fig 5.1.2.6 Sequence Diagram for Report Generation

System Design
Fig 5.1.2.7 Sequence Diagram deletes data

System Design
Fig 5.1.2.8 Sequence Diagram for create correspondence
Fig 5.1.2.9 Sequence Diagram for forward correspondence

System Design
Fig 5.1.2.10 Sequence Diagram for approve correspondence
Fig 5.1.2.11 Sequence Diagram for Reject correspondence

System Design
5.1.2 Deployment Diagram
Fig 5.1.3.1 Deployment Diagram

System Design
5.2 DATABASE DESIGN
5.2.1 Database Table and Relationship
Table 5.2.1.1 Person Table

Field Type Null Key
DB_ID BIGINT(20) NO FK(database_mst)
LOC_ID BIGINT(20) NO FK( LocationDb )
LANG_ID BIGINT(20) NO FK(lang_mst)
PERSON_ID BIGINT(20) NO PK
PERSON_CODE BIGINT(20) NO
FIRST_NAME VARCHAR(50) NO
MIDDLE_NAME VARCHAR(50) YES
LAST_NAME VARCHAR(50) YES
DOB DATETIME YES
AGE BIGINT(20) NO
GENDER_LOOKUPID BIGINT(20) NO FK(lookup_mst)
RELIGION_LOOKUPID BIGINT(20) YES FK(lookup_mst)
RELIGION_OTHER VARCHAR(50) YES
NATIONALITY_ID BIGINT(20) YES FK
PERSON_CASTE VARCHAR(50) YES
CATEGORY VARCHAR(20) YES
OCCUPATION_LOOKUPID BIGINT(20) YES FK(lookup_mst)
OCCUPATION_OTHER VARCHAR(50) YES
COUNTRY_ID BIGINT(20) NO FK( NationalityDb)
IS_ADULT CHAR(1) YES
MARITAL_LOOKUPID BIGINT(20) YES FK(lookup_mst)
MARRIAGE_DURATION DECIMAL (10,0) YES
RES_WITH_INLAWS BIGINT(20) YES
IS_INJURED BIGINT(20) YES
DATE_IDENTIFIED DATETIME YES
Table 5.2.1.2 City Table

System Design
Field Type Null Key

CITY_ID BIGINT(20) NO PRI
DISTRICT_ID BIGINT(20) YES FK(DistrictDb)
CITY_NAME VARCHAR(50) NO
CITY_CODE VARCHAR(10) NO
Table 5.2.1.3 Contact Table

Field Type Null Key
SR_NO BIGINT(20) NO PK
PERSON_ID BIGINT(20) YES FK(PersonDb)
MASTER_LOOKUPID BIGINT(20) NO FK(lookup_mst)
RESIDENCE_PHONE BIGINT(20) YES
OFFICE_PHONE BIGINT(20) YES
MOBILE BIGINT(20) YES
EMAIL VARCHAR(150) YES
FAX BIGINT(20) YES
Table 5.2.1.4 Country Table

Field Type Null Key
COUNTRY_ID BIGINT(20) NO PK
COUNTRY_NAME VARCHAR(50) NO
COUNTRY_CODE VARCHAR(10) NO
Table 5.2.1.5 District Table

Field Type Null Key
DISTRICT_ID BIGINT(20) NO PRI
STATE_ID BIGINT(20) NO FK(StateDb)
DISTRICT_NAME VARCHAR(50) NO
DISTRICT_CODE VARCHAR(10) NO
POPULATION BIGINT(20) YES

System Design
Table 5.2.1.6 Language Table

Field Type Null Key
LANG_ID BIGINT(20) NO PK
LANG_NAME VARCHAR(20) NO
LANG_SHORT_NAME VARCHAR(10) NO
Table 5.2.1.7 Location Table

Field Type Null Key
LOC_ID BIGINT(20) NO PK
LOC_NAME VARCHAR (100) NO
LOC_SHORT_NAME VARCHAR(30) NO
DEPARTMENT_ID BIGINT(20) NO FK(lookup_mst)
PARENT_LOC_ID BIGINT(20) NO
LOC_ADDR_1 VARCHAR(50) YES
LOC_ADDR_2 VARCHAR(50) YES
LOC_CITY_ID BIGINT(20) YES FK(CityDb)
LOC_DISTRICT_ID BIGINT(20) YES FK(DistrictDb)
LOC_STATE_ID BIGINT(20) YES FK(StateDb)
LOC_PIN VARCHAR(10) NO
TYPE_LOOKUP_ID BIGINT(20) NO FK(lookup_mst)
START_DATE DATETIME NO
END_DATE DATETIME YES
ACTIVATE_FLAG BIGINT(10) NO
Table 5.2.1.8 Nationality Table

Field Type Null Key
NATIONALITY_ID BIGINT(20) NO PK
NATIONALITY_NAME VARCHAR(50) NO
Table 5.2.1.9 State Table

Field Type Null Key
STATE_ID BIGINT(20) NO PK

System Design
COUNTRY_ID BIGINT(20) NO FK(CountryDb)

STATE_NAME VARCHAR(50) NO
STATE_CODE VARCHAR(10) NO
Table 5.2.1.10 Occupation Table

Field Type Null Key
OCCUPATION_ID BIGINT(20) NO PK
OCCUPATION_NAME VARCHAR(50) NO
Table 5.2.1.11 Taluka Table

Field Type Null Key
TALUKA_ID BIGINT(20) NO PK
DISTRICT_ID BIGINT(20) NO FK(DistrictDb)
TALUKA_NAME VARCHAR(50) NO
TALUKA_CODE VARCHAR(10) NO
Table 5.2.1.12 Village Table

Field Type Null Key
VILLAGE_ID BIGINT(20) NO PK
TALUKA_ID BIGINT(20) NO FK(TalukaDb)
VILLAGE_NAME VARCHAR(50) NO
VILLAGE_CODE VARCHAR(10) NO
Table 5.2.1.13 Religion Table

Field Type Null Key
RELIGION_ID BIGINT(20) NO PK
LANG_ID BIGINT(20) NO FK (lang_mst)
RELIGION_NAME VARCHAR(50) NO
Table 5.2.1.14 Action_Flag Table

System Design
Field Type Null Key

ACTION_ID BIGINT(20) NO PK
ACTION_NAME VARCHAR(100) NO
SERVICE_ID BIGINT(11) NO FK(Service Table)
ACTION_DESC VARCHAR(512) YES
ORDER_NO BIGINT(10) NO
ACTION_STATUS VARCHAR(45) YES
AUDIT_ACTV VARCHAR(10) YES
Table 5.2.1.15 Service Table

Field Type Null Key
SERVICE_ID BIGINT(20) NO PK
SERVICE_TYPE VARCHAR(5) YES
SERVICE_CLASS VARCHAR(512) YES
SERVICE_METHOD VARCHAR(100) YES
SERVICE_DESC VARCHAR(512) YES
SERVICE_STATUS VARCHAR(6) YES
SERVICE_NAME VARCHAR(45) YES
AUDIT_ACTV VARCHAR(10) YES
TRN_COUNTER BIGINT(11) YES
Table 5.2.1.16 Lookup_master table
Field Type Null Key

LOOKUP_ID(PK) BIGINT(20) NO PK
PARENT_LOOKUP_ID BIGINT(20) NO
LOOKUP_NAME TEXT NO
LOOKUP_SHORT_NAME TEXT NO
LOOKUP_DESC TEXT NO
ORDER_NO BIGINT(20) NO
LANG_ID BIGINT(20) NO
Table 5.2.1.17 Borderactivites_mst
Field Type Null Key

SR_NO bigint(20) NO PRI
LOC_ID bigint(20) NO FK(LocationMst)

System Design
CRIME_COMMITED char(1) NO
ACTIVITY_TYPE bigint(20) NO FK(ActMst)
PERSON_ID bigint(20) NO FK(PersonMst)
IS_NATIONAL char(1) NO
EDU_QUALIFY varchar(50) YES
BIRTH_PLACE varchar(50) YES
ISSUE_AUTHR varchar(50) YES
HEIGHT varchar(50) YES
WEIGHT varchar(50) YES
BUILT varchar(50) YES
MARK_ON_BODY varchar(50) YES
OTHER_DTLS varchar(50) YES
TYPE_FISHERMAN bigint(20) YES FK(FishermanMst)
NAME_BOAT varchar(50) YES
BOAT_OWNER varchar(50) YES
REG_BOAT bigint(20) YES FK(FishermanMst)
REL_PERSON_NAME bigint(20) YES FK(RelativeMst)
TYPE_REL bigint(20) YES FK(RelativeMst)
SUB_CASTE varchar(45) YES
BOAT_REG_NO varchar(45) YES
ATTACHMENT_ID bigint(20) YES FK(AttachmentMst)
OTHER_REL varchar(45) YES
TRN_COUNTER int(11) YES
CORR_ID bigint(20) unsigned YES
APP_KEY bigint(20) unsigned YES
ORG_LOC bigint(20) unsigned YES
RC_STATUS varchar(30) NO
ACT_TAKEN varchar(30) NO
Table 5.2.1.18 Bordercustody_dtl
Field Type Null Key

BORDERMST_ID bigint(20) NO FK(BorderMst)
CUSTODY_DATE datetime NO
CUSTODY_PLACE varchar(50) NO

System Design
DELETE_FLAG char(1) YES
Table 5.2.1.19 Border_release_dtl
Field Type Null Key

RELEASE_DATE datetime NO
IS_RELEASE_BOAT char(1) NO
TRN_COUNTER int(11) YES
RT_PATH text YES
REMARK text YES
EMP_F_NAME varchar(45) YES
EMP_M_NAME varchar(45) YES
EMP_L_NAME varchar(45) YES
EMP_DGN varchar(45) YES
AGENCY bigint(20) YES FK(Agency)
OTHER_AGENCY varchar(45) YES
PLACE varchar(45) YES
EMP_OF_NAME varchar(45) YES
EMP_OM_NAME varchar(45) YES
EMP_OL_NAME varchar(45) YES
EMP_ODGN varchar(45) YES
OTH_AGN_HAND varchar(45) YES
PLACE_OTHER varchar(45) YES
Table 5.2.1.20 Border_lang_mpg
Field Type Null Key

BORDER_MST_ID bigint(20) NO FK(BorderMst)
LANGUAGE varchar(50) NO
IS_SPEAK char(1) YES
IS_READ char(1) YES

System Design
IS_WRITE char(1) YES
Table 5.2.1.21 Border_crmreg_mpg
Field Type Null Key

DB_ID bigint(20) NO MUL
CASE_MST_ID bigint(20) NO FK(CaseMst)
FIR_JJ_FLAG varchar(50) NO
Table 5.2.1.22 Border_contact_dtl
Table 5.2.1.23 Reports
Field Type Null Key

report_id int(11) NO PRI
report_name varchar(1020) NO
parent_report_id int(10) NO
report_dao_classname varchar(255) NO
COLUMN_SELECTION_ALLOWED decimal(1,0) YES
lang_id varchar(5) NO
Field Type Null Key
loc_id varchar(5) NO
crt_dt datetime NO
crt_user varchar(16) NO
PERSON_ID bigint(20) NO FK(PersonMst)
lst_upd_dt datetime YES
BORDER_MST_ID bigint(20) NO FK(BorderMst)
lst_upd_user varchar(16) YES
RELATION_LOOKUPID bigint(20) NO
export_format decimal(10,0) YES
RELATION_OTHER varchar(45) YES
report_type decimal(10,0) YES
Table 5.2.1.24 Reports _ parameter
Field Type Null Key

REPORT_ID int(11) NO FK (Reports)
PARAMETER_ID int(11) NO PRI
PARAMETER_TYPE int(11) NO
PARAMETER_NAME varchar(100) NO

System Design
MANDATORY decimal(1,0) NO
TABLE_NAME varchar(255) NO
COLUMN_NAME varchar(255) NO
CLASS_NAME varchar(255) YES
METHOD_NAME varchar(255) YES
METHOD_ARGS varchar(255) YES
DISPLAY_IN_HEADER decimal(1,0) NO
VO_CLASS_NAME varchar(255) YES
PARAMETER_DISPLAY_NAME varchar(800) YES
Table 5.2.1.25 Reports _ column
Field Type Null Key

report_id int(10) NO FK (Reports)
column_id int(10) unsigned NO PRI
column_header varchar(500) NO
data_type decimal(2,0) NO
TABLE_NAME varchar(255) NO
COLUMN_NAME varchar(255) NO
PARENT_COL int(11) YES
COL_LEVEL int(10) unsigned NO
MANDATORY decimal(10,0) YES
COL_WIDTH decimal(10,0) YES
5.2.2 Table Relationship Diagram

System Design
Fig 5.2.2.1 Table Relationship Diagram

System Design
Fig 5.2.2.2 Table Relationship Diagram

System Design
5.3 INPUT/OUTPUT AND INTERFACE DESIGN
HOME PAGE
Help
Date Settings Change Password Logout
Home
InBox OutBox
Holiday
All the correspondences List
and their Notification of Displayed
Approval or Rejection are here.
stored here.
All the Links to the
different Applications
are here.
Most Wanted
Criminal’s Details are Latest News is
displayed here with his flashed here.
Photographs .
Fig 5.3.1 Input/Output and Interface Design- Main Page

System Design
Help
Home
Form1 Form 2 Form3 Form4 Form 5 Form 6 Form7
For all the forms Required Labels, Textboxes, Drop Down Lists, Radio
buttons, Attachments etc all the components are arranged here as per the
given format
Previous Submit Create Correspondence Next Reset
Fig 5.3.2 Input/Output and Interface Design-Common Form
Help
Home
Report Name
ALL PARAMETERS ARE ARRANGED HERE
For all the forms Required Labels, Textboxes, Drop Down Lists, Radio
buttons, Attachments etc all the components are arranged here as per the
given format.
Generate Report Create Correspondence Reset
Fig 5.3.3 Input/Output and Interface Design-Report Form

System Design
5.3.1 State Transition Diagrams
Fig 5.3.1.1 State Transition Diagram to insert new data

System Design
Fig 5.3.1.2 State Transition Diagram to update data

System Design
Fig 5.3.1.3 State Transition Diagram to view data

System Design
Fig 5.3.1.4 State Transition Diagram for correspondence

Implementation Planning
6. IMPLEMENTATION PLANNING
The right strategy for implementation of a huge system like Intelligence Bureau is very
critical to make it successful over a period of time. The strategy should cover the people,
processes, and the technology with broad view of the current status on these aspects in
mind.
6.1 IMPLEMENTATION ENVIRONMENT

6.1.1 Key Implementation Objectives
The implementation objectives are as follows
• The customized version with duly incorporated Acceptance testing

comments is installed in Client.
• Ensure smooth functioning of the installed software at Client.
• Train the selected end-users in the operations of Intelligence Bureau
application system as per plan.
With our experience of implementation at various sites of similar systems, we

found that the skill levels on computers, Client processes varies on a wide range
at various levels and also at the same level among officers. Also, the drive and
motivation of the officer heading the particular department would really boost the
implementation and ensure that the activities are completed on time and
Intelligence Bureau rollout exercise is faster.
Hence, TCS proposes the following methodology for implementation.
• Implement the Intelligence Bureau in phases with set of departments in

each phase.
• Rollout the applications in a phased manner in these sets of departments
• Ensure that all the Users are trained in time to start working on the
Intelligence Bureau
• Infrastructure is in place before the Intelligence Bureau is rolled out in
these set of departments in a phased manner

Critical Success Factors
Successful Intelligence Bureau Implementation based on the above methodology is

critically dependent on certain prerequisites, which are considered as critical
success factors. This section outlines such prerequisites.
Table 6.1.1 Prerequisites
SrNo.. Factors
No.
1 Infrastructure (Servers, Network Components, Desktops, Scanners, Printers,
etc.)
2 Identification of implementation team from CLIENT
3 Training of DPOs (Departmental Trainers) for training the departmental users
4 Procurement of System Software licenses
5 Training of officers
6 Extraction of Data and entry into masters
7 Digitization of Acts, Rules, Statutes etc and their verification for correctness
and completeness
8 Providing the inputs for Gap Analysis study to TCS
9 Availability of additional servers for maintenance activities for sometime
Each of these critical success factors is taken as inputs for identifying the requirements
for implementation and is discussed in detail in the further sections of this document.
6.1.2 Implementation Plan
The phases/activities prior to and during implementation, like startup, site preparation,
infrastructure procurement, installation of servers, installation of system software,
Customization and Installation of Intelligence Bureau software are explained in the above
sections.

6.2 MODULES SPECIFICATION

The Intelligence Bureau is divided in to many sub branches. Each Sub branch gathers
information, investigates and tracks different kinds of crimes. Intelligence Bureau has the
following sub branches.
1. Political Module
2. Communal Branches
3. Security Module
4. Election module
5. Reports
6. Worklist
1.Political Module:
• DSI stands for Daily Summary of Information. It is prepared on daily

basis & includes all the happenings in the state which are related to Law
and Order.
• To store Political Personality Details like MLA, MP, and Member of
Rajya Sabha etc. These include his Personal Details, Address Details,
Relatives Details, Position Held Details, Political Career Details and
Income Details.
• Other then this Office Bearer Details, College Details, University Details,
Political Party Details, Activity Details, Constituency Details, Nomination
Details, Election Agent Details, Campaign Details, Polling Phase /Voter
Turnout Details, Election Result Details, Natural Calamities Details, Pre-
Poll Survey Details are there in this module.
2. Communal Branches:
Religious Place Details

This Application captures all the important details of the Religious Place
of Gujarat. These details include its basic details including Date of
Establishment and its Registration Details, details of its Priest and Trustee
and details of the majority community surrounding the area where
Religious Place is located.
Curfew Details
This Application captures all the required details of the curfew imposed in
Gujarat. These details include basic details of curfew, details of the
persons detained during the curfew, the details of communal disturbance
occurred during the curfew.

Other then these applications Festival/Fair Details, Madrasa Details are there in this
module.
3. Security Module:
• Foreigners Details, VIP Visit Details, VIP Security Details, Border

Activity Details, Look Out Notice Details, Details of Ineligible Persons for
Issuing Passport, Disposal of Passport Applications, Fake Passport/Visa,
Security Application Details, Suspect Details, ONGC Security Details,
Religious & Dam Security Details, Wanted Criminals Details, Information
of Gang and Gangster, Security of Vital Installation, Wireless Telegraphy
Application Details, Airport Security Details, Case wise Bomb Explosion
Details, Details of Seized Arms, Security of Road & Bridge all these
applications are there in this module.
• All the applications are related to security details
4. Election module:
• Political Party Details, Activity Details, Constituency Details, Nomination

Details, Election Agent Details, Campaign Details, Polling Phase /Voter
Turnout Details, Election Result Details, Natural Calamities Details, Pre-
Poll Survey Details all these applications are there in this module.
• All the applications are related to election details.
5. Reports:
• In this section, it contains all the reports that is generated by different

applications as mentioned above.
6. Worklist:
• Worklist shows all the correspondence created by the officers. It has two
sections inbox and outbox.

6.3 SECURITY FEATURES

Any infrastructure/application development for the web should adhere to the Security
Policy detailed by the organization. It is assumed that Client has a detailed Security
policy for protecting its resources and information. What follows is a “common”
approach for protecting the resources and information when a web application is
Published in the web.
6.3.1 Security Layers
TCS proposes an Intelligence Bureau solution that has the capability to minimize
security risks by deploying multiple layers of security controls
• Application Security
• Database Security
• Network - Data Transfer Security
• External Security: Firewall and Antivirus
6.3.1.1 Application Security
Single sign-on provides users with a single point of entry to all authorized
applications with a single authentication or login process. Application Server
Security includes
a) Identification: System supports User identification with Server, which is a

secure repository for Identification & authorization information. Each user of the
system will be given a unique username / employee identification number.
b) Authentication: System supports strong user Authentication with Server.

Server Password-based authentication will support Password-based schemes, to
be secure, must facilitate change of passwords regularly, sufficient complexity
and cannot be easily guessed. built-in robust password management enables
administrators to enforce various password checks.
c) Authorization: User Authorization in the system is implemented as access

control. Access control deals with the concept of who has access to what

information and what type of operations can be accessed. System provides a

strong set of access control security mechanisms through privileges. Application
enforces the Principle of Least Privilege - that is, granting only those privileges to
a user that allows him to perform his job functions, but no more. This ensures that
the users will only be able to access files and data that they are privileged to. The
access control Module in system is defined for creation, opening and editing of
objects/data and by route – users not in the route of a file will not be able to
access the file.
d) Data Confidentiality: Encryption is the mechanism that is used to provide

data confidentiality. Required data can be encrypted and sent through SSL
(Secure Socket Layer). SSL can be enabled for accessing the applications through
Internet.
e) Data integrity: System maintains the Data Integrity by detecting whether,

either stored or being transmitted has been accidentally or maliciously altered. As
an Option, the data on the form can be “digitally signed” using TCS PKI enabling
tool called FormSigner™, which ensure data integrity and non-repudiation. This
digital signature is in the PKCS#7 formats as defined in the IT Act, 2000 and is
legally valid.
f) Non-repudiation: Non-repudiation is data integrity and entity authentication

provable to the user. It is achieved by the system by associating the user identity
with Audit of crucial operations performed. Further non-repudiation is achievable
when digital certificate is used for digitally signing coupled with the appropriate
policies and procedures. As an Option, the data on the form can be “digitally
signed” using TCS PKI enabling tool called FormSigner™, which ensure data
integrity and non-repudiation. This digital signature is in the PKCS#7 formats as
defined in the IT Act, 2000 and is legally valid.
g) Audit: A critical aspect of any system security policy is the monitoring and
recording of activities within that system i.e., “auditing”. To address this
requirement, System provides a number of features and functions to enable
accountability of actions taken by users of the database. System does this by
providing accounting and auditing features, which are designed to be as granular
and flexible as possible to ensure that exactly what needs to be accounted and
audited, as dictated by the application or system security policy, is recorded. This

helps to ensure that the size of audit trail remains manageable and the important
records are easily accessible. Application also provides capabilities to permit
accounting and auditing plans to be quickly enabled to implement crisis plans.
6.3.1.2 Database Security
Server-Enforced, Row Level Access Control - The system will be the using
RDBMS Databases. These databases will be deployed on the database server and
database access checks will be defined at the system level. No direct access is
granted to RDBMS Databases, all access to these databases is via applications and
hence governed by Access controls.
Comprehensive Auditing - To spot and respond to security breaches, fine-

grained, extensible auditing is an important aspect. For example, if a user abuses
access privileges and performs abnormal actions such as repeatedly trying to
login, an alert is automatically sent to the administrator.
Audit Trail: The audit trail will be maintained for the following:
• Date/Time stamp for all logins
• Date/Time stamp for all database access, new inserts, updates and
deletions
• Date/Time stamp on access of important files, attempt on such accesses
• Audit trail for the data access
6.3.1.3 Network - Data Transfer Security
In view of the threat of cyber attacks TCS proposes the below options to
implement the network security through the software installed on the firewall.
However, this is part of the Network architecture and out of scope of current
proposal.
Encryption of All Data in Transmission - encrypts data traveling over the

network everywhere.

• Browser to application server

• Application server to database
• Server to server
•
Selective database encryption feature, sensitive data becomes unreadable over the
network.
The connection from browser to application server is protected through HTTPS’s
Secure Socket layer with data encryption and encapsulation. In addition to strong
user authentication, SSL also provides network data confidentiality and data
integrity for multiple types of connections: LDAP (Lightweight Directory Access
Protocol), IIOP (Internet Intra-ORB Protocol), and Net (formerly known as Net8).
The data traffic can further be secured through the use of Internet Firewall and
Proxy Servers. Intrusion detection software will be used for analyzing the network
traffic and warning possible breach to the security of the system. Firewall will be
implemented for preventing un-authorized users to logon through the Internet.
6.3.1.4 External Security
In order to have a comprehensive secure environment TCS recommends the use

of Firewalls and anti virus kits in the data center. The detailed requirements for
the same can be arrived in consultation with the technical team of CLIENT during
“Site Preparation and Infrastructure Study” phase.
Firewalls: TCS proposes the use of a firewall that provides required protection
for the Client from internet traffic. Its architecture and functionality should
combine to secure organizations networks, delivering full-featured security and
ensuing complete control of information entering and leaving the Client network.
Anti-Virus Kits: All the Application servers, database servers and the Web-
servers should have the latest anti-virus kits to detect new viruses. These anti-
virus kits will be updated with the latest versions frequently.
6.2.1.5 Security Policy and Audit
Client needs to define security policy for their IT solutions. Security audit needs
to be conducted for conformance with the defined IT Security Policy. However

defining the security policy for the Client or conducting audits is out of the scope
of current proposal.
If the security policy is defined and available during system study, the same will
be incorporated into the security design of the system. However, the overall
Intelligence Bureau related security aspects are discussed in the previous sub-
sections of this Section.
Note: - The above section describes the methodology of securing the application
at various levels by deploying additional software / hardware components. The
proposed application architecture of the system is based on the open standards and
is capable to incorporate the above modes of security.
6.4 CODING STANDARDS
Objects
The below are the naming convention for the design element used in the form.
Table 6.4.1 Naming Convention Table
Control Type Prefix Example

Text Filed txt txt_ProjectName
Check Box chk chk_StudentProfessor
Radio Button rad rad_Gender
List Box lst lst_YesNo
Combo Box cmb cmb_Industry
Rich Text Field rt rt_Body
Number Field num num_TeamSize
Time tm tm_StartTime
Date dt dt_EndDate
Date & Time dtm dtm_Now
Authors ats ats_fileowner
Names dms nms_selectedperson
Readers rds rds_reviewers

Password pwd pwd_Useri

Formula frl frl_CurrentDate
Rich Text Lite rtl rtl_Nothings
Time Zone tz tz_India
Color col col_Fileinfo
All Hidden Fields should be place one after the other to reserve the space in the form.
Description & purpose of each hidden field should be documented in the design spec of
the appropriate components.
Variables
<prefix>_<meaningful name>
prefix : 2 character code.
First alphabet represents the scope of the variable
l - Local
g - Global
Second alphabet represents the type
b - Boolean
c - Currency
s - String
f - Float
i - Integer
l - Long
t - Time
a - Array
v - Variant
The body of the variable names and function names should use mixed case and should be
as long as needed to describe their purpose. To keep the name length reasonable,

abbreviations can be used for standard terms like Init for initialization, Tbl for table, Cnt
for count, Grp for Group etc. Wherever abbreviations are used, try to use them
consistently to improve readability. And in meaningful variable name variable name start
with lower case alphabet and second part of the name should be start with upper case
alphabet like for student name variable name should be studentName.
Recommended Maximum Length for variable names is 32 characters.
Example:
For declaring a global string variable for Group name: gs_grpName.
When passing values to a subroutine/function, use the same variable names in the called
routine as in the calling routine.
For Functions and Subroutines

<prefix>_<meaningful name>
For Functions: prefix is fn
Comments and description of functions, Script etc
All code -should be well commented (Date, Developer etc). All procedures and
functions should begin with a comment to explain what the function/procedure performs.
A brief synopsis is sufficient.
The below is the Comment template for procedure and function:

‘***********************************************************************
‘Purpose : This function performs so on operation.
‘Input : Input if any
‘Output : Output if any
‘Limitation:
‘Developer Name:
‘Date :

‘***********************************************************************
Ex:
‘***********************************************************************
‘Purpose : This function sends a mail with the doc link attached.
‘Input : Input for this function is the person name to whom it has to be send
‘Output : This function will return a true If the mail is sent else false
‘Limitation : This function will not send a internet mail.
‘Developer Name: Mr. Joe
‘Date : 16th Apr '2007
***********************************************************************
If the some code is function is modified. Then that section of the code should be mark
with comments indicating why the change was made, by whom, when. Format for
Change history is:
‘***********************************************************************
‘Change Requested
‘By whom:
‘When :
‘Why :
‘Developer:
‘***********************************************************************
Ex:
‘***********************************************************************
‘Change Requested
'By whom: Mr. Smith
'When : 20th Apr '2007
'Why : Instead of doc link, main document should be opened
‘Developer: Mr. Joe

‘***********************************************************************
Class
The name of the Class should start with a capital letter and must be a meaningful name
that represents the functionality of the class. Header information is mandatory for all the
java class. This information gives a detailed description about the change history and the
creator of the class. Below format shows the structure of the class.
/*
* PACKAGE : <package name>
* FILENAME : <filename>. java
* @VERSION : 1.0
* @AUTHOR :
* DATE :
*
* REV. HISTORY :
*-----------------------------------------------------------------------------
* DATE AUTHOR DESCRIPTION
*
*-----------------------------------------------------------------------------
*/
Immediately following this header would be the package declaration with a comment as a
header. The name of the package differs with respect to each class. For e.g.,
/* PACKAGE DECLARATION */
package com.tcs;
The required module related class files that are imported, to be placed after packages
have been declared. For e.g.,

/* IMPORTED <module name> CLASSES */

import com.tcs. <module name>.ABC;
The required java package classes will follow after the module level class imports (if
applicable). For e.g.,
/* IMPORTED JAVA CLASSES */

import java.util.Calendar;
import java.util.ArrayList;
The required javax package classes will follow after the java class imports (if applicable).
For e.g.,
/* IMPORTED JAVAX CLASSES */

import javax.xml.parsers.DocumentBuilder;
The required org package classes will follow after the javax class imports (if applicable).
For e.g.,
/* IMPORTED ORG CLASSES */

import org.w3c.dom.Document;
Then comes the description about the class and the comments written at various levels in
the class.
/**
* DESCRIPTION ABOUT THE CLASS
*/

public class Abc

{
// Single line description about the variable

public String strA = "";
// Single line description about the table

Hashtable abcList = null;
/**
* DESCRIPTION ABOUT THE METHOD.
* @param <parameter name> <parameter description>
* @return <description about what the method returns>
* @exception <list of exceptions that the method throws (if any)
*/
public void method1(String abc)
{
} //end of method1
For one particular application all the classes should be start with the same name. Suppose
for BorderActivityDtls, classname should be BorderActivityDtlsVogenImpl,
BorderActivityDtlsServiceImpl, BorderActivityDtlsDaoImpl, BorderActivityDtlsVO etc.
Only postfixes should be changed.

JSP Format
Every JSP would start with a common header.

Next follows the various classes imported in the JSP. For e.g.,
<%-- IMPORTED JAVA CLASSES --%>
<%@ page language="java" import="com.tcs.ABC,
java.util.ResourceBundle"%>
Next follows the various beans used in the JSP. For e.g.,
<%-- BEANS USED --%>

<jsp:useBean id="abc" class="com.tcs.ABCD" scope=""/>
Other standards that need to be followed are specified below. This template shows the
sequence in which the specific content resides in a JSP.
<html>
<head>

<title>Sample JSP</title>
<LINK rel="STYLESHEET" type="text/css" href="/abc/sample.css">

<META http-equiv="Content-Style-Type" content="text/css">
</head>
<script language=”javascript”>
function sample()
{
}
</script>
<body>
<form name="" method="post" action="">
<center>
<%
VARIABLE DECLARATIONS
request.getParameters() --> if applicable
BUSINESS LOGIC
AFTER EVERY 5 LINES OF CODING ADD AN EMPTY LINE FOR

CLARITY
%>

<input type="hidden" name="" value="">
<input type="hidden" name="" value="">
</center>

</form>
</body>
</html>
Method Names
All method names should start with the appropriate functionality done by that
function and it should be start with small case alphabet. Like if I want to insert
student record then method name should be insertStudentRecord.
Class StudentServiceImpl
{
public ResultObject insertStudentRecord (Map objectArgs)
{
//business logic
}
}

Testing
7. TESTING
Testing is the process carried out on software to detect the differences between its
behavior and the desired behavior as stipulated by the requirements specifications.
Testing is advantageous in several ways. Firstly, the defects found help in the process of
making the software reliable. Secondly, even if the defects found are not corrected,
testing gives an idea as to how reliable the software is. Thirdly, over time, the record of
defects found reveals the most common kinds of defects, which can be used for
developing appropriate preventive measures such as training, proper design and
reviewing
7.1 TESTING PLAN
The testing sub-process includes the following activities in a phase dependent manner:
a) Create Test Plans.

b) Create Test Specifications.
c) Review Test Plans and Test Specifications.
d) Conduct tests according to the Test Specifications, and log the defects.
e) Fix defects, if any.
f) When defects are fixed continue from activity.
UNIT
TESTINGG
MODULE
TESTING SYSTEM
SUB-SYSTEM TESTING
TESTING
ACCEPTANCE
TESTING TESTING
G
Fig 7.1.1 Testing Plan

Testing
7.2 TESTING STRATEGY
The development process repeats this testing sub-process a number of times for the
following phases.
a) Unit Testing.
b) Integration Testing
Unit Testing tests a unit of code (module or program) after coding of that unit is
completed. Integration Testing tests whether the various programs that make up a system,
interface with each other as desired, fit together and whether the interfaces between the
programs are correct. System Testing ensures that the system meets its stated design
specifications. Acceptance Testing is testing by the users to ascertain whether the system
developed is a correct implementation of the Software Requirements Specification.
Testing is carried out in such a hierarchical manner to ensure that each component is
correct and the assembly/combination of components is correct. Merely testing a whole
system at the end would most likely throw up errors in components that would be very
costly to trace and fix.
We have performed both Unit Testing and System Testing to detect and fix errors. A
brief description of both is given below.
Unit Testing
Objective
The objective of Unit Testing is to test a unit of code (program or set of programs)
using the Unit Test Specifications, after coding is completed. Since the testing
will depend on the completeness and correctness of test specifications, it is
important to subject these to quality and verification reviews.
Input: Unit Test Specifications
Testing Process
• Checking for availability of Code Walk-thru reports which have

documented the existence of and conformance to coding standards.
• Review of Unit Test Specifications
Verify the Unit Test Specifications conform to the program specifications.
Verify that all boundary and null data conditions are included.

Testing
7.3 TESTING METHODS
Black-box and White-box Testing
In black-box testing a software item is viewed as a black box, without knowledge of its
internal structure or behavior. Possible input conditions, based on the specifications (and
possible sequences of input conditions), are presented as test cases.
In white-box testing knowledge of internal structure and logic is exploited. Test cases are
presented such that possible paths of control flow through the software item are traced.
Hence more defects than black-box testing are likely to be found.
The disadvantages are that exhaustive path testing is infeasible and the logic might not
conform to specification. Instrumentation techniques can be used to determine the
structural system coverage in white box testing. For this purpose tools or compilers that
can insert test probes into the programs can be used.
Code Coverage
The way to make sure that you have got all the control flow covered is to cover all the
paths in the program during the testing (via white-box testing). This implies that both
branches are exercised for an ‘if’ statement, all branches are exercised for a case
statement, the loop is taken once or multiple times as well as ignored for a while
statement, and all components of complicated logical expressions are exercised. This is
called Path Testing. Branch Testing reports whether entire Boolean expression tested in
control structures evaluated to both true and false.
Additionally it includes coverage of switch statement cases, exception handlers and

interrupts handlers. Path testing includes branch testing as it considers all possible
combination of individual branch conditions. A simpler version is Statement Testing
which determines if each statement in the program has been executed at least once. The
coverage via Path Testing includes the coverage via Statement Testing. Since Path
Testing is extremely comprehensive it is costly, hence a viable minimum should be
measuring Statement Testing coverage.

Testing
7.4 TEST CASES
Table 7.4.1 Test Case for Border Activity Details
Project Name Intelligence Bureau

Test Item Border Activities Details
Environment Windows XP Professional
Function Test Condition Expected Result Actual Result Pass/Fail

Application
Border When the user A form is displayed First tab Personal Pass
Activities clicks on Border which is the first Details is displayed
Details Activities Details tab. Personal
New Entry link on the top Details -- form for
frame in the filling the details of
Applications Suspect.
home page.
1) In the Personal The following fields Form For personal Pass
Details form will appear:- details is displayed
Details of Personal with all the fields
List: and buttons.
• all the details of
the person like
his name, caste,
age, occupation
are filled
Document Found:
• document detail
The page also

contains the
following buttons
1) Add-To add
multiple person
Details and
document found
details
2) Submit-To
submit the request
3) Reset- To reset
all fields of the
page.
Testing
4) add-To add
documents found
details.
5) Next- to go to
next tab
6) Create
correspondence-to
create
correspondence
User clicks on Message “Please Alert is popped up Pass
submit without enter personal “Please enter at least
entering values in detailt list for one person‘s
Details of period from/to is" details”.
Personal List for should be popped
period from/to up.
field
User clicks on Message Please Alert is popped up Pass
submit without enter the category" “Please select
entering value in should be popped category”.
Category field up
On click of Message Alert is popped up Pass
submit button “<corresponding “<corresponding
without entering field name> is field name> is
any one of the mandatory" should mandatory".
mandatory fields be popped up.
On click of button Message Alert is popped up Pass

create “<corresponding “<corresponding
correspondence field name> is field name> is
without entering mandatory" should mandatory".
values in Details be popped up.
of Personal List
for period from/to
field
On Click Of The detail entered On the screen Pass
Submit button in gets inserted in the Message displayed.
the Border respective table(s). “Border Activities
Activities Details inserted Successfully
form after filling ”
all mandatory
Fields.
On Click of Reset Confirmation All Fields Of the Pass
button in the message is popped Form are Reset i.e.
Suspect Details up and clicking on cleared.
form. OK button a page
Testing
gets refreshed.
On Click of Next Next tab of the Next Tab is Pass
button in the application is Displayed.
application page opened.
On Click of Add Multiple add table Data is inserted into Pass
personal details ofis generated with multiple add table
the suspect button edit link and table is
in the application displayed on the
page screen.
On Click of Add Multiple add table Data is inserted into Pass
documents is generated with multiple add table
obtained details of edit link and table is
the suspect button displayed on the
in the application screen.
page
2) In the Address The following Form For Address Pass

Details form fields will appear:- Details is displayed
• Details of with all the fields
Personal present and buttons.
address
• Details of
Personal
permanent
address
• Person contact
details
The page also
contains the
following
buttons
1) Submit-To
submit the request
2) Reset- To reset
all fields of the
page.
3) Next- to go to
next tab
4)Create
correspondence-to
create
correspondence
User clicks on submit Message “Please Alert is popped up Pass

Testing
without entering enter Address “please insert at

values in Details of detail list for period least one adress".
address List for from/to is" should
period from/to field be popped up.
On click of submit Message Alert is popped up Pass
button without “<corresponding “<corresponding
entering any one of field name> is field name> is
the mandatory fields mandatory" should mandatory".
be popped up.
On click of button A table in which Alert is popped up Pass
create Police Station and “<corresponding
correspondence case Details related field name> is
without entering field values, to be mandatory".
values in Details of entered by user,
address List for will be displayed.
period from/to field
On Click Of Submit The detail entered On the screen Pass
button in the Border gets inserted in the Message displayed.
Activities Details respective table(s). “Border Activities
form. inserted
Successfully ”
button in the Border message is popped Form are Reset i.e.
Activities Details up and clicking on cleared.
gets refreshed.
3) In the physical The following Pass

description form fields will appear:-
• physical
description
Details of
Personal
permanent
address
1) Submit-To
submit the request
2) Reset- To reset
all fields of the
page.

Testing
3) Next- to go to
next tab
4)Create
correspondence-to
create
correspondence
without entering enter physical Please enter physical
values in Details of description detail description detail list
physical description list for period for period from/to is".
List for period from/to from/to is" should
field be popped up.
button without “<corresponding “<corresponding field
entering any one of the field name> is name> is
mandatory fields mandatory" should mandatory".
be popped up.
gets refreshed.
Photo attachment-click Photo is attached Table containing Pass
on the add attachment attachment is
button displayed with view
or remove link.
4) In the contact in India The following Pass

form fields will appear:-
• contact in India
Personal
details, present
and permanent
address
1) Submit-To
submit the request
2) Reset- To reset
all fields of the
page.
3) Next- to go to

Testing
next tab
4)Create
correspondence-to
create
correspondence
without entering enter Contact in “Please enter Contact
values in Details of India detail list for in India detail list for
Contact in India List period from/to is" period from/to is ".
for period from/to should be popped
field up.
button without “<corresponding “<corresponding field
entering any one of the field name> is name> is
mandatory fields mandatory" should mandatory".
be popped up.
gets refreshed.
5) In the Apprehension The following fields Pass

details form will appear:-
• Apprehension
details like
arrested by
whom, where,
when etc…
1) Submit-To submit
the request
2) Reset- To reset all
fields of the page.
3) Next- to go to next
tab
4)Create
correspondence-to
create
correspondence
without entering enter Apprehension “Please enter
values in Details of details list for period Apprehension
Apprehension details from/to is" should be details list for
List for period from/to popped up. period from/to is ".
Testing
field
button without “<corresponding field “<corresponding
entering any one of the name> is mandatory" field name> is
mandatory fields should be popped up. mandatory".

button in the Border message is popped up Form are Reset i.e.
Activities Details and clicking on OK cleared.
form. button a page gets
refreshed.
6) In the Criminal The following fields Pass

antecedents details will appear:-
form • Criminal
antecedents
details
1)Submit-To submit
the request
fields of the page.
tab
4)Create
correspondence-to
create
correspondence
without entering enter Criminal “Please enter
values in Details of antecedents l list for Criminal
Criminal antecedents period from/to is" antecedents l list
List for period from/to should be popped up. for period from/to
field is"

refreshed.

Testing
7) In the Release details The following fields Pass

form will appear:-
• Release details
like Release by
whom, where,
when etc…
1) Submit-To submit
the request
fields of the page.
tab
4)Create
correspondence-to
create
correspondence
without entering enter Release list for “Please enter
values in Details of period from/to is" Release list for
Release List for period should be popped up. period from/to is".
from/to field

refreshed.
On Click Of Submit The detail entered On the screen Pass
button in the Border gets inserted in the Message displayed.
Activities Details form respective table(s). “Border Activities
after filling all inserted
mandatory Fields. Successfully ”
Table 7.4.2 Test Case for ONGC Details - Report

Testing
Test Item ONGC Details - Report

Function Test Expected Result Actual Result Pass/Fail

Condition
Application
ONGC On click of Parameter page is Parameter page is Pass
Details- the report opened opened
Report ONGC
link from
the home
page
On click of Report is generated All data/filtered data Pass
Generate with entered data. are displayed.
Report Data is filtered if
button any parameter is
passed else each
and every entered
data is displayed.
Table 7.4.3 Test Case for Campaign Details- Report

Test Item Campaign Details- Report
Function Test Expected Result Actual Pass/Fail

Condition Result
Application
Campaign On click of the Parameter page is Parameter page is Pass
Details-Report report ONGC opened opened
link from the
home page
On click of Report is All data/filtered data Pass
Generate generated with are displayed.
Report button entered data.
Data is filtered if
any parameter is
passed else each
and every entered

Testing
data is displayed.

User Manual
8. USER MANUAL
The User Manual Guide makes you facilitated to use the software in a very proper manner. For,
Further details use User Manual Guide as below.
Help
This tool is provided with a concept of providing help to solve the queries related to the
project.
Home
This tool will divert the action to the home page
Password Change
This tool is provided to change the existing password.
Logout
This tool is provided to exit from the current form and switch to the login page
Attachment
This tool is used for attaching any file with application.
Calendar
This tool provides a facility to select date.

User Manual
Fig 8.1 Main Page
This is the main page of the complete IB module. This page contains all the application
Link, work list, Holiday List etc.

User Manual
Fig 8.2 Personal Details Form
In this form all the Personal details of the accused and Documents Found from the
accused is entered by the user. Both details have multiple add functionality.

User Manual
Fig 8.3 Address details form
In this form all the Contact Details of the accused entered by the user. Here two types of
addresses are there. Present Address and permanent address of the accused.

User Manual
Fig 8.4 Physical Description form
In this form all the Physical Description of the accused entered by the user. Other then
physical description photo attachment of the accused is there.

User Manual
Fig 8.5 Contact in India details form
In this form Contact Details of relatives or friend of the accused in India entered by the
user. Other then these details photo attachment is also there. More then one friend or
relative’s entry can be done.

User Manual
Fig 8.6 Apprehension details form
In this form Apprehension details of the accused entered by the user. Other then these
details Custody details are also there. More then one Apprehension details and Custody
details entry can be done.

User Manual
Fig 8.7 Criminal Antecedents details form
In this form Criminal Antecedents details of the accused entered by the user. Here two
search components are there-Location search (To search location of the Police Station)
and another is Case search(To search case details).

User Manual
Fig 8.8 Release details form
In this form Release details of the accused entered by the user. Release Date, time, Name
and details of the agency handing over and Name and details of the agency hand over all
these details are there in this form.
And after filling this(last form) ,submit the form. If submission is successful then Success
message is displayed else Error massage will display.

User Manual
Fig 8.9 Edit/Update search details form
In this form just we have to entered particular details to search particular details. If no
parameter is entered and if we press “Search” each and every data is displayed. By
clicking on “edit” link all forms are populated for updation.Here all the entries for India
is searched i.e. crime committed in india.

User Manual
Fig 8.10 Case search form
Case search-To search case no and related details.
Here on basis of Date the search result is displayed.

User Manual
Fig 8.11 Location details form
Location search -To search location of the Police Station (complete address).
Here on basis of state Gujarat search result is displayed.

User Manual
Fig 8.12 Correspondence
Here correspondence is created and lower level officer Forward these details to the higher
level Officer. Higher level officer can approve or Reject this correspondence.

User Manual
Fig 8.13 Ongc details – Report parameter page
Fig 8.14 Campaign details – Report parameter page

User Manual
Fig 8.15 Ongc details – Report Generation page

User Manual
Fig 8.16 Campaign details – Report Generation page
Fig 8.17 Search Parameter

User Manual
Fig 8.18 Advanced Search Page
Fig 8.19 Advanced Search Page-Results

Limitations and Enhancement
9. LIMITATIONS AND ENHANCEMENTS
LIMITATIONS
The part of the system can be implemented using the current technology although some
modifications had to be done at various places. At various places some alterations with
the prototypes and functionalities would be done in order to work out the cost constraints
and to cope with the scheduling constraints.
In the Parameterized report limitations like selecting at most up to eight fields, etc would
be implemented. This is done to get optimum balance between the requirements and cost
factors.
Moreover, in Query based Parameterized Report the conditional field would be

configured and it would be limited to only one query, however long it may be with any
number of conjunctions could be evaluated.
This application is used by only Government Officers. Not used by common person. So if
any one wants to know the status of their FIR or complain then its not Possible. This can
be solved by designing a Portal.
In this application search is limited to String or by number. Can not do search by photo
and figure prints.
ENHANCEMENT
In Future we are going to design a Portal through which any person besides Government
officers can check the status of their FIR or Complain Status.
We are going to design a search component by which we can search by criminal’s

photograph or figure print.
Our system can use MYSQL in back-end. In future we are going to make such system in
which any back end can use.
The following activities would be undertaken, as appropriate, as part of the application

maintenance and would focus on elimination of production errors if any:
• Understand and analyze any enhancement requests

• Propose a solution and estimate to develop the enhancement request

• Construction and testing of the enhancement
• Helpdesk
TCS would setup a Helpdesk facility at the Client Side to help users at different locations
within the client. The help-desk will deal with the problems faced by end-users in the
areas of:
• Operation of the System

• Database Administration
• Application software
• Difficulties in understanding navigation flow and general functionality of the
Application system.
The setup allows TCS to solve problems by providing solution to the users either over a
telephone or by simulating the problem, logging it, marking it as a defect. The problem
reported could be a defect in the system due to non-satisfaction of requirements or a
change in requirements leading to enhancements. The following are the methods, which
will be used to facilitate the help desk.
• Telephone call support, Fax – the user can call to specified office numbers to get
their queries solved. This facility will be operational during the normal working
hours.
• E-mail support – the user can send their queries through e-mails.
• FAQs – the support will also be offered through Frequently Asked Questions
(FAQs). This is a list that will be compiled from the most frequently encountered
doubts and questions and will be provided to all users at a central location and
updated periodically.
Based on its experience, TCS proposes to extend this helpdesk as a centralized helpdesk
for all Client officers/users so that all calls either related to Intelligence Bureau or
Hardware, Network, Anti-Virus are received here first and later diverted to relevant
vendors working on these profiles. In this case, the centralized helpdesk need to be made
up with personnel from all the vendors working on the above areas at Client. This
helpdesk would the single point of contact for all the help that users require at Client.
Usage of Libraries:
Configuration control would be implemented through the use of Software libraries. These
libraries provide the means of identifying, labeling and capturing software items and
tracking changes to them. Libraries to be used in would be identified depending on their
usage.

The future of the e-Governance is in going wireless. Laptops with Wi-Fi, Mobiles all
wireless devices can be used in e-Governance and can play an important role for effective
administration.
Any new update in Knowledge Bank can be delivered to employees on their wireless
devices. Employees can subscribe to such facilities to get themselves updated at any time,
even when they are not at their desk.
We can connect all the district administrative offices to Client.
Fig 9.1 Connecting District Offices
Home Department would be committed to:

• Upholding the highest standard of performance, behavior and ethics
through our conduct, appearance and demeanor
• Providing innovative solutions to issues, in partnership with our
community
• Accepting future challenges by learning and developing new skills and
techniques to provide the highest quality police services to our community

• Database and search on biometric information

• Data mining with tolerances to get the pool of suspects
• Identification based on index generated through use of Biometric/body
parameters
Fig 9.2 Search Component

Conclusion and Discussion
10. CONCLUSION AND DISCUSSION
10.1 CONCLUSION
• HDIITS will be helpful to perform paperless work and manage all data.
• This provides easy, accurate, unambiguous and faster data access.

• Automating routine tasks - enabling officers to spend quality time on value
added tasks.
• Help in decision making - building knowledge base with structured information
storage and accesses. Access points to gather, build and customize knowledge
base.
• Improve inter and intra department information sharing – SOA (Service
Oriented Architecture) enabling quick and dynamic interfaces between various
government entities and the freedom to choose from competing technologies also.
• Lesser learning curve - Consistent user interface, customized for the group of
users, MIS and statistical information in various graphical and tabular forms.
10.2 DISCUSSION
10.2.1 Self Analysis of Project Viabilities

Intelligence Bureau is intended to address all these requirements and aspects discussed
earlier such as Security, Network Management, Filing System and Desktop Applications
that will enable users to perform their work.
This Application provides Document management, Workflow, Collaboration

environment and Knowledge Management in an integrated fashion and delivers as
Electronic Workplace that will result in productivity improvement in an Organization.
ITS –IB will be helpful to perform paperless work and manage all data.
This provides easy, accurate, unambiguous and faster data access.
SOA (Service Oriented Architecture) enabling quick and dynamic interfaces between
various government entities and the freedom to choose from competing technologies also.

10.2.2 Problem Encountered and Possible solutions
• First problem I faced in framework understanding as frame work is depends on

Spring and Hibernate which were new to me.
By making demo application and using online material to study spring and
Hibernate and with help of my mentors I solved it.
• The problems encountered during the training undergone at Tata Consultancy

Services were purely due to lack of knowledge in various technical aspects. The
lack of in depth knowledge in various concepts of java, database concepts,
hibernate concepts, etc. were the problems faced.
• Moreover the lack of practical know-how of these aspects did cause a few
hindrances in early stages of training but later with the help and guidance of team
members it became easier to cope up with these concepts and applications.
10.2.3 Summary of Project Work
• Firstly working in an elite organization like Tata Consultancy Services has

been and endeavor of extreme pleasure and in depth knowledge imbibing.
• Initially I did face certain hiccups because of the lack of knowledge about the
working patterns in actual software Industry. But with passage of time I coped
up with the pressures of working in a tight schedule trying to beat the clock to
complete given tasks in time slots allotted.
• To be a bit more precise about the learning during the project work I would
like to mention the technical knowledge gained about Java programming,
Spring and Hibernate Frameworks, version control tools like VSS,
development tools like Eclipse and many more such technical aspects.
• The greatest learning curve during these months was learning about the work
culture in software industries, the interpersonal skills gained through the team
work and efficient work patterns to resist against stress and work pressure yet
achieve the targets given.

REFERENCES
WEB RESOURCES
• www.javaworld.com
• www.springframwork.com
• www.javascriptkit.com
• www.java2s.com
• www.w3schools.com
• www.roseindia.net
BOOKS
• The Complete Reference

• HEAD FIRST for Java Server Pages and Servlets By – Bert Bates & Kathy Sierra
• JSP and SERVLET : BLACK BOOK Edition By – Bryan Basham
• Core Servlets AND Java Server Pages By – Marty Hall
• Guide to J2EE By – John Hunt & Chris Loftus
DDU(Faculty of Tech., Dept. of IT) 138

EXPERIENCE
Throughout the process, I enjoyed working with the organization and it was a great
learning experience. I had the privilege of going through entire Software Development
Life Cycle right from the requirement gathering phase.
Working with a globally renowned CMM level-5 company, was a great learning
experience to learn their standards and application areas. This company has widened my
horizons of knowledge to a very large extent. Till now I was exposed only to the
theoretical side of learning. With this project I have attained a lot of understanding from
the practical point of view.
This immeasurable knowledge gaining experience for me has already sown its seeds into
my career and I hope to carry it with me throughout my professional life.
This firm has not only helped me develop as a programmer but as an individual by letting
me realize my potential and believing in my capabilities and hence boosting my
confidence.
This project will always remain an integral part of my resume and I hope my wonderful
experience here would provide a boost in my career as well.
DDU(Faculty of Tech., Dept. of IT) 139

Final Print

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Print

Uploaded by

Copyright:

Available Formats

PROJECT REPORT ON

IT SOLUTIONS FOR INTELLIGENCE BUREAU

Under the guidance of

DEPARTMENT OF INFORMATION TECHNOLOGY

DDU (Faculty of Tech., Dept. of IT)

DDU (Faculty of Tech., Dept. of IT)

This is to certify that the project “IT SOLUTIONS FOR INTELLIGENCE

Prof. Harshad Prajapati

Prof. R.S. Chhajed

DDU (Faculty of Tech., Dept. of IT)

It gives us immense pleasure and satisfaction in presenting this report of System

With sincere regards,

DDU (Faculty of Tech., Dept. of IT) i

• Building up of Master Data for various applications

DDU (Faculty of Tech., Dept. of IT) ii

Quality – a key business driver

Research and Development

Working with TCS

DDU (Faculty of Tech., Dept. of IT) iii

• Business process outsourcing

The Company partners with enterprises to make their IT infrastructure flexible,

• Engineering and industrial services

DDU (Faculty of Tech., Dept. of IT) iv

• Banking and financial services

DDU (Faculty of Tech., Dept. of IT) v

DDU (Faculty of Tech., Dept. of IT) vi

2.0 Project Management 15

2.3 Project Scheduling 23

3.0 System Requirements Study 24

DDU (Faculty of Tech., Dept. of IT) vii

4.0 System Analysis 31

5.0 System Design 57

5.2 Database Design/Data Structure Design 67

6.0 Implementation Planning 84

7.0 Testing 102

DDU (Faculty of Tech., Dept. of IT) viii

8.0 User Manual 115

9.0 Limitation and Future Enhancement 132

10.0 Conclusion and Discussion 136

Fig 1.5.1 J2EE Technologies 6

Fig 1.5.2 J2EE Multi-tier Distributed Application Model 6

Fig 1.5.3 Hibernate Model 7

Fig 1.5.4 MVC Architecture 9

Fig 1.5.5 MVC 2 Architecture 11

Fig 1.5.6 MVC 2 Architecture 11

DDU (Faculty of Tech., Dept. of IT) ix

Fig 1.5.8 ITSIB flow of the process 14

Fig 2.2.2.1 Project Planning and Management Approach 18

Fig 2.2.4.1 Project Team Structure 21

Fig 2.3.1 Time Allotted to Various Activities 23

Fig 3.1.1 Typical Workflow in an organization 26

Fig 4.4.1 Navigation chart 53

Fig 4.5.1 Use Case Diagram 54

Fig 4.6.1 ER Diagram for Border Activities Details 55

Fig 4.6.2 ER Diagram for Border Activities Details 55

Fig 5.1.1 Class Diagram 58

Fig 5.1.2.1 Sequence Diagram for insert data 59

Fig 5.1.2.2 Sequence Diagram for Login 60

Fig 5.1.2.3 Sequence Diagram for Logout 60

Fig 5.1.2.4 Sequence Diagram for update data 61

Fig 5.1.2.5 Sequence Diagram for View data 62

Fig 5.1.2.6 Sequence Diagram for Report Generation 62

Fig 5.1.2.7 Sequence Diagram delete data 63