A business capability map defines what a business does (its abilities) independently of how it is done. By showing how the ‘Inventory Management’ capability enables specific value streams and business outcomes, it clarifies the strategic context and criticality of the capability. This understanding is fundamental for making an informed build vs. buy decision, as it frames the investment in terms of business value rather than just technical features or immediate cost.

Phase C: Information Systems Architectures is explicitly dedicated to developing the target architectures for the Data (C1) and Application (C2) domains. This phase takes the business architecture defined in Phase B and elaborates how data will be structured and managed and what application components and services will be needed to realize the business architecture and vision.

Availability is a quality that ensures a system or component is operational and accessible when required for use. A single point of failure is a direct threat to system availability. While other requirements like cost-effectiveness are important, the core issue described is the risk of downtime, which is fundamentally an availability concern.

The ADM is a method for deriving an organization-specific architecture. Its early phases (A and B) are crucial for establishing the Architecture Vision, business principles, and business architecture. This foundational work defines the ‘why’ and ‘what,’ creating the necessary context and boundaries. A project plan created without this understanding risks being misaligned with business objectives, missing key requirements, or addressing the wrong problems.

In the TOGAF metamodel, Platform Services are a key artifact of Technology Architecture. They abstract the underlying hardware and software to provide standardized, consumable infrastructure capabilities (e.g., messaging, compute, database services). This concept is central to building service-oriented technology platforms and cloud-based architectures.

The Head of Compliance has high power (veto authority) but low current interest. The appropriate strategy is to ‘Keep satisfied.’ This means ensuring their major concerns (regulatory compliance) are addressed without overwhelming them with excessive detail. Failing to satisfy this stakeholder could lead to late-stage project blockage, despite their low day-to-day involvement.

Phase G: Implementation Governance is the phase where architects provide oversight for the implementation projects. A core activity in this phase is conformance reviews, where the architect checks that the build and implementation work aligns with the agreed target architecture, addressing any compliance issues or authorized deviations.

Gap analysis is a key technique used to identify differences between the Baseline and Target Architectures. These gaps are the primary input for formulating the Architecture Roadmap in Phase E. Each significant gap implies the need for a work package, project, or other initiative to transition from the current state to the future state.

The implications of a principle are critical for making it actionable. They answer the question, ‘What does adhering to this principle mean in practice?’ For ‘Business Continuity,’ implications might include requirements for redundant systems, documented disaster recovery procedures, and specific RTO/RPO targets. This guides designers and implementers in making choices that align with the principle.

A business capability map defines what a business does (its abilities) independently of how it is done. By showing how the ‘Inventory Management’ capability enables specific value streams and business outcomes, it clarifies the strategic context and criticality of the capability. This understanding is fundamental for making an informed build vs. buy decision, as it frames the investment in terms of business value rather than just technical features or immediate cost.0