JUNAID JABBAR 14816 BSCS-V

RAILWAY E-TICKETING SYSTEM

SOFTWARE REQUIREMENTS SPECIFICATION
INTRODUCTION

The presentation of the Software Requirements Specification (SRS) gives an outline of

the whole SRS with reason, scope, definitions, abbreviations, condensings, references
and review of the SRS. It incorporates a lot of utilization cases that depict every one of
the connections the clients will have with the product. Use cases are otherwise called
practical prerequisites. Notwithstanding use cases, the SRS likewise contains non-
utilitarian (or beneficial) prerequisites. Non-useful prerequisites are necessities which
force limitations on the structure or execution, (for example, operational efficiency
prerequisites, quality guidelines, or plan imperatives). The point of this report is to
assemble and investigate and give an inside and out understanding of the RAILWAY E-
TICKETING framework by characterizing the issue proclamation in detail.

OBJECTIVE

The motivation behind the archive is to gather and dissect every single arranged thought
that have come up to characterize the framework, its necessities regarding travelers.
Additionally, we will anticipate and deal with how we trust this item will be utilized so as
to increase a superior comprehension of the undertaking, diagram ideas that might be
grown later, and archive thoughts that are being considered, yet might be disposed of as
the item creates.

The source of most programming frameworks is in the need of a customer, who either
needs to robotize the current manual framework or wants another product framework.
The product framework is itself made by the engineer. At long last, the end client will
utilize the finished framework. In this manner, there are three significant gatherings
inspired by another framework: the customer, the client, and the engineer. By one way
or another the prerequisites for the framework that will fulfill the necessities of the
customers and the worries of the clients must be conveyed to the designer. The issue is
that the customer doesn't generally plan the product, or the product advancement
process and the designer doesn't comprehend the customer's concern and the
application territory. This causes a correspondence hole between the gatherings engaged
with the improvement of the venture.

PURPOSE

The essential reason for Software Requirement Specification (SRS) is to connect this
correspondence hole. SRS is the medium through which the customer's and the client's
needs are precisely determined; for sure, SRS shapes the premise of programming
improvement. Another significant reason for building up a SRS is helping the customers
understanding their very own needs. A SRS sets up the reason for understanding
between the customer and the provider on what the product item will do. A SRS gives a
reference to approval of the last item. A top notch SRS is an essential to top notch
programming and it likewise decreases the advancement cost.
A few factors that direct us to develop a new system are given below:

1- Quicker System 2- Exactness 3- Reliability 4- Availability

SCOPE

The railroad reservation framework encourages the travelers to enquire about the trains
accessible based on source and goal, booking and dropping of tickets, enquire about the
status of the booked ticket, and so on. The point of contextual analysis is to plan and
build up a database keeping up the records of various trains, train status, and travelers.
The record of train incorporates its number, name, source, goal, and days on which it is
accessible, while record of train status incorporates dates for which tickets can be
reserved, all out number of seats accessible, and number of seats previously reserved.