How do you apply the Enterprise Continuum to different types and levels of architecture projects?

1 What is the Enterprise Continuum?

The Enterprise Continuum is a model that shows the relationships and dependencies among different architecture artifacts. It consists of two complementary aspects: the Architecture Continuum and the Solutions Continuum. The Architecture Continuum defines the general and reusable architecture assets, such as reference models, architectures, and patterns. The Solutions Continuum defines the specific and implemented solutions, such as products, services, and systems. The Enterprise Continuum helps you to select and adapt the most appropriate artifacts for your architecture projects, based on your requirements, constraints, and context.

2 How does the Enterprise Continuum relate to the ADM?

The Enterprise Continuum is a tool that supports the ADM throughout its cycle. It helps to define the scope and boundaries of architecture projects, establish the vision and principles, develop architecture descriptions and deliverables, evaluate and select architecture alternatives, and implement and govern architecture outcomes. This is done by identifying relevant domains and layers, such as business, data, application, and technology; aligning with strategic direction and goals; selecting and tailoring assets from the Architecture Continuum and Solutions Continuum; comparing options; and ensuring compliance with standards while monitoring progress.

5 What are some examples of using the Enterprise Continuum?

Illustrating how the Enterprise Continuum can be used in architecture projects, here are some examples of different types and levels of architecture assets and their relation to each other. The highest level of abstraction is the TOGAF Reference Models, such as the Technical Reference Model (TRM) and the Integrated Information Infrastructure Reference Model (III-RM). These provide a common vocabulary and structure for defining technology architectures and identifying generic services and functions that support business needs. At a lower level of abstraction, industry or domain-specific architectures like eTOM for telecommunications or ACORD for insurance, can provide a more detailed and relevant view of business architectures, aligning them with best practices and standards. Organization-specific architectures like enterprise or segment architectures, provide a more customized and tailored view of architectures reflecting the organization’s unique vision, goals, values and culture. Lastly, solution-specific architectures like system or application architectures provide a concrete implemented view of architectures specifying products, services and systems that deliver business capabilities.