The purpose of this source is to describe the railway reservation system which provides the train timing details, reservation, billing and cancellation on various types of reservation namely, • Confirm Reservation for confirm Seat. • Reservation against Cancellation. • Waiting list Reservation. • Online Reservation. • PNR generation 3. TECHNOLOGY (Hardware and Software Requirements) USER INTERFACE: Keyboard and Mouse HARDWARE INTERFACE: • Printer • Normal PC • CPU – Intel Core 2 Duo E7300 • RAM – 1 GB (MIN) • Hard disk – 160 GB • Operating System – Windows XP OPERATING ENVIRONMENT: The OS types are • Windows XP Windows 98 The initial specifications 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?
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 is the portability, correctness, maintainability, security, etc. onsiderations? 4. SOFTWARE REQUIREMENTSPECIFICATIONS FOR RAILWAY RESERVATION SYSTEM An SRS should be :- a) Correct b) Unambiguous c) Complete d) Consistent e) Ranked for importance and/or stability f) Verifiable g) Modifiable h) Traceable
The purpose of this source is to describe the railway reservation system which provides the train timing details, reservation, billing and cancellation on various types of reservation namely :- • Confirm Reservation for confirm Seat. • Reservation Against Cancellation. • Waiting list Check. • Online Reservation. • PNR Generation . 1. 2 INTENDED AUDIENCE AND READING SUGGESTIONS: The different types of readers are •Developers • Customers Management people specifically, Passengers Clerk 4. 1. 3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS • NTES – National Train Enquiry System • IVRS – Interactive Voice Response system • PRS – passenger reservation system It consists of • Train details • Reservation form • Billing • Cancellation. 4. 2 GENERAL DESCRIPTION: 4. 2. 1. PRODUCT PERSPECTIVE: It enables us to maintain the railway train details like their timings, number of seat available and reservation billing and cancelling the tickets.
COMMUNICATION INTERFACES • Indian Railway’s web-site, www. indianrail. gov. in offers PRS enquiries on the internet Berth/Seat availability, Passenger Status, Fare, Train Schedule etc,. • National Train Enquiry System (NTES) website, www. trainenquiry. com gives dynamic information about the running status of any train and its expected arrival/departure at any given station. • Mobile telephone based SMS enquiry service. A new mobile phone based facility for rail users’ viz. , • Country wide extension of Universal Rail Enquiry number “ 139” through setting up of Interactive Voice Response System (IVRS)
OPERATIONS • Any Reservation counter from 8 am to 8 pm. • Prior to 90 days of Journey. • One form for 6 persons only. • To save time & queues Agent is others guides. 4. 2. 2 PRODUCT FUNCTION : It tells the short note about the product. 4. 2. 2. 1 TRAIN DETAILS: Customers may view the train timing at a date their name and number of tickets. 4. 2. 2. 2 RESERVATION: After checking the number of seats available the customers reserve the tickets. 4. 2. 2. 3 BILLING: After reserving the required amount of tickets, the customer paid the amount. 4. 2. 2. 4 CANCELLATION:
If the customers want to cancel the ticket. 4. 2. 2. 4. USER CHARACTERISTICS: •Knowledgeable user •No voice user • Expert user 4. 2. 4 CONSTRAINTS There is no maintainability of back up so availability will get affected. Real-life credit card validation and Banking system is not implemented. No multilingual support. Given below is an overall picture of the system, as depicted in the above use-case diagrams: Administrator: Database Management: Control the database and keep track of all records of customers. View all details: View the details of all orders and control the whole application. Customers:
Login: Customers must have a valid login id(PNR number) to enter into the site. Registration: New users can sign up by creating new ID. View and edit Own Details: Can view/edit his preservation details, payment details, and details about services provided. Choosing and comparing products: Can view all reservation products. Order: Can order any service through valid credit card. Logout: Customer must logout of the site after purchasing products. 4. 3 SPECIFIC REQUIREMENTS 4. 3. 1 Functional requirements definitions Functional Requirements are those that refer to the functionality of the system, i. . , what services it will provide to the user. Nonfunctional (supplementary) requirements pertain to other information needed to produce the correct system and are detailed separately. Use cases The system will consist of CIS Alumni Home page with five selections. The first selection is to fill out a survey. The questions on the survey will be created by a designated faculty member. The survey will ask the Alum questions concerning their degree, job experience, how well their education prepared them for their job, and what can the CIS department do to improve itself.
This information will be retained on the departmental server and an e-mail will be sent to the designated faculty member. The second selection is to the Entries section. There are two choices on this page. One choice is to add a new entry. A form is presented to the Alum to be filled in. Certain fields in the form will be required, and list boxes will be used where appropriate. A password typed twice will be required of all new entries. The second selection of the Entries page is to update an Alum entry. A form will be presented allowing the Alum to enter their year of graduation and then to select themselves from a list.
A password will be required before the information will be presented to the Alum to be updated. The third selection is to search or e-mail an Alum. A form will be presented requiring the requested Alum’s year of graduation. The requesting Alum will search a table to see if the requested Alum is in the database, and if so non-sensitive information will be returned. At this time the Alum can select to e-mail the Alumnus or search for another Alumnus. If the Alum chooses to e-mail the Alumnus a form will be presented for the message to be entered with the sending Alum’s name and e-mail.
