Building Model-based Enterprise Architecture (Mudar Bahri)（Z-Library）

【One-Line Pitch】 A hands-on guide for practicing enterprise architects who want to move from scattered slides and spreadsheets to a single, governed EA repository—built with Sparx EA, custom MDG extensions, and the TOGAF Standard. Read it if you already know EA concepts and UML basics and need a repeatable, tool-driven method. 【Book Arc】 - **Opening (~0%–15%)**: Frames why an EA practice needs a real repository (a database of interconnected artifacts) and previews the toolchain—Sparx EA as software, TOGAF 10 as framework, MDG to bridge them. Solves the "why a tool, not just documents" question. - **Early (~15%–33%)**: A Sparx EA crash course, then MDG fundamentals and advanced MDG techniques (shape scripts, tagged values, custom connectors and diagram types), followed by structuring the repository per TOGAF guidelines. Solves the setup and customization problem. - **Middle (~33%–48%)**: Domain-by-domain modeling—business capabilities, projects/courses of action, applications, application integrations, cloud environments, business services, organizations and strategies. Each chapter extends the MDG, then builds artifacts. Solves "how do I actually model X." - **Late (~48%–58%)**: Repository management processes—maintaining elements, merging duplicates, managing artifacts and diagrams, customizing navigation, adding charts. Solves keeping a mature repository trustworthy. - **Ending (~58%+)**: Publishing EA artifacts—documents, templates, virtual documents, and web/HTML output. Solves getting artifacts into stakeholders' hands. 【Key Takeaways】 - **The EA repository is the backbone of a successful practice** (Opening): documents and slides can't reveal cross-element dependencies; a single interconnected store can. This is the book's founding argument. - **Sparx EA + TOGAF + MDG is the chosen stack** (Early): Sparx EA doesn't natively support TOGAF, so you must build custom MDGs to embed the framework—mastering MDG is a core promised outcome. - **MDG customization is a skill you build incrementally** (Early): start with basic stereotypes from the TOGAF content metamodel, then layer on shape scripts, tagged values, and custom diagram types as new artifact types demand. - **Repository structure must follow TOGAF guidelines** (Early): with thousands of elements in a mature environment, disciplined hierarchy preserves user trust and findability. - **Business capabilities come first** (Middle): the book treats capability modeling as the foundational EA artifact, then links capabilities to organization units, functions, processes, value streams, and information. - **Model at multiple abstraction levels** (Middle): applications, integrations, and cloud/technology each get conceptual, logical, and physical treatments so different stakeholders get what they need. - **Distinguish services from functions and processes** (Middle): consumers care about services, not internal mechanics—a modeling discipline the book stresses with practical examples. - **Maintenance and publishing are first-class concerns** (Late): merging duplicates, changing stereotypes, customizing views, and generating documents/web output keep the repository useful over time. 【Reading Tips】 - Skim Chapters 1–2 if you already know EA and Sparx EA basics; deep-read the MDG chapters (3–4) since everything downstream depends on them. - Treat the modeling chapters (6–12) as a working sequence: each one updates the MDG before building artifacts, so follow the order rather than jumping around. - Keep Sparx EA open alongside the book—the MDG and diagram-building steps are procedural and hard to absorb passively. - Don't skip Chapter 13 (repository management); it's where long-term repository quality is won or lost. - Note the author's stated prerequisite: familiarity with EA, TOGAF, UML, and modeling tools is assumed, not taught. 【Coverage Limits】 The excerpts cover the front matter, table of contents, and chapter previews; detailed chapter content beyond introductions is not available, so specific techniques and examples are summarized at the structural level only.