Chapter 5Dig for Architecturally Significant Requirements
Every design discussion starts with who, what, and why. In Chapter 4, Empathize with Stakeholders you learned how to identify who is affected by the software system and why they care. In this chapter, you’ll learn how to define the what, the requirements, from the perspective of software architecture.
An architecturally significant requirement, or ASR, is any requirement that strongly influences our choice of structures for the architecture. It is the software architect’s responsibility to identify requirements with architectural significance. You’ll do this by thinking about four ...
Get Design It! 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.
