Everyday Enterprise Architecture : Sense-making, Strategy, Structures, and Solutions

Discover what needs to happen in enterprise-architecture practice—and not just its outcomes, but also the activities from which those outcomes would arise. This book reveals how business and enterprise architects can deliver fast solutions to an always-on-the-go business world. To begin, you'll review a new technique called "context-space mapping," which provides a structured method for sense-making across the entire context of an enterprise. Throughout the book, you'll concentrate on the routine practices that underpin each of the architecture disciplines. Working step-by-step through a real 10-day architecture project, this book explores the activities that underpin the strategy, structures and solutions in the real-time turmoil of an enterprise architect’s everyday work. You'll explore how and why and when the various documents, artefacts and items of ‘theory-stuff’ come into the practice – all those mainstream methods, frameworks, models, metamodels and other information sources. In the end, Everyday Enterprise Architecture will help you develop the skills, judgment, and awareness to keep enhancing the value of your architectural projects. What You'll Learn • Work on architectures at "business-speed" • Adapt architectures for different tasks • Gather, use, and manage architectural information Who This Book Is For Enterprise and business architects. About the author Tom Graves has been an independent consultant for more than four decades, in business transformation, enterprise architecture and knowledge management. His clients in Europe, Australasia and the Americas cover a broad range of industries including banking, utilities, manufacturing, logistics, engineering, media telecoms, research, defence and government. He has a special interest in architectures beyond IT, and integration between IT-based and non-IT-based services. Table of Contents About the Author About the Technical Reviewer Acknowledgments Introduction Chapter 1: Day 1: Getting Started Overall Aim, Scope, and Purpose Initial Aim, Scope, and Stakeholders Initial Assessment Initial Implementation Wrap-Up on Initial Cycle Application Summary Chapter 2: Day 2: Purpose, Scope, and Context Main Project: “The Architecture of Architecture” Step 1: Identify Purpose and Scope of the Architecture Cycle Step 2: Identify and Review Applicable Principles, Policies, etc. Step 3: Identify Business Goals and Strategic Drivers Step 4: Establish Architecture-Framework Scope of Cycle Step 5: Identify Other Stakeholders, Concerns, Requirements Step 6: Identify Additional Requirements Step 7: Finalize Plan and Secure Approval to Proceed Example Project: “Respect,” for a Bank Step 1: Identify Purpose and Scope of Architecture Cycle Step 2: Identify and Review Applicable Principles, Policies, etc. Step 3: Identify Business Goals and Strategic Drivers Step 4: Establish Architecture-Framework Scope of Cycle Step 5: Identify Other Stakeholders, Concerns, Requirements Step 6: Identify Additional Requirements Step 7: Finalize Plan and Secure Approval to Proceed Application Summary Chapter 3: Day 3: What’s Going On? Main project: “To-Be” Assessment of Architecture Step 1: Develop Baseline Architecture for “To-Be” Context Step 2: Select Reference-Models, Views, Viewpoints, and Notational Standards Step 3: Create and Update “To-Be” Architecture Models Step 4: Review “To-Be” Architecture Against Qualitative Criteria Step 5: Finalize Building-Blocks for Architectural Scope Step 6: Conduct Checkpoint-Review for Stakeholders Example Project: “As-Is” Assessment for the Bank Step 1: Develop Baseline Architecture for “As-Is” Context Step 2: Select Reference-Models, Views, Viewpoints, and Notational Standards Step 3: Create and Update “As-Is” Architecture Models Workshop for Executive-Team Workshop for Operations Staff Follow-On Assessment Step 4: Review “As-Is” Architecture Against Qualitative Criteria Step 5: Finalize Building-Blocks for Architectural Scope Step 6: Conduct Checkpoint-Review for Stakeholders Application Summary Chapter 4: Day 4: What Do We Want? Main Project: Architecture “As-Is” Assessment Step 1: Develop Baseline Architecture for “As-Is” Context Step 2: Select Reference-Models, Views, Viewpoints, and Notation-Standards Step 3: Create and Update “As-Is” Architecture Models Step 4: Review “As-Is” Architecture Against Qualitative Criteria Step 5: Finalize Building-Blocks for Architectural Scope Step 6: Conduct Checkpoint-Review for Stakeholders Example Project: Bank Past/Future Assessment Step 1: Baseline Architecture for “Past/Future” Context Step 2: Select Reference-Models, Views, Viewpoints, and Notation-Standards Step 3: Create and Update “Past/Future” Architecture Models Exploratory Session Follow-On Assessment Step 4: Review Architecture Against Qualitative Criteria Step 5: Finalize Building-Blocks for Architectural Scope Step 6: Conduct Checkpoint-Review for Stakeholders Application Summary Chapter 5: Day 5: What’s the Difference? Main Project: Architecture Gaps Step 1: Compare “As-Is” to “To-Be” Architectures Scope The Art of Architectural Investigation Tools and Skill-Sets Architectural Entities for Architecture Step 2: Derive Change-Requirements from Comparison Step 3: Review Requirements Against Existing Dispensations Step 4: Review Requirements Against Qualitative Criteria Step 5: Conduct Checkpoint-Review for Stakeholders Example Project: Change-Requirements for the Bank Step 1: Compare “As-Is” to “Past/Future” Architectures Step 2: Derive Change-Requirements from Comparison Step 3: Review Requirements Against Existing Dispensations Step 4: Review Requirements Against Qualitative Criteria Step 5: Conduct Checkpoint-Review for Stakeholders Application Summary Chapter 6: Day 6: How Do We Get from Here to There? Main Project: Enhance “Architecture of Architecture” Step 1: Review Gap-Analysis and Change-Requirements Step 2: Identify Business-Drivers and Constraints Step 3: Derive Technical Requirements from Functions Step 4: Derive Co-existence and Interoperability Requirements Step 5: Perform Architecture Re-assessment and Gap-Analysis Step 6: Develop Preliminary Solution-Designs Step 7: Identify Major Work-Packages or Projects Step 8: Conduct Stakeholder Review of Preliminary Solution Designs and Obtain Approval to Continue Example Project: Reclaim Respect for the Bank Step 1: Review Gap-Analysis and Change-Requirements Step 2: Identify Business-Drivers and Constraints Steps 3, 4, and 5: Not Applicable Step 6: Develop Preliminary Solution-Designs Step 7: Identify Major Work-Packages or Projects Step 8: Conduct Stakeholder Review of Preliminary Solution Designs and Obtain Approval to Continue Application Summary Chapter 7: Day 7: Step-by-Step Details Main Project: A Plan to Extend the Discipline Example Project: Envisioning Vision at the Bank Visioning Exercise Functional Business Model Linking It All Together Application Summary Chapter 8: Day 8: Putting It into Practice Main Project: Implementing Architecture Base-Maps and Cross-Maps Problem-Space and Solution-Space Example Project: Vision and Function for the Bank Functional Business Model Visioning Wrap-Up Application Summary Chapter 9: Day 9: What Did We Achieve? Main Project: What Next for Our Architecture? Phase A: Set Up the Architecture-Cycle Phase B: Assess the Primary Time-Horizon (“To-Be”) Phase C: Assess the Comparison Time-Horizon (“As-Is”) Phase D: Assess Gaps Between As-Is and To-Be Phase E: Decide on What to Do About Those Gaps Phase F: Develop a Detailed Action-Plan Phase G: Execute the Action-Plan Phase H: Review Our Progress So Far Example Project: What Next for the Bank? Application Summary Chapter 10: Day 10: What Happens Next? What Was Supposed to Happen? What Actually Happened? What Was the Source of the Difference? What Can We Learn from This? Application Summary Appendix A: The Architecture Information-Stores Architecture-Governance Repository Architecture-Models Repository Requirements Repository Issues, Dispensations, Risks, and Opportunities Registers Glossary and Thesaurus Application Appendix B: More on Context-Space Mapping SCAN Cross-Map (Response-Patterns) Jungian-Type Base-Map (“Embodied Best-Practice”) Repeatability and “Truth” Marketing Versus Sales Plan/Do/Check/Act ISO-9000 Core Skill-Levels Automated Versus Manual Processes Appendix C: Resources Books and Publications Websites and Other Online Resources Index