Architecture Content, the Content Framework, Enterprise Continuum, and Architecture Repository
Content Framework
The Architecture Content Framework describes the types of work products the ADM creates. Deliverables are formal, reviewed outputs, such as an Architecture Definition Document. Artifacts are more granular work products inside deliverables, grouped as catalogs (lists of things), matrices (relationships), and diagrams (visual representations). Building blocks are reusable components: Architecture Building Blocks (ABBs) capture architecture requirements and are technology-neutral; Solution Building Blocks (SBBs) are concrete implementations.
Enterprise Continuum and Repository
The Enterprise Continuum classifies architecture and solution assets to support reuse. It has an Architecture Continuum and a Solutions Continuum, each moving from foundation or generic assets through common systems and industry assets to organization-specific assets. The Architecture Repository stores the enterprise's architecture assets and includes the Architecture Metamodel, Architecture Capability, Architecture Landscape (strategic, segment, and capability architectures), Standards Information Base, Reference Library, and Governance Log.
Traps
A common error is treating the continuum as a storage location; the repository stores, while the continuum classifies. Another is mixing ABB and SBB. Questions may also confuse the Architecture Landscape with the Reference Library: the landscape is what the enterprise has, while the library is reference material that may be reused. Deliverables versus artifacts is another frequent distinction.
Worked example
Suppose a team needs a payment integration component. An SBB is the reusable implementation pattern or product; an ABB is the capability it must provide. Rule of thumb: ABB equals what, SBB equals how; continuum equals classification, repository equals storage.