### 5. TOGAF † **TOGAF** (The Open Group Architecture Framework) is the framework the course uses from Week 3 onward. Distinction to keep clean: - **TOGAF is a *method*** — it tells you what to do, in what order, and what to produce. - **ArchiMate is a *language*** — it tells you what to draw and what the shapes mean. They're independent (you can use TOGAF with any notation) but designed to work together; both are Open Group standards. #### 5.1 The Architecture Development Method (ADM) † The ADM is TOGAF's cycle. Phases run A→H around a ring, with **Requirements Management** in the hub touching every phase. | Phase | Name | Produces | MBUA514 week | |---|---|---|---| | **Prelim** | Preliminary | Architecture principles, governance framework, tailoring of the method itself | — | | **A** | **Architecture Vision** | Scope, stakeholders, goals, capabilities, value; high-level target sketch; the business case for doing this at all | **W4** | | **B** | **Business Architecture** | Actors, roles, functions, processes, org structure, events, business footprint | **W5** | | **C** | **Information Systems Architectures** | Data architecture + application architecture | **W6** (data) and **W7** (applications) | | **D** | **Technology Architecture** | Platforms, networks, hardware, infrastructure | **W8** | | **E** | **Opportunities & Solutions** | Solution options, work packages, benefits — the first "how" | **W10** | | **F** | **Migration Planning** | Gap analysis, dependencies, prioritised roadmap, transition architectures | **W11** | | **G** | Implementation Governance | Architecture contracts; conformance of delivery to design | ❓ not on schedule | | **H** | Architecture Change Management | Handling change requests; deciding when a change triggers a new cycle | ❓ not on schedule | | **Hub** | Requirements Management | Requirements captured, stored and fed to *every* phase continuously | throughout | Three things about the ADM that repay attention: 1. **It's a cycle, not a waterfall.** Phase H feeds back into Phase A. Architecture is never "finished"; it's re-entered. 2. **Phases A–D describe *states*; E–F describe *movement*.** A–D answer "what does good look like?"; E–F answer "how do we get from here to there, and in what order?" 3. **Requirements Management sits in the middle, not at the start.** Requirements aren't gathered once — they arrive, change and are traced throughout. Week 3's **ADM 4×4 matrix** was the course's compressed walkthrough of these phases applied to Coffee Co. ❓ *The exact template lives in the W3 weekly PDF — not in this folder. Retrieve from Canvas and record its axes here.* #### 5.2 Nine elements of digital transformation † Used in W3 to analyse the W2 case. Almost certainly Westerman, Bonnet & McAfee's framework — three domains × three elements: | Domain | Elements | |---|---| | **Customer experience** | Customer understanding · Top-line growth · Customer touchpoints | | **Operational processes** | Process digitisation · Worker enablement · Performance management | | **Business models** | Digitally modified businesses · New digital businesses · Digital globalisation |