Introduction
The major purpose of the SRS is to form a structured layout containing all the functional and non-functional requirements thereby providing ease and depicting the overview of the project, its goals and parameters. The purpose of the document is to collect and analyze all assorted ideas that have come up to define the system, its requirements with respect to customers.
This SRS is also aimed at specifying requirements of software to be developed. Software requirements specification permits a rigorous assessment of requirements before design can begin and reduces later redesign. This SRS can be further used by the designer, database administrator, programmer etc.
- SRS : Software Requirement Specifications
- GUI : Graphical User Interface
- GPS : Global Positioning System
- HTTP : HyperText Transfer Protocol
- LAN : Local Area Network
- WAMP / XAMPP / LAMP : Windows (W) / Cross-Platform (X) / Linux (L), Apache (A), MYSQL (M), PHP (P)
- PHP : Hypertext Pre-Processor
- CSS : Cascading Stylesheet
Consider travelling from Tilak Nagar (Mumbai) to SIES Graduate School of Technology (Navi Mumbai), very first the passenger will buy a train ticket and then a bus ticket. Due to change in modes of transport, he has to buy a new valid ticket everytime. Considering this inconvenience, we are designing a “All in One Ticket System” which aims at generating a single ticket which will be valid for travelling by bus, local train and metro as well in Mumbai. The Basic Authentication System Module will provide the user with an account upon registration (Sign Up). It will then take the unique user name of each user to log into the system. In the User profile Module, the personal details of the user will be maintained. In the Booking System module, the information regarding the travel will be filled by the user through a GUI display. Source and Destination will be entered by the user and the fare will be calculated. Wallet system will be implemented for user transactions. Payment can be done through the account of each user as identified by the user name. After filling the details if the user agrees to proceed then the equivalent amount of the ticket will be deducted from his account. As soon as the payment is done, the ticket will be generated which can then be printed. This will be handled by the Billing System module.
