Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

TOGAF > TOGAF Artifacts > Flashcards

TOGAF Artifacts Flashcards

1
Q

Describes what a “good” solution or architecture should look like. Used to evaluate
and agree an outcome for architecture decision points. Are also used as a tool to assist
in architectural governance of change initiatives.

A

Principles Catalogue - Preliminary Phase

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

The purpose is to identify the stakeholders for the architecture
engagement, their influence over the engagement, and their key questions, issues, or concerns
that must be addressed by the architecture framework.

A

Stakeholder Map Matrix - Architecture Vision Phase.

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

Provides a high-level orientation view of an enterprise and how it interacts with the outside world.

A

Value Chain Diagram - Architectural Vision Phase

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

Provides a high-level orientation of the solution that is envisaged in order to meet the objectives of the architecture engagement. Represents a “pencil sketch” of the expected solution at the outset of the engagement

A

Solution Concept Diagram - Architectural Vision Phase

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

A family of diagrams representing a definitive listing of a particular ability that a business may possess or exchange to achieve a specific purpose.

A

Business Capability Map - Architectural Vision Phase

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

A model describing the rationale for how an enterprise creates, delivers, and captures value.

A

Business Model Diagram - Architectural Vision Phase

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

A family of diagrams representing a definitive listing of an end-to-end collection of value adding activities that create an overall result for a customer, stakeholder, or end user.

A

Value Stream Map - Architectural Vision Phase

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

The purpose is to capture a definitive listing of all
participants that interact with IT, including users and owners of IT systems. The catalog can be referenced when developing requirements in order to test for completeness.

A

Organization/Actor Catalog - Business Architecture Phase

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

The purpose of this catalog is to provide a cross-organizational reference of how an organization meets its drivers in practical terms through goals, objectives, and (optionally) measures.

A

Driver/Goal/Objective Catalog - Business Architecture Phase

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

The purpose of this catalog is to provide a listing of all authorization levels or zones within an enterprise.

A

Role Catalog - Business Architecture Phase

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

The purpose of this catalog is to provide a functional decomposition in a form that can be filtered, reported on, and queried, as a supplement to graphical Functional Decomposition diagrams.

A

Business Service/Function Catalog - Business Architecture Phase

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

Provides a listing of all locations where an enterprise carries out business operations or houses architecturally relevant assets, such as data centers or end-user computing equipment.

A

Location Catalog - Business Architecture Phase

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

This catalog provides a hierarchy of processes, events that trigger processes, outputs from processes, and controls applied to the execution of processes. This catalog provides a supplement to any Process Flow diagrams that are created and allows an enterprise to filter, report, and query across organizations and processes to identify scope, commonality, or impact.

A

Process/Event/Control/Product Catalog - Business Architecture Phase

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

This catalog provides a listing of all agreed service contracts and the measures attached to those contracts. It forms the master list of service levels agreed to across the enterprise.

A

Contract/Measure Catalog - Business Architecture Phase

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

A definitive listing of particular abilities that a business may possess or exchange to achieve a specific purpose.

A

Business Capabilities Catalog - Business Architecture Phase

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

A definitive listing of end-to-end collections of value-adding activities that create an overall result for a customer, stakeholder, or end user.

A

Value Stream Catalog - Business Architecture Phase

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

A definitive listing of end-to-end collections of the different stages for the value-adding activities that create an overall result for a customer, stakeholder, or and user; it includes the following metamodel entities:
■ Business Capability
■ Value Stream

A

Value Stream Stages Catalog - Business Architecture Phase

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

The purpose of this matrix is to depict the relationship interactions between organizations and business functions across the enterprise.
It is important as it helps to highlight value chain and dependencies across organizations.

A

Business Interaction Matrix - Business Architecture Phase

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

The purpose of this matrix is to show which actors perform which roles, supporting definition of security and skills requirements.

Understanding these relationships is a key supporting tool in definition of training needs, user security settings, and organizational change management.

A

Actor/Role Matrix - Business Architecture Phase

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

The purpose of this matrix is to show the capabilities required to support each stage of a value stream.

A

Value Stream/Capability Matrix - Business Architecture Phase

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

The purpose of this matrix is to show the capabilities required to support specific strategy statements.

A

Strategy/Capability Matrix - Business Architecture Phase

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

The purpose of this matrix is to show the organization elements that implement each capability. This matrix includes the following metamodel entities:
■ Business Capability
■ Value Stream
■ Organization Unit

A

Capability/Organization Matrix - Business Architecture Phase

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

This diagram describes the links between business goals, organizational units, business functions, and services, and maps these functions to the technical components delivering the required capability.
The diagram provides a clear traceability between a technical component and the business goal that it satisfies, while also demonstrating ownership of the services identified.
The diagram demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (CxO) stakeholders.

A

Business Footprint Diagram - Business Architecture Phase

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

This diagram shows the information needed to support one or more business services. The diagram shows what data is consumed by or produced by a business service and may also show the source of information.

A

Business Service/Information Diagram - Business Architecture Phase

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

The purpose this diagram is to show on a single page the capabilities of an organization that are relevant to the consideration of an architecture. By examining the capabilities of an organization from a functional perspective, it is possible to quickly develop models of what the organization does without being dragged into extended debate on how the organization does it.

A

Functional Decomposition Diagram - Business Architecture Phase

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

The purpose of this diagram is to assist in understanding the lifecycles of key entities within the enterprise.

A

Product Lifecycle Diagram - Business Architecture Phase

27
Q

The purpose of this diagram is to define the ways in which a service contributes to the achievement of a business vision or strategy.

A

Goal/Objective/Service Diagram - Business Architecture Phase

28
Q

This diagram displays the relationships between consumers and providers of business services. Business services are consumed by actors or other business services and this diagram provides added richness in describing business capability by illustrating how and when that capability is used.

A

Business Use-Case Diagram - Business Architecture Phase

29
Q

This diagram describes the links between actor, roles, and location within an organization tree. An organization map should provide a chain of command of owners and decision-makers in the organization.

A

Organization Decomposition Diagram - Business Architecture Phase

30
Q

The purpose of this diagram is to depict all models and mappings related to the process metamodel entity.

A

Process Flow Diagram - Business Architecture Phase

31
Q

The purpose of this is to depict the relationship between events and process.

A

Event Diagram - Business Architecture Phase

32
Q

A family of diagrams representing a definitive listing of the particular abilities that a business may possess or exchange to achieve a specific purpose.

A

Business Capability Map - Business Architecture Phase

33
Q

A family of diagrams representing a definitive listing of end-to-end collections of value-adding activities that create an overall result for a customer, stakeholder, or end user. This map includes the following metamodel entities:
■ Business Capability
■ Value Stream

A

Value Stream Map - Business Architecture Phase

34
Q

A diagram showing the relationships between the primary entities that make up the enterprise, its partners, and stakeholders.

A

Organization Map - Business Architecture Phase

35
Q

The purpose of the this catalog is to identify and maintain a list of all the data use across the enterprise, including data entities and also the data components where data entities are stored. An agreed catalog supports the definition and application of information management and data governance policies and also encourages effective data sharing and re-use.

A

Data Entity/Data Component Catalog - Data Architecture Phase

36
Q

The purpose of this matrix is to depict the relationship between data entities and business functions within the enterprise.

A

Data Entity/Business Function Matrix - Data Architecture Phase

37
Q

The purpose of this matrix is to depict the relationship between applications (i.e., application components) and the data entities that are accessed and updated by them.

A

Application/Data Matrix - Data Architecture Phase

38
Q

The key purpose of the Conceptual Data diagram is to depict the relationships between critical data entities within the enterprise.

A

Conceptual Data Diagram - Data Architecture Phase

39
Q

The key purpose of this diagram is to show logical views of the relationships between critical data entities within the enterprise.

A

Logical Data Diagram - Data Architecture Phase

40
Q

The purpose of this diagram is to show the relationship between data entity, business service, and application components.

A

Data Dissemination Diagram - Data Architecture Phase

41
Q

The purpose of this diagram is to depict which actor (person, organization, or system) can access which enterprise data. This relationship can be shown in a matrix form between two objects or can be shown as a mapping.

A

Data Security Diagram - Data Architecture Phase

42
Q

The purpose of this diagram is to show the flow of data from the source to the target applications.

A

Data Migration Diagram - Data Architecture Phase

43
Q

This diagram is an essential part of managing business data throughout its lifecycle from conception until disposal within the constraints of the business process.

A

Data Lifecycle Diagram - Data Architecture Phase

44
Q

The purpose of this catalog is to identify and maintain a list of all the applications in the enterprise.
The catalog contains the following metamodel entities:
■ Information System Service
■ Logical Application Component
■ Physical Application Component

A

Application Portfolio Catalog - Application Architecture Phase

45
Q

The purpose of this catalog is to scope and document the interfaces between applications to enable the overall dependencies between applications to be scoped as early as possible.

A

Interface Catalog - Application Architecture Phase

46
Q

The purpose of this matrix is to depict the relationship between applications and organizational units within the enterprise.

A

Application/Organization Matrix - Application Architecture Phase

47
Q

The purpose of this matrix is to depict the relationship between applications and the business roles that use them within the enterprise.

A

Role/Application Matrix - Application Architecture Phase

48
Q

The purpose of this matrix is to depict the relationship between applications and business functions within the enterprise.

A

Application/Function Matrix - Application Architecture Phase

49
Q

The purpose of the this matrix is to depict communications relationships between applications.

A

Application Interaction Matrix - Application Architecture Phase

50
Q

The purpose of this diagram is to depict all models and mappings related to communication between applications in the metamodel entity.

A

Application Communication Diagram - Application Architecture Phase

51
Q

This diagram shows the geographical distribution of applications. It can be used to show where applications are used by the end user; the distribution of where the host application is executed and/or delivered in thin client scenarios; the distribution of where applications are developed, tested, and released; etc.

A

Application and User Location Diagram - Application Architecture Phase

52
Q

This diagram displays the relationships between consumers and providers of application services. Application services are consumed by actors or other application services and the diagram provides added richness in describing application functionality by illustrating how and when that functionality is used.

A

Application Use-Case Diagram - Application Architecture Phase

53
Q

This diagram shows how one or more applications interact with application and technology components that support operational management of a solution.

A

Enterprise Manageability Diagram - Application Architecture Phase

54
Q

The purpose of this diagram is to clearly depict the sequence of events when multiple applications are involved in executing a business process.

A

Process/Application Realization Diagram - Application Architecture Phase

55
Q

This diagram breaks applications into packages, modules, services, and operations from a development perspective.

A

Software Engineering Diagram - Application Architecture Phase

56
Q

This diagram identifies application migration from baseline to target application components.

A

Application Migration Diagram - Application Architecture Phase

57
Q

This diagram shows how application software is structured and distributed across the estate. It is useful in systems upgrade or application consolidation
projects.

A

Software Distribution Diagram - Application Architecture Phase

58
Q

This catalog documents the agreed standards for technology across the enterprise covering technologies, and versions, the technology lifecycles, and the refresh cycles for the technology.

A

Technology Standards Catalog

59
Q

The purpose of this catalog is to identify and maintain a list of all the technology in use across the enterprise, including hardware, infrastructure software, and application software.

A

Technology Portfolio Catalog

60
Q

This matrix documents the mapping of applications to technology platform.

A

Application/Technology Matrix

61
Q

This diagram depicts which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally
identifies the locations from which business users typically interact with the applications.

A

Environments and Locations Diagram

62
Q

This diagram depicts the technology platform that supports the operations of the Information Systems Architecture.

A

Platform Decomposition Diagram

63
Q

This diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform.

A

Processing Diagram

TOGAF (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions