
Design Requirements
Data Requirements
The product needs to be able to access GPS data of buses and include a robust algorithm that incorporates information such as GPS location and local traffic density to provide accurate arrival estimates for UMD students that use the transportation system.
Usability Requirements
Our system should be easy to learn and navigable for users. Some of our users have expressed difficulties regarding learning routes and times so our system would make these key features easily accessible.
User Experience Goals
Our system should be helpful and satisfying for our users. UMD students should not have to feel stressed or frustrated when trying to gain information regarding bus routes and times.
User Characteristics
Personal Circumstances
Our users are UMD students who will use the bus frequently and have to get to class on time. Arriving to class on time is crucial since being late would disrupt their learning experience and consequently have an impact on their grades
Experience
Most UMD students are experienced with using the bus or some sort of public transportation so they typically know how to navigate shuttle tracking systems to some degree.
Preferences
They primarily prefer receiving bus stop information that is more accurate, consistent, and reliable since they rely on this information to plan ahead before going to class and after class to go back home or to nearby locations. Safety at night is also a concern for some of our users so accurate arrival times would be highly preferable, reducing their wait times at bus stops and help alleviate safety concerns.
Environmental
A social requirement is the ability to share data about the buses, similar to how Waze functions. Students should be allowed to notify if there are service alerts to others automatically.
A physical requirement would be the ability to request a bus stop through a function. Much like how crosswalk buttons work, the individual can request a stop. The button exists inside the buses themselves to request a stop, there can be a button to notify bus drivers and the system that you are at the stop.
Functional Requirements
Should provide UMD students the ability to track bus locations and accurate information regarding bus routes and time estimates. It should be accessible to any user at any time near the bus stops.

Design Methodology
In order to create design alternatives we used contextual inquiry notes from our observations and interviews that we then categorized by the issues presented by our stakeholders. We then used this data to generate affinity diagrams and flowcharts which helped inform our brainstorming on effective ways to alleviate the issues and concerns raised by our stakeholders and users. By reviewing our personas, we pooled several random ideas together no matter the rationale that can best reach the goals of each fictitious stakeholder. We thought of both practical and impractical solutions and came up with three ideas.