SRS for Railways Reservation System

Software Requirement Specification for Railways Reservation System.

1. RESERVE -ALL Online railways reservation System THE SMARTER WAY TO GRAB A RAiL TICKET….. SRS for RESERVE-ALL System 1

2. USER REQUIREMENTS USER REGISTRATION/LOGIN ENQUIRIES CHECKING AVAILABILITY OF TRAINS AND SEATS TATKAAL TICKET BOOKING GENERAL BOOKING FACILITIES CANCELLATION AND REFUND FACILITIES. HISTORY OF TRANSACTIONS,BOOKINGS AND REFUND

3. ADMIN REQUIREMENTS POPULARITY ASSESMENTS USER DATABASE MANAGEMENT ADS MANAGEMENT PAYMENT MANAGEMENT TRANSACTION DATABASE MANAGEMENT SYNC WITH OFFICIAL RAILWAYS RESERVATION SYSTEM.

4. LEVEL 1 DATA FLOW DIAGRAM OF RESERVE-ALL ONLINE RAILWAY RESERVATION SYSTEM SRS for RESERVE-ALL System 4

5. SOFTWARE REQUIREMENT SPECIFICATIONS (SRS) FOR ONLINE RAILWAYS RESERVATION SYSTEM RESERVE -ALL SRS for RESERVE-ALL System 5

6. 1 .Introduction SRS for RESERVE-ALL System 6 1.1 Purpose RESERVE-ALL Online Railway Reservation System is intended to serve as an efficient ,fast and secure system for Railway Reservations and concerned activities. Its special features makes it the quickest way to book a ticket. This document is meant to describe the features of the RESERVE –ALL system and to guide the developers as well as it serves as a software validation document for the client.

7. 1.2 Scope SRS for RESERVE-ALL System 7 Following features are described as the scope of the System to be developed : INSCOPE Providing facilities for booking a railway ticket Enquiry Facilities. Provisions for Tatkaal Tickets booking. Facilities for cancellation and Refunds. Managing Users and maintaining the database for users and transactions. OUT OF SCOPE 1. Features for booking a flight or any other transport ticket. Tour Packages. Goods Transports. Hotels and Catering facilities.

8. 1.3 Definitions and Abbreviations. SRS for RESERVE-ALL System 8 Definitions a. Transaction: A real event that involves flow of personal money. In the context of shares, it is buying/selling a group of shares of the same company, and in context of Bank it is deposit/withdrawal of money to/from one’s account. b. Security: A set of all transactions pertaining to a company share or a bank. c. IP : Unique Address of a machine Connected to the Internet .

9. SRS - Software Requirement Specification . PNR - Passenger Name Record. ID - Identity Card EMI - Easy Manageable Installments TDR - Transfer Of Development Rights. IP - Internet Protocol Address. RAM - Random Access Memory. SRS for RESERVE-ALL System 9 Abbreviations

10. SRS for RESERVE-ALL System 10 The rest of this SRS is organized as follows : Section 2 gives an overall description of the software. It gives what level of proficiency is expected of the user, some general constraints while making the software and some assumptions and dependencies that are assumed . Section 3 gives specific requirements which the Software is expected to serve. Some performance requirements and design constraints are also given. Section 4 gives some possible future extensions of the system . 1.5 Overview .

11. 2. Overall Description 2.1 Product Prespective RESERVE-ALL Online Railway Reservation System is aimed to provide a Simple ,Quick and efficient Way to Book a railway Ticket . This System Should be User friendly, smooth , Fast ,secure , reliable and hassle- free to provide the user a pleasant Experience Booking a Ticket. RESERVE-ALL is intended to be a Stand-alone Online Portal and should be independent of any Other Software . It should be compatible With any Browser and Should be Platform Independent. SRS for RESERVE-ALL System 11

12. 2.2 Product Functions: User Management 1.1 New User Registration 1.2 Existing User Login/Logout 1.3 Forgot Password Recovery mechanism 3.1 Recovery Via Phone 1.3.2 Recovery Via Mail. RESERVE – ALL Should support the following Cases :

13. 2 . Enquiries 2.1 Trains Between Stations 2.2 Seat Availability 2.3 Special Trains 2.4 Train Running Information 2.5 PNR enquiries 2.6 Ticket Related Enquiries. RESERVE – ALL Should support the following Cases :

14. RESERVE – ALL Should support the following Cases : 3. Booking Facilities. 3.1 Booking a Ticket . 3.1.1 Booking a general/ Tatkaal Ticket. 3.1.2 Booking History . 3.1.3 Ticket Reprint Facility. 3.1.4 Booking Status/Current Status

15. RESERVE – ALL Should support the following Cases : 3. Booking Facilities. 3.2 Providing Passenger Details. 3.2.1 Personal Details. 3.2.2 ID details. 3.2.3 Choice of Berth. 3.2.4 Food Options. 3.2.5 Senior Cetizen / Govt.Employee /Railway Passes details.  

16. RESERVE – ALL Should support the following Cases : 3. Booking Facilities. 3.3 Payment Options. Credit Cards. Debit Cards. Mobile/Net Banking. Cash Cards. EMI Options .  

17. RESERVE – ALL Should support the following Cases : 4. Cancellation and Refund Facilities . 4.1   Cancel a ticket . 4.2 Print Cancelled Ticket Facility. 4.3 Cancellation Status. 4.4 Cancelled Ticket History. 4.5 Refunds Status. 4.6 Refunds History. 4.7 TDR 4.7.1 File TDR. 4.7.2 TDR Status. 4.7.3 TDR Refunds.

18. “RESERVE – ALL” Should support the following cases : SRS for RESERVE-ALL System 18 Popularity Assesment Hits Counter. Usage Statics. Number Of Users Currently Online .  Users Management New User Registration. Special Offers For Frequent Users. Keeping Track of All Activities of Users . Advertisment Management. Accomodating Ads of Sponsers in the System. Attracting New Sponsers .

19. “RESERVE – ALL” Should support the following Cases : SRS for RESERVE-ALL System 19 Payment Management. Manging Payment Gateways. Managing Merchant Sites Security Services Management.   Transactions Database Management.   Synchronising with Official Indian Railways Reservation System.   ‘ About Us’ Interface and Other Details of the Agency.

20. SRS for RESERVE-ALL System 20 2.3 USER CHARACTERISTICS The User Shall be familiar With the Procedure and Provisions to Book a ticket. The User shall have a average knowlegde of Computer and Internet. The User should know the methods of transactions and Payment.

21. SRS for RESERVE-ALL System 21 2.4 Principal Actors . The principal Actors in RESERVE-All are : User Administrator. System

22. 2.5 General Constraints For Working RESERVE-All Requires :- a) A Secured working Internet Connection With least Speed of 128 Kbps. b) A Java® Enabled Browser. c) Payment Method(When required). d)Only One user can login in the system from an IP address at a time. SRS for RESERVE-ALL System 22

23. 2.6 Assumptions and Dependencies SRS for RESERVE-ALL System 23 The system requires an Internet Connection to work. The Availability of Trains and Seats is fully governed and managed by the official portal of Indian railways www.irctc.co.in . The system doesn’t acquires any special quotas for seats. The RESERVE –All System provides Booking Services from 00hrs to 2200 hrs. Booking facility is not provided by Indian Railways between 2200 hrs-00hrs. However ,Other Facilities eg . Enquiry are available 24x7 on the System.

24. 3.1 Performance Requirements SRS for RESERVE-ALL System 24 The performance of the System depends Upon the Availability of a fast and Steady Internet Connection with least speed of 128 Kbps. The system works comfortably on a machine faster than 1Ghz and having atleast 1 gb of RAM. The response time of the System is ≈ 2 seconds but is affected by the efficiency of the browser and Internet Connection.

25. 3.2 Design Constraints: 1. Security : The files and databases in which the information regarding Users and Transactions should be secured against malicious deformations . 2. Fault Tolerance : Data should not become corrupted in case of system crash or power failure. SRS for RESERVE-ALL System 25

26. 4.Future Extensions: Possible future Extensions in the System could be: Flights and Bus Ticket Bookings. Hotels and Other similar Facilities. Tour and Holiday Packages. SRS for RESERVE-ALL System 26

27. Thank You SRS for RESERVE-ALL System 27