Requirement Specification

Ex No: 2.1
SRS Generation for Passport Automation System & Library Management System

Aim:
To generate SRS document for Passport Automation System and Library Management
System using Rational Requisite Pro.
SRS Generation for Passport Automation System

1.0 Introduction
Passport Automation System is an interface between the Applicant and the Authority
responsible for the Issue of Passport. It aims at improving the efficiency in the Issue of Passport
and reduce the complexities involved in it to the maximum possible extent.

1.1 Purpose
If the entire process of 'Issue of Passport' is done in a manual manner then it would take
several months for the passport to reach the applicant. Considering the fact that the number of
applicants for passport is increasing every year, an Automated System becomes essential to meet
the demand. So this system uses several programming and database techniques to elucidate the
work involved in this process. As this is a matter of National Security, the system has been
carefully verified and validated in order to satisfy it.

1.2 Scope
• The System provides an online interface to the user where they can fill in their personal details
and submit the necessary documents (may be by scanning).
• The authority concerned with the issue of passport can use this system to reduce his workload
and process the application in a speedy manner.
• Provide a communication platform between the applicant and the administrator.
• Transfer of data between the Passport Issuing Authority and the Local Police for verification of
applicant's information.
• Users/Applicants will come to know their status of application and the date in which they must
subject themselves for manual document verification.

1.3 Definitions, Acronyms and the Abbreviations

• 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.
• Applicant - One who wishes to obtain the Passport.
• PAS - Refers to this Passport Automation System.
• HTML - Markup Language used for creating web pages.
• J2EE – Java 2 Enterprise Edition is a programming platform and it is the partof the java
platform for developing and running distributed java applications.
• HTTP - Hyper Text Transfer Protocol.
• TCP/IP – Transmission Control Protocol/Internet Protocol is the communication protocol used
to connect hosts on the Internet.

1.4 References
IEEE Software Requirement Specification format.

1.5 Technologies to be used

• HTML • JSP • Javascript
• Java • XML • AJAX

1.6 Tools to be Used

• Eclipse IDE ( Integrated Development Enivronment)
• Rational Rose tool ( for developing UML Patterns)

1.7 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.

2.0 Overall Description

2.1 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.

2.2 Software Interface

• Front End Client - The applicant and Administrator online interface is built using JSP and
HTML. The Administrators's local interface is built using Java.
• Web Server - Glassfish application server(Oracle Corporation).
• Back End - Oracle database.

2.3 Hardware Interface

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

2.4 System 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.5 User 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.6 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.7 Use Case Model Description

The usecase model is a representation of the interaction between the users and the system. It
captures the goals of the users and the responsibility of the system to the users. It is a special
flow of events through the system. Grouping of usecases can manages the complexities and
reduce the number of usecases in the package. The usecase model describes the uses of the
system and show the courses of events that can be performed. A usecase is an interaction
between user and system; it captures the goals of the user and the responsibility of the system to
its users. It defines what happens in the system when the usecase is performed.

2.8 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.
Result: Thus the software requirements specification for passport automation system was
studied.
SRS Generation for Library Management System

Contents
1. Introduction
1.1 Purpose
1.2 Scope
2. Overall Description
2.1 Individual phases in the project
2.1.a. Product perspective
2.1.b. System interface
2.1.c. user interface
2.1.d.hardware interface

2.2 Software interface

3.Communication interface
3.1. Memory constraints
3.2.Operations
3.3 Product functions
3.4.User characteristics
4. Constraints
5. Assumptions and dependencies
6. Specific requirements
6.1. external interface requirements
6.1.a. User interface
6.1.b. Screen formats/organization
6.1.c. Windows formats/organization
6.1.d. Data format
6.1.e. End message
7. Use case specification
1.Introduction
1.1 Purpose
 The main purpose of specification is to provide a clear view of requirements of LIBRARY
MANAGEMENT SYSTEM to the devoloper. This will be given to the customer for their reference.

1.2.Scope
The main purpose of LIBRARY MANAGEMENT SYSTEM is to specify what data and function are
to be given and what sorts result will be produced for the customers and business analyst for their
references.
2.Overall Description
2.1.Individual phases in the project
2.1.a. Product perspective
This software runs on a stand alone personal computers which is used to maintain the details of
the borrowers,books and membership details.
2.1.b.System interface
This software does not require any external system for running the software.
2.1.c. User interface
Necessary details are entered and consequent results appear in the window.
2.1.d Hardware interface
Printer should be interfaced with software for getting the bill for fine amount paid.
2.2 Software interface
 Window 98 or higher version
 Turbo c/turbo c++

3.Communication interface
LAN connection is necessary to interact with the system in the library for updating the borrowers
details.
3.a. Memory constraints
The software requires a disk space of 256mb for each system it is loaded.

3.b Operations
The software is active whenever necessary and can be used to store the borrowers details,membership
details and available book details.
3.c.Product functions
The major function include
 Availability of books.
  New availability of books
 Borrower’s details
 Membership details
 Bill generation

3.d.User characteristics
The software has a simple interface that even uses who has no experience of using this software before
can use it. The only thing is that the user needs to know English.
4.Constraints
 Hardware limitations:
There must be 512MB on-board memory in the central server system.
 Control functions
In case of error and service problems,proper error handling and data recovery mechanism must
be included.
 Parallel operations:
Rank calculation
 Reliability requirements
Use of special/blank characters must be avoided.
 Safety/security consideration
The application must be terminated properly for proper functioning of software.

5.Assumptions and Dependencies

The details entered should be valid during borrowers details and bill generation phases.
6. Specific Requirements
6.1 External Interface Requirements
6.1.a. User interface
The user interface of the system is simple and it can be accessed by the users even if they don’t have
experience in accessing it,provided they must have knowledge in English.
6.1.b. Screen formats/Organisation
By selecting each option it will show the another window where the analyst will be provided with the
corresponding details.

6.1.c Windows format/organization

By selecting each option it will show the another window where the analyst will be provided with
corresponding details.
6.1.d Data format
The users are allowed to enter both alphabet and numbers whenever necessary.
6.1.e. End message
If an invalid data is entered ,then it will ask for correct data entry by displaying a message.
7. Use case specification
Use case 1: Login
7.1. Brief Description
This feature describes about the login process in the LIBRARY MANAGEMENT SYSTEM.
7.2. Flow of details
7.2.a. Basic flow
 Enter the username and password.
 If the username and password is valid then the user will get access to the system.

7.2.b. Alternative flow:

If the username and password are invalid , then access is denied to software and again the login
process should be done.
7.3. Specific Requirement
This login feature unauthorized access to the system.
7.4 Pre condition
The analyst should login only using their respective id and password.

7.5. Post conditions

The software validates the entered login id and password.
Use case 2-Store Borrowers details
7.1 Brief Description
This feature describes about the gathering of borrowers details in the LIBRARY MANAGEMENT
SYSTEM
7.2. Flow of Details
7.2.a. Basic flow
 Enter Borrowers details
 If valid input is provided then save those records for future retrieval.

7.2.b. Alternative flow

If the borrowers details should be saved for efficient analysis of progress of the borrowers.
7.3 Pre condition
 The borrowers details should be stored only if all the fields are filled correctly.
7.5 Post conditions
NIL
Use case 3 – To Check the availability of books
7.1. Brief Description
This feature describes about gathering information about the books available in the library management
system.
7.2. Flow of details
7.2.a. Basic flow
Check the availability of books and update the availability in the system.
7.2.b. Alternative flow
If the availability of books is invalid then the books cannot be stored.
7.3. Specific Requirements
The availability of books should be checked for efficient usage of borrowers details
7.4. Pre conditions
The availability of books can be stored only if all the fields are filled correctly
7.5. Post conditions
Nil
Use case 4– Bill Generation
7.1. Brief Description
This feature gives the complete description of all events made in the LIBRARY MANAGEMENT
SYSTEM.
7.2. Flow of details
7.2.a. Basic flow
Generate the bill if any request has been made.
7.3. Specific Requirements
The bill generation will be useful in determining the progress of the users.
7.4. Pre condition
At least one entry should have been made prior to Bill generation.
7.5. Post condition
NIL
Result:
Thus the SRS document for Passport Automation System and Time Table Generation
System was generated using Rational Requisite Pro in Rational Rose.