RESULTS
We drew up the following requirements together and divided them into technical, functional and user requirements. We then checked with the stakeholder whether these corresponded to their requirements.
Technical Requirements:
- As a user, I want an app that works on Android (Google Pixel)
- As a user, I want an app with smartwatch integration (Samsung Galaxy Watch)
- As a user, I want the app to use my smartwatch's microphone.
- As a user, I want my data to be stored using an account.
Functional Requirements:
- As a user, I want to see a heatmap of where the noise in the room is coming from.
- As a user, I want to be able to schedule my classes based on potential noise pollution
- As a user, I want to see a weekly summary of my classes and the noise I experienced.
- As a user, I want to be informed of my daily dose of noise.
- As a user, I want to be notified when I have prolonged exposure to loud noise.
- As a user, I want to be notified when the weather is good.
- As a user, I want to be able to create an account.
- As a user, I want to be able to log in.
- As a user, I want to be able to log out.
User Requirements:
- As a user, I want playful elements to make insights easier
- As a user, I want a dark mode.
- As a user, I want one clear element on the homepage as the main insight
- As a user, I don't want tooltips but clear language
- As a user, I want a dashboard
As not all requirements are equally important, we have classified them using the MoSCoW method. The parts at Must will therefore have the highest priority.
CONCLUSION
LEARNING OUTCOME
Learning outcome 1: User interaction (analysis & advice)
By analysing the technical, functional and user needs. And advise on the stakeholder on what would be the most important to start working on.