Embedded Files
1 Day(s)
🎯 LEARNING OBJECTIVES
By the end of this course, you will be able to:
Understand the purpose and structure of the TOGAF Enterprise Continuum.
Differentiate between the Architecture Continuum and Solutions Continuum.
Classify architecture and solution assets from generic to organization-specific.
Understand the difference between Architecture Building Blocks (ABBs) and Solution Building Blocks (SBBs).
Understand how the Architecture Content Framework organizes Deliverables, Artifacts, and Building Blocks.
Understand the role of the Content Metamodel in defining relationships between architecture building blocks.
Relate the Enterprise Continuum to the Architecture Repository.
Understand how the Architecture Landscape represents architecture across time, domains, and levels of detail.
Apply the Continuum concepts to improve reuse, standardization, traceability, and architecture governance.
🧠 PREREQUISITES
Basic understanding of Enterprise Architecture and TOGAF ADM.
Familiarity with the Business, Data, Application, and Technology Architecture domains.
Basic understanding of architecture artifacts, deliverables, and building blocks.
Familiarity with Architecture Repository and architecture governance concepts.
Basic knowledge of ArchiMate is beneficial but not mandatory.
Architecture Continumm
1.What is the Architecture Continuum?
1.What is the Architecture Continuum?
The Architecture Content Framework (with the Content Metamodel) informs 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.
2.Objectives of it?
2.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 to 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".
3.Building Blocks classification?
3.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. Viewpoints: relevant to different personas
3. Deliverables: expected outputs for EA process
4.Content Metamodel
4.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".
5.Architecture Content Framework
5.Architecture Content Framework
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
So the enterprise continuum consists of:
Foundation solutions
Common systems solutions
Industry solutions
Organization specific solutions
6.Architecture Landscape
6.Architecture Landscape
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.
Tools
Tools
Enterprise Architect
Archimate
Dr. Ghoniem Lawaty
Tech Evangelist
Page updated
Google Sites
Report abuse