Quality Characteristics for Technical Testing - General Planning Issues - Stakeholder Requirements
3 important questions on Quality Characteristics for Technical Testing - General Planning Issues - Stakeholder Requirements
Non-functional requirements are often poorly specified or even non-existent. What's a common approach?
What's important when gathering information about non-functional requirements?
How can non-functional requirements handled in Agile projects?
- user stories
- to the functionality specified in use cases as non-functional constraints.
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding