Online Train Schedule Information System
Software Requirement Specification
Table of Contents
2.1 Product Perspective 4 2.2 Product Functions 5
2.3 User Characteristics 6
2.4 Constraints 6
2.5 Assumptions and Dependencies 7
3.3.2Mean Time Between Failures (MTBF)8
3.3.3Mean Time to Repair (MTTR)8
3.3.5Maximum Bugs or Defect Rate8
3.5.2Information Security Requirement9
3.5.3Billing System Data Compatibility9
3.6.1Software Language Used9
3.7On-line User Documentation and Help System Requirements10 3.8Purchased Components10
3.11Legal, Copyright, and Other Notices13
Software Requirements Specification
In India millions of commuters have to travel from one place to another by trains every day. For this the commuters have to check the schedule of the train to plan their travel. Till now they used to do it manually using the Train Schedule Book which was published by Indian Railways Annually. It was a cumbersome process as the user had to first search for the train number from a list of hundreds of train and then check their schedule.
Thus we have decided to investigate the use of an Online Train Scheduling Information System. This system would be used by members who may be travelers to check the schedule of the train and by the Railway Administrators to update the database of trains and train schedule. This system would also show the respective trains for which the passenger has queried for. After choosing the train as per his/her convenience the passenger will be able to see the schedule of that train. The purpose of this document is to analyze and elaborate on high level needs and features of Train Schedule Information System. This document focuses on facilities provided by the system to the passengers.
The purpose of Software Requirements Specification (SRS) document is to describe the external behavior of the Online Train Schedule Information System. Requirements Specification defines and describes the operations, interfaces, performance, and quality assurance requirements of the Online Train Schedule Information System. The document also describes the nonfunctional requirements such as the user interfaces. It also describes the design constraints that are to be considered when the system is to be designed, and other factors necessary to provide a complete and comprehensive description of the requirements for the software. The Software Requirements Specification (SRS) captures the...