-
Notifications
You must be signed in to change notification settings - Fork 0
requirements
Requirements describe what the system we are creating should be able to do, such as user or technical requirements.
Once there is a clear set of requirements, it is important to prioritize them. This will help understand the most important requirements, in what order to develop them, and what not to deliver if there is not enough time. The prioritization can be done by using the MoSCoW method, which was developed by Dai Clegg of Oracle UK. MoSCoW stands for:
- Must have: no point in delivering without this requirement
- Should have: important but not vital
- Could have: wanted or desirable, but less important compared to a Should Have requirement
- Would have: will likely not be delivered
It is important to aim to deliver as many of the “Should Have” requirements as possible. Could and Would requirements are more of a “nice to have” requirement and therefore do not affect the overall success of the project. “Could have” requirements are the first to go if the project timeline or budget undergoes any kind of pressure. In the table below you will see all the current requirements for the matching application.
Id | Requirement | Priority |
---|---|---|
R1 | Users must be able to create an account with a username, e-mail and password | Must have |
R2 | Students must be able to add their current best CMD skills to their account | Must have |
R3 | Students must be able to add their learning skills to their account | Must have |
R4 | Users must be able to see an overview of all students from a specific class | Must have |
R5 | Users must be able to change account/profile details | Must have |
R6 | Teachers must be able to generate team suggestions based on compatible CMD skills | Must have |
R7 | Users must be able to see an overview of all teams and its details | Must have |
R9 | The matching application must be work on mobile | Must have |
R10 | The matching application design must match the CMD brand | Must have |
R11 | Students should be able to define favorite students they want to work with | Could have |
R12 | Users could be able to reflect on teamwork within the application | Could have |
R13 | Teachers could be able to grade students' CMD skills within the application | Would have |
Wiki for Blok Tech | Maijla Ikiz | Juliette Groot | Aidan Omwando | Tejo van der Burg | TECH2 |