The Open Group Architecture Framework (TOGAF) is (probably) the most popular current-day framework for [[Enterprise Architecture]]. Unlike the [[Zachman]] and [[CSVLOD]] models[^1], which are merely ways to frame a *description* of an Enterprise Architecture, TOGAF contains descriptive elements AND a process for applying them. > [!note] TOGAF != [[Archimate]] > - The Open Group also made [[Archimate]], which *can* be used with TOGAF, but the two are not synonymous. > - Archimae includes diagrammatic constructs that can align with the TOGAF process, but both can be used without the other. The prototypical visual associated with TOGAF actually depicts the **Architecture Development Method** prescribed by TOGAF: ![[IMG_1543.png]] ## Architecture Development Method (ADM) ### Preliminary - Decide how you will customize the rest of the approach to fit the particulars of your situation. What does the business need and what do you need to do to achieve that. - You can borrow ideas & practices from other frameworks if you like - Where you establish the team, tools, [[Principles Index|principles]] and process support structures (e.g. wiki, meeting cadences, etc) - Typically includes review of existing governance practices & policies to ensure you know the constraints you operate within ### A) Vision - Define scope & stakeholders. - Create a "vision" of the architecture - #todo find a better explanation for this - Obtain buy-in from stakeholders --- B, C, and D can be done in parallel ### B) Business Arch - Describe workflow changes, strategy changes necessary to support the [[#A) Vision]]. ### C) Information Systems Arch - The logical & physical data models necessary to support the [[#A) Vision]] ### D) Technology Arch - Hardware, software, platforms, & infrastructure changes necessary to support the [[#A) Vision]] --- ### E) Opportunities & Solutions - Create roadmap & corresponding projects - AKA "Interim states" & plans on how to get there ### F) Migration Planning - Expand on [[#E) Opportunities & Solutions]] to determine expected ROI of projects, their risks, dependencies, the logistics of implementation. - Goal is to walk away knowing what you're doing to move through the interim states ### G) Implementation Governance - Defining acceptance criteria - "how are we done" - Tracks issues, unique constraints, & ensures alignment between implementation projects ### H) Arch Change Management - Governs & manages project implementation - Are the projects on track? Are they actually delivering on the architectural [[#A) Vision]] **** # More ## Source - https://www.opengroup.org/togaf - [[Wikipedia]] - https://togaf.visual-paradigm.com/2025/03/06/comprehensive-guide-navigating-the-preliminary-phase-of-togaf-10-for-enterprise-architecture-success/ - That whole series of articles - https://youtu.be/AihWJ3_klRQ?si=-diMFwQnDy4qNf5I [^1]: and arguably [[UAF]]