Railway Reservation System

Software Requirements
Specification
For
RAILWAY RESERVATION
SYSTEM
Version 1.0 approved
Prepared by - Pammi Kumari
Silicon Institute of Technology, Bhubaneswar
<23.07.2019>
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
Railway Reservation System 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......................................................................................................................................2
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.......................................................................................................................4
2.7 Assumptions and Dependencies.....................................................................................................4
3. External Interface Requirements...........................................................................................4
3.1 User Interfaces................................................................................................................................4
3.2 Hardware Interfaces........................................................................................................................4
3.3 Software Interfaces.........................................................................................................................4
3.4 Communications Interfaces............................................................................................................4
4. System Features.......................................................................................................................5
4.1 System Feature 1............................................................................................................................5
4.2 System Feature 2 (and so on)..........................................................................................................7
5. Other Nonfunctional Requirements.......................................................................................8
5.1 Performance Requirements.............................................................................................................8
5.2 Safety Requirements.......................................................................................................................8
5.3 Security Requirements....................................................................................................................8
5.4 Software Quality Attributes............................................................................................................8
5.5 Business Rules................................................................................................................................9
6. Other Requirements................................................................................................................9
Appendix A: Glossary....................................................................................................................9
Revision History
Name Date Reason For Changes Version
Railway Reservation System Page 1
1. Introduction
1.1 Purpose
The purpose of this project is to describe the Railway Reservation System which provides
the train timing details, reservation, billing and cancellation on various types of reservation
namely,
 Confirm Reservation for confirm Seat.

 Reservation against Cancellation.
 Waiting list Reservation.
 Online Reservation.
 Tatkal Reservation.
1.2 Document Conventions
Title
 Font Size- 32 pt
 Font – Arial
 Font Style- Bold
 Alignment- Right
Heading
 Font – Arial
 Font Style- Italics
 Alignment- Left
Sub Heading
 Font – Arial
 Alignment- Left
Simple text
 Font Size- 11pt
 Font – Arial
 Alignment- Left
Line Spacing- 1:5
Margin- L-R-T-B-“1”
1.3 Intended Audience and Reading Suggestions
 Developers
 Project Managers
 Marketing Staff
 Product testers
 Documentation Writers
 Users
1.4 Product Scope
“Railways Reservation System” is an attempt to simulate the basic concepts of an online

Reservation System. The system enables to perform the following functions:
 Search for train
 Booking of a selected train
 Payment
 Cancellation
 Freight Revenue enhancement
 Passenger Revenue enhancement
 Improved & optimized service
1.5 References
 Geeks for geeks

 SlideShare
 www.programforu.com
2. Overall Description
2.1 Product Perspective
Before the automation, the system suffered from a lot with traditional drawbacks. Hence
the railways reservation system is proposed with the following features:
 The computerization of the reservation system will reduce a lot of paperwork and
hence the load on the administrative staff.
 The machine performs all calculations. Hence chances of error are nil.
 The passenger, reservation, cancellation list can easily be retrieved, required
addition, deletion or updation can be performed.
 The system provides for user-ID validation, hence unauthorized access is
prevented.
2.2 Product Functions
 Search: This function allows the booking agent to search for trains, which are
available between the two travel cities. It then displays a list of train available
between the designated cities on the specified date and time.
 Selection: This function allows a particular train to be selects from the displayed list.
All the details of the train are:
o Train number
o Date, time and place of departure
o Date, time and place of arrival
o TRAIN Duration
o Fare per head
o Number of stoppages- 0,1,2….
 Review: If the seats are available, then the software prompts for the booking of
train. The train information is shown.
 Traveler Information: It asks for the details of all the passengers supposed to travel
including name, address, telephone number and e-mail id.
 Payment: It asks the agent to enter the various card details of the person
making the reservation.
o Credit card type

o Credit card number
o CVC number of the card
o Expiration date of the card
o The name on the card
 Cancellation: The system also allows the passenger to cancel an existing

reservation.
 Discount Coupons: It allows a user to avail discount on their bill if any.
2.3 User Classes and Characteristics
 Knowledgeable user
 No voice user’
 Expert user
 Capable for providing transaction for 24 hours per day.
2.4 Operating Environment
 It can be opened on Windows 98,XP,7,8,1,10,Linux,Unix.

 One can access it using any Internet Browser or Explorer.
 The processor should be at-least Pentium 3 or above.
 This site support graphics. For the clear view of graphics and to see video latest
flash player should be installing.
2.5 Design and Implementation Constraints
 Users must be having the train details.

 For discount they must valid discount coupons.
 Full Document Verification required.
 Easily cancellation.
 The computers must be equipped with web browsers such as Internet explorer.
 Response time should be less than a minute.
 To implement online user help, link and search fields shall be provided
2.6 User Documentation
 User manuals
 Tutorials
 Filters available
 Audience Analysis Template
 FAQs
 Embedded Assistance
 Support Portals
2.7 Assumptions and Dependencies
 Booking Agents will be having a valid user name and password to

access the software
 The software needs booking agent to have complete knowledge

of reservation system.
 Software is dependent on access to internet.
3. External Interface Requirements
3.1 User Interfaces
The user who wants to search for trains, train timing details can easily perform their task
without the burden of login into the system. But if a user wants to book a train or cancel or
payment, then they have to login into the system. Payment is very secure in this system.
Users are even provided with various discount coupons. There is no burden of standing in
a queue for platform tickets as one can easily book it online.
3.2 Software Interfaces
An Oracle DBMS will be used to manage the database and any changes made to it.
Furthermore, the DBMS will make regular backups of the database and generate reports
regularly so that they can be accessed by the CRM. The Apache server between the client
and the database will handle all communication, and the server will run on a Linux
operating system. Furthermore, the HTML pages must be implemented such that they can
be displayed on two common browsers: Netscape and Internet Explorer.
Information about the products used for the ARRS:
(1) Name: Oracle

(2) Mnemonic: Oracle
(3) Version Number: 8
(4) Source: Oracle
(1) Name: Linux

(2) Mnemonic: Linux
(3) Version Number: 6.2
(4) Source: Unix
(1) Name: Internet Explorer

(2) Mnemonic: IE
(4) Source: Microsoft
(1) Name: Netscape Communicator

(2) Mnemonic: Netscape Communicator
(4) Source: America Online
(1) Name: Apache

(2) Mnemonic: Apache
(3) Version Number: 1.3.14
(4) Source: Apache Software Foundation
3.3 Communications Interfaces
 OTP will be send through SMS.

 The system can be accessible by any browser.
 E-mail Interface- This interface uses the SMTP/POP services provided by third party
to send emails to the required user. This service will notify users with required
actions through a conventional medium.
4. System Features
4.1 Login
4.1.1 Description and Priority
The user will be able to login. It is a high priority feature.
4.1.2 Stimulus/Response Sequences
In the Login page either User can sign-in if he is not a new user or can sign-
up if he is a new user. For Login one just has to enter the registered email id
and the password and for the new user they have to fill the registration form
giving other useful details like phone number, address etc.
4.1.3 Functional Requirements
REQ-1: Login User
REQ-2: New User
4.2 Search
The user will be able to search a particular train It’s the early phase before
any booking.
The user will be able to search a particular train as per his needs. He will be
able to check the discount or EMI availability.
REQ-1: Search
REQ-2: Check availability
REQ-3: Discount Coupons.
4.3 Selection
4.31 Description and Priority
The user will be able to select a particular train as per his needs.
The user will be able to select a particular train as per his needs. He will be
able to check the discount or EMI availability.
REQ-1: Train number
REQ-2: Date and time of availability
REQ-3: Place
4.4 Review
If the seats are available, then the software prompts for the booking of train.
The train information is shown.
After the user has selected a particular train and if seats are available one
can easily book a train.
REQ-1: Selected train.
4.5 Traveler Information
It asks for the details of all the passengers supposed to travel including,
name, address, telephone number and e-mail id.
One can easily book a train by giving the personal information.
REQ-1: Name
REQ-2: Address
REQ-3: Telephone Number.
REQ-4: Email
REQ-5: Number of persons
REQ-6: Age
4.6 Payment
It asks the agent to enter the various card details of the person making
the reservation.
For successfully booking a ticket one has to provide the mode of payment by
different cards or any. After the completion the ticket is confirmed and one
can travel as per his/her bookings.
o REQ-1: Credit card type
o REQ-2: Credit card number
o REQ-3: CVC number of the card.
o REQ-4: Expiration date of the card
o REQ-5: The name on the card.
4.7 Cancellation
The system also allows the passenger to cancel an existing reservation.
If one wish to cancel an existing reservation than he can do this easily by
providing various details like train number, place, PNR number, mobile
number, etc.
REQ-1: Train Number
REQ-2: Place
REQ-3: Telephone Number.
REQ-4: Email
REQ-5: PNR Number
4.8 Discount
The system also allows the passenger to cancel avail the discount coupons
if any.
If any coupons are available the you can easily use it by providing coupon
code in the bill if it is valid.
REQ-1: Coupon code
REQ-2: Bill
5. Other Nonfunctional Requirements
5.1 Performance Requirements
 Scalability- System should be able to handle a large number of users. For example
handling thousands of users at the same time.
 Speed- The application should be fast. It should not slow down with increase of
number of users. Search functionality should be fast to enable better end-user
experience. The system should be quick enough to be able to respond to the user
actions within a short period of time.
5.2 Safety Requirements
 Do not press the back button during ant transaction.

 Do not share your OTP with anyone.
 Provide the authenticated documents.
 Once the transaction is done money will be not refunded unless it is manually
canceled.
5.3 Security Requirements
 During user registration, the given email address is validated.

 Re-Captcha service is used during registration for human identification.
 We are transferring all data via HTTPS i.e. via SSL so that the data is encrypted
during the transit. Thus safeguarding the user information.
5.4 Quality Attributes
 It can be opened with any browser.

 It will be easy to operate.
 It will show easy to locate the buttons.
 It uses simple English Language so that user cannot confuse with terms.
 It will be easy to upgrade.
5.5 Business Rules
 The user should know the pin of the ATM card.

 The user will be notified about transaction made or of the status of their bookings.
 In case of any errors, revert any changes made to the system.
 The amount the user is trying to withdraw shouldn't exceed the account balance.
6. Other Requirements
Appendix A: Glossary
Some of the few ACRONYMS, ABBREVIATIONS used in Ticket Reservation System are as
follows:
 NTES- National Train Enquiry System
 IVRS- Interactive Voice Response System
 PRS- Passenger Reservation System
 RAC- Reservation against Cancellation.

Railway Reservation System

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Railway Reservation System

Загружено:

Авторское право:

Доступные форматы

Software Requirements

Version 1.0 approved

Prepared by - Pammi Kumari

Silicon Institute of Technology, Bhubaneswar

 Confirm Reservation for confirm Seat.

Line Spacing- 1:5

“Railways Reservation System” is an attempt to simulate the basic concepts of an online

 Geeks for geeks

o Credit card type

 Cancellation: The system also allows the passenger to cancel an existing

 Discount Coupons: It allows a user to avail discount on their bill if any.

 It can be opened on Windows 98,XP,7,8,1,10,Linux,Unix.

 Users must be having the train details.

 Booking Agents will be having a valid user name and password to

 The software needs booking agent to have complete knowledge

 Software is dependent on access to internet.

Information about the products used for the ARRS:

(1) Name: Oracle

(1) Name: Linux

(4) Source: Unix

(1) Name: Internet Explorer

(1) Name: Netscape Communicator

(1) Name: Apache

 OTP will be send through SMS.

 Do not press the back button during ant transaction.

 During user registration, the given email address is validated.

 It can be opened with any browser.

 The user should know the pin of the ATM card.

Вам также может понравиться