A Software Requirement Specification

ON

RAILAY RESERVATION SYSTEM

Submitted by:
NITIN JAIN(124)
VIKAS NANDWANA(128)
VARUN VIJAYVERGIA(106)
PRERIT CHAWDA(131)

Department of computer science

ARYA COLLEGE OF ENGINEERING & I.T. KUKAS, JAIPUR.
System requirement Specification
OVERVIEW:- A System Requirement Specification is a document where the requirement of
the system that is planning to be developed is listed. A software requirements document
establishes boundaries on the solution space of MPSEB client requirements of developing a
useful software system. This bsoftware requirements document allows a design to be validated -
if the software design, then that design is an acceptable solution to the problem satisfies the
constraints and properties specified in the document.

The initial specification of user requirements may be based on interviews with the database users
and on the designers own analysis of the enterprise.

The basic issues that the SRS writer(s) shall address are the following:

A)Functionality. What is the software supposed to do?

b) External interfaces. How does the software interact with people, the system’s hardware,
other hardware, and other software?

c) Performance. What is the speed, availability, response time, recovery time of various
software functions, etc.?

d) Attributes. What are the portability, correctness, maintainability, security, etc.

considerations?

e) Design constraints imposed on an implementation. Are there any required standards in effect,
implementation language, policies for database integrity, resource limits, operating
environment(s) etc.

SRS should be:

a)Correct
b)Unambiguous
c)Complete
d)Consistent

f)Verifiable
g)Modifiable
h) Traceable

ABSTRACTION:- The objective of Railway Reservation System Project is to design

software to fully automate the process of issuing a railway ticket. That is

1)To create a database of the trains

2)To accept the user information and issue PNR (Passenger Name Record) number.
3)To calculate fare
4)To develop a journey planner

INTRODUCTION:-

REQUIREMENT:- This process is also known as feasibility study. In this phase, the
development team visits the customer and studies their system. They investigate the need for
possible software automation in the given system. By the end of the feasibility study, the team
furnishes a document that holds the different specific recommendations for the candidate system.
It also includes the personnel assignments, costs, project schedule, target dates etc. The
requirement gathering process is intensified and focused specially on software. To understand
the nature of the program(s) to be built, the system engineer or "Analyst" must understand the
information domain for the software, as well as required function, behavior, performance and
interfacing. The essential purpose of this phase is to find the need and to define the problem that
needs to be solved.

Functional Requirement Specification:- The functional system requirements are those

system services, which are expected by the user of the system. These are followings.

1) All the important topics should be covered.

2) The directory should contain updated and relevant information.

3) All the links of other websites given in the directory should be of relevance and provide the
required content.

4) The search directory option should return the results with mentioned keywords.

5) The content should not be outdated and redundant.

NON FUNCTIONAL REQUIREMENT:-

SPECIFIC REQUIREMENT:-

DATA FLOW DIAGRAM:- The general principle in Data Flow Diagramming is

that a system can be decomposed into subsystems, and subsystems can be
decomposed into lower level subsystems, and so on.

• Each subsystem represents a process or activity in which data is processed.

At the lowest level, processes can no longer be decomposed.

• Each 'process' in a DFD has the characteristics of a system.

• Just as a system must have input and output (if it is not dead), so a process
must have input and output.

• Data enters the system from the environment; data flows between
processes within the system; and data is produced as output from the
system

Context level Data Flow Diagram:-

Paid Details

LEVEL1:-

LEVEL2:-
Reservation
Database
III. LEVEL
Invalid
REFRENCES:-

i. www.southernrailway.org

ii. www.wikipedia.org

iii. www.indianrailways.gov.in

iv. www.irctc.co.in

v. www.trainenquiry.com

vi. Indian Railways timetable