Passport Automation System

1.Objective:
To develop the passport automation system software using UML language. It is the interface
between applicant and authority responsible for issue the passport. It aims at improving
efficiency and reducing complexities.
2.Scope:
 The system provides the online interface to the user where we can fill their form and
personal detail with necessary proof.The authority concerned with the issue of passport
can use this system to reduce is workload and process it speedy manner.
 It provides communication platform between administrator and applicant.
 To transfer the data between passport authority and local police verifying the applicant’s
information.
3.Project description:
 In this project we can develop the 5 modules such as login, fill the form with necessary
proof, verifying the applicant’s information, validity checking and issue the passport for
that particular applicant.
 In this login module, we can perform that that perform that enters into the login website
for the different actors, and then fill for the can be done by the primary and verification,
validation checking and issuing the passport can be done for the supporting actor.
PROBLEM STATEMENT
1.Passport Automation System is used in the effective dispatch of passport to all of the
applicants.This system adopts a comprehensive approach to minimize the manual work and
schedule resources, time in a cogent manner.
2.The core of the system is to get the online registration form filled by the applicant whose
testament is verified for its genuineness by the Passport Automation System with respect to the
already existing information in the database.
3.This forms the first and foremost step in the processing of passport application. After the first
round of verification done by the system, the information is in turn forwarded to the regional
administrator's office.
4.The application is then processed manually based on the report given by the system, and any
 forfeiting identified can make the applicant liable to penalty as per the law.
5.The system forwards the necessary details to the police for its separate verification whose
report is then presented to the administrator. After all the necessary criteria have been met, the
original information is added to the database and the passport is sent to the applicant.
4.Requirements:
*Functional requirements:
 It is defined as how they should react in the particular input and how the system should
react in the particular situations and what the system do not do.
 In this project, login as functional requirement. In that functional requirement we may
check the user name and password is correct or not. After checking entity of login, we
can show the detail based on the type of actor.
Ø Analysis:
In this place, the project requirement is analyzed and availability of requirement is seen.
Ø Design:
Project manager makes the design of the project.
Ø Implementation:
The construction of project is done and coding is developed.
Ø Maintenance:
In this the software maintenance and the ways to avoid the drawback of software is made.
Hardware requirements:
 Processor: Pentium –IV
 Hard drive: 320 GB
 RAM: 4GB
 DVD-Drive: 1
Software requirements:
 Operating system : Windows XP
 Front-end : C# .Net
 Back-end : Ms-Access Database
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS
1. Administrator - Refers to the super user who is the Central Authority who has been
vested with the privilege to manage the entire system. It can be any higher official in
the Regional Passport Office of Ministry of External Affairs.
2. Applicant - One who wishes to obtain the Passport.
3. PAS - Refers to this Passport Automation System.

OVERVIEW
SRS includes two sections overall description and specific requirements - Overall
description will describe major role of the system components and inter-connections.
Specific requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION

PRODUCT PERSPECTIVE

The PAS acts as an interface between the 'applicant' and the 'administrator'. This
system tries to make the interface as simple as possible and at the same time not risking
the security of data stored in. This minimizes the time duration in which the user receives
the passport.

SOFTWARE INTERFACE
1. Front End Client - The applicant and Administrator online interface is built using C# .Net
2. Back End – MS Access database

HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have
access to the database in the server.

USER CHARACTERISTICS
1.Applicant - They are the people who desires to obtain the passport and submit the
information to the database.
2.Administrator - He has the certain privileges to add the passport status and to approve the
issue of passport. He may contain a group of persons under him to verify the documents and
give suggestion whether or not to approve the dispatch of passport.
3.Police - He is the person who upon receiving intimation from the PAS, perform a personal
verification of the applicant and see if he has any criminal case against him before or at
present.

CONSTRAINTS
1. The applicants require a computer to submit their information.
2. Although the security is given high importance, there is always a chance of intrusion in
the web world which requires constant monitoring.
5.Module description:
In this project consists of 5 modules, namely, login, fill the form, verifying applicant details,
validity check.
 Login:
In this module, we can perform operation such as enter the user name and password. If the
user name and password is correct then it can be entered into the specific web page. Otherwise
re-enter the user name and password at the particular time’s only.
 Fill the application:
When we are go to fill the application form before you can tell either apply for new passport
or renewal the old passport. We can fill the application form with corresponding ID proof and
address proof and then submit the form.
 Verification of the form:
After submission of the form, to the responsible authority are verified that given information
is true or not and they are forwarded to local police. Local police enquiry that corresponding
information is true or not. After collecting the information it will forwarded to higher authority.

 Validation checking:
When the customer, go to apply for the airline ticket. The passport must be checked if it
is valid or not. Every passport as valid up to 5 years only. The applicant’s must renewal the
passport for every five years.
 Issue the passport:
After verification and validation the passport can be issued to the applicant through the
post. Then the passport can be checked and signed the post record the accepted the passport.
6.Domain model:
A domain is a visual representation of conceptual classes or real situation object in a domain.
* In object-oriented analysis, the domain model is the most important.
* It illustrates the concept in the domain.
* It acts as a source of inspiration for designing some software objects.
In our project, when we are entered into the corresponding web page, we can perform the
operation such as status information, fill the form, verification is done in the web site.
8.Logical architecture:
The logical architecture is the large-scale organization of software classes into packages,
sub classes and layers. This is called logical architecture.
9.Risk architecture:
It defines that some process loss, or any problem can be faced while creating the project.
*Software risk:
If the software for passport automation, it is works very fast, after some times software
works very slowly because of virus attack. It can be rectified by the new way.
*Hardware risk:
If the hardware component is suddenly burn or broke down due to over burden, while
creating the project.
*Non-function risk:
Due to failure of Hardware and software, then it can’t be completed with in the time
schedule and budget schedule.
10.Gantt chart:
It describes the time schedule for the planning to complete the core product and after
complete of core product, what is the time taken for the project action of core project.
11.PRE-FUNCTION AND POST-FUNCTION:
*Login:
Pre-function: enter the username and password.
Post-function: Verify the username and password.
*Application form:
Pre-function: Fill the form with details.
Post-function: Submit the form.
*Verification:
Pre-function: Taking the applicant form.
Post-function: Verify the information and enquiry to applicant.
*Validity checking:
Pre-function: Checking validity date.
Post-function: Renewal the old passport.
*Issue the passport:
Pre-function: Send the passport to applicant address.
Post-function: Receive the passport form the postman.
12. Technical service layer:
This shows the interaction between the actor and object in sequence diagram. The forward arrow
from system admin to authority it indicates verifies the applicant’s details. The system admin
verify the application details and then the authority issue the passport.
13. Domain object layer:
After composing the technical service layer from partial layer architecture. Since we are going to
generate the coding in java/VB the project domain is experienced in java/VB using rational rose
software.
14. User interface layer:
This layer shows the interface with sequence diagram by changing the sequence symbol. The
sequence symbol is replaced by an actor symbol, which shows interface between use case and
sequence diagram.
15.UML package diagram:
An UML package diagram provides a way to group elements.
A UML package can group anything classes other package is very common. A UML package is
a general concept then simply a java package or .net name space through a UML package can
represent two and more forward allow from strew manage to customer.

UML DIAGRAM

1.Use Case diagram

2.Class diagram

3.Interaction diagram
 4.Sequence diagram

5.Collaboration diagram

6.State Chart diagram

7.Activity diagram

8.Component diagram

9.Deployment diagram

10.Package diagram

USE CASE DIAGRAM

A use case is a methodology used in system analysis to identify, clarify, and

organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It is represented using ellipse.
DOCUMENTATION OF USECASE DIAGRAM
1. The actors in use case diagram are Applicant, regional administrator, database,
passport Administrator, Police.
2. The use cases are Login, givedetails, logout, collectdetails, verification, issue. The
actors use the use case are denoted by the arrow
3. The login use case checks the username and password for applicant, regional
administrator, passport administrator and police.
4. The submit details use case is used by the applicant for submitting his details
5. The check status use case is used by the applicant for checking the status of the
application process.
6. The get details, verify and store verification use case is used by passport administrator,
regional administrator, and police.
7. The details use case is used for getting the details form the database for verification.

DOCUMENTATION OF CLASS DIAGRAM

1. APPLICANT-The applicant has attribute such as name and password and

operations are login, givedetails and logout. The applicant login and fill the details
that are required for applying the passport .After applying the person can view the
status of the passport verification process
2. THE DATABASE-The database has attributed such as name and operation is
store. The purpose is to store the data.
3. REGIONAL ADMINISTRATOR- The regional administrator has attribute such
as name and operation are get details, verify details and send. The regional
administrator get the details form database and verify with their database
 4. PASSPORT ADMINISTRATOR-The passport administrator has attributed such
as name and operation are get details, verify details and issue. The passport
administrator get the details form database and verify with their database , update
the verification and issue the passport
5. THE POLICE-The police has attribute such as name and operation are get details,
verify details and send. The police get the details form database and verify with
their database , update the verification in the database

SEQUENCE DIAGRAM
A sequence diagram shows an interaction arranged in time sequence. It shows
object participating in interaction by their lifeline by the message they exchange arranged
in time sequence. Vertical dimension represent time and horizontal dimension represent
object.
OBJECT : Applicant, Enquiry officer, Passport management system
DOCUMENTATION OF SEQUENCE DIAGRAM.

1. The applicant login the database and give his details and database store the details.

2. The passport administrator get the details from the database and do verification and
the forward to regional administrator.

3. The regional administrator get details form passport administrator and perform
verification and send report to passport administrator.

COLLABORATION DIAGRAM

A collaboration diagram is similar to sequence diagram but the message in number

format. In a collaboration diagram sequence diagram is indicated by the numbering the
message. A collaboration diagram, also called a communication diagram or interaction
diagram, A sophisticated modeling tool can easily convert a collaboration diagram into a
sequence diagram and the vice versa. A collaboration diagram resembles a flowchart that
portrays the roles, functionality and behavior of individual objects as well as the overall
operation of the system in real time

STATE CHART DIAGRAM

The state chart diagram contains the states in the rectangle boxes and starts in
indicated by the dot and finish is indicated by dot encircled. The purpose of state chart
diagram is to understand the algorithm in the performing method.

DOCUMENTATION OF STATE CHART DIAGRAM

1. The states of the passport automation system are denoted in the state chart diagram
2. Login state represent authentication for login the passport automation system.
3. In this state, it checks whether the applicant has provided all the details that is
required.
4. Police, regional administrator and passport administrator get necessary details and
verification of the applicant are denoted from the Get detail state and verification state.

ACTIVITY DIAGRAM
An activity diagram is a variation or special case of a state machine in which the
states or activity representing the performance of operation and transitions are triggered by
the completion of operation. The purpose is to provide view of close and what is going on
inside a use case or among several classes. An activity is shown as rounded box
containing the name of operation.
DOCUMENTATION OF ACTIVITY DIAGRAM

1. The activities in the passport automation system are login, submit details, get
details, issue passport and penalty and verification.
2. In the login activity applicant give username and password and then login into the
passport automation system after then fill the details that are required for
application.
3. After the verification procedure completed successfully the passport is issued to the
applicant.

COMPONENT DIAGRAM

The component diagram is represented by figure dependency and it is a graph of

design of figure dependency. The component diagram's main purpose is to show the
structural relationships between the components of a systems. It is represented by boxed
figure. Dependencies are represented by communication assosiation.
DOCUMENTATION OF COMPONENT DIAGRAM

1. The components in the passport automation system are passport automation

system, applicant, passport administrator, regional administrator, and police.
2. Applicant ,passport administrator, regional administrator and police are dependent
on passport automation system are shown by the dotted arrow

DEPLOYMENT DIAGRAM

It is a graph of nodes connected by communication association. It is represented by

a three dimensional box. A deployment diagram in the unified modeling language serves
to model the physical deployment of artifacts on deployment targets. Deployment
diagrams show "the allocation of artifacts to nodes according to the Deployments defined
between them. It is represented by 3-dimentional box. Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two
types

DEVICE NODE

A physical computing resource with processing and memory service to execute

software, such as a typical computer or a mobile phone.

EXECUTION ENVIRONMENT NODE

This is a software computing resource that runs within an outer node and which
itself provides a service to host an execute other executable software element.
DOCUMENTATION OF DEPLOYMENT DIAGRAM

The device node is passport automation system and execution environment node
are applicant passport administrator, regional administrator, and police.

PACKAGE DIAGRAM

A package diagram is represented as a folder shown as a large rectangle with a top

attached to its upper left corner. A package may contain both sub ordinate package and
ordinary model elements. All uml models and diagrams are organized into package. A
package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements
in the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are
1. User interface layer
2. Domain layer
3. Technical services layer

DOCUMENTATION OF PACKAGE DIAGRAM

The three layer in the passport automation system are user interface layer, domain layer,
technical service layer

1. The user interface layer- represents the user interface components such as web,
applicant, passport administrator, police, and regional administrator.
2. The domain layer- has major actions such as give and get details, verification and
issues.
3. Technical service layer- authenticated user only can access the technical services.
25. Implementation:
After completing the 8 diagrams we have to select the respective programming language
domain from the tool menu for each diagram we have to select main class and generate code for
respective diagram.
FORM1:
26. Testing:

 After completing the code generation for each diagram. Select the tool menu under
quality architect performs unit testing and scenario testing for each code.
 Testing activities are made several types of testing is carried on.
27. Conclusion:

Thus, the above project for passport automation system has been successfully executed
and codes are generated.