Академический Документы
Профессиональный Документы
Культура Документы
Specification
for
Prepared by
Shubham Gupta
JSSATE NOIDA
28 JAN 2019
SRS DOCUMENT 1
Software Requirements Specification for Railway Reservation System
Page 2
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............................................................................................................2
2.7 Assumptions and Dependencies..........................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces.....................................................................................................................3
3.2 Hardware Interfaces.............................................................................................................3
3.3 Software Interfaces..............................................................................................................3
3.4 Communications Interfaces.................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1..................................................................................................................4
4.2 System Feature 2 (and so on)...............................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements..................................................................................................4
5.2 Safety Requirements............................................................................................................5
5.3 Security Requirements.........................................................................................................5
5.4 Software Quality Attributes.................................................................................................5
5.5 Business Rules.....................................................................................................................5
SRS DOCUMENT 2
Software Requirements Specification for Railway Reservation System
Page 1
1. Introduction
1.1 Purpose
The purpose of this source is to describe the railway reservation system which provides the train
timing details,reservation,,billing,cancelaation on various types of reservation namely.
i. Confirm Reservation for confirm Seat.
ii. Reservation against Cancellation
iii. Waiting list Reservation.
iv. Online Reservation.
v. Tatkal Reservation
1.4 References
https://www.ieee.org/
https://www.scribd.com/doc/106534282/SRS-Railway-Reservation-System
2. Overall Description
It enables us to maintain the railway train details like their timings, number of seat available and
reservation billing and cancelling the tickets.
SRS DOCUMENT 1
Software Requirements Specification for Railway Reservation System
Page 2
OMBS will have two users interface layers,first one is guest interface and the second one is Train
Management Interface.
i. The OS
ii. Windows NT
iii. Linux
iv. Windows XP
v. Windows 98
i. To allow a user post various query about ticket information available at present. User can use
any combination available
ii. To show the user the resulting list of query. This should allow users to further sort the list by
sub fields of the ticket information (e.g. price). The view should be friendly and flexible.
iii. To allow a user place a reservation
iv. To detect the conflict if a user placed two incompatible reservations.
v. To allow a user view his/her reservation
vi. To allow user modify his/her reservation
vii. To allow user to manage his/her account in RRS
keyboard,mouse,printer.
SRS DOCUMENT 2
Software Requirements Specification for Railway Reservation System
Page 3
SERVER SIDE
i. Operating System: Windows 7
ii. Processor:Intel i5
iii. Memory: 4 GB
iv. Hard Drive Capacity: 750GB
CLIENT SIDE
v. Operating System:Windows XP, Windows Vista or Windows7
vi. Browser:Internet Explorer and above.Mozilla or Google Chrome.
vii. Memory:512 MB
i. Database
ii. Microsoft office Access
iii. Web Server
iv. Programming Languages
i. Broadband Internet
ii. Broadband Internet
4. System Feature
PE1: The system shall accommodate 400 users during the peak usage time window of 8:00am to
10:00am local time, with estimated average session duration of 45 minutes.
PE2: All Web pages generated by the system shall be fully downloadable in no more than 10
seconds over a 40KBps modem connection.
PE3: Responses to queries shall take no longer than 10 seconds to load onto the screen after the
user submits the query.
SRS DOCUMENT 3
Software Requirements Specification for Railway Reservation System
Page 4
SE1: Users shall be required to log in to the RRS for their own reservation information and
modification with email address and password.
SE2: The system shall permit only authorized members who are on the list of authorized Menu
Managers to do administrator’s task.
SE3: The system shall permit customers to view only their own previously placed orders, not
orders placed by other customers.
The system shall be web based system that runs on different type of browsers such as Internet
Explorer,Mozilla,Google chrome.
There are a number of factors in the client’s environment that may restrict the choices of a designer.
Such factors include standards that must be followed, resource limits, operating environment,
reliability and security requirements and policies that may have an impact on the design of
thesystem. An SRS (Software Requirements Analysis and Specification) should identify and specify
all such constraints.
This specifies the requirements for the standards the system must follow. The standards may include
the report format and accounting properties.
SRS DOCUMENT 4