Scribd
Upload
53 views3 pages

Content & Core Concepts

Togaf Content & Core Concepts

Uploaded by

Bruno Correia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
53 views3 pages

Content & Core Concepts

Togaf Content & Core Concepts

Uploaded by

Bruno Correia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

(Architecture) Content Framework - Introduction

https://pubs.opengroup.org/togaf-standard/architecture-content/chap02.html

The concept is a categorization framework for architecture content

- Structure the Architecture Desciption , work products, artifacts &


models
- Defines artifacts and work products to be developed and to describe
the Architecture
- Top-level structure mirros the ADM phases
- Provides an underlying structure and companion for the ADM
- Puts each deliverable into the context of the holistc architecture
view of the enterprise
- Multiple Framewors are available(TOGAF Content Framewor(Estudar),
Zachman Framework, DoDAF, NAF)
- Frameworks decisions is influenced by the Architecture Framework an
used EA software tool
- Usually adapted to fit organization needs

Desribe what the architecture should look like once it is done.

- Detailed model of architecture work products


- Enhances consistancy in the outputs
- Comprehensive checklist of architecture output
- Reduces the risk of gaps
- Defines standarts(architecture concept, terms and deliverables)

Enterprise Metamodel(created in preliminar phase)

https://pubs.opengroup.org/togaf-standard/architecture-content/chap02.html

The model defines entities within the enterprise & the relationships between
them

- Starter pack for architects withtypes of things to investigate &


cover in models.
- Provides context for the artifacts suggested in the ADM
- Complementeness-check for architecture modeling languages and
metamodels.
- Improves consistancy, completeness & traceability.
- Structure architectural information to meet stakeholders needs.

Exemple: Foundation-Level Core "Enterprise Metamodel" found in the


TOGAF Library

Development

The Enterprise Metamodel is specific to an idividual Enterprise

- Its types of entity and their relationships are specific to the


inidividual enterprise.
- A high-quality metamodel is important for establishing the EA
Capabilty.
- TOGAF does not constrain the selection of architects & modeling
notation.
- Modeled in a variety languages(ArchiMate, BPM Notation, UML,
flowchart, entiry relationship diagram).
1. Based on viewpoints which address stakeholder concerns
2. Based on available/established metamodels.

In both cases:

- Minimize the informations in Metamodel according to the purpose


of the EA Capabilty.
- Each entity, relationship and their attributes must be
maintained and tracked.

Architecture Repository

https://pubs.opengroup.org/togaf-standard/architecture-content/chap07.html

Just a structural framework for an architecture respository.

Diference between Architecture Repository and content Framework

Architecture Repository: is structured to store the artifacts and work


products identified in the content Framework, In other words, the content framework
therefore defines the artifacts and work products for the development and
description of an architecture.

Introduction

the concept stores different classes of architecture output at


different levels

- Part of Enterprise Repository


- Often implemented by modeling software, analytic tools, file
repository or document management system.

The content facilitates understanding & co-operation of stakeholders

(Blue box "Architecture Landscape" at the middle)


- Architectural representation of assets deployed withing the
enterprise at a particular point in time (current, target, transitions, candidate)
often at multiple level of abstractions.

The landscape is likely to exist at multiple levels of


abstraction to suit different architecture objectives.
A distinction is made between strategic segment and
capability architectures.
This is where you save your developed artifacts that
describe your architecture landscape.
If the artifacts to be saved have a low level of detail,
save the artifacts as strategic architecture.
If the artifacts have a very high level of detail, save the
artifacts as a capability.

(Green box "Architecture Metamodel" at the top)


- The organizationally tailored application of an architecture
framework, including a meta model for architecture content. This is where you save
your customized enterprise meta model, for example.

(Green box "Architecture Capability" at the bottom)


- of the repository defines the parameters, structures and
processes that support governance of the architecture repository.
(Blue box "Standards Library" on the right hand side)
- The standard with which new architectures must comply. (It may
include industry standards, selected products and services from suppliers or shared
services)

(Pink "Solution Landscape" box)


- It presents an architectural representation of the solution
building blocks supporting the architecture landscape, which have been planned or
deployed by the enterprise. This is where you save your documented solution
Building blocks. Solution building blocks are components that will be used to
implement a required capability or in other words, to implement an architecture
building block.

(Blue box "Reference Library" on the right hand side)


- Provides guidelines, templates, patterns, and other form of
reference material that can be leveraged in order to accelerate the creation of new
architectures for the enterprise.
This is where you save reference materials that should be used to
develop architectures, for instance templates and enterprise best practices.
It should also contain reference architectures, reference models,
and a viewpoint library.

(Pink box "Architecture Requirements" at the bottom left)


- provides a view of all authorized architecture requirements
which have been agreed with the Architecture Board.
This is where you store your architectural requirements. A
distinction is again made between strategic segment and capability requirements.

(Purple box "Governance Repository")


- It provides a record of governance activity across the
enterprise. This is where you store decision logs, compliance assessments,
capability assessments and so on.

Enterprise Continuum

https://pubs.opengroup.org/togaf-standard/architecture-content/chap06.html

The concept structures & categorizes assets held in Enterprise Repositores.

- Set a broader context for re-using architects


- Explains how generic solutions can be leveraged & specialized to
support architecture requirements of an idividual organization.
- Comprises the architecture & Solution Continuum

The enterprise continuum is just a few of the repository of all the


architecture assets and their way of classifying your architectures and solutions
as either being very generic or very specific to your enterprise.
It can contain architecture, descriptions, models, building blocks, patterns,
architecture, viewpoints, and other artifacts which the enterprise considers to
have available for the development of architectures for the enterprise.

You might also like