Software Requirements

Specification
for

PASSPORT AUTOMATION SYSTEM

Version 1.0 approved

Prepared by Janani.D(16CSR078)

Kongu Engineering College

12 July, 2018

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics....................................................................................................2
2.4 Operating Environment..................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................3
2.7 Assumptions and Dependencies.....................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................4
3.3 Software Interfaces.........................................................................................................................4
3.4 Communications Interfaces............................................................................................................4
4. System Features.......................................................................................................................4
4.1 System Feature 1...........................................................................Error! Bookmark not defined.
4.2 System Feature 2 (and so on).........................................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements.......................................................................................5
5.1 Performance Requirements............................................................Error! Bookmark not defined.
5.2 Safety Requirements......................................................................Error! Bookmark not defined.
5.3 Security Requirements...................................................................Error! Bookmark not defined.
5.4 Software Quality Attributes...........................................................Error! Bookmark not defined.
5.5 Business Rules...............................................................................Error! Bookmark not defined.
6. Other Requirements...................................................................Error! Bookmark not defined.
Appendix A: Glossary......................................................................Error! Bookmark not defined.
Appendix B: Analysis Models.........................................................Error! Bookmark not defined.
Appendix C: To Be Determined List..............................................Error! Bookmark not defined.

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose 

The purpose of the document is to build an online system to manage the passport registration. It is 
the interface between the Applicant and the Authority for the issue of the passport. It aims at 
improving efficiency and reducing complexities to the maximum possible extent.

1.2 Document Conventions

This document uses the following conventions
      
PAS  Passport Automation System

DB  Database

HTML Hypertext Markup Language

ER Entity Relationship

UML Unified Modeling Language

1.3 Intended Audience and Reading Suggestions

This project is a prototype for passport management system. This project is useful for the passport 
Management Team (Administration) and the Applicant.

1.4 Product Scope

 Automated System becomes essential to meet the demand for online registration . So this system uses 
several programming and database techniques to elucidate the work involved in this process. The 
Authority concerned with the issue of passport can use the system to reduce the work load and process 
the application in speedy manner . As this is a matter of National Security, the system has been carefully
verified and validated in order to satisfy it.

1.5   References
Database Management System, IEEE Software Requirement Specification format
Software Requirements Specification for <Project> Page 2

2. Overall Description

2.1 Product Perspective

The Passport Automation System 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.

2.2 Product Functions

• Secure Registration of information by the Applicants.

•Schedule the applicants an appointment for manual verification of original documents.
• Panel for Passport Application Status Display by the Administrator.
• SMS and Mail updates to the applicants by the administrator.
• Administrator can generate reports from the information and is the only authorized personnel to
add the eligible application information to the database.

2.3 User Classes and Characteristics

• Applicant
- They are the people who desires to obtain the passport and submit the information to the database.
• 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.
• 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. He has been vetoed
with the power to decline an application by suggesting it to the Administrator if he finds any
discrepancy with the applicant. He communicates via this PAS.

2.4 Operating Environment

Operating system :  Windows/Linux/Android/ios
Processor :  Intel or AMD
Hard Disk : 1GB
RAM : 256MB
Software Requirements Specification for <Project> Page 3

2.5 Design and Implementation Constraints

•The applicants require a computer to submit their information.

• The user has to be careful while submitting the information. Much care is required.

Constraints :

• The applicants require a computer to submit their information.

• Although the security is given high importance, there is always a chance of

intrusion in the web world which requires constant monitoring.

• The user has to be careful while submitting the information. Much care is required.

2.6 User Documentation

2.7 Assumptions and Dependencies

 The Applicants and Administrator must have basic knowledge of computers and English
Language.

 The applicants may be required to scan the documents and send.

 Each User must have a UserID and password

 There must be a Administrator

 Internet connection is a must

Software Requirements Specification for <Project> Page 4

 Proper browsers should be installed in the user’s system.

3. External Interface Requirements

3.1 User Interfaces

• Applicant
- They are the people who desires to obtain the passport and submit the information to the database.
• 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.
• 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. He has been vetoed
with the power to decline an application by suggesting it to the Administrator if he finds any
discrepancy with the applicant. He communicates via this PAS.

3.2 Hardware Interfaces

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

3.3 Software Interfaces

• Front End Client - The applicant and Administrator online interface is built using JSP and HTML.
The Administrator’s local interface is built using Java.
• Web Server
- Glassfish application server (Oracle Corporation).
• Back End
- Oracle database.
Software Requirements Specification for <Project> Page 5

3.4 Communications Interfaces

Online Passport registration uses internet. Hence, it uses HTTP for transmission of data. This protocol allows 
easy interaction between client and server.

4. System Features
In this project, we have developed a system which is used for applying new passport or renewal of a passport
after the expiry date of passport .

3.1 Description and Priority
The hardware component is suddenly burn or broke down due to over burden, while creating the
project. If the software for passport automation, it is works very fast, after some times software
works very slowly because of virus attack.
3.2 Stimulus/Response Sequences
The system is explained through the activity diagram.
3.3 Functional Requirements
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: visit the passport seva kendra in scheduled appointment.
Post-function: Verify the information and enquiry to applicant.
Validity checking:
Pre-function: Checking validity date.Appointment date is valid for 1 year
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.
Software Requirements Specification for <Project> Page 6

5. Other Nonfunctional Requirements

5.1 Performance Requirements
In order to assess the performance of the system ,the following should be given importance
1.Response time
2.Workload
3.Scalability
5.2 Safety Requirements
If there is extensive damage to a wide portion of the database due to failure, such as a disk crash, the
recovery method restores a past copy of the database that was backed up to archival storage
(typically tape) and reconstructs a more current state by reapplying or redoing the operations of
committed transactions from the backed up log, up to the time of failure.
5.3 Security Requirements
Security systems need database storage just like many other applications. However, the special
requirements of the security market mean that vendors must choose their database partner carefully

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and

distribute this document.

Software Requirements Specification for <Project> Page

11 4.4 Software Quality Attributes

AVAILABILITY: Server should be available for all the applicants concurrently without any delay
CORRECTNESS: Information provided by the user should be true and valid
MAINTAINABILITY: The administrators in chargers should maintain correct information of
applicant in database
USABILITY: The system should be user-friendly and should satisfy a maximum number of
customers needs.

5.5 Business Rules
Software Requirements Specification for <Project> Page 7

1. The user need a gmail account to login

2. The user should know the username and password
3. The user should have to scan DOB proof, Identity proof with photo, residence proof and
nationality proof

6. Other Requirements
1. The applicant should have credit or debit card or internet banking for online payment
2. The applicant should be provided with the registration ID through email
3. The applicant should bring his/her ID during Verification at Passport seva kendra

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and

distribute this document.