CBA (Other exams) cheat sheet

Business Architecture is defined as a blueprint of the enterprise that provides a common understanding of the organization and is used to align strategic objectives and tactical demands.

The BIZBOK® Guide is organized around a set of business architecture domains: value delivery, capability, information, organization, and strategy; initiatives and stakeholders are cross-cutting concerns.

The Business Architecture Guild® publishes the BIZBOK® Guide; the CBA (Certified Business Architect) credential is associated with that body of knowledge, but this material is independent and not affiliated with the Guild.

Core mapping technique: value stream maps show how value is delivered to a stakeholder; each value stream stage is enabled by capabilities drawn from a capability map.

Capability maps are structured hierarchically (Level 1, Level 2, Level 3) and describe what the business does, not how, who, or when - they are stable relative to processes and org charts.

The Business Architecture Framework (BAF) in BIZBOK aligns business architecture with business strategy, IT architecture, and execution via a set of blueprints and mappings.

A business model canvas or value proposition view connects strategy to business architecture by identifying customers, value propositions, channels, and revenue/cost structures.

Cross-mapping principle: business architecture artifacts are linked through mappings (e.g., capability-to-value-stream, capability-to-organization, capability-to-initiative) rather than duplicated in each view.

Business architecture is used for decision support across transformation, investment prioritization, merger integration, and regulatory response - it is a discipline, not a one-time deliverable.

A value stream is an end-to-end collection of activities that create value for a customer/stakeholder; it is triggered by a value item and ends when that value item is delivered.

Value stream stages are named with a verb-noun pattern (e.g., "Acquire Product") and each stage has entry/exit criteria plus participating capabilities.

A capability is the ability of the business to do something; capabilities are named as noun-verb (e.g., "Customer Management") and are business-facing, not technology-facing.

Capability decomposition rules: a capability at Level 2 should be a meaningful, stable business ability; Level 3 decomposes further only when needed for mapping or heat-mapping.

Heat maps overlay a dimension (e.g., maturity, investment, risk, performance) on a capability or value stream map to support prioritization decisions.

Value stream mapping outputs include: stakeholder value items, stages, stage descriptions, triggering/entry/exit events, capabilities, and value items produced per stage.

A capability map is not an org chart: the same capability may be performed by multiple business units, and one unit may own multiple capabilities.

Information map artifacts include business objects, information concepts, and their relationships; information maps link to capabilities and value streams to show what information is needed where.

Organization map artifacts include business units, teams, and their relationships; organization-to-capability mappings reveal ownership and gaps.

Strategy mapping connects business architecture to strategy via value proposition, business model, and strategic objectives; strategy is a cross-cutting domain in BIZBOK.

Initiative mapping links business architecture to execution: initiatives are mapped to capabilities and value streams to show impact and dependencies.

Stakeholder mapping identifies who consumes business architecture outputs and what decisions they support; stakeholder concerns drive which views are produced.

Business architecture governance defines how artifacts are created, maintained, versioned, and approved; without governance, maps become stale and untrusted.

The business architecture 'blueprint' is a set of integrated views (capability, value, information, organization) plus mappings, not a single diagram.

Maturity model for business architecture typically progresses from ad hoc/isolated diagrams to standardized frameworks, to integrated enterprise-wide architecture, to strategy-driven decision support.

Business architecture value is measured by decisions enabled: cost reduction, faster time-to-market, reduced duplication, improved regulatory compliance, and better investment prioritization.

A capability-based investment analysis compares initiatives by which capabilities they change, their cost, and their strategic value - supporting portfolio prioritization.

Business architecture supports merger and acquisition integration by comparing capability maps and value streams of two organizations to identify overlap and gaps.

Business architecture supports customer-centric design by starting from value streams (customer journey) and tracing to enabling capabilities and information.

Business architecture is often positioned as the bridge between business strategy and IT architecture: strategy defines intent, business architecture defines what the business must do, IT architecture defines how systems support it.

Common failure mode: treating business architecture as a documentation exercise rather than a decision-support discipline tied to active initiatives.

Value stream vs. process: a value stream is a business-level, end-to-end view of value delivery; a process is a detailed, often system-level sequence of tasks that implements a value stream stage.

Capability vs. process: capabilities are stable 'what' the business can do; processes are 'how' work is performed and change more frequently.

Capability vs. function: functions often reflect organizational structure (departments); capabilities reflect business abilities independent of structure.

Value stream vs. capability: value streams show flow and sequence; capabilities show ability and are reusable across multiple value streams.

Business architecture artifact quality criteria: clear scope, consistent naming, defined owner, version control, and traceability to other artifacts via mappings.

Mapping discipline: every capability in a value stream should trace to a capability in the capability map; orphan capabilities or orphan stages signal gaps in the architecture.

Business architecture frameworks (e.g., BIZBOK, TOGAF) overlap but differ in emphasis: BIZBOK emphasizes business architecture domains and mappings; TOGAF provides an enterprise architecture method (ADM) that consumes business architecture.

CBA exam preparation should focus on definitions, artifact purposes, and mapping relationships rather than tool-specific implementation.

A business architecture 'view' is a representation of one or more artifacts for a specific stakeholder concern; multiple views can be generated from the same underlying model.

Business architecture repositories should support relationships (many-to-many) between capabilities, value streams, information, organization units, and initiatives.

Capability heat maps commonly use color coding (e.g., red/amber/green) to show performance, maturity, or risk; the legend must be defined explicitly.

Value stream stages should be mutually exclusive and collectively exhaustive for the value item being delivered; overlapping stages create ambiguity.

Business architecture should be maintained at a level of abstraction that is stable over 12-24 months; lower-level detail belongs to process or solution architecture.

Stakeholder communication: executives need capability/value stream summaries and heat maps; operational teams need detailed mappings and stage descriptions.

Business architecture's relationship to IT: business capabilities and value streams define requirements and context for application and technology architecture.

Business architecture's relationship to data: information maps identify business objects and concepts that data architecture must support.

Business architecture's relationship to operating model: the operating model defines how the organization delivers value; business architecture provides the structured views that describe it.

Business architecture's relationship to portfolio management: capability maps provide the organizing structure for application and initiative portfolios.

Business architecture's relationship to risk and compliance: value streams and capabilities can be mapped to regulatory obligations to show where controls are needed.

Business architecture's relationship to customer experience: value streams model the customer journey and reveal pain points and opportunities for improvement.

Business architecture's relationship to change management: impact analysis uses mappings to determine which capabilities, information, and organizations are affected by a change.

Business architecture artifacts should be traceable: strategy objective → value stream → capability → information → organization → initiative.

Traceability enables impact analysis: a change in strategy can be traced forward to initiatives; a change in a system can be traced back to capabilities and value streams.

Business architecture governance roles typically include architecture owner, artifact owners, and a review board; roles must be defined to avoid stale artifacts.

Business architecture should be versioned and baselined; changes should be recorded with rationale and approval to maintain trust.

Business architecture should be published in a consumable form (e.g., navigable repository, summary views) for stakeholders, not just stored in modeling tools.

Business architecture maturity assessment should evaluate: artifact coverage, mapping completeness, governance, stakeholder adoption, and decision impact.

Business architecture value story: reduce duplication, speed change, improve decisions, and align business and IT - each claim should be supported by evidence from actual use.

Capability naming convention: use noun-verb or noun-noun phrases that describe a business ability (e.g., "Order Management"), avoid technology terms and organizational names.

Value stream naming convention: use verb-noun phrases for stages that describe the value-adding activity (e.g., "Fulfill Order"), and name the value stream after the value item delivered.

Information map naming: business objects should be named as business concepts (e.g., "Customer", "Order"), not as database tables.

Organization map naming: use official organizational unit names and define reporting relationships clearly.

Initiative mapping naming: use initiative names from the portfolio and map to the capabilities and value streams they affect.

Stakeholder map naming: identify stakeholder groups by role and decision authority, not by individual names.

Consistent naming across artifacts is a prerequisite for reliable cross-mapping and search.

Business architecture is not a project: it is an ongoing capability that maintains a set of integrated views and mappings over time.

Business architecture outputs should be tied to a decision calendar: which decisions need which views, and when.

Business architecture should be scoped: enterprise-wide, business unit, or domain-level scope changes the level of detail and governance required.

Business architecture should be validated with business stakeholders, not only architects; validation ensures the maps reflect reality.

Business architecture should be linked to performance metrics: capabilities and value streams can be measured to show improvement over time.

Business architecture should be linked to funding: initiatives funded should trace to strategic capabilities and value streams.

Business architecture should be linked to risk: capabilities and value streams with high risk exposure should be identified and mitigated.

Business architecture frameworks provide a common language; without a common language, mappings across business units are unreliable.

Business architecture should be built incrementally: start with a capability map and a few value streams, then add information, organization, and initiative mappings as needed.

Business architecture should be reusable: artifacts built for one initiative should be reused for others to avoid duplicated effort.

Business architecture should be governed by a lightweight process: artifact creation, review, approval, publication, and periodic refresh.

Business architecture should be measured by adoption: how many initiatives use the maps, how many decisions cite them, and how often they are refreshed.

Business architecture should be communicated visually: heat maps, value stream diagrams, and capability maps are more effective than text-heavy documents.

Business architecture should be honest about uncertainty: mark artifacts as draft or needs-review when evidence is incomplete.

Business architecture's core question: what does the business do, for whom, with what information, and how is it organized to deliver value?

Business architecture's core answer: a set of integrated, mapped views (capability, value, information, organization, strategy, initiative, stakeholder) that support decisions.

Business architecture's core discipline: maintain mappings and traceability so that changes can be analyzed end-to-end.

Business architecture's core stakeholders: executives, business unit leaders, IT leaders, risk/compliance, and initiative owners.

Business architecture's core outputs: capability map, value stream map, information map, organization map, and cross-mappings.

Business architecture's core value: better decisions about investment, change, and organization design.

Business architecture's core risk: stale or unused artifacts that create false confidence.

Capability-based planning uses the capability map as the organizing structure for planning investments and initiatives.

Value stream-based planning uses value streams to prioritize improvements that directly affect customer/stakeholder value.

Business architecture supports business model innovation by exposing which capabilities and value streams would need to change for a new business model.

Business architecture supports operating model design by defining capabilities, value streams, information, and organization views that describe the target operating model.

Business architecture supports digital transformation by providing the business context and priorities for technology investments.

Business architecture supports regulatory change by mapping obligations to value streams and capabilities to identify impacted areas.

Business architecture supports cost optimization by revealing duplicated capabilities and redundant value stream stages across business units.

Business architecture artifact ownership: each artifact should have a named owner responsible for accuracy and refresh.

Business architecture review cadence: artifacts should be reviewed at least annually or when a major change occurs.

Business architecture versioning: use version numbers and change logs to track artifact evolution.

Business architecture access: publish artifacts to a repository with role-based access and search.

Business architecture training: stakeholders need orientation on how to read and use the maps.

Business architecture metrics: track artifact coverage, mapping completeness, refresh timeliness, and usage in decisions.

Business architecture continuous improvement: use feedback from stakeholders to refine artifacts and mappings.

A capability map should be stable: capabilities change slowly, while processes and organizations change faster.

A value stream map should be customer-centric: start and end with the value item delivered to the stakeholder.

An information map should be business-facing: name business objects and concepts, not database schemas.

An organization map should be structural: show units, reporting lines, and relationships, not individual performance.

A strategy map should be intent-focused: show objectives and value propositions, not detailed plans.

An initiative map should be impact-focused: show which capabilities and value streams each initiative changes.

A stakeholder map should be decision-focused: show who needs which views and for what decisions.

Business architecture is a team sport: it requires collaboration between business and IT, and between architects and stakeholders.

Business architecture requires executive sponsorship: without it, artifacts are not adopted and mappings are not maintained.

Business architecture requires a common language: define terms and naming conventions up front.

Business architecture requires discipline: mappings must be maintained, not created once and forgotten.

Business architecture requires pragmatism: produce the minimum set of artifacts needed for the decisions at hand.

Business architecture requires transparency: mark assumptions and uncertainties clearly.

Business architecture requires iteration: start small, prove value, and expand.

Business architecture's relationship to enterprise architecture: business architecture is a domain of enterprise architecture focused on business capabilities, value, information, and organization.

Business architecture's relationship to solution architecture: business architecture provides context and requirements; solution architecture provides the detailed design.

Business architecture's relationship to process architecture: business architecture defines capabilities and value streams; process architecture defines the detailed processes that implement them.

Business architecture's relationship to data architecture: business architecture defines business information concepts; data architecture defines the data structures and models.

Business architecture's relationship to application architecture: business architecture defines capabilities and value streams; application architecture defines the applications that support them.

Business architecture's relationship to technology architecture: business architecture defines business requirements; technology architecture defines the infrastructure.

Business architecture's relationship to security architecture: business architecture defines business assets and value flows; security architecture defines controls to protect them.

Business architecture should be used to answer: where should we invest, what should we change, how should we organize, and what information do we need?

Business architecture should be used to avoid: duplicated capabilities, redundant initiatives, and misaligned technology investments.

Business architecture should be used to accelerate: change delivery by providing reusable context and impact analysis.

Business architecture should be used to align: business strategy, operating model, and technology roadmap.

Business architecture should be used to communicate: a shared understanding of the business across stakeholders.

Business architecture should be used to govern: change and investment decisions with traceable evidence.

Business architecture should be used to measure: performance of capabilities and value streams over time.

Business architecture's core artifacts are not documents but models: structured, related, and queryable representations of the business.

Business architecture models should be stored in a repository that supports relationships and queries.

Business architecture models should be exportable to views for stakeholders who do not use modeling tools.

Business architecture models should be validated with business stakeholders to ensure accuracy.

Business architecture models should be versioned and baselined to support change analysis.

Business architecture models should be governed to ensure quality and consistency.

Business architecture models should be used to support decisions, not just documentation.

Business architecture's value is realized when artifacts are used in decisions: investment, change, organization design, and risk management.

Business architecture's value is measured by outcomes: reduced duplication, faster change, better alignment, and improved compliance.

Business architecture's value is communicated through stories: show how a specific decision was improved by using the maps.

Business architecture's value is sustained through governance: without refresh, artifacts lose value.

Business architecture's value is amplified through reuse: artifacts built once should serve many initiatives.

Business architecture's value is protected through quality: inaccurate maps undermine trust.

Business architecture's value is expanded through adoption: more stakeholders using the maps increases value.

Business architecture's scope should be defined explicitly: enterprise, business unit, or domain.

Business architecture's level of detail should be defined explicitly: capability level, value stream stage level, and information concept level.

Business architecture's stakeholders should be identified explicitly: who needs which views and for what decisions.

Business architecture's governance should be defined explicitly: who creates, reviews, approves, and refreshes artifacts.

Business architecture's metrics should be defined explicitly: coverage, completeness, timeliness, and usage.

Business architecture's roadmap should be defined explicitly: which artifacts to build first and why.

Business architecture's risks should be defined explicitly: stale artifacts, low adoption, and misalignment.

Business architecture's relationship to strategy: strategy defines goals; business architecture defines what the business must do to achieve them.

Business architecture's relationship to execution: business architecture defines the capabilities and value streams that initiatives change.

Business architecture's relationship to governance: business architecture provides the traceability needed to govern change and investment.

Business architecture's relationship to risk: business architecture identifies where capabilities and value streams are exposed to risk.

Business architecture's relationship to compliance: business architecture maps obligations to capabilities and value streams.

Business architecture's relationship to customer experience: business architecture models the customer journey as a value stream.

Business architecture's relationship to innovation: business architecture exposes where change is needed to support new value propositions.

Business architecture's core technique is mapping: linking artifacts to show relationships and enable analysis.

Business architecture's core discipline is maintenance: keeping maps current and accurate.

Business architecture's core output is insight: understanding the business well enough to make better decisions.

Business architecture's core constraint is time: artifacts must be produced fast enough to be useful.

Business architecture's core risk is irrelevance: artifacts that are not used or not trusted.

Business architecture's core opportunity is reuse: artifacts that serve many decisions.

Business architecture's core measure is impact: decisions improved by using the maps.

Business architecture's relationship to business model: the business model defines how value is created and captured; business architecture defines the capabilities and value streams that deliver it.

Business architecture's relationship to operating model: the operating model defines how the organization is structured to deliver value; business architecture provides the views that describe it.

Business architecture's relationship to capability-based planning: capability maps are the organizing structure for planning.

Business architecture's relationship to value stream-based planning: value streams are the organizing structure for customer-centric improvement.

Business architecture's relationship to information management: information maps define the business information needed to support capabilities and value streams.

Business architecture's relationship to organization design: organization maps define units and relationships that support capabilities and value streams.

Business architecture's relationship to initiative portfolio: initiative maps link initiatives to the capabilities and value streams they change.

Business architecture's key deliverable is a set of integrated views, not a single document.

Business architecture's key success factor is executive sponsorship and stakeholder adoption.

Business architecture's key challenge is maintaining accuracy over time.

Business architecture's key enabler is a repository that supports relationships and queries.

Business architecture's key metric is usage in decisions.

Business architecture's key risk is stale or inaccurate artifacts.

Business architecture's key opportunity is reuse across initiatives.

Business architecture's relationship to IT portfolio: capability maps organize applications and initiatives by business capability.

Business architecture's relationship to data governance: information maps define business information concepts that data governance must manage.

Business architecture's relationship to risk management: value streams and capabilities can be assessed for risk exposure.

Business architecture's relationship to compliance: obligations can be mapped to capabilities and value streams to identify controls.

Business architecture's relationship to customer experience: value streams model the customer journey and reveal improvement opportunities.

Business architecture's relationship to change management: impact analysis uses mappings to determine affected areas.

Business architecture's relationship to performance management: capabilities and value streams can be measured to track improvement.

Business architecture's core question for any artifact: what decision does this support?

Business architecture's core question for any mapping: what does this relationship enable us to analyze?

Business architecture's core question for any view: who is the audience and what do they need to see?

Business architecture's core question for any governance: who owns this and when will it be refreshed?

Business architecture's core question for any metric: how does this demonstrate value?

Business architecture's core question for any initiative: which capabilities and value streams does it change?

Business architecture's core question for any stakeholder: what decisions do they make and what views support them?

Business architecture's relationship to strategy: strategy sets direction; business architecture translates direction into capabilities and value streams.

Business architecture's relationship to execution: business architecture provides the context for initiatives and change.

Business architecture's relationship to governance: business architecture provides traceability for decisions.

Business architecture's relationship to risk: business architecture identifies exposure and controls.

Business architecture's relationship to compliance: business architecture maps obligations to business areas.

Business architecture's relationship to customer experience: business architecture models value delivery to customers.

Business architecture's relationship to innovation: business architecture identifies where change is needed.

Business architecture's core artifact set: capability map, value stream map, information map, organization map, strategy map, initiative map, stakeholder map.

Business architecture's core mapping set: capability-to-value-stream, capability-to-information, capability-to-organization, capability-to-initiative, value-stream-to-stakeholder.

Business architecture's core governance set: artifact ownership, review cadence, versioning, publication, and metrics.

Business architecture's core value set: better decisions, reduced duplication, faster change, improved alignment, and stronger compliance.

Business architecture's core risk set: stale artifacts, low adoption, misalignment, and inaccurate maps.

Business architecture's core opportunity set: reuse, cross-initiative insight, and strategic alignment.

Business architecture's core discipline set: mapping, maintenance, validation, and communication.

Business architecture's relationship to business model canvas: the canvas defines value proposition and customer segments; business architecture defines the capabilities and value streams that deliver them.

Business architecture's relationship to operating model canvas: the operating model canvas defines how value is delivered; business architecture provides the structured views.

Business architecture's relationship to capability-based planning: capability maps are the organizing structure for investment planning.

Business architecture's relationship to value stream-based planning: value streams are the organizing structure for customer-centric improvement.

Business architecture's relationship to information management: information maps define business information needs.

Business architecture's relationship to organization design: organization maps define units and relationships.

Business architecture's relationship to initiative portfolio: initiative maps link initiatives to capabilities and value streams.

Business architecture's core principle: describe what the business does, not how it does it.

Business architecture's core principle: keep artifacts stable and reusable.

Business architecture's core principle: map relationships to enable analysis.

Business architecture's core principle: govern artifacts to maintain trust.

Business architecture's core principle: use artifacts to support decisions.

Business architecture's core principle: communicate visually and clearly.

Business architecture's core principle: iterate and improve based on feedback.

Business architecture's relationship to strategy: strategy defines goals and value propositions; business architecture defines the capabilities and value streams required to achieve them.

Business architecture's relationship to execution: business architecture defines the capabilities and value streams that initiatives change, enabling impact analysis.

Business architecture's relationship to governance: business architecture provides traceability from strategy to initiative, supporting investment decisions.

Business architecture's relationship to risk: business architecture identifies where capabilities and value streams are exposed to risk and where controls are needed.

Business architecture's relationship to compliance: business architecture maps regulatory obligations to capabilities and value streams.

Business architecture's relationship to customer experience: business architecture models the customer journey as a value stream and identifies improvement opportunities.

Business architecture's relationship to innovation: business architecture exposes where capabilities and value streams must change to support new value propositions.

Business architecture's core artifact: capability map - a hierarchical view of what the business can do.

Business architecture's core artifact: value stream map - an end-to-end view of how value is delivered to a stakeholder.

Business architecture's core artifact: information map - a view of business objects and concepts and their relationships.

Business architecture's core artifact: organization map - a view of business units and their relationships.

Business architecture's core artifact: strategy map - a view of objectives and value propositions.

Business architecture's core artifact: initiative map - a view of initiatives and the capabilities/value streams they change.

Business architecture's core artifact: stakeholder map - a view of stakeholders and the decisions they make.

Business architecture's core mapping: capability-to-value-stream shows which capabilities enable which value stream stages.

Business architecture's core mapping: capability-to-information shows which information concepts are needed by which capabilities.

Business architecture's core mapping: capability-to-organization shows which units own or perform which capabilities.

Business architecture's core mapping: capability-to-initiative shows which initiatives change which capabilities.

Business architecture's core mapping: value-stream-to-stakeholder shows which stakeholders receive which value.

Business architecture's core mapping: strategy-to-capability shows which capabilities are strategic priorities.

Business architecture's core mapping: risk-to-capability shows where risk exposure is concentrated.

Business architecture's core governance: define artifact owners and review cadence.

Business architecture's core governance: version and baseline artifacts.

Business architecture's core governance: publish artifacts for stakeholders.

Business architecture's core governance: measure artifact usage and quality.

Business architecture's core governance: refresh artifacts on a schedule and on major change.

Business architecture's core governance: validate artifacts with business stakeholders.

Business architecture's core governance: maintain mappings as artifacts evolve.

Business architecture's core value: better investment decisions through capability-based prioritization.

Business architecture's core value: faster change through reusable context and impact analysis.

Business architecture's core value: reduced duplication through visibility of overlapping capabilities and value streams.

Business architecture's core value: improved alignment through shared understanding of strategy, business, and IT.

Business architecture's core value: stronger compliance through mapping obligations to business areas.

Business architecture's core value: better customer experience through value stream analysis.

Business architecture's core value: improved risk management through capability and value stream risk assessment.

Business architecture's core risk: artifacts become stale and are no longer trusted.

Business architecture's core risk: low adoption because artifacts are not tied to decisions.

Business architecture's core risk: misalignment because mappings are incomplete or inconsistent.

Business architecture's core risk: over-documentation that slows delivery.

Business architecture's core risk: under-documentation that leaves decisions without context.

Business architecture's core risk: unclear ownership that leads to unmaintained artifacts.

Business architecture's core risk: inconsistent naming that breaks cross-mapping.

Business architecture's core metric: artifact coverage - percentage of the business covered by capability and value stream maps.

Business architecture's core metric: mapping completeness - percentage of artifacts with defined cross-mappings.

Business architecture's core metric: refresh timeliness - percentage of artifacts reviewed within the defined cadence.

Business architecture's core metric: usage - number of decisions or initiatives that reference the artifacts.

Business architecture's core metric: stakeholder satisfaction - feedback from stakeholders on artifact usefulness.

Business architecture's core metric: quality - accuracy and consistency of artifacts.

Business architecture's core metric: impact - measurable outcomes attributed to business architecture use.

Business architecture's core practice: start with a capability map and a few value streams to establish a common language.

Business architecture's core practice: add information, organization, and initiative mappings as decisions require.

Business architecture's core practice: validate artifacts with business stakeholders.

Business architecture's core practice: govern artifacts with clear ownership and cadence.

Business architecture's core practice: publish artifacts in a consumable form.

Business architecture's core practice: measure usage and impact.

Business architecture's core practice: iterate based on feedback.

Business architecture's core relationship to strategy: strategy defines intent; business architecture defines the business abilities and value flows required to realize it.

Business architecture's core relationship to execution: business architecture defines the context for initiatives and change.

Business architecture's core relationship to governance: business architecture provides traceability for decisions.

Business architecture's core relationship to risk: business architecture identifies exposure and controls.

Business architecture's core relationship to compliance: business architecture maps obligations to business areas.

Business architecture's core relationship to customer experience: business architecture models value delivery.

Business architecture's core relationship to innovation: business architecture identifies where change is needed.

Business architecture's core artifact quality: clear scope, consistent naming, defined owner, version control, traceability.

Business architecture's core artifact quality: stakeholder relevance - each artifact supports a specific decision.

Business architecture's core artifact quality: accuracy - validated with business stakeholders.

Business architecture's core artifact quality: currency - refreshed on schedule.

Business architecture's core artifact quality: accessibility - published and searchable.

Business architecture's core artifact quality: consistency - naming and mapping conventions applied.

Business architecture's core artifact quality: completeness - mappings defined for all relevant artifacts.

Business architecture's core technique: capability mapping - hierarchical decomposition of business abilities.

Business architecture's core technique: value stream mapping - end-to-end modeling of value delivery.

Business architecture's core technique: information mapping - modeling business objects and concepts.

Business architecture's core technique: organization mapping - modeling units and relationships.

Business architecture's core technique: strategy mapping - modeling objectives and value propositions.

Business architecture's core technique: initiative mapping - linking initiatives to capabilities and value streams.

Business architecture's core technique: stakeholder mapping - linking stakeholders to decisions and views.

Business architecture's core output: a set of integrated views that describe the business.

Business architecture's core output: mappings that enable impact analysis and traceability.

Business architecture's core output: heat maps that support prioritization.

Business architecture's core output: governance artifacts that maintain quality.

Business architecture's core output: metrics that demonstrate value.

Business architecture's core output: communication materials for stakeholders.

Business architecture's core output: decision support for investment, change, and organization design.

Business architecture's core audience: executives, business unit leaders, IT leaders, risk/compliance, and initiative owners.

Business architecture's core audience need: clear, visual, decision-relevant views.

Business architecture's core audience need: traceability from strategy to execution.

Business architecture's core audience need: impact analysis for change.

Business architecture's core audience need: prioritization support for investment.

Business architecture's core audience need: shared understanding across business and IT.

Business architecture's core audience need: confidence in artifact accuracy and currency.

Business architecture's core challenge: maintaining accuracy as the business changes.

Business architecture's core challenge: achieving adoption across stakeholders.

Business architecture's core challenge: balancing detail with usability.

Business architecture's core challenge: aligning business and IT perspectives.

Business architecture's core challenge: demonstrating value with evidence.

Business architecture's core challenge: governing artifacts without slowing delivery.

Business architecture's core challenge: keeping mappings complete and consistent.

Business architecture's core enabler: executive sponsorship.

Business architecture's core enabler: a common language and naming conventions.

Business architecture's core enabler: a repository that supports relationships and queries.

Business architecture's core enabler: clear governance and ownership.

Business architecture's core enabler: stakeholder engagement and validation.

Business architecture's core enabler: metrics that demonstrate value.

Business architecture's core enabler: iteration and continuous improvement.

Business architecture's core principle: describe what, not how.

Business architecture's core principle: keep artifacts stable and reusable.

Business architecture's core principle: map relationships to enable analysis.

Business architecture's core principle: govern artifacts to maintain trust.

Business architecture's core principle: use artifacts to support decisions.

Business architecture's core principle: communicate visually and clearly.

Business architecture's core principle: iterate and improve based on feedback.

Business architecture's core relationship to strategy: strategy defines goals; business architecture defines the capabilities and value streams required.

Business architecture's core relationship to execution: business architecture defines the context for initiatives.

Business architecture's core relationship to governance: business architecture provides traceability for decisions.

Business architecture's core relationship to risk: business architecture identifies exposure and controls.

Business architecture's core relationship to compliance: business architecture maps obligations to business areas.

Business architecture's core relationship to customer experience: business architecture models value delivery.

Business architecture's core relationship to innovation: business architecture identifies where change is needed.

Business architecture's core artifact: capability map - hierarchical view of business abilities.

Business architecture's core artifact: value stream map - end-to-end view of value delivery.

Business architecture's core artifact: information map - view of business objects and concepts.

Business architecture's core artifact: organization map - view of business units and relationships.

Business architecture's core artifact: strategy map - view of objectives and value propositions.

Business architecture's core artifact: initiative map - view of initiatives and their impacts.

Business architecture's core artifact: stakeholder map - view of stakeholders and their decisions.

Business architecture's core mapping: capability-to-value-stream.

Business architecture's core mapping: capability-to-information.

Business architecture's core mapping: capability-to-organization.

Business architecture's core mapping: capability-to-initiative.

Business architecture's core mapping: value-stream-to-stakeholder.

Business architecture's core mapping: strategy-to-capability.

Business architecture's core mapping: risk-to-capability.

Business architecture's core governance: artifact ownership.

Business architecture's core governance: review cadence.

Business architecture's core governance: versioning and baselining.

Business architecture's core governance: publication and access.

Business architecture's core governance: metrics and reporting.

Business architecture's core governance: refresh on change.

Business architecture's core governance: stakeholder validation.

Business architecture's core value: better investment decisions.

Business architecture's core value: faster change.

Business architecture's core value: reduced duplication.

Business architecture's core value: improved alignment.

Business architecture's core value: stronger compliance.

Business architecture's core value: better customer experience.

Business architecture's core value: improved risk management.

Business architecture's core risk: stale artifacts.

Business architecture's core risk: low adoption.

Business architecture's core risk: misalignment.

Business architecture's core risk: over-documentation.

Business architecture's core risk: under-documentation.

Business architecture's core risk: unclear ownership.

Business architecture's core risk: inconsistent naming.

Business architecture's core metric: artifact coverage.

Business architecture's core metric: mapping completeness.

Business architecture's core metric: refresh timeliness.

Business architecture's core metric: usage in decisions.

Business architecture's core metric: stakeholder satisfaction.

Business architecture's core metric: artifact quality.

Business architecture's core metric: measurable impact.

Business architecture's core practice: start with a capability map and a few value streams.

Business architecture's core practice: add information, organization, and initiative mappings as needed.

Business architecture's core practice: validate with business stakeholders.

Business architecture's core practice: govern with clear ownership and cadence.

Business architecture's core practice: publish in a consumable form.

Business architecture's core practice: measure usage and impact.

Business architecture's core practice: iterate based on feedback.

Business architecture's core relationship to strategy: strategy defines intent; business architecture defines the business abilities and value flows required.

Business architecture's core relationship to execution: business architecture defines the context for initiatives and change.

Business architecture's core relationship to governance: business architecture provides traceability for decisions.

Business architecture's core relationship to risk: business architecture identifies exposure and controls.

Business architecture's core relationship to compliance: business architecture maps obligations to business areas.

Business architecture's core relationship to customer experience: business architecture models value delivery.

Business architecture's core relationship to innovation: business architecture identifies where change is needed.

Business architecture's core artifact quality: clear scope.

Business architecture's core artifact quality: consistent naming.

Business architecture's core artifact quality: defined owner.

Business architecture's core artifact quality: version control.

Business architecture's core artifact quality: traceability.

Business architecture's core artifact quality: stakeholder relevance.

Business architecture's core artifact quality: accuracy and currency.

Business architecture's core technique: capability mapping.

Business architecture's core technique: value stream mapping.

Business architecture's core technique: information mapping.

Business architecture's core technique: organization mapping.

Business architecture's core technique: strategy mapping.

Business architecture's core technique: initiative mapping.

Business architecture's core technique: stakeholder mapping.

Business architecture's core output: integrated views.

Business architecture's core output: mappings for traceability.

Business architecture's core output: heat maps for prioritization.

Business architecture's core output: governance artifacts.

Business architecture's core output: metrics.

Business architecture's core output: communication materials.

Business architecture's core output: decision support.

Business architecture's core audience: executives.

Business architecture's core audience: business unit leaders.

Business architecture's core audience: IT leaders.

Business architecture's core audience: risk and compliance.

Business architecture's core audience: initiative owners.

Business architecture's core audience: architects.

Business architecture's core audience: stakeholders across the enterprise.

Business architecture's core challenge: maintaining accuracy.

Business architecture's core challenge: achieving adoption.

Business architecture's core challenge: balancing detail and usability.

Business architecture's core challenge: aligning business and IT.

Business architecture's core challenge: demonstrating value.

Business architecture's core challenge: governing without slowing delivery.

Business architecture's core challenge: keeping mappings consistent.

Business architecture's core enabler: executive sponsorship.

Business architecture's core enabler: common language.

Business architecture's core enabler: repository with relationships.

Business architecture's core enabler: clear governance.

Business architecture's core enabler: stakeholder engagement.

Business architecture's core enabler: metrics.

Business architecture's core enabler: iteration.

Business architecture's core principle: describe what, not how.

Business architecture's core principle: keep artifacts stable.

Business architecture's core principle: map relationships.

Business architecture's core principle: govern artifacts.

Business architecture's core principle: support decisions.

Business architecture's core principle: communicate visually.

Business architecture's core principle: iterate.

Business architecture's core relationship to strategy: strategy defines goals; business architecture defines capabilities and value streams.

Business architecture's core relationship to execution: business architecture defines context for initiatives.

Business architecture's core relationship to governance: business architecture provides traceability.

Business architecture's core relationship to risk: business architecture identifies exposure.

Business architecture's core relationship to compliance: business architecture maps obligations.

Business architecture's core relationship to customer experience: business architecture models value delivery.

Business architecture's core relationship to innovation: business architecture identifies change needs.

Business architecture's core artifact: capability map.

Business architecture's core artifact: value stream map.

Business architecture's core artifact: information map.

Business architecture's core artifact: organization map.

Business architecture's core artifact: strategy map.

Business architecture's core artifact: initiative map.

Business architecture's core artifact: stakeholder map.

Business architecture's core mapping: capability-to-value-stream.

Business architecture's core mapping: capability-to-information.

Business architecture's core mapping: capability-to-organization.

Business architecture's core mapping: capability-to-initiative.

Business architecture's core mapping: value-stream-to-stakeholder.

Business architecture's core mapping: strategy-to-capability.

Business architecture's core mapping: risk-to-capability.

Business architecture's core governance: artifact ownership.

Business architecture's core governance: review cadence.

Business architecture's core governance: versioning.

Business architecture's core governance: publication.

Business architecture's core governance: metrics.

Business architecture's core governance: refresh on change.

Business architecture's core governance: stakeholder validation.

Business architecture's core value: better decisions.

Business architecture's core value: faster change.

Business architecture's core value: reduced duplication.

Business architecture's core value: improved alignment.

Business architecture's core value: stronger compliance.

Business architecture's core value: better customer experience.

Business architecture's core value: improved risk management.

Business architecture's core risk: stale artifacts.

Business architecture's core risk: low adoption.

Business architecture's core risk: misalignment.

Business architecture's core risk: over-documentation.

Business architecture's core risk: under-documentation.

Business architecture's core risk: unclear ownership.

Business architecture's core risk: inconsistent naming.

Business architecture's core metric: artifact coverage.

Business architecture's core metric: mapping completeness.

Business architecture's core metric: refresh timeliness.

Business architecture's core metric: usage.

Business architecture's core metric: stakeholder satisfaction.

Business architecture's core metric: quality.

Business architecture's core metric: impact.

Business architecture's core practice: start with a capability map and a few value streams.

Business architecture's core practice: add mappings as needed.

Business architecture's core practice: validate with stakeholders.

Business architecture's core practice: govern with clear ownership.

Business architecture's core practice: publish in a consumable form.

Business architecture's core practice: measure usage and impact.

Business architecture's core practice: iterate based on feedback.

Business architecture's core relationship to strategy: strategy defines intent; business architecture defines capabilities and value streams.

Business architecture's core relationship to execution: business architecture defines context for initiatives.

Business architecture's core relationship to governance: business architecture provides traceability.

Business architecture's core relationship to risk: business architecture identifies exposure.

Business architecture's core relationship to compliance: business architecture maps obligations.

Business architecture's core relationship to customer experience: business architecture models value delivery.

Business architecture's core relationship to innovation: business architecture identifies change needs.

Business architecture's core artifact quality: clear scope.

Business architecture's core artifact quality: consistent naming.

Business architecture's core artifact quality: defined owner.

Business architecture's core artifact quality: version control.

Business architecture's core artifact quality: traceability.

Business architecture's core artifact quality: stakeholder relevance.

Business architecture's core artifact quality: accuracy.

Business architecture's core technique: capability mapping.

Business architecture's core technique: value stream mapping.

Business architecture's core technique: information mapping.

Business architecture's core technique: organization mapping.

Business architecture's core technique: strategy mapping.

Business architecture's core technique: initiative mapping.

Business architecture's core technique: stakeholder mapping.

Business architecture's core output: integrated views.

Business architecture's core output: mappings.

Business architecture's core output: heat maps.

Business architecture's core output: governance artifacts.

Business architecture's core output: metrics.

Business architecture's core output: communication materials.

Business architecture's core output: decision support.

Business architecture's core audience: executives.

Business architecture's core audience: business unit leaders.

Business architecture's core audience: IT leaders.

Business architecture's core audience: risk and compliance.

Business architecture's core audience: initiative owners.

Business architecture's core audience: architects.

Business architecture's core audience: stakeholders.

Business architecture's core challenge: maintaining accuracy.

Business architecture's core challenge: achieving adoption.

Business architecture's core challenge: balancing detail and usability.

Business architecture's core challenge: aligning business and IT.

Business architecture's core challenge: demonstrating value.

Business architecture's core challenge: governing without slowing delivery.

Business architecture's core challenge: keeping mappings consistent.

Business architecture's core enabler: executive sponsorship.

Business architecture's core enabler: common language.

Business architecture's core enabler: repository.

Business architecture's core enabler: governance.

Business architecture's core enabler: stakeholder engagement.

Business architecture's core enabler: metrics.

Business architecture's core enabler: iteration.

Business architecture's core principle: describe what, not how.

Business architecture's core principle: keep artifacts stable.

Business architecture's core principle: map relationships.

Business architecture's core principle: govern artifacts.

Business architecture's core principle: support decisions.

Business architecture's core principle: communicate visually.

Business architecture's core principle: iterate.

Business architecture's core relationship to strategy: strategy defines goals; business architecture defines capabilities and value streams.

Business architecture's core relationship to execution: business architecture defines context for initiatives.

Business architecture's core relationship to governance: business architecture provides traceability.

Business architecture's core relationship to risk: business architecture identifies exposure.

Business architecture's core relationship to compliance: business architecture maps obligations.

Business architecture's core relationship to customer experience: business architecture models value delivery.

Business architecture's core relationship to innovation: business architecture identifies change needs.

Business architecture's core artifact: capability map.

Business architecture's core artifact: value stream map.

Business architecture's core artifact: information map.

Business architecture's core artifact: organization map.

Business architecture's core artifact: strategy map.

Business architecture's core artifact: initiative map.

Business architecture's core artifact: stakeholder map.

Business architecture's core mapping: capability-to-value-stream.

Business architecture's core mapping: capability-to-information.

Business architecture's core mapping: capability-to-organization.

Business architecture's core mapping: capability-to-initiative.

Business architecture's core mapping: value-stream-to-stakeholder.

Business architecture's core mapping: strategy-to-capability.

Business architecture's core mapping: risk-to-capability.

Business architecture's core governance: artifact ownership.

Business architecture's core governance: review cadence.

Business architecture's core governance: versioning.

Business architecture's core governance: publication.

Business architecture's core governance: metrics.

Business architecture's core governance: refresh on change.

Business architecture's core governance: stakeholder validation.

Business architecture's core value: better decisions.

Business architecture's core value: faster change.

Business architecture's core value: reduced duplication.

Business architecture's core value: improved alignment.

Business architecture's core value: stronger compliance.

Business architecture's core value: better customer experience.

Business architecture's core value: improved risk management.

Business architecture's core risk: stale artifacts.

Business architecture's core risk: low adoption.

Business architecture's core risk: misalignment.

Business architecture's core risk: over-documentation.

Business architecture's core risk: under-documentation.

Business architecture's core risk: unclear ownership.

Business architecture's core risk: inconsistent naming.

Business architecture's core metric: artifact coverage.

Business architecture's core metric: mapping completeness.

Business architecture's core metric: refresh timeliness.

Business architecture's core metric: usage.

Business architecture's core metric: stakeholder satisfaction.

Business architecture's core metric: quality.

Business architecture's core metric: impact.

Business architecture's core practice: start with a capability map and a few value streams.

Business architecture's core practice: add mappings as needed.

Business architecture's core practice: validate with stakeholders.

Business architecture's core practice: govern with clear ownership.

Business architecture's core practice: publish in a consumable form.

Business architecture's core practice: measure usage and impact.

Business architecture's core practice: iterate based on feedback.

Business architecture's core relationship to strategy: strategy defines intent; business architecture defines capabilities and value streams.

Business architecture's core relationship to execution: business architecture defines context for initiatives.

Business architecture's core relationship to governance: business architecture provides traceability.

Business architecture's core relationship to risk: business architecture identifies exposure.

Business architecture's core relationship to compliance: business architecture maps obligations.

Business architecture's core relationship to customer experience: business architecture models value delivery.

Business architecture's core relationship to innovation: business architecture identifies change needs.

Business architecture's core artifact quality: clear scope.

Business architecture's core artifact quality: consistent naming.

Business architecture's core artifact quality: defined owner.

Business architecture's core artifact quality: version control.

Business architecture's core artifact quality: traceability.

Business architecture's core artifact quality: stakeholder relevance.

Business architecture's core artifact quality: accuracy.

Business architecture's core technique: capability mapping.

Business architecture's core technique: value stream mapping.

Business architecture's core technique: information mapping.

Business architecture's core technique: organization mapping.

Business architecture's core technique: strategy mapping.

Business architecture's core technique: initiative mapping.

Business architecture's core technique: stakeholder mapping.

Business architecture's core output: integrated views.

Business architecture's core output: mappings.

Business architecture's core output: heat maps.

Business architecture's core output: governance artifacts.

Business architecture's core output: metrics.

Business architecture's core output: communication materials.

Business architecture's core output: decision support.

Business architecture's core audience: executives.

Business architecture's core audience: business unit leaders.

Business architecture's core audience: IT leaders.

Business architecture's core audience: risk and compliance.

Business architecture's core audience: initiative owners.

Business architecture's core audience: architects.

Business architecture's core audience: stakeholders.

Business architecture's core challenge: maintaining accuracy.

Business architecture's core challenge: achieving adoption.

Business architecture's core challenge: balancing detail and usability.

Business architecture's core challenge: aligning business and IT.

Business architecture's core challenge: demonstrating value.

Business architecture's core challenge: governing without slowing delivery.

Business architecture's core challenge: keeping mappings consistent.

Business architecture's core enabler: executive sponsorship.

Business architecture's core enabler: common language.

Business architecture's core enabler: repository.

Business architecture's core enabler: governance.

Business architecture's core enabler: stakeholder engagement.

Business architecture's core enabler: metrics.

Business architecture's core enabler: iteration.

Business architecture's core principle: describe what, not how.

Business architecture's core principle: keep artifacts stable.

Business architecture's core principle: map relationships.

Business architecture's core principle: govern artifacts.

Business architecture's core principle: support decisions.

Business architecture's core principle: communicate visually.

Business architecture's core principle: iterate.