Enterprise Architecture Language Exercises

TOGAF (The Open Group Architecture Framework) is a widely used enterprise architecture framework that provides a method (the Architecture Development Method, or ADM) and a common vocabulary for planning, designing, and governing enterprise IT architectures. Key TOGAF terms include: Architecture Domain (Business, Data, Application, Technology — the BDAT layers), Stakeholder (any party with an interest in the architecture), Architecture Vision (the high-level aspiration for the target state), Architecture Building Block (ABB — a reusable component of capability), and Solution Building Block (SBB — a candidate solution component). Architects use TOGAF vocabulary to structure governance discussions and deliverables.

Business Architecture describes an organisation's structure, capabilities, processes, and value streams independent of technology. Architects discuss business architecture using capability maps ("we have a gap in our customer analytics capability"), value stream analysis ("the order-to-cash value stream has three handoff points that introduce delay"), and organisational structure. Key vocabulary includes business capability (what the organisation can do), business function (how it does it), and business service (the externally visible result). Business architecture provides the requirements context for IT architecture decisions.

An Architecture Decision Record (ADR) is a short document that captures a single architecturally significant decision, the context in which it was made, the options considered, and the rationale for the chosen option. ADRs create an auditable decision log that helps new team members understand why the architecture is shaped as it is and prevents relitigating settled decisions. Standard sections include Status (Proposed / Accepted / Deprecated / Superseded), Context, Decision, and Consequences. Engineers and architects maintain ADRs in version control alongside code, typically in an /docs/adr or /architecture/decisions directory.

Integration patterns describe standard approaches for connecting systems and applications. Core patterns from the Enterprise Integration Patterns catalogue (Hohpe and Woolf) include: Message Channel (a conduit for messages between systems), Message Broker (a mediator that routes and transforms messages), Request-Reply (synchronous call-response), Publish-Subscribe (one sender, multiple receivers), and Event-Driven Architecture (systems react to events rather than polling). Architects discuss integration choices using language like "a choreography-based event-driven approach reduces coupling compared to orchestration via a central workflow engine."

Enterprise Architecture (EA) operates at the organisational level, defining principles, standards, and target states across the entire IT landscape. Solution Architecture operates at the project level, designing a specific system or set of systems to meet defined requirements within the EA guardrails. Solution architects produce solution design documents, component diagrams, integration specifications, and technology selection justifications. Language in solution architecture includes "the proposed solution conforms to the enterprise messaging standard" and "we are requesting an exception to the standard for this component because…"

Enterprise data architecture vocabulary includes: Master Data Management (MDM) — the discipline of creating a single authoritative source for key business entities; Data Governance — policies and processes for ensuring data quality and accountability; Data Lineage — the ability to trace data from source to consumption; Data Mesh — a decentralised approach where domain teams own their data as a product; and Data Fabric — a unified data management layer across distributed sources. Architects also discuss data domains, canonical data models, and golden records (the authoritative version of a master data entity).

IT governance ensures that IT investments align with business strategy and are managed with appropriate oversight. Enterprise architects use governance vocabulary including: Architecture Review Board (ARB) — a committee that reviews and approves architectural decisions; exception process — the formal route for deviating from standards; architecture principles — high-level rules that guide decision-making (e.g. "prefer cloud-native services over custom builds"); compliance — conformance to standards and principles; and technical debt register — a tracked list of known architectural compromises. Phrases like "this solution will require ARB sign-off" and "we're incurring intentional technical debt here, documented in the register" are common.

A capability maturity model assesses the current state and desired future state of a business or technical capability on a maturity scale — typically 1 (Initial/Ad hoc) through 5 (Optimised/Continuously improving). Enterprise architects use capability maturity assessments to prioritise investment, communicate gaps to stakeholders, and track progress. Language includes "our current-state maturity for cloud operations is Level 2 (Repeatable) and we are targeting Level 4 (Managed) by end of year" and "the maturity gap between current and target state defines the transformation programme scope."

Digital transformation vocabulary in enterprise architecture includes: Operating Model — the way an organisation delivers its services (processes, people, technology, partners); Platform Business Model — creating value by enabling interactions between producers and consumers; API Economy — monetising business capabilities as APIs; Cloud-Native — applications designed for cloud environments using microservices, containers, and serverless; and Legacy Modernisation — migrating or re-architecting aging systems. Architects use phrases like "the transformation programme shifts us from a product-centric to a platform-centric operating model" and "we are strangling the monolith by extracting capabilities service by service."

ArchiMate is an open enterprise architecture modelling language maintained by The Open Group, designed to describe and analyse architectures across the Business, Application, and Technology layers. It provides a standardised notation for representing architecture elements (e.g. Application Component, Business Process, Technology Service) and their relationships (realisation, assignment, composition, association). Architects use ArchiMate to create precise, tool-independent architecture diagrams that can be understood across organisations and over time. Common tools include Archi (free), Sparx Enterprise Architect, and BiZZdesign. ArchiMate is often used alongside TOGAF deliverables.