Knowledge Base & Metamodel Flashcards

1
Q

Business Unit decomposes into

A

Business Unit

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

Business Unit composed from

A

Business Unit

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

Capability delivered by

A

Business Unit

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

Business Unit delivers

A

Capability

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

Business Unit belongs to

A

Organisation

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

Organisation has

A

Business Unit

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

Capability supported by

A

Information Concept

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

Information Concept supports

A

Capability

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

Capability is impacted by

A

Initiative

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

Initiative impacts

A

Capability

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

Capability enabled by

A

Product

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

Product enables

A

Capability

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

Capability is enabled by

A

Value Stage

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

Value Stage enables

A

Capability

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

Information Concept informed by

A

Capability

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

Capability informs

A

Information Concept

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

Information Concept informed by

A

Objective

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

Objective informs

A

Information Concept

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

Information Concept defines

A

Stakeholder

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

Stakeholder defined by

A

Information Concept

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

Initiative realizes

A

Objective

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

Objective is realized by

A

Initiative

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

Initiative impacts

A

Product

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

Product is impacted by

A

Initiative

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

Objective motivates

A

Initiative

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

Initiative is motivated by

A

Objective

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

Organisation is guided by

A

Objective

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

Objective guides

A

Organisation

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

Organisation delivers

A

Product

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

Product delivered by

A

Organisation

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

Organisation integrates through

A

Strategy

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

Strategy integrates for

A

Organisation

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

Product owned by

A

Business Unit

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

Business Unit owns

A

Product

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

Product relies on

A

Capability

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

Capability guides

A

Product

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

Product is valuable to

A

Stakeholder

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

Stakeholder receives value from

A

Product

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

Product is impacted by

A

Initiative

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

Initiative impacts

A

Product

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

Product provided by

A

Organisation

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

Organisation provides

A

Product

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

Productis similar to

A

Product

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

Stakeholder enables

A

Capability

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

Capability is enabled by

A

Stakeholder

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

Stakeholder owns

A

Initiative

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

Initiative is owned by

A

Stakeholder

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

Stakeholder may be an

A

Organisation

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

Organisation a kind of

A

Stakeholder

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

Stakeholder instantiated as

A

Organisation

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

Organisation type of

A

Stakeholder

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

Stakeholder owns

A

Strategy

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

Strategy is owned by

A

Stakeholder

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

Stakeholder triggers

A

Value Stream

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

Value Stream triggered by

A

Stakeholder

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

Stakeholder participates in

A

Value Stream Stage

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

Value Stream Stage is participant of

A

Stakeholder

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

Strategy impacts

A

Product

59
Q

Product impacted by

A

Strategy

60
Q

Strategy owned by

A

Stakeholder

61
Q

Stakeholder owns

A

Strategy

62
Q

Strategy aligned with

A

Value Stream

63
Q

Value Stream aligns

A

Strategy

64
Q

Value Stream enables

A

Business Unit

65
Q

Business Unit is enabled by

A

Value Stream

66
Q

Value Stream guides the direction for

A

Product

67
Q

Product relies on

A

Value Stream

68
Q

Value Stream parent of

A

Value Stream Stage

69
Q

Value Stream Stage child of

A

Value Stream

70
Q

Value Stream Stage is supported by

A

Stakeholder

71
Q

Stakeholder participates in

A

Value Stream Stage

72
Q

The business architecture knowledgebase provides the foundational perspective for formalising the

A

definition, relationships, and management of business architecture artifacts

73
Q

The metamodel identifies the artefacts and relationships that serve as the foundation for

A

storing and automating a business architecture practice.

74
Q

As a general rule, this metamodel would serve as the basis for automating

A

the capture and dissemination of business architecture artefacts.

75
Q

The knowledgebase can be leveraged as a foundation for ensuring business blueprints are consistent, complete, and aligned

A

across the organisation (vertically and horizontally).

76
Q

The knowledgebase can be leveraged as a foundation for ensuring ___ across the organisation (vertically and horizontally).

A

business blueprints are consistent, complete, and aligned

77
Q

The knowledgebase should be aligned and informed using a metamodel to ensure blueprints are

A

consistent, complete, and enable best practices and formal disciplines.

78
Q

The knowledgebase can be__ (a few documents and spreadsheets) or formal (__).

A

informal, suggesting a sophisticated environment supported by a tool

79
Q

The knowledgebase may be formalised as part of

A

an individual or federated repository.

80
Q

A standard practice involves having a small group of business architects govern

A

The business architecture and its use across the organisation

81
Q

A standard practice involves having a small group of business architects ensure that business architecture artefacts

A

Are properly identified (catalogued) and captured in the knowledgebase.

82
Q

A standard practice involves having a small group of business architects ensure that the underlying metamodel

A

Supports a robust set of business architecture artefacts, relationships, and scenarios identified within the practice of business architecture.

83
Q

The overall business architecture objectives that the organisation has established for the knowledgebase.

A

Consideration when defining the knowledgebase

84
Q

The desire for an organisation to shift from an ad hoc, simplistic business architecture environment to a sophisticated, highly leveraged business architecture environment.

A

Consideration when defining the knowledgebase

85
Q

The ultimate level of sophistication envisions that business architecture can be used to trace

A

strategy through execution and solution deployment across initiatives and business units.

86
Q

The ability of an organisation to engage tooling to allow the knowledgebase to fully support and enable the business architecture.

A

Consideration when defining the knowledgebase

87
Q

__and __, will aid an organisation’s tool selection process.

A

Well-considered objectives, enabling a knowledgebase, supported by a formal metamodel

88
Q

Every organisation has something in place for capturing their business architecture artefacts __, or __.

A

Explicitly or implicitly

89
Q

A business architecture knowledgebase is built upon a metamodel that defines __, __, and the __.

A

The core set of concept terms, definitions, relationships among those concepts

90
Q

In order to populate the knowledgebase with their own business-specific information, organisations must identify aspects of their business architecture, including:

A

Value stream, capability, information, organisation, strategy and related concepts that contribute to achieving practice- related objectives.

91
Q

Promote the capture and sharing of business architecture knowledge to support consistent communications and understanding across business practices.

A

Guideline for development of an effective business architecture knowledgebase

92
Q

The capture and sharing of business architecture knowledge includes

A

The ability to provide traceability across planning, strategy, and initiative execution

93
Q

The capture and sharing of business architecture knowledge enables

A

Business architecture to align with complementary disciplines including BPM, Lean Six Sigma, or business requirements analysis.

94
Q

Ensure that the knowledgebase and practice are informed by scenarios that cover the enterprise perspective and relevant local and regional perspectives.

A

Guideline for development of an effective business architecture knowledgebase

95
Q

Establish and maintain a metamodel that encapsulates the core concepts (terms) and relationships as used across the organisation.

A

Guideline for development of an effective business architecture knowledgebase

96
Q

Any enterprise business architecture repository must be able to ___ in order to provide an integrated view of the organization.

A

coexist with and link to multiple existing repositories

97
Q

Ensure the knowledgebase is populated properly with relevant business architecture artifacts to support value delivery for business initiatives and business scenarios.

A

Guideline for development of an effective business architecture knowledgebase

98
Q

A knowledgebase is only as good as __ and __ of the business information being represented.

A

the currency, integrity

99
Q

A knowledgebase is only as good as the currency and integrity of the business information being represented, particularly with

A

The more volatile aspects such as strategy or initiative, which can evolve on a more fluid basis than core concepts

100
Q

Leverage technology to support the knowledgebase using a pragmatic approach.

A

Guideline for development of an effective business architecture knowledgebase

101
Q

Ensure that the knowledgebase can integrate and link information from various domains and sources.

A

Guideline for development of an effective business architecture knowledgebase

102
Q

Ensure that the business architecture knowledgebase can provide multiple business perspectives.

A

Guideline for development of an effective business architecture knowledgebase

103
Q

In order to provide a holistic view of an organization it is essential that the business architecture reference model not embed ___, including, for example, an explicit business model that is likely to change often over time.

A

Any particular perspective that would restrict its ability to support other perspectives

104
Q

Ensure that elements in the business architecture knowledgebase must not be restricted to any single element of the business architecture framework.

A

Guideline for development of an effective business architecture knowledgebase

105
Q

The underlying metamodel helps align the semantics that exist in an organisation through

A

Its glossary and the extensions that incorporate the context associated with different perspectives.

106
Q

A logical element or segment of a company (such as accounting, production, marketing) representing a specific business function, and a definite place on the organisational chart, under the domain of a manager. Also called department, division, or functional area.

A

Business Unit (Metamodel Entity)

107
Q

A particular ability or capacity that a business may possess or exchange to achieve a specific purpose or outcome.

A

Capability (Metamodel Entity)

108
Q

Core subject areas used to define the organization’s business model (e.g., Asset, Customer, Product, Location, Contract)

A

Information Concept (Metamodel Entity)

109
Q

A course of action that is being executed or has been selected for execution.

A

Initiative (Metamodel Entity)

110
Q

Measurable goals for guiding strategy and aligning initiatives with execution. They can be applied at individual, operational, business unit, and organisational levels.

A

Objective (Metamodel Entity)

111
Q

A social unit of people, systematically structured and managed to meet a need or to pursue collective goals on a continuing basis.

A

Organisation (Metamodel Entity)

112
Q

Customers “hire” them to help them achieve a set of desired outcomes associated with one or more jobs they are trying to get done. The value that one provides for a customer is measured by how well it helps that customer address their desired outcomes.

A

Product (Metamodel Entity)

113
Q

An internal or external individual or organisation with a vested interest in achieving value through a particular outcome.

A

Stakeholder (Metamodel Entity)

114
Q

The pattern or plan that integrates an organisation’s major goals, policies and action sequences into a cohesive whole.

A

Strategy (Metamodel Entity)

115
Q

Representation of the series of interchanges with stakeholders as the value stream moves from left to right.

A

Value Stage (Metamodel Entity)

116
Q

An end-to-end collection of activities that create a result for a customer, who may be the ultimate customer or an internal end-user of the value stream.

A

Value Stream (Metamodel Entity)

117
Q

A value in formalising the metamodel as part of launching a business architecture practice is that

A

It creates alignment around the key terms used by the organisation leadership

118
Q

A value in formalising the metamodel as part of launching a business architecture practice is that

A

It helps everyone in the organization understand the relationships in the underlying business architecture

119
Q

A value in formalising the metamodel as part of launching a business architecture practice is that

A

It helps everyone in the organization understand the importance of embracing the disciplines underlying business architecture

120
Q

One of the most common uses of the metamodel is for conducting

A

Impact analysis to understand cause and effect (causality) or for planning change.

121
Q

Knowledgebase enabled analysis is important because it provides insights into __ that require examining business-wide impacts, failure points, transformation perspectives, and related priorities.

A

How to meet significant and far-reaching objectives and strategies

122
Q

Knowledgebase enabled analysis is important because it provides insights into how to meet significant and far-reaching objectives and strategies that require

A

Examining business-wide impacts, failure points, transformation perspectives, and related priorities.

123
Q

Facilities to load business architecture capabilities, value representations, information and business units

A

Business architecture tool criteria (Capture)

124
Q

Ability to represent additional concepts including objectives, initiatives, stakeholders, products and services, and external third parties

A

Business architecture tool criteria (Capture)

125
Q

Ability to view loaded artifacts in list, graphical, or other formats

A

Business architecture tool criteria (Capture)

126
Q

Standard import facility using standards based and other industry input formats

A

Business architecture tool criteria (Capture)

127
Q

Ability to support the definition of and relationships among business architecture representations, such as capability to business unit or capability to value stage

A

Business architecture tool criteria (Capture)

128
Q

Ability to input data via application programming interfaces (APIs)

A

Business architecture tool criteria (Capture)

129
Q

Robust repository for storing, cross-referencing, and accessing business architecture

A

Business architecture tool criteria (Manage)

130
Q

Metamodel based repository that reflects industry standard relationships where available and practice-based relationships where appropriate

A

Business architecture tool criteria (Manage)

131
Q

Ability to access the tool by authorized administrators and users that enables version control and historical management of metadata

A

Business architecture tool criteria (Manage)

132
Q

Support for multiple simultaneous users and the ability to allow multiple streams of work to be managed and synchronized

A

Business architecture tool criteria (Manage)

133
Q

Ability to generate standardized views of capability, organization, information, and value maps

A

Business architecture tool criteria (Communicate)

134
Q

Ability to create customized or extended business architecture mapping views

A

Business architecture tool criteria (Communicate)

135
Q

nabling of ad hoc views based on usage requirements

A

Business architecture tool criteria (Communicate)

136
Q

Ability to export webpage views of business architecture blueprints and related information

A

Business architecture tool criteria (Share)

137
Q

Business architecture export facility that uses industry standard exchange formats

A

Business architecture tool criteria (Share)

138
Q

Open interchange formats as necessitated by evolution of data exchanges standards and protocols

A

Business architecture tool criteria (Share)

139
Q

Export of views into standard tooling (e.g., MS Office) in a manner that enables further customization of views within these tools

A

Business architecture tool criteria (Share)

140
Q

Initial building efforts may use Word or Excel to build out the business architecture

A

Business Architecture Tool Selection Consideration

141
Q

Excel representations provide flexibility in initiating the business architecture and can be used to export those representations into an enterprise architecture tool

A

Business Architecture Tool Selection Consideration

142
Q

Drawing tools can be used to enhance the limitations of MS Excel or the high-end enterprise architecture tools and creating custom blueprints

A

Business Architecture Tool Selection Consideration

143
Q

Lightweight business architecture tools can co-exist with high-end enterprise architecture tools because the tools essentially serve a different purpose

A

Business Architecture Tool Selection Consideration

144
Q

The business architecture tool should not dictate

A

How to manage or represent the business architecture