Enterprise Architecture Foundation Training Course

Participants can locate and use the main parts of the TOGAF Standard.

• TOGAF Standard concepts: fundamental content, series guides and terminology
• Architecture Development Method phases and their iterative delivery cycle
• Architecture content, enterprise metamodel and architecture repository relationships
• Applying TOGAF guidance proportionately to different change initiatives
• Deliverables, artefacts and building blocks within architecture work
• Architecture landscapes, partitions and levels of enterprise detail

Participants can define architecture principles and governance arrangements for an engagement.

• Architecture principles structured through name, statement, rationale and implications
• Business, data, application and technology principle categories
• Principle conflicts resolved through explicit trade-offs and decision records
• Architecture governance roles: sponsor, board, architect, owner and delivery team
• Architecture contracts and compliance assessments for implementation control
• Governance repository records for standards, decisions, exceptions and reusable assets

Participants can prepare an architecture capability and engagement approach using the Preliminary Phase.

• Preliminary Phase objectives, inputs, outputs and key stakeholder decisions
• Architecture capability assessment using maturity, skills, process and tool criteria
• Tailoring the ADM for programme scale, urgency and governance needs
• Defining architecture principles, repository structure and reference materials
• Establishing architecture board terms of reference and escalation routes
• Selecting architecture viewpoints for executive, operational and technical audiences

Participants can create an Architecture Vision that secures stakeholder agreement on scope and value.

• Phase A Architecture Vision purpose, inputs, outputs and approval decisions
• Stakeholder map using power, interest, concerns and communication needs
• Business scenario technique for eliciting drivers, goals and desired outcomes
• Statement of architecture work defining scope, constraints and deliverables
• Value proposition linking architecture effort to measurable business outcomes
• Communications plan for sponsors, delivery teams, users and assurance functions

Participants can describe baseline and target business architecture using capabilities, value streams and processes.

• Phase B business architecture objectives, content and review points
• Business capability map organised by stable abilities rather than organisation charts
• Value stream stages connecting stakeholder needs with delivered outcomes
• Operating model elements: processes, roles, locations, partners and controls
• BPMN process models for critical service journeys and handoffs
• Baseline-to-target capability assessment using maturity, performance and investment evidence

Participants can define data architecture views, data ownership and information flow requirements.

• Phase C data architecture scope, deliverables and quality considerations
• Conceptual data model identifying core entities, relationships and business definitions
• Data ownership, stewardship, classification and retention accountabilities
• Information flow mapping between processes, applications, partners and reporting consumers
• Master data, reference data and transactional data distinctions
• Data quality dimensions: accuracy, completeness, timeliness, consistency and uniqueness

Participants can map application services, interfaces and portfolio issues against business needs.

• Application architecture views linking capabilities, services, applications and interfaces
• Application portfolio catalogue recording lifecycle, owner, cost and business fit
• Service decomposition using business services, application services and components
• Interface inventory covering APIs, files, events, messages and manual exchanges
• Application rationalisation criteria: duplication, risk, cost, fit and technical condition
• Target application architecture patterns for integration and service reuse

Participants can define target technology architecture and assess platform-level constraints.

• Technology architecture building blocks: platforms, networks, storage, middleware and endpoints
• Technology reference model for grouping common infrastructure and platform services
• Platform standards catalogue covering approved products, versions and support status
• Deployment environments: development, test, production, recovery and monitoring
• Non-functional requirements for availability, performance, security, resilience and scalability
• Technology lifecycle assessment identifying obsolescence, vendor dependence and operational risk

Participants can use core ArchiMate concepts to produce clear cross-domain architecture views.

• ArchiMate layers: business, application, technology, physical and motivation elements
• Active structure, behaviour and passive structure element distinctions
• Core ArchiMate relationships: serving, access, flow, triggering and realisation
• Viewpoints selected according to stakeholder concerns and decision questions
• Capability, value stream and course of action modelling
• Traceability from strategic drivers through capabilities to technology services

Participants can organise architecture artefacts in a usable content structure and repository.

• Architecture content framework: deliverables, artefacts and architecture building blocks
• Catalogues, matrices and diagrams selected for specific architecture questions
• Architecture repository areas: reference library, standards, governance log and capability
• Architecture metamodel entities, attributes and relationships for consistent documentation
• Reusable reference architectures and patterns managed with ownership and versioning
• Content quality checks for completeness, consistency, traceability and decision relevance

Participants can identify architecture gaps and organise solution options into work packages.

• Phase E inputs from approved baseline, target architecture and stakeholder concerns
• Gap analysis comparing baseline and target capabilities, applications, data and platforms
• Architecture gap matrix recording deficiency, impact, dependency, owner and response
• Solution building blocks grouped into coherent work packages
• Dependency analysis across business readiness, data migration, integration and infrastructure
• Risk assessment using likelihood, impact, treatment and ownership criteria

Participants can create transition architectures and prioritised implementation roadmaps.

• Phase F migration planning objectives, inputs, outputs and governance decisions
• Transition architectures defining viable intermediate states between baseline and target
• Implementation roadmap sequencing work packages, dependencies, milestones and decision gates
• Capability-based planning connecting investment increments with measurable business outcomes
• Prioritisation using value, risk, urgency, cost, dependency and resource criteria
• Implementation and migration plan linking architecture work to portfolio governance

Participants can govern delivery against approved architecture and manage justified deviations.

• Phase G implementation governance purpose, controls and accountability model
• Architecture contract clauses covering standards, deliverables, reviews and exceptions
• Compliance assessment checkpoints at initiation, design, build, test and release
• Architecture review board decisions: approve, conditionally approve, defer or reject
• Exception process documenting rationale, risk, compensating controls and expiry
• Conformance evidence drawn from designs, test results, inventories and release records

Participants can manage architecture change requests and maintain architecture relevance over time.

• Phase H change management triggers from strategy, regulation, incidents and technology
• Change request classification: simplification, incremental change or re-architecture
• Impact analysis across capabilities, data, applications, platforms, cost and risk
• Architecture backlog management for approved changes and deferred decisions
• Architecture maturity reviews measuring process adoption, asset use and governance effectiveness
• Continuous architecture monitoring through portfolio metrics and technology lifecycle signals

Participants can maintain traceable architecture requirements throughout ADM work.

• Central requirements management operating across all ADM phases
• Requirement sources: strategy, regulation, stakeholders, architecture gaps and delivery constraints
• Requirements catalogue fields: identifier, statement, rationale, owner, priority and status
• Traceability matrix linking requirements to architecture views, work packages and tests
• Prioritisation methods: MoSCoW, weighted scoring and dependency-based sequencing
• Change control for requirement conflicts, assumptions, approvals and baselines

Participants can incorporate security, privacy, risk and compliance needs into architecture decisions.

• Security architecture aligned with confidentiality, integrity, availability and accountability requirements
• Threat modelling using assets, threats, vulnerabilities, controls and residual risk
• Privacy-by-design considerations for personal data collection, use, retention and sharing
• Control mapping between architecture components, policies, standards and assurance evidence
• Business continuity and disaster recovery requirements reflected in target technology views
• Regulatory obligations translated into architecture principles, constraints and acceptance criteria

Participants can communicate architecture findings to executives, delivery teams and governance bodies.

• Executive architecture briefing structured around decision, evidence, options and recommendation
• Architecture viewpoints matched to stakeholder concerns, authority and technical depth
• Decision records capturing context, alternatives, consequences, owner and review date
• Heat maps communicating capability performance, risk exposure and investment priority
• Roadmap storytelling linking transition milestones with benefits, dependencies and decisions
• Facilitating architecture workshops using agendas, prompts, assumptions and action logs

Participants can build, review and present a complete enterprise architecture case pack for a transformation decision.

• Case brief translated into scope, drivers, stakeholders, constraints and architecture principles
• Baseline and target architecture views produced across all four domains
• Capability map, value stream and application portfolio linked through traceability
• Gap matrix and risk register converted into prioritised work packages
• Transition roadmap sequenced with dependencies, governance gates and measurable outcomes
• Architecture board review tests assumptions, compliance evidence, trade-offs and exceptions
• Executive presentation communicates recommended target state, investment choices and next actions