Those Other Requirements: Quality Attributes and Their Inescapable Trade-Offs

You understand the functional requirements for your product, but did you explore the necessary quality attributes? They’re essential too.

Karl Wiegers
Analyst’s corner
Published in
6 min readJan 19, 2020

--

Graphic adapted from Pixabay

I’ll bet you’ve used software systems that did just what they were supposed to do but you hated them. Maybe they were too slow, or they crashed a lot, or the user interface was clumsy. These are examples of products that satisfied their functional requirements but not your quality expectations.

Not surprisingly, nearly all sets of software requirements focus on functionality, the things a product must be able to do or let the user do. Thoughtful analysts and designers also need to explore various types of nonfunctional requirements. The largest set of these fit in the category of quality attribute requirements, also called quality factors or quality of service requirements. Sometimes they’re called the “ilities” because many of them end in “-ility.”

This article provides a brief introduction to quality attributes and points out the trade-off decisions you’ll need to make among the various attributes. It’s not possible to optimize all of the quality factors at once. You need to determine which ones are most important to customer success…

--

--

Karl Wiegers
Analyst’s corner

Author of 14 books, mostly on software. PhD in organic chemistry. Guitars, wine, and military history fill the voids. karlwiegers.com and processimpact.com