Scribd
Upload
110 views4 pages

SRS Document For Railway Management Systems Project

The document outlines requirements for a train ticket booking system that allows users to book and cancel tickets and order food on trains. It describes functional requirements like booking, cancelling, and viewing tickets and ordering food as well as non-functional requirements around usability, performance, reliability, and security.

Uploaded by

gvnviki17
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
110 views4 pages

SRS Document For Railway Management Systems Project

The document outlines requirements for a train ticket booking system that allows users to book and cancel tickets and order food on trains. It describes functional requirements like booking, cancelling, and viewing tickets and ordering food as well as non-functional requirements around usability, performance, reliability, and security.

Uploaded by

gvnviki17
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SRS DOCUMENT FOR RAILWAY

MANAGEMENT SYSTEMS PROJECT.


1. Introduction:
1.1 Purpose:
The purpose of this document is to outline the software
requirements for a train ticket booking system with food ordering
functionality.

1.2 Scope:
The software system described in this document will allow users to
perform the following tasks:
1.Book train tickets.
2.Cancel train tickets.
3.View booked tickets.
4.Order food during the train journey.
5.View food orders.

2. Functional Requirements:
2.1 Ticket Booking:
1.Users can enter their name and age to book train tickets.
2.They can choose from available train schedules.
3.Each booked ticket should have a unique seat number

2.2 Ticket Cancellation:


1.Users can cancel their booked tickets by providing the seat number.
2.The system should display a confirmation message upon successful
cancellation.

2.3 View Booked Tickets:


Users can view the details of their booked tickets, including
passenger information and train schedule.

2.4 Food Ordering:


1.Users can order food items from the available menu during the
train journey.
2.They can select the desired food item and specify the quantity.

2.5 View Food Orders:


Users can view the list of food orders they have placed, along with
the total price for each order.

3. Non-Functional Requirements:
3.1 Usability:
1.The system should have a user-friendly interface with clear
instructions for each functionality.
2.Error messages should be informative and guide users to resolve
issues.

3.2 Performance:
1.The system should handle multiple concurrent users efficiently.
2.Response time for booking tickets and ordering food should be
minimal.
3.3 Reliability:
1.The system should accurately process ticket bookings,
cancellations, and food orders without errors.
2.It should maintain data integrity and consistency throughout the
user interactions.

3.4 Security:
1.User authentication and authorization mechanisms should be
implemented to ensure secure access to the system.
2.Personal and payment information, if collected, should be
encrypted and stored securely.

4. Constraints:
1.The system relies on the availability and accuracy of the train
schedule dataset.
2.It may require an internet connection to fetch real-time train
schedule information in future versions.
3.The system's functionality is limited to booking tickets, cancelling
tickets, and ordering food; additional features may be implemented
in future iterations.

5. Glossary:
5.1 Train Schedule:
A predefined list of train stations, arrival and departure times, and
platform numbers.

5.2 Ticket:
A reservation for a seat on a specific train schedule.
5.3 Food Order:
A request placed by a user to purchase food items during
the train journey.

You might also like