Group Number #4

Depart: CS & IT

BS (CS) 4th
Roll No: Name

25 Ubaid Ur Rehman

11 Zeeshan Ali

31 Afzal Ishaq

41 Muzammil
<Project code> Functional Specifications Document

[Railways Reservation System]

SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENT

Date of Submission
3.12.2018
Sept. 15, 2003 Page 2 of
12
<Project code> Functional Specifications Document

Sept. 15, 2003 Page 3 of

12
<Project code> Functional Specifications Document

Table of Contents

1. Introduction 4
1.1 Objectives.................................................................................4
1.2 Purpose of Document.............................................................4
1.3 Overview...................................................................................4
1.4 TECHNOLOGY (TOOLS AND CONTENTS…………………………….4

2. Functional Requirements 4
3. Non-functional Requirements 4
3.1 Performance Requirements..................................................4
3.2 Reliability Requirement..........................................................4
3.3 Security Requirements...........................................................4
3.4 Maintainability…………………………………………..........4

Sept. 15, 2003 Page 4 of

12
<Project code> Functional Specifications Document

Document Information

Category Information

Customer FAST-NU

Project <Railway Reservation System>

Document Functional Specifications

Document Version 11.5

identifier PGBH01-2005-FS

Status Draft

Author(s) <Ubaid Ur Rehman, Afzal Ishaq, Zeeshan Ali, Muzammil>

Approver(s) Shaikh Rasheed

Issue Date Dec. 3, 2018

Document Location

1. Advisor
Distribution 2. PM
3. Project Office

Sept. 15, 2003 Page 5 of

12
<Project code> Functional Specifications Document

Software process model

 Spiral model is the best process model for online railway reservation system
Spiral model combines the idea of iterative development with
systematic, controlled aspects of like waterfall model.
 Very high emphasis on risk analysis.
 It allows for increment release of the product or increment refinement
through
 each iteration around the spiral.
 Changing requirements van be accommodated.
 Allows for extensive use of prototype.
 Requirement can be captured more accurately.
 Development can be divided into smaller parts and more risky part can be
 developed earlier which help better risk management.
 Therefore, we use Spiral model for Online Railway Reservation System

Spiral Model
 It is similar to the incremental model, more emphasis placed risk analysis.
The spiral model has for phases: Planning, Risk analysis, Engineering and
Evaluation

 A software project repeatedly passes through these phases in iteration –

called spiral in this model

 The baseline spiral, starting in the planning phase, requirement is gathered

and risk is assessed. Each subsequent spiral build on the baseline spiral.

 High amount of risk analysis hence, Avoidance of risk is enhanced.

 Good for large and mission-critical project.

 Additional functionality can be added at a later date.

Sept. 15, 2003 Page 6 of

12
<Project code> Functional Specifications Document

 Software is produced early in the software lifestyle.

1.Introduction

1.1 Objective
Our project introduces railway reservation system with an objective to make the
reservation system more efficient, easier and fast. This project explores how
computer technology can be used to solve the problem of user. The main objectives
provided by this software are as follows:

 We can enquire about availability of trains

 We can reserve and cancel their seats

 We can modify the information related to

 t r a i n s

 Timetable
 Train Name
 Train Number 
  T i c k e t  F a r e

This project is dedicated to model existing railway reservation systems that aim at
development of Railway Reservation System that facilitates the railway customer to manage
their reservations and the railway administrator to modify the backend database in a user-
friendly manner

1.2 Purpose of Document

In this emerging world of computers, almost all-manual system has
switched to automated and computerized system. Therefore, we are developing
the software for “Railway Reservation System “to model the present system and to
remove the drawbacks of the present system. This project explores how computer technology
can be used to solve the problem of user. This being a big step in terms of improvement
in the railway system it is widely accepted across the country. Rather than designing
manually, we have made use of computer. Use of computer has solved many problems,
which are faced during manual calculation. Once data
are fed, it can perform accurate functions. Therefore, to reduce the complexity

Sept. 15, 2003 Page 7 of

12
<Project code> Functional Specifications Document

and efficiency a versatile and an outsourcing railway reservation system has been

developed. This project introduces railway reservation system. It explains
how reservation is being done in Indian Railways. The systematic procedure
is explained. This project is developed in C++ language. All most all the header
files have been used in this project. Proper comments have been given at
desired locations to make the project user friendly. Various functions and structures are used to
make complete use of this language

1.3 OVERVIEW:
This project aims at development of a Railway Reservation System that
facilitates the Railway customers to manage their reservations and the Railway
administrators to modify the backend databases in a User-Friendly manner. This project
includes the following functions:
 Create new database
 Add new Record
 Modify
 Display record
 Ticket reservation
 Ticket Modification
 Ticket Cancellation
 Ticket printing

1.4 TECHNOLOGY (TOOLS AND CONTENTS)

Platform Used:
 Hardware Platform:
•System Model: Compaq Presario C700

•Processor: Intel Pentium Dual Core T2370, 1.73 GHz

•RAM: 512 MB
 Software Platform:

•Operating System: Windows XP with Service Pack 3(CHT)

Sept. 15, 2003 Page 8 of

12
<Project code> Functional Specifications Document

•Compiler: Turbo C++

2.Functional Requirements
Functional requirements are requirements that define the fundamental actions that the system
must perform. The functional requirements for the system are.

Red ID Description
SRS-01 The system will be able to display the seat reservation detail having the picture of
available and reserved Train seats so that the customers will know which seats
they can reserve before they go for purchasing ticket.

SRS-02 The system should allow the administrator to add new train schedule and notify
to the driver.

SRS-03 The system should allow the administrator to edit train schedule that is already
assigned.

SRS-04 The system should allow the branch manager and administrator to view train
schedule.

SRS-05 The system should allow the administrator to delete a particular train schedule.

SRS-06 The system should allow the branch manager to request service for train when it
is required.

SRS-07 The system should allow the administrator to approve service request.

SRS-08 The system should update the status of a train which gets a service approval.

SRS-09 The system should allow the administrator to add new train which the
organization imports

Sept. 15, 2003 Page 9 of

12
<Project code> Functional Specifications Document

SRS-10 The system should allow the administrator to edit train information.

SRS-11 The system should allow the administrator to delete a specific train
SRS-12 The system should allow the administrator to view all trains with their assigned
driver information.

SRS-13 The system should allow the customer to reserve a ticket via online.
SRS-14 The system has online payment functionality

SRS-15 The system should allow the administrator to add new staff to the database /
system.

SRS-16 The system should allow the customer service agent and manager,
collectively called staff, to request sign-up
SRS-17 The system should allow the administrator to approve sign-up request.

SRS-18 The system should allow the staff to create account / register for the system.

SRS-19 The system should allow the administrator to view staff details.

SRS-20 The system should allow the administrator to delete staff account.

SRS-21 The system should allow the customer and customer service agent to cancel
reservation.

SRS-22 The system should allow the customer to rate a service / reservation via online

3.Non-Function Requirement
Non-functional requirements are those requirements that could facilitate the functional
requirements to be active without any intrusion. Here are some of the non-functional
requirements for the Railways Reservation System are.

Sept. 15, 2003 Page 10 of

12
<Project code> Functional Specifications Document

3.1 Performance Requirements

It is available during all 24 hours

• Ac first class
• Ac sleeper
• First class
•  AC chair car
• Sleeper class
•  44 types of quotas
•  8 types of trains
  • 9 types of classes  
• 162 types of concessions
• 127 types of bogies.

3.2 Reliability.
 The system is reliable enough is database permanently stored and backup can
be
kept easily,
3.3 Security Requirements
 The system secure enough, as limited privileges are given to other.
 They cannot make any changing in database
 The system must automatically log out all after a period of activity. The
system should not leave any cookies on the computer containing the user
password

3.4 Maintainability.
 The system should be easy to maintain for the administrator.

Sept. 15, 2003 Page 11 of

12
<Project code> Functional Specifications Document

Sept. 15, 2003 Page 12 of

12