Non-functional Requirements
In 2009, Miller proposed a battery of over 2,000 questions to elicit non-functional requirements. Her approach is to build a stakeholder profile and then interview those stakeholders extensively. The questions are grouped into three sections, all focused on user needs:
- Operation: how well does the system perform for daily use?
- Revision: how easy is it to correct errors and add functions?
- Transition: How easy is it to adapt to changes in the technical environment?
Read more about this topic: Requirements Elicitation