软件架构理论与实践 (架构师书库) (李必信 等)（Z-Library）

【One-Line Pitch】 A systematic Chinese textbook-style guide to software architecture: what it is, how it is modeled and described, and how it is designed, evaluated, and evolved in practice. Best for students, instructors, and working developers who want a structured, method-by-method map of the field rather than a single-framework how-to. 【Book Arc】 - **Opening (~0%–10%)**: Frames why architecture matters, surveys competing definitions (decision-centric vs. composition-centric vs. others), and introduces core ideas—stakeholders, separation of concerns, quality-driven design, conceptual integrity. - **Early (~10%–32%)**: Moves into modeling and description: five generations of modeling methods (informal graphics, UML, formal, UML-formal hybrids, textual), MDA/PIM-PSM transformation, and architecture description languages (ADLs) with their trade-offs. - **Middle (~32%–48%)**: Covers architecture styles and patterns (data-flow, call/return, independent components, virtual machines, repositories, plus C2, REST, etc.), then connects architecture to agile development via XP, Scrum, and FDD iteration models. - **Late (~48%–70%)**: Shifts to design and implementation: deriving architecture from requirements, mapping requirements to design, and the principles (business, data, application, technology; separation of concerns, single responsibility, least knowledge, DRY) that guide architects. - **Ending (~70%–100%)**: The excerpts do not cover the later chapters in detail; the teaching plan indicates chapters 17–23 form an advanced module (evaluation, evolution, and related topics) reserved for graduate-level study. 【Key Takeaways】 - **Architecture is more than structure** (Opening): It includes quality attributes and the mapping between requirements and implementation—design decisions, not just boxes and lines. - **Definitions are plural and unresolved** (Opening): Over 100 definitions cluster into decision-centric, composition-centric, and other camps; understanding the differences is itself a learning goal. - **Modeling evolved in five waves** (Early): From informal graphics and module interconnection languages, through UML and formal methods, to UML-formal hybrids and textual languages like xADL/xADLite. - **MDA separates platform-independent from platform-specific models** (Early): PIM→PSM→code, with MOF, UML, and CWM as the underlying metamodeling standards; AIM/ASM refine this further for architecture independence. - **ADLs emphasize different concerns** (Early): Aesop, MetaH, C2 SADL, Rapide, SADL, UniCon, Wright each target different aspects—style support, real-time guidance, simulation, formal foundations—making selection a real design decision. - **Styles and patterns are not the same** (Middle): The author distinguishes patterns (named problem–solution pairs) from styles (design effects independent of a specific problem); the same system can yield different styles from different viewpoints. - **Agile and architecture can coexist** (Middle): XP, Scrum, and FDD each handle architecture differently—XP favors simple design and YAGNI, Scrum uses sprints and backlogs, FDD builds design packages from feature lists. - **Design principles are layered** (Late): General principles (business, data, application, technology) sit alongside key principles (separation of concerns, single responsibility, least knowledge, DRY) that directly shape module boundaries and coupling. 【Reading Tips】 - **Deep-read Chapters 1–3** if you are new to the field; the definition debates and modeling taxonomy are the conceptual backbone and are referenced throughout. - **Skim the ADL chapter (Ch. 5)** unless you need a specific language; use the comparison table to pick one or two relevant to your domain rather than memorizing all twelve. - **Treat the agile chapter (Ch. 6) as a bridge**: read it after styles/patterns so you can see how architecture decisions play out in iterative processes. - **Use the design principles chapter (Ch. 8) as a checklist**: map each principle to a project you know and ask where it was violated. - **Note the teaching plan**: chapters 1–16 are the core module; chapters 17–23 are advanced and, per the excerpts, not covered in detail here—plan supplementary reading if you need evaluation and evolution topics. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book (through Chapter 8), with heavy emphasis on definitions, modeling, ADLs, styles, agile, and design principles. Later chapters on evaluation, evolution, and advanced topics are indicated by the teaching plan but their content is not detailed in the excerpts.