Opens in the Canvas studio
Structured diagram studios for system design, workshops, and diagram-as-code.
The diagram route brings canvas, diagram, architecture, and automation studios into one workflow so workshops, incident flows, C4 views, and coded diagrams can be built, reviewed, and exported without moving between separate tools.
4 studios
126 templates
Choose a studio
My Projects →Four editors, one for each kind of work. Projects, drafts, and exports stay shared across all of them.
- CanvasOpen a blank whiteboard for workshops, story maps, and early structure.
- DiagramOpen the structured editor for flowcharts, sequences, ERDs, and org views.
- ArchitectureOpen enterprise, software, or process architecture tabs and map the system directly.
- AutomationWrite Mermaid, D2, PlantUML, Graphviz, DBML, and more with live preview and export-ready output.
Boards open seeded for real sessions: retros, story maps and pre-mortems with frames already in place.
Open blank CanvasBrowse templates
Every card is the real artefact. Studio templates open straight in their editor, interactive tools score and edit the framework itself, and Enterprise Architecture workspace templates open their full tool page.
Collection
Topic
Framework
126 of 126 templates
Template catalogue
Opens in the Canvas studio
Opens in the Canvas studio
Opens in the Diagram studio
Opens in the Diagram studio
Opens in the Diagram studio
Opens in the Architecture studio
Opens in the Automation studio
Opens in the Automation studio
Opens in the Automation studio
Porter five forces: where the pressure on industry margins comes from
Competitive rivalry sits at the centre and the four outside forces press in on it. Each card carries its canonical prompts and, once scored, the pressure that force is exerting.
Porter
PESTLE analysis: six lenses on the macro environment
Political, Economic, Social, Technological, Legal and Environmental categories in one scan. Each card holds up to four factors, and unedited cards show the canonical prompts from Aguilar's environmental scanning.
PESTLE
Eisenhower matrix: sorting the week by urgency and importance
Four quadrants prescribe a default action: do first what is urgent and important, schedule what matters but can wait, delegate the urgent noise, and eliminate the rest.
Eisenhower
BCG growth share matrix: where the portfolio earns and spends its cash
Market growth crossed with relative market share sorts every product into Stars, Question marks, Cash cows or Dogs, each quadrant carrying the investment posture Henderson prescribed for it.
BCG
Cynefin framework: matching the decision approach to the problem
Clear, Complicated, Complex and Chaotic domains each prescribe a different decision approach, from best practice to novel action, with Disorder at the centre for questions not yet placed.
Cynefin
OKR quarterly plan: one objective measured by four key results
A single qualitative objective for the quarter with up to four measurable key results beneath it, each carrying a progress bar so the state of the whole plan reads at a glance.
OKR
NIST CSF 2.0 function map: the six functions and their category counts
Govern, Identify, Protect, Detect, Respond and Recover, each with its official two letter code, its purpose in brief and its category count. Once scored, every card carries the coverage you have claimed for that function.
NIST CSF
ISO 27001 Annex A: four control themes and the Statement of Applicability
Annex A of ISO/IEC 27001:2022 groups 93 controls into four themes: Organisational with 37, People with 8, Physical with 14 and Technological with 34. Each card carries the theme's scope and, once scored, its readiness.
ISO 27001
CIS Controls v8.1: the eighteen controls by implementation group
All eighteen CIS Critical Security Controls v8.1, numbered 01 to 18, each carrying the lowest implementation group that activates it. Choose a target group and the controls in scope take the red tint.
CIS Controls
MITRE ATT&CK Enterprise: coverage across the fourteen tactics
The fourteen enterprise tactics in kill chain order, from Reconnaissance to Impact, read down the left column and on down the right. Each card shows your declared detection coverage at one of four levels.
MITRE ATT&CK
AWS Well-Architected Framework: maturity across the six pillars
Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimisation and Sustainability, each with its published focus. Once scored, every pillar card carries its maturity line.
AWS Well-Architected
Value proposition canvas: the value map answering the customer profile
The customer profile captures jobs, pains and gains on the right; the value map answers them on the left with products and services, pain relievers and gain creators. The fit connector between the halves is the test the canvas exists to run.
Strategyzer
Lean Canvas: nine blocks for testing an early-stage business model
Ash Maurya's adaptation of the Business Model Canvas keeps the nine-block grid but swaps the infrastructure blocks for Problem, Solution, Key Metrics and Unfair Advantage, the questions an unproven product has to answer first.
Lean Canvas
Jobs to be done: the four forces that decide whether a customer switches
The job statement fixes what the customer is trying to get done. Push of the present and pull of the new drive the switch; anxieties about switching and habits of the present resist it. The customer moves only when the first pair outweighs the second.
Jobs-to-be-Done
RAID register: risks, assumptions, issues and dependencies in view
Four quadrants hold a delivery's open exposure: the risks that might bite, the assumptions being relied on, the issues already live and the dependencies waiting on others.
RAID
DAMA-DMBOK wheel: eleven knowledge areas with Data Governance at the hub
Data Governance sits at the hub of the DMBOK wheel and the ten other knowledge areas sit around it, from Data Architecture to Data Quality. Each card carries the maturity you have claimed for that area on the one-to-five scale.
DAMA-DMBOK
GDPR Article 30 register: processing activities, purposes, bases and retention
Up to six processing-activity cards, each recording what the activity is, why the data is processed, which Article 6(1) lawful basis applies and how long the data is kept, the bones of an Article 30(1) record.
GDPR
NIST CSF 2.0 profile: current and target tiers across the six functions
Each CSF 2.0 function carries two bars on the four-tier scale, Partial to Adaptive: a solid bar for where practice stands today and an outlined bar for where the organisation intends to be.
NIST CSF
STRIDE threat canvas: six categories and the properties they violate
Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service and Elevation of Privilege, each card naming the security property the category violates and holding your threat and mitigation.
STRIDE
SABSA matrix: six layers by six questions, the 36 artefacts in one grid
The six SABSA layers from Contextual to Operational cross the six questions What, Why, How, Who, Where and When; every cell names the artefact a security architect produces at that intersection.
SABSA
OSI seven layer model: the ISO/IEC 7498-1 reference stack
The seven layers of the OSI Basic Reference Model stacked from layer 7 Application at the top to layer 1 Physical at the bottom, each with its number, official name, core function and canonical protocol examples.
OSI model
TCP/IP four layer model: the RFC 1122 internet protocol stack
The four layers of the TCP/IP model from RFC 1122, stacked from Application at the top to Link at the bottom, each with its core function, canonical protocols and the OSI layers it spans on the right.
TCP/IP
ITIL 4 service value chain: six activities turning demand into value
The six activities of the ITIL 4 service value chain. Engage, Design and Transition, Obtain or Build, and Deliver and Support form the central flow, while Plan and Improve span the whole chain above and below it.
ITIL 4
BPMN 2.0 level 1 process flow: an order to cash worked example
A descriptive level 1 BPMN flow through one order to cash pool: a start event, three tasks across the Customer and Sales lanes, one exclusive gateway and a thick bordered end event, joined by labelled sequence flows.
BPMN
Architecture maturity profile across eight capability dimensions
Each spoke is one maturity dimension scored from one to five. The shape of the filled area shows at a glance where the architecture capability is strong and where it has the furthest to climb.
Preliminary
Stakeholder power and interest grid: who to manage closely
Mendelow's grid places each stakeholder by how much power they hold against how much interest they take, and that position sets the engagement strategy for each one.
Preliminary
Architecture principle test board: four named tests run against a candidate
Four cards arranged in a 2x2 grid name the four tests every architecture principle has to pass. Each card carries the test question on top and the failure signature on the bottom.
Preliminary
Framing a business scenario: from vague symptom to scoped statement
Five cards left to right show each step that promotes a vague symptom into a scoped scenario statement the architecture work can act on.
Phase A, Architecture Vision
Capability gap heatmap: severity encoded by fill intensity per dimension
Six capabilities as rows against four gap dimensions as columns. Red-soft fill marks the high-severity gaps so the priority pattern is visible at a glance.
Phase B, Business Architecture
RACI matrix: one accountable role for each architecture deliverable
Each row is a deliverable and each column a role. R does the work, A is the single accountable owner, C is consulted and I is informed. Exactly one A per row is what keeps accountability clear.
Phase G, Implementation Governance
TOGAF gap analysis: baseline against target across the domains
Each architecture domain is one row. Read across to see today's baseline, the agreed target, the gap that separates them and the action type that closes it, so every domain carries a decision.
Phase B, Business Architecture
Architecture Decision Record: adopting the IEC CIM for the LTDS
A Nygard-format decision record with its number, title and status in the header, then the context, the decision itself, its consequences and the alternatives that were rejected.
Phase G, Implementation Governance
Transition roadmap: baseline to target through operable states
Each state is a viable architecture that must run before the next begins. The arrow into a state carries the work packages that deliver it, and every card lists its packages with the evidence gates that prove the state is real.
Phase E, Opportunities and Solutions
Readiness heatmap: capabilities against four readiness dimensions
Five capabilities as rows against four readiness dimensions. Red cells mark the dimension that blocks rollout for that row.
Phase E, Opportunities and Solutions
Governance decision: the path that passes and the path that stalls
An architecture change moves through submission, board review and decision. At each stage the top zone is what carries it forward and the bottom zone is what sends it to waiver, rework or rejection.
Phase G, Implementation Governance
Business Model Canvas: a distribution network operator on nine blocks
The nine building blocks of Osterwalder's canvas, from key partners through the value proposition to revenue streams, filled in for a regulated electricity distribution business.
Phase B, Business Architecture
The TOGAF Architecture Repository: its eight partitions
The Architecture Repository as eight partitions, from the metamodel that frames the work and the live landscape, through the standards base and reference library, to the governance log and the solutions landscape.
ADM-wide
Lean value stream map: process time, queues and the bottleneck
Each stage shows its process time; the labels between stages are the queues that work waits in. Lead time is the sum of both, so the longest queue, not the slowest step, is usually the bottleneck to attack first.
Phase B, Business Architecture
ABB and SBB selector: reuse, buy or build the building block
Each candidate building block is one row, scored one to five on reusability, maturity and total cost of ownership. The type and the decision read across so the buy-or-build call sits next to the scores behind it.
Phase C, Information Systems Architecture
TOGAF iteration cycles as a loop, not a one-way line
The ADM runs as four iteration cycles that pass work round a loop: the Capability cycle frames Development, Development feeds Transition Planning, planning is held by Governance, and Governance reopens the next round.
ADM-wide
TOGAF tailoring as a cycle: scope, scale, review, adjust
Four cards form a closed cycle. The dashed loopback says the next programme inherits the tailored method as its starting baseline.
ADM-wide
Board-pack review: every artefact scored against the four gates
Every artefact in the board pack is one row, read across the four gates the board scores: is it complete, can each item be traced to a concern, are its decisions defensible, and does it read without the author in the room. One Fail is enough to hold the whole package back.
ADM-wide
Information domains: owners, sources of truth, consumers
Three columns trace each information domain by named owner, the source-of-truth system, and the downstream consumers that depend on it.
Phase C, Information Systems Architecture
TOGAF data entity catalogue: source, type, quality, lifecycle
Each core data entity is one row, tied to its domain, the system that owns it, the source type, a quality rating and a lifecycle stage. The catalogue is the single register of what data exists across the estate.
Phase C, Information Systems Architecture
Master data authority: one system of record per entity
Master data entities run down the side and the five systems that hold them run across the top. Each cell marks the system as Master, Replica or read-only Consumer, so exactly one system owns each entity.
Phase C, Information Systems Architecture
Asset and network data architecture: store, model, consumer mapped per domain
Three columns trace each network-asset data domain: the store of record, the data model it conforms to, and the operational consumers that read from it.
Phase C, Information Systems Architecture
Metadata register: definition, lineage, quality and owner
Each data entity is one row, marked Yes or No on whether it has a definition, traceable lineage, an enforced quality rule and a named owner. The coverage column rolls the four into one status so the gaps are obvious.
Phase C, Information Systems Architecture
Analytics prioritisation: which questions are worth funding
Each business question is one row, scored one to five on data readiness, tool maturity and appetite. The three roll into a composite percentage and a priority band so ready questions rise above ones blocked on data.
Phase C, Information Systems Architecture
Integration coupling profile across five coupling dimensions
Each spoke scores how tightly two systems are coupled on one dimension, from data and timing through to platform and transaction. The smaller the shape, the looser and more resilient the integration.
Phase C, Information Systems Architecture
Application portfolio strategy on the Gartner TIME quadrant
Each application is placed by business value against technical quality and fit, sorting the estate into the TIME quadrants: invest in strong high-value systems, migrate valuable systems on weak technology, tolerate sound but low-value systems, and eliminate the rest.
Phase C, Information Systems Architecture
LTDS and CIM information walkthrough: from operator data to LTDS publication
Six cards trace the LTDS information journey: operator data, CIM model, validation, package, publication, regulator consumption.
Phase C, Information Systems Architecture
Platform trade-off: scoring build, buy and SaaS side by side
Each platform option is one row, scored one to five on cost, control, speed, scale, risk and vendor independence. The totals sum each row across thirty so the strongest option stands out without hiding its trade-offs.
Phase D, Technology Architecture
Risk and control catalogue: inherent against residual risk
Each row is one risk scored for likelihood and impact to give an inherent rating, with the residual column showing what is left once the mapped control is in place and working.
Phase D, Technology Architecture
Microservice fit: independent change on Y, independent failure on X
Two axes encode the microservice fitness call. Top-right is where microservices belong. Bottom-left is where the monolith is the right answer.
Phase D, Technology Architecture
Sustainable IS decision matrix: carbon intensity on Y, business value on X
Two axes pair business value against carbon intensity. Top-right is high-value-high-carbon: optimise. Top-left is high-value-low-carbon: scale. Bottom-right is low-value-high-carbon: retire.
Phase D, Technology Architecture
The TOGAF Technical Reference Model: entities, interfaces, qualities
The TOGAF TRM is not a layered stack. It is three entities, application software, the application platform, and the communications infrastructure, joined by two interfaces, with twelve platform service categories and a backplane of qualities.
Phase D, Technology Architecture
Technology standards catalogue: adopt, trial, hold or retire
Each technology standard is one row, placed in a category, given a lifecycle status of Adopt, Trial, Hold or Retire, and assigned an owner, so every standard carries an accountable decision rather than drifting.
Phase D, Technology Architecture
OT, IT and Telecom resilience: dependencies named per stack
Three columns name the dependencies in each stack: what the stack depends on, what depends on it, and the failure mode when the dependency breaks.
Phase D, Technology Architecture
Voltage tiers from generation to your wall socket
Five voltage tiers stacked top to bottom encode the step-down from transmission to customer outlet. The four lower tiers carry the red-soft emphasis fill because they sit inside the DNO licence boundary.
Preliminary
London Grid Distribution operating model: inputs, accountability, outputs
Three rows pair the external input on the left, the DNO function that processes it in the middle, and the public output on the right. Cross-arrows labelled 'produces' make the input-to-output trace explicit.
Preliminary
Why architecture matters: the same outcome, with it and without
Four outcomes a sponsor cares about: cost, delivery speed, risk and change. The top zone is what each looks like with enterprise architecture in place; the bottom zone is the failure mode without it.
Preliminary
What enterprise architecture is, set beside its neighbours
Enterprise architecture is easiest to define by contrast. Read the same three rows, scope, horizon and output, across enterprise architecture, solution architecture and IT strategy to see where each one stops.
Preliminary
Where the TOGAF Standard sits and what publications surround it
Three columns separate the normative source from its internal parts and the explanatory layer around it. The normative column carries red-soft emphasis so the source of truth is visible at a glance.
ADM-wide
TOGAF certification levels are cumulative; each level absorbs the previous
Three columns left to right (Foundation, Practitioner, EA Practitioner) list the publications each level draws from. Repeated publications across columns encode the cumulative nature explicitly.
ADM-wide
Containment hierarchy: Deliverable contains Artefacts contains Building Blocks
An outer Deliverable card visually wraps the Artefacts card which visually wraps the Building Blocks card. A Viewpoint pill on the right points at whichever inner card the stakeholder is reading.
ADM-wide
Three reading paths by reader profile, not by table of contents
Three parallel columns each list the TOGAF sections to read in order for a specific reader. The geometry shows that there is no single right path; legitimate paths exist for each profile.
ADM-wide
London case study evidence chain: every claim has to clear five checkpoints
Five cards show the chain from claim back to regulator record. Each card has VALID IF on the top and INVALID IF on the bottom so the failure mode at each step is visible.
ADM-wide
Drawing the enterprise boundary: who is inside the architecture, who is outside
Seven functional groups on the left list every organisational unit, partner, and adjacent body the architecture touches. Two zone cards on the right span the rows they include.
Preliminary
Architecture scope on two axes: breadth and depth, with the trade-off in each quadrant
The grid encodes the two scope decisions on the X and Y axes. Each quadrant shows what the chosen combination produces and what it sacrifices.
Preliminary
Kickoff readiness: owner, status and gap for each prerequisite
Each prerequisite for starting an engagement is one row, read across to its owner, its RAG status and the gap that remains. The board can start Phase A only once the not-ready and partial rows have a credible path to close.
Preliminary
Architecture Vision through the Phase A gate to the Statement of Architecture Work
Vision card on the left, SoW card on the right. Between them sit four named gate checks. All four must clear or the vision returns for iteration.
Phase A, Architecture Vision
Kickoff artefact readiness board: six artefacts against four criteria
Each row is a kickoff artefact, each column a readiness criterion. A row that has any block is not ready for kickoff.
Phase A, Architecture Vision
Phase B: from SoW inputs through business architecture activities to Phase C/D outputs
Five stacked layers go top to bottom: inputs, activities, deliverables, governance gate, outputs. Each layer carries the artefact name and the named owner.
Phase B, Business Architecture
Process-to-organisation RACI: who is Responsible, Accountable, Consulted, Informed
Five processes as rows and four organisational units as columns. Each cell carries a single RACI letter; Accountable cells are emphasised so the single owner per row is visible.
Phase B, Business Architecture
Business footprint: goals on the left, services in the middle, measures on the right
Three parallel columns make the trace from a business goal to the service that realises it to the measure that proves it. Each row reads as one accountability statement.
Phase B, Business Architecture
London connections modernisation walkthrough: from baseline to RIIO-ED filed evidence
Six stages from baseline survey to filed evidence. Each card carries the artefact produced at that stage and the owner accountable.
Phase B, Business Architecture
Business architecture theatre: four warning signs paired with the real-architecture cure
Four cards left to right name the most common theatre signals. Each card carries the warning sign on top in red-soft and the real-architecture cure on the bottom.
Phase B, Business Architecture
Architecture landscape partitioning: breadth on Y, depth on X
Two axes encode how to slice the architecture landscape. Top-right is enterprise-wide deep; bottom-left is local shallow. The chosen partition determines how the work is governed.
Phase E, Opportunities and Solutions
Agile ceremonies mapped to the TOGAF ADM phases
Each recurring Scrum ceremony is one row, tied to the ADM activity it carries, the architecture artefact it produces and the cadence it runs at, so the TOGAF method has a clear home inside the sprint rhythm.
ADM-wide
London roadmap evidence gates: from RIIO-ED commitment to filed regulator evidence
Six cards trace the London transformation roadmap evidence chain. Each card carries the milestone and the artefact filed at that gate.
Phase F, Migration Planning
Operating model grid: standardisation against integration
The Ross, Weill and Robertson model places a business by how standard its processes are against how much its units share data, and that position names one of four operating models.
Preliminary
Wardley map: a network operator value chain by evolution
A Wardley map plots a value chain by how visible each part is to the user against how evolved it is, so you can see where to build, buy or treat a component as a utility.
Phase A, Architecture Vision
C4 system context: who uses a system and what it depends on
A C4 context diagram puts one software system in the centre, shows the people who use it and the systems it relies on, and labels every relationship between them.
Phase C, Information Systems Architecture
C4 container view: the moving parts inside one software system
A C4 container diagram zooms one level into the system boundary: the applications, services and data stores it is built from, who uses each entry point, and which source systems feed it.
Phase C, Information Systems Architecture
Application to organisation: who owns and who depends on each system
Each application is one row and the five organisation units are the columns. Primary marks the unit accountable for the application; Uses marks a unit that depends on it day to day, so ownership and reach can be read together in one grid.
Phase C, Information Systems Architecture
Role to application access: who may read, edit and approve in each system
Business roles run down the side and six applications run across the top. Each cell records the access the role needs to do its job: Read to view, Edit to change records, Approve to sign off. Access maps to duty, not to convenience.
Phase C, Information Systems Architecture
Application to function: where support is full, partial or missing
Applications run down the side and the six business functions run across the top. Full marks an application that meets a function on its own; Partial marks a contribution that needs others alongside it, so functional gaps surface as columns with no Full entry.
Phase C, Information Systems Architecture
Application interactions: what each system sends and what each receives
The same six applications run down the side and across the top. A filled cell names the data that flows from the row application to the column application, so each row reads as what a system provides and each column as what it consumes. The diagonal stays empty.
Phase C, Information Systems Architecture
Application to technology: which platform hosts, stores and distributes each system
Applications run down the side and the five technology platforms run across the top. Runs on names the host, Stores in the persistence and Publishes via the distribution channel, which makes this matrix the bridge from Phase C applications into Phase D technology.
Phase C, Information Systems Architecture
ArchiMate layered viewpoint: business to technology in one view
The layered viewpoint stacks the business, application and technology layers of one architecture, with each layer realising services that serve the layer above it.
ADM-wide
Business interaction matrix: which unit provides which service to whom
Five organisation units appear as both rows and columns. A filled cell names the business service the row unit provides to the column unit, so every handoff inside the distribution business is written down once and owned.
Phase B, Business Architecture
Actor and role matrix: who performs and who approves each role
Five actors down the side, five business roles across the top. Performs marks the actor who carries out the role and Approves marks the actor who signs off its output, so accountability is explicit before any process design starts.
Phase B, Business Architecture
Value stream and capability matrix: what each connection stage depends on
The six stages of the Deliver a new connection value stream run down the side and six business capabilities run across the top. Primary marks the capability each stage depends on; Supports marks capabilities that contribute to it.
Phase B, Business Architecture
Strategy and capability matrix: which capabilities each strategy needs
Six courses of action drawn from the three London Grid strategies run down the side, six capabilities across the top. Critical marks a capability the course of action cannot proceed without growing; Needed marks one used as it stands.
Phase B, Business Architecture
Capability and organisation matrix: one owner for every capability
Six business capabilities run down the side and five organisation units across the top. Owns marks the one unit accountable for each capability; Contributes marks every unit that shares the work without owning the outcome.
Phase B, Business Architecture
Data entity and function matrix: who creates, reads, updates, deletes
Six data entities run down the side and six business functions across the top. Each cell carries C, R, U and D marks showing which function creates, reads, updates or deletes the entity, with one creating function per row.
Phase B, Business Architecture
Technology radar: rings and quadrants for a GB network operator
A ThoughtWorks-style radar plots twelve technologies on four rings, Adopt, Trial, Assess and Hold, across four quadrants, so a network operator can state one shared position on every technology in play.
Phase D, Technology Architecture
Service blueprint: deliver a new connection at London Grid Distribution
A Nielsen Norman Group service blueprint maps one journey step per column across five lanes, from the evidence a customer can touch down to the support processes that keep the service running.
Phase B, Business Architecture
Customer journey map: a developer's path from discovery to energisation
A Nielsen Norman Group journey map follows one persona through five stages, recording what they do, what they think and how they feel, then turns the pain at each stage into an improvement the operator can own.
Phase B, Business Architecture
Business Process Cooperation viewpoint: a process chain in context
The ArchiMate Business Process Cooperation viewpoint relates business processes to each other and to their environment: the roles assigned to them, the objects they share and the application services that serve them.
Phase B, Business Architecture
Service realisation viewpoint: tracing a service to what delivers it
The Service realisation viewpoint shows how a business service is realised by a business process, who is assigned to that process, and which application service and component sit beneath it.
Phase B, Business Architecture
Capability Map viewpoint: a two level view of what the business can do
The ArchiMate Capability Map viewpoint gives a structured overview of enterprise capabilities, usually two or three levels deep, and doubles as a heat map for deciding where investment should go.
Phase A, Architecture Vision
Goal realisation viewpoint: from one goal to outcomes and requirements
The Goal realisation viewpoint refines a high-level goal into concrete sub-goals, then shows the outcomes that realise them and the principles and requirements that influence how they are pursued.
Phase A, Architecture Vision
Motivation viewpoint: who drives change, what it aims at, what shapes it
The ArchiMate motivation elements in three bands: the stakeholders, drivers and assessments that drive change; the goals, outcomes and values it aims at; and the principles, requirements and constraints that shape the answer.
Preliminary
ArchiMate Application Cooperation viewpoint: the application landscape
The Application Cooperation viewpoint maps the application landscape: the components, the information that flows between them and the data objects they share.
Phase C, Information Systems Architecture
ArchiMate Application Usage viewpoint: applications supporting processes
The Application Usage viewpoint shows how applications support the business: services in the middle serve the processes above and are realised by the components below.
Phase B, Business Architecture
ArchiMate Technology viewpoint: nodes, system software and networks
The Technology Viewpoint shows the software and hardware that support the application layer: nodes, system software, devices and the networks that join them.
Phase D, Technology Architecture
ArchiMate Implementation and Deployment viewpoint: software onto nodes
The Implementation and Deployment viewpoint maps applications onto the artifacts that realise them and the nodes those artifacts are deployed on.
Phase D, Technology Architecture
ArchiMate Migration viewpoint: plateaus and gaps from baseline to target
The Migration viewpoint plots the journey from a baseline architecture to a target architecture as a row of plateaus, with a gap element naming what changes between each pair.
Phase E, Opportunities and Solutions
EA operating model: how the architecture function actually runs
The enterprise architecture function as six layers, from the board mandate that gives it authority down to the maturity target it measures itself against each year.
ADM-wide
London governance repository assurance: from decision capture to Ofgem-readable evidence
Five cards trace LGD board decisions from capture through assurance to the Ofgem-readable evidence pack.
Phase G, Implementation Governance
TOGAF and ArchiMate complement map: which artefact each side owns
Three columns name what TOGAF owns alone, what ArchiMate owns alone, and where both meet in the joint artefact.
ADM-wide
BIZBOK to TOGAF handshake: business architecture artefacts that cross the bridge
Five cards show the BIZBOK output passed across to the TOGAF Phase B input.
Phase B, Business Architecture
TOGAF, DODAF, FEAF: same problems, different artefacts
Three columns name the equivalent artefact in each framework for stakeholders, capability, and viewpoint.
ADM-wide
The Zachman Framework 3.0: the six by six classification grid
Six perspectives from the Executive down to the Enterprise as rows, six interrogatives from What across to Why as columns. Every architecture artefact has one home cell where a perspective meets a question.
ADM-wide
TOGAF misconception repair: MYTH on top, REPAIR on bottom
Four common TOGAF misconceptions. Each card carries the myth on top and the repair on the bottom in red-soft.
ADM-wide