Enterprise Architecture Continumm

What is?

The Architecture Content Framework (with the Content Metamodel) informs on what content to produce at what phase of the ADM cycle, and also gives a model to structure those Architecture Deliverables. The produced content fall into three categories: Deliverables, Artifacts and Building Blocks.

Objectives of it?

The Enterprise Continuum is the classification method for organizing architecture and solution artifacts, both internal and external to the Architecture Repository. It can be considered as a virtual repository containing the Architecture Repository amongst other things.

So: We classify the content according the the continuum.

A building block represents a (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and solutions Building blocks can be defined at various levels of detail, depending on what stage of architecture development has been reached. For instance, at an early stage, a building block can simply consist of a name or an outline description. Later on, a building block may be decomposed into multiple supporting building blocks and may be accompanied by a full specification. Building blocks can relate to "architectures" or "solutions".

Building Blocks classification?

• Architecture Building Blocks (ABBs) typically describe required capability and shape the specification of Solution Building Blocks (SBBs); for example, a customer services capability may be required within an enterprise, supported by many SBBs, such as processes, data, and application software

• Solution Building Blocks (SBBs) represent components that will be used to implement the required capability; for example, a network is a building block that can be described through complementary artifacts and then put to use to realize solutions for the enterprise.

The content produced during the ADM cycle is mainly to be stored in the Architecture Repository. 

The Enterprise Continuum is the classification method for organizing architecture and solution artifacts, both internal and external to the Architecture Repository. It can be considered as a virtual repository containing the Architecture Repository amongst other things.

It defines the following:

1. Views: like business or app or infrastructure

2. View points: relevant to different personas

3. Deliverable: expected outputs for EA process 

Architects executing the Architecture Development Method (ADM) will produce a number of outputs as a result of their efforts, The Architecture Content Framework uses the following three categories to describe the type of architectural work product within the context of use:

•A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the.

•An artifact is an architectural work product that describes an aspect of the architecture

A building block represents a (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and 

Content Metamodel

The content metamodel provides a definition of all the types of building blocks that may exist within an architecture, showing how these building blocks can be described and related to one another. For example, when creating an architecture, an architect will identify applications, "data entities" held within applications, and technologies that implement those applications. These applications will in turn support particular groups of business user or actor, and will be used to fulfil "business services". 

It's the full architecture considering the following

1. Time

2. Pillar (business, data, systems, tech)

3. Depth/breadth (to which level of mentioned pillars)

The application of science can be considered as the highest problem in both education and business. 

It's a common practice across all domains, As an example:

1. Leading organization business without building any small business model. 

2. Building mega solutions without practicing any software engineering activities 

3. Building analysis models without clear understanding of statistics and data analysis 

Excellent, it implies positive behavior, setting clear objectives, planning, follow-up, and being process based.

1. Enterprise Architect

2. Archimate