Summary
Summary · Chapter 1
Chapter 1 recap
Section titled “Chapter 1 recap”- What it is: the structure or structures of a system, their elements, and the relationships between them — an abstraction of the system.
- Why it matters: every system has an architecture, and it is the system’s foundation. Benefits include enabling/inhibiting quality attributes, predicting qualities, easing stakeholder communication, easing change, providing a reusable model, imposing complexity-reducing constraints, improving cost/effort estimates, and training new members.
- The architect: a technical leader ultimately responsible for the architecture and its documentation, performing many technical and non-technical duties, and expected to know a broad range of topics. Challenging but rewarding if you care about the software and its stakeholders.
What’s next
Section titled “What’s next”Chapter 2 covers software architecture within an organization: architect roles, development methodologies, project and configuration management, office politics, and product lines that leverage architectural reuse.
Citations
Section titled “Citations”- Software Architect’s Handbook (Packt, 2018), Ch.1 “Summary”, p. 80.