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?

To use the existing version as benchmark when customers are satisfied with the product.

What's important when gathering information about non-functional requirements?

They must be elicited from many different stakeholders such as customers, product owners, users, operations staff and maintenance staff.

How can non-functional requirements handled in Agile projects?

They may be stated as:
  • 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
Remember faster, study better. Scientifically proven.
Trustpilot Logo