Goals
- To provide users with the information they need during an event, without requiring internet access all the time.
Background and strategic fit
In previous years, a third-party app was created that did not communicate with the colloquium website — changes made in users' personal schedules in the app did not show up on the website and vice versa. Developing the app in-house means we can enable communication between the app and the website, and prevent organizers from incurring the cost of hiring a third party to develop an app.
Assumptions
- The user has an Android smartphone or tablet with Android 4.0 or newer, or an Apple iPod touch, iPhone or iPad with iOS 9 or newer.
- The user has internet access at least some of the time.
Requirements
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | View schedule | As an event visitor, I want to view the event's full schedule. | Must have | |
| 2 | Update schedule | As an event visitor, I want to view the latest version of the event's schedule. | Must have | |
| 3 | Sign up | As an event visitor, I want to sign up for events. This needs to be synced with the website. | Must have | |
| 4 | Personal schedule | As an event visitor, I want to be able to see my personal schedule. | Must have | |
| 5 | Navigate colloquium | As an event visitor, I want to browse the locations and see where the events take place. | Should have | |
| 6 | View schedule after connection loss | As an event visitor, I want to be able to still view the full schedule and my personal schedule after I have lost internet connection | Must have | |
| 7 | Navigate colloquium after connection loss | As an event visitor, I want to browse the locations and see where the events take place after I have lost internet connection. | Should have | |
| 8 |
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|