Architecture Content Framework Flashcards

describes the TOGAF content framework

1
Q

3 categories of Work products for Architecture Content Framework

A
  1. Deliverables
  2. Artifacts
  3. Building Blocks
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Deliverable

A

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

Can contain multiple artifacts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Artifacts

A

An artifact is an architectural work product that describes an aspect of the architecture.
Classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Building Blocks

A

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.
Eg: ABBs & SBBs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Metamodel

A

A model that describes how and with what the architecture will be described in a structured
way.

It is a precise definition of the constructs and rules needed for creating models.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Metamodel has 2 type

A
  1. Core
  2. Extension
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Architecture Content Framework

A

It provides a detailed model of architectural work products.
It provides a comprehensive checklist of architectural work products.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the Arch. content framework for ADM phase - Arch. Vision

A

Architecture principles, Vision and Requirements.

Captures strategic context as vision

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the Arch. content framework for ADM phase - Business Architecture

A

Arch. models of business, enterprise structure and capabilities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the Arch. content framework for ADM phase - IS Architeture

A

Arc. models of IT systems - application & data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the Arch. content framework for ADM phase - Technology Architecture

A

Procured technology assets, used to implement the solution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the Arch. content framework for ADM phase - Architecture Realization

Realization = Opportunities & solution + Migration planning + implementation governance

A

Transitions between architectural states, used to steer and govern implementation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Content Framework & ADM

A

Content framework provides a structure for defining the niput and output of each ADM phase.

ADM describes what needs to be done to create and architecture, and content framework describes what it should look like in the end.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Core and Extension Content

A

Core - Minimum set of architectural content to support tracebility ocross artifacts.
Extension - Allows for more specific or more in-depth modeling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Core Metamodel Entity

Actor

A

a person, organization, or system that is outside the consideration of the
architecture model, but interacts with it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Core Metamodel Entity

Application Component

A

an encapsulation of application functionality that is aligned to
implementation structure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Core Metamodel Entity

Business Capability

A

a particular ability that a business may possess or exchange to
achieve a specific purpose

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Core Metamodel Entity

Business Service

A

supports business capabilities through an explicitly defined interface
and is explicitly governed by an organization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Core Metamodel Entity

Course of Action

A

direction and focus provided by strategic goals and objectives, often to
deliver the value proposition characterized in the business model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Core Metamodel Entity

Data Entity

A

an encapsulation of data that is recognized by a business domain expert as a
discrete concept

21
Q

Core Metamodel Entity

Function

A

delivers business capabilities closely aligned to an organization, but not
explicitly governed by the organization

22
Q

Core Metamodel Entity

Information System Service

A

the automated elements of a business service

23
Q

Core Metamodel Entity

Organization Unit

A

a self-contained unit of resources with goals, objectives, and measures

24
Q

Core Metamodel Entity

Role

A

an actor assumes a role to perform a task

25
# Core Metamodel Entity Technology Component
an encapsulation of technology infrastructure that represents a class of technology product or specific technology product
26
# Core Metamodel Entity Technology Service
a technical capability required to provide enabling infrastructure that supports the delivery of applications
27
# Core Metamodel Entity Value Stream
a representation of an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end-user
28
# Relationship concept: Core Metamodel Entity Process
A process is a flow of interactions between functions and services and cannot be physically deployed ## Footnote normally be used to describe flow
29
# Relationship concept: Core Metamodel Entity Function
The term "function" is used to describe a unit of business capability at all levels of granularity, encapsulating terms such as value chain, process area, capability, business function, etc. ## Footnote describes units of business capability at all levels of granularity
30
# Relationship concept: Core Metamodel Entity Business services
Support organizational objectives - A business service operates as a boundary for one or more functions. The granularity of business services is dependent on the focus and emphasis of the business (as reflected by its drivers, goals, and objectives). Deployed onto application components - Business services may be realized by business activity that does not relate to IT, or may be realized through IT. ## Footnote explicity governed by the org.
31
# Relationship concept: Core Metamodel Entity Application components
An application component is implemented by a suite of technology components. ## Footnote Are deployed onto technology components
32
Governance extension
Required when changes impact operational governance or when service level requirements differ fropm service to service. ## Footnote Enterprise Manageability diag to be created
33
Services Extension
Required when business services do not align to technical & architectural needs ## Footnote Business Use-case Diag, Organization Decomposition Diag
34
Process Modeling Extension
Required when process control step need to be identified and stored, when architecture has crtitcal or elaborate process flows. ## Footnote Process Flow Diag Event Diag
35
Data Extension
Where the architecture features significant complexity and risk around location, encapsulation, management/access of data. ## Footnote Data Security Diag Data Migration Diag Data Lifecycle Diag
36
Infrastructure Consolidation Extension
When technology products/application are duplicate/overlapping, or geographically dispersed, when application/features are migrated to consolidated platform/application. ## Footnote Process/Application Realization diagram, Software Engineering diagram, Application Migration diagram, Software Distribution diagram, Processing diagram, Networked Computing/Hardware diagram, Network and Communications diagram
37
Motivation Extension
When org has conflicting drivers/objectives, when service levels are unclear/unknown. ## Footnote Goal/Objective/Service Diag
38
System
It is a combination of interacting elements organized to achieve one or more stated purposes.
39
Stakeholders
Individuals, teams, organizations, or classes thereof, having an interest in a system.
40
Concerns
Interests in a system relevant to one or more of its stakeholders. Concerns may pertain to any aspect of the system’s functioning, development, or operation, including considerations such as performance, reliability, security, distribution, and evolvability and may determine the acceptability of the system.
41
Architecture view
It is representation of a system from the perspective of a related set of concerns.
42
Architecture viewpoint
Defines the perspective from which an architectural view is taken.
43
ADM phase vs View/Viewpoint
Used in phase A to D for developing all architecture domains.
44
Architecture view
A representation of an overall architecture with meaning to one or more stakeholders in the system.
45
Catalogs
Lists of building blocks of a specific type, or of related types, that are used for governance or reference purposes
46
Matrices
Show relationships between two or more model entities. ## Footnote Represents list-based relationships
47
Diagrams
Representing building blocks in a rich and visual way, especially suited to stakeholder communication.
48
Good Building Block
1. Considers implementation and usage and evolves to exploit technology and standards. 2. Is reusable and replaceable 3. Can be assembled from or subassembly of other building blocks