What is the Enterprise Continuum?
The Enterprise Continuum is a classification scheme for architecture and solution assets. It helps you:
- Classify architectures and solutions from generic to specific
- Leverage existing assets rather than reinventing
- Communicate how your architecture fits into the broader context
Think of it as a "library classification system" for architecture assets.
The Two Continua
Architecture Continuum
Contains Architecture Building Blocks (ABBs) - what capabilities are needed.
Levels (Generic to Specific):
- Foundation Architectures - TRM (Technical Reference Model), Industry-standard patterns
- Common Systems Architectures - Widely applicable patterns, Cross-industry solutions
- Industry Architectures - Banking reference architecture, Healthcare data models, Retail commerce patterns
- Organization-Specific Architectures - Your company's enterprise architecture, Business-specific solutions
Solutions Continuum
Contains Solution Building Blocks (SBBs) - how capabilities are implemented.
Levels (Generic to Specific):
- Foundation Solutions - Operating systems, Database platforms, Middleware products
- Common Systems Solutions - ERP systems, CRM platforms, Identity management
- Industry Solutions - Banking core systems, Healthcare EMR systems, Retail POS systems
- Organization-Specific Solutions - Custom applications, Configured products, Integrated solutions
The Architecture Repository
The Architecture Repository is the physical/virtual storage of all architecture assets.
Repository Structure
- Architecture Metamodel - Defines artifact types and relationships
- Architecture Capability - Guidelines, templates, governance
- Architecture Landscape - Strategic Architecture, Segment Architectures, Capability Architectures
- Standards Information Base - Industry standards, Technology standards, Organization standards
- Reference Library - Reference architectures, Patterns, Templates
- Governance Log - Decision records, Compliance assessments, Capability assessments
Architecture Landscape Levels
Strategic Architecture
- Scope: Enterprise-wide, 3-5 year horizon
- Purpose: Long-term direction and roadmap
- Detail: High-level, principle-driven
Segment Architecture
- Scope: Major business areas or programs
- Purpose: Support specific business domains
- Detail: Medium-level, capability-focused
Capability Architecture
- Scope: Specific capabilities or projects
- Purpose: Detailed design for implementation
- Detail: High detail, solution-specific
Standards Information Base
Types of Standards
| Category | Examples | |----------|----------| | Business Standards | Business process standards, Data naming conventions | | Data Standards | Data formats, Master data definitions | | Application Standards | Coding standards, API standards | | Technology Standards | Approved products, Security protocols |
Technology Standards Example
| Category | Standard | Emerging | Retiring | |----------|----------|----------|----------| | Cloud Platform | Azure | - | - | | Container Orch | Kubernetes | - | Docker Swarm | | API Gateway | Azure APIM | Kong | - | | CI/CD | GitHub | - | Jenkins | | Database | PostgreSQL | CosmosDB | Oracle | | Identity | Entra ID | - | On-prem AD |
Leveraging the Enterprise Continuum
Process for Reuse
- Search the repository for existing assets
- Evaluate fitness for your need
- Adapt if necessary (don't copy without understanding)
- Apply to your architecture
- Contribute back improvements
Example: Building New Capability
Scenario: Need customer analytics capability
Step 1: Search Architecture Continuum
- Foundation: Generic data analytics patterns ✓
- Common: BI/Analytics reference architectures ✓
- Industry: Retail customer analytics models ✓
- Organization: Existing data platform ✓
Step 2: Search Solutions Continuum
- Foundation: Database, compute platforms ✓
- Common: Power BI, Databricks ✓
- Industry: Customer 360 solutions ✓
- Organization: Existing data lake ✓
Step 3: Compose Solution
- Reused Assets: Organization data lake (existing SBB), Databricks analytics (approved SBB), Power BI dashboards (approved SBB), Customer 360 pattern (industry ABB)
- New Development: Customer scoring model (new component)
- New Development: 15%, Reuse: 85%
Exam Tips
Key Concepts:
- Enterprise Continuum = Classification scheme (not storage)
- Architecture Repository = Physical/virtual storage
- Generic → Specific direction in both continua
- ABB in Architecture Continuum, SBB in Solutions Continuum
Common Questions:
- "What does the Enterprise Continuum classify?" → Architecture and solution assets from generic to specific
- "Where are architecture assets stored?" → Architecture Repository
- "What are the three levels of Architecture Landscape?" → Strategic, Segment, Capability
- "What does the Standards Information Base contain?" → Approved standards and guidelines
Key Takeaway
The Enterprise Continuum helps classify and communicate architecture context, while the Architecture Repository provides the practical storage and governance of assets. Together, they enable enterprise-wide reuse and consistency. The key is not just storing assets, but making them discoverable and maintaining them as living documentation.