Requirements

Purpose of the page

The purpose of this Wiki page is to have an accessible place to store all requirements that are related to the project. Therefore, we have split the requirements into 5 parts.

1. Android UI: This section will include all the requirements needed of the UI. Meaning all the requirements derived from the visual aspects for the android app go there.
2. MQTT communication: Includes requirements that are related to establishing a connection between the WIO terminal and the android phone
3. Music Player: A big part of the app is the ability to play music. Hence, why we gathered all music playing requirements in that page.
4. Workout Tracker: The app serves as a mean to motivate users achieve their fitness goals. So, all requirements related to tracking workouts such as calories burnt and starting a workout are there.

Methodologies used for gathering requirements

• Our requirements stem from first and foremost, forming a minimal viable product that is functional and delivers value to its users. Therefore, we looked at popular music players and music streaming services and stripped their content to the core of what makes them viable. Platforms we looked at include: Spotify, Deezer and YouTube
• As for workout tracking requirements we brainstormed ideas of what are the essential features to include. Moreover we used creativity techniques such as Hall Of Fame

Traceability

• Requirements can be traced through Milestones to the issues that are contained within them. Each of the milestones are derived from the requirements that are within the wiki pages. Each requirement typically has multiple issues assigned to it that are aimed to fully completed and refine the features

• Traceability is an essential aspect of requirements management, which ensures that the project remains aligned with its goals and objectives. By establishing a clear traceability framework, you can easily track the progress of each requirement through the project's milestones and associated issues