Why the Enterprise Continuum is a classification scheme rather than a place, and what it does for communication and re-use.
From Ultra Transcenders OGEA-101 by Tony Rough (publishing soon)
The Enterprise Continuum is best understood as a classification scheme rather than a place. It gives the enterprise a way to sort its assets so that people can find, discuss and re-use them.
The Enterprise Continuum is a set of methods for categorising architecture and solution artifacts, whether held inside the Architecture Repository or outside it, as they progress from generic Foundation Architectures towards Organization-Specific Architectures. The core definition also allows movement the other way: assets can be classified as they evolve from generic to specific, or from specific back to generic.
It earns its place for several reasons:
In its simplest form, the continuum can be pictured as a view of the repository of every architecture asset available to the enterprise: descriptions, models, building blocks, patterns and viewpoints. These assets come from two directions:
| Source | Examples |
|---|---|
| Internal to the enterprise | Deliverables from earlier architecture work, available for re-use |
| External, from the industry at large | Industry reference models and patterns, such as the TOGAF Technical Reference Model (TRM), web services models, e-Commerce models, and models from vertical consortia such as TM Forum, ARTS and Energistics |
The enterprise itself decides which assets go into its repository, and the potential for re-use is a major factor in that decision.
Common trap: The Enterprise Continuum is the Architecture Repository - it is not. The continuum is a way of classifying and viewing assets; the repository is where the assets are actually stored.
This note is one section of Ultra Transcenders OGEA-101: Enterprise Architecture Foundation, an independent study guide that explains every learning unit the exam covers, topic by topic, with comparison tables, diagrams and the common traps, plus a glossary linked to the TOGAF Standard.
Publishing soon on Amazon in Kindle and paperback editions.
About the book · OGEA-101 terms in the glossary · All OGEA-101 study notes
What the Business, Data, Application and Technology domains each describe, and which subjects cut across all four.
The contextual, conceptual, logical and physical levels, the question each answers, and the difference between logical and physical.
The Preliminary Phase, Phases A to H and Requirements Management, each with its purpose and essential output.
How to set Baseline Architecture Building Blocks against Target ones to see what is included, what is new and what is eliminated.
Architecture Capability, Architecture Development, Transition Planning and Architecture Governance iterations, and the phases each one spans.
What an Architecture Board is accountable for, who should sponsor it and how large it should be.
How stakeholders' concerns are framed by viewpoints and addressed by views, and why a view and a viewpoint are not the same thing.