Chapter 3: Quality Attributes in Software Design

The text emphasizes that while systems are often designed around basic functional requirements—which the author suggests are more precisely described as sets of responsibilities—system failure or redesign is frequently driven by deficiencies in qualities like maintainability, speed, or scalability. Architecture's main function is structuring the system to satisfy these essential qualities, as functionality alone does not determine architectural structure. A key issue in addressing QAs is the historical lack of testable definitions, overlapping concerns (like a denial-of-service attack touching on performance, availability, and security), and inconsistent terminology across different quality communities. To standardize and ensure rigor, the chapter proposes using Quality Attribute Scenarios (QASs), a common, testable form for specifying requirements, whether general or system-specific. Every QAS consists of six defined components: the Stimulus, its Source, the system Artifact affected, the prevailing Environment, the required system Response, and a definitive Response Measure. Architects achieve QAs primarily through design decisions categorized as Architectural Patterns or Tactics. Patterns are proven, recurring solutions that often bundle multiple individual tactics and necessitate explicit quality tradeoffs, since enhancing one attribute (like portability) may negatively affect another (like performance). Tactics are isolated, fundamental design primitives that directly influence a system’s response to a stimulus and are crucial for refining patterns or building specialized design fragments from "first principles". The discussion also covers the common problem of architectural deterioration, or architecture debt, which occurs when continuous changes erode structural integrity, often requiring focused refactoring efforts to restore security or modifiability. Finally, the process of analyzing QA achievement during design is made systematic through tactics-based questionnaires, a lightweight auditing tool that compels the architect to systematically assess design choices, risks, and rationale associated with supporting (or not supporting) specific tactics.