Ücretsiz Kullanmaya Başla

Enterprise Continuum and Architecture Re-Use Knowledge-Based Study

TOGAF · Architecture Content · Foundation · Enterprise Continuum

Foundation topic explanations on Enterprise Continuum and Architecture Re-Use.

Study notes

  1. What is the Enterprise Continuum?

    In the TOGAF Standard, 10th Edition, the Enterprise Continuum provides a conceptual framework and structure for classifying and organizing architecture and solution artifacts. It serves as a "view" of the Architecture Repository that emphasizes how assets evolve from generic abstractions to organization-specific implementations.

    Key principles of the Enterprise Continuum include:

    • Asset Classification: It offers a consistent categorization model for architectural assets across the entire enterprise.
    • Communication Mechanism: It enables clear communication across architecture teams and stakeholders by structuring assets along a spectrum of abstraction.
    • Context for Architecture Activities: It aids architects in identifying where existing assets can be leveraged across various phases of the Architecture Development Method (ADM).

    The Philosophy of Architecture Re-Use

    A fundamental purpose of the Enterprise Continuum is fostering structured architecture re-use. Rather than developing architecture assets from scratch, architects search the continuum to discover pre-existing patterns, reference models, and implementations.

    Assets within the continuum move along a spectrum from left to right:

    • Generic to Specific: Architectures and solutions become progressively more tailored and contextualized as they move toward organization-specific assets.
    • Inheritance and Specialization: Highly specific enterprise assets inherit principles, requirements, and structural elements defined in generic industry or foundation assets.
    • Feedback Loops: Proven solutions developed specifically within an organization can be abstracted and reclassified as reusable industry or common systems patterns for broader deployment.

    Structure of the Architecture Continuum

    The Architecture Continuum structures architectural building blocks (ABBs), models, and specifications across four distinct levels of abstraction:

    1. Foundation Architectures: Broad, fundamental architectures such as fundamental concepts, international standards, and foundational reference models (e.g., technical reference models).
    2. Common Systems Architectures: Architectures that address common functional needs across multiple business domains (e.g., identity management, security services, messaging buses).
    3. Industry Architectures: Models, standards, and data structures specific to a vertical industry sector (e.g., banking, telecommunications, healthcare).
    4. Organization-Specific Architectures: Highly customized architectures and business designs tailored directly to the unique requirements, structure, and goals of a specific enterprise.

    Structure of the Solutions Continuum

    Running parallel to the Architecture Continuum, the Solutions Continuum represents physical implementations, solutions building blocks (SBBs), and commercial products that realize architectural intent:

    1. Foundation Solutions: Core technology products, operating platforms, and fundamental hardware or virtualized infrastructure services.
    2. Common Systems Solutions: Reusable enterprise software products, common off-the-shelf (COTS) applications, and cross-functional solutions (e.g., unified communication platforms).
    3. Industry Solutions: Domain-specific software packages and marketplace solutions engineered for a given industry sector.
    4. Organization-Specific Solutions: Fully implemented, deployed, and configured operational systems that execute the specific business processes of the enterprise.

    Leveraging the Continuum across ADM Cycles

    During ADM execution, the Enterprise Continuum acts as an active navigation map for architecture teams:

    • In Phase A (Architecture Vision) and Phases B, C, and D (Architecture Domains), architects query the Architecture Continuum for reusable standards, reference architectures, and industry blueprints.
    • In Phase E (Opportunities & Solutions), architects consult the Solutions Continuum to evaluate existing implementations, vendor offerings, and common services against the target architecture definitions.
    • By balancing generic guidance with organization-specific constraints, enterprise architects optimize delivery speed, minimize redundancy, and ensure technical consistency.