1/7
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Requirements describe __ a system should do, not how it should do it.
what
Requirements describe what a system should do, not __ it should do it.
how
__ requirements define what a product should do, what it should not do, and can be verified individually.
functional
__ requirements describe properties of the system as a whole and are also known as “Quality Requirements”
non-functional
__ restrict how the system must be designed or implemented, limiting the options available to developers.
constraints
__ is the process of gathering requirements from stakeholders, through interviews, surveys or observations.
elicitation
__ confirms the requirements reflect stakeholders real needs. (Are we building the right system?)
validation
__confirms the system was built per the requirements. (Did we build the system right?)
verification