1st iteration - rajeevnairb/Trip-Planner GitHub Wiki
Functional Requirements:
End users must be able to input any source stop, destination stop of their choice.
End users must be able to input any date and time of travel of their choice.
When the users provide source, destination,date and time, they should be provided a list of
trips available close to the given time.
If journey with the requested date is unavailable due to no connections with less than 4 trips, a message " No trip available" should be shown.
If the last trip between the source and destination for the particular date is before the time requested by the user, a message " No more trip available for the requested date" should be shown.
If multiple trips matching the user inputs are available, a trip that takes least commuting time and a trip that takes least amount of stops should be shown
Non Functional Requirements
Availability: The system should be available 99% of the time
Response Time: Response time should be under 2 sec 95% of the time
Platform Independence: The system should work in Windows and Linux platforms
Usability: User should be able to use the system with ease. The output should be user friendly