Chapter 3

1. What are quality attributes?
   • Traits, or qualities, that a system may have. Often called "ilities," as many of them have this postfix in their names, for instance, portability.
2. What sources should you use when gathering requirements?
   • The context of your system, existing documentation, and the system's stakeholders.
3. How should you be able to tell whether a requirement is architecturally significant?
   • Architecturally significant requirements (ASRs) often require a separate software component, impact a large part of the system, are hard to achieve, and/or force you to make trade-offs.
4. How should you document graphically the functional requirements various parties may have regarding your system?
   • Prepare a use case diagram.
5. When is development view documentation useful?
   • In cases where you're developing a large system with many modules and need to communicate global constraints and common design choices to all the software teams.
6. How should...