Chapter 8. Addressing Nonfunctional Requirements
A common challenge when specifying software is how to assess the expected quality. Many stakeholders like to believe that quality is implicit and emerges without any special effort. Unfortunately, this is rarely the case. First, what is meant by quality? Crosby’s work is definitely the place to start when you try to get a simple definition of quality. In Quality Is Free [1], Crosby defines quality as “conformance to requirements,” and this has become the standard definition of quality—not just in software development, but universally across all industries. As stated by Crosby, quality is closely linked to requirements. And like requirements, which are covered extensively in this book, what drives ...
Get Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
