Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

TOGAF > Enterprise Continuum & Tools > Flashcards

Enterprise Continuum & Tools Flashcards

taxonomies and tools to categorize and store the outputs of architecture activity

1
Q

Enterprise Continuum is partitioned into 3 continua

A

Enterprise Continuum (outermost continuum and classifies assets related to the context of the overall Enterprise Architecture)
Architecture Continuum - Foundation Arch.s, Common System Arch.s, Industry Arch.s, Org-Specific Arch.s
Solution Continuum -Foundation Solution Arch.s, Common System Solution Arch.s, Industry Solution Arch.s, Org-Specific Solution Arch.s

Relationship between the Architecture Continuum and the Solutions Continuum is one of guidance, direction, and support.

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

Tools in Enterprise Continuum

A

Needed to manage and control the artifacts within Enterprise Continuum
Promotes reuse
Enables sharing arch. information with org.
Facilitates easier maintenance of arch.
Ensures common terminology is used
Provides stakeholders with relevant models.

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

Enterprise Continuum vs architecture Repository

A

The Enterprise Continuum is a view of the architecture Repository that provides methods for classifying architecture and
solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific
Architectures.
The practical implementation of the Enterprise Continuum takes the form of an Architecture Repository

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

Architecture Repository vs ADM

A

Arch. Repository stores different classes of architectural output at different levels of abstraction, created by
the ADM.
TOGAF ADM has reminders on when to use assets from Arch. repository.

The practical implementation of the Enterprise Continuum takes the form of an Architecture Repository.

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

Major components within an Architecture Repository

A
  1. Architecture metamodel
  2. Architecture Capability
  3. Architecture Landscape
  4. Standards Information Base (SIB)
  5. Reference Library
  6. Governance Log
  7. Architecture Requirements Repository
  8. Solutions Landscape
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Architecture metamodel

A

Describes architecture framework in use within this enterprise

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

Architecture Capability

  • contains Skills Repository, Org structure, Arch. Charter
A

Defines the parameters, structures, and processes that support governance of the Architecture Repository.

Describes the org, roles, skill and responsibilities of EA practice.

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

Architecture Landscape

A

It is architectural representation of assets deployed within the operating enterprise at a particular point in time — the landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives.

Shows the state of the operating enterprise at particular points in time.

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

Types of Arch. Landscape

A
  1. Strategic Architectures (shows log-term summary view of entire enterprise) - Allow direct setting at executive level.
  2. Segment Architecture (provides more detailed operating models for areas within an enterprise) - Used at program or portfolio level.
  3. Capability Architecture (shows in detail how a particular capability is supported by the enterprise) - overview of current capability, target capability, capability increments.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Reference Library

A

Provides guidelines, templates, patterns, and other forms of reference material for creation of new architectures for the enterprise.

Contains reusable arch. work products.

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

Standards Information Base (SIB)

A

A repository area to hold set of specifications, to which arch.s must conform.

Defines the complaince criteria for work governed by architecture

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

Types of standard in SIB

A
  1. Legal and Regulatory Obligations
  2. Industry Standards
  3. Organizational Standards
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Standards Lifecycle stages

A

1.Provisional Standard (aka Trial Standard)
2. Standard (aka Active Standard)
3. Phasing-Out Standard (aka Deprecated Standard)
4. Retired Standard (aka Obsolete Standard)

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

Standards classified with the TOGAF architecture domains

A
  1. Business Standards:— Standard for shared business functions, role and actor definitions, Security and governance for business activity
  2. Data Standards:— Standard for coding and values for data, structures and formats for data, origin and ownership of data, restrictions on replication and access
  3. Applications Standards:— Standard/shared applications supporting specific business functions, Standards for application communication and interoperation, access, presentation, and style
  4. Technology Standards:— Standard hardware products, software products, standards for software development
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Governance log

-Decision log, Compliance assessments, Capability assessments, Calendar, Project portfolio, Performance Measurement

A

Provides a record of governance activity across the enterprise.

Captures results of governance activity.

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

Architecture Requirements Repository

A

Record and manage all information relevant to the architecture
requirements.

A view of authorized architectural requirements.

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

Three levels of granularity of Arch. Requirements

A

Similar to arch. landscapes:
1. Strategic Architecture Requirements
2. Segment Architecture Requirements
3. Capability Architecture Requirements

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

Solutions Landscape

A

Holds the Solution Building Blocks (SBBs) which support the
Architecture Building Blocks (ABBs) specified, developed, and deployed.

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

Enterprise Repository

A

Support the architecture both inside and outside of the enterprise.
Contains the Arch. repository.
Connects to External Reference models (industry ref models), External Standards (industry best practices) and Arch. boards (approvals for arch. board is held in Enterprise Repository).

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

Enterprise Continuum

A

Repository of all architecture assets. It is a virtual repository of architectural artifacts (kept in Architecture Continuum) and solution artifacts (placed in Solution continuum)

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

Architecture Continuum

A

Architecture Continuum offers a consistent way to define and understand the generic rules, representations, and relationships in an architecture, including traceability and derivation relationships

Architecture Continuum represents a structuring of Architecture Building Blocks (ABBs) which are re-usable architecture assets.

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

Solutions Continuum

A

Solutions Continuum provides a consistent way to describe and
understand the implementation of the assets defined in the Architecture Continuum

The Solutions Continuum defines what is available in the organizational environment as
re-usable Solution Building Blocks (SBBs).

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

Architecture Continuum parts

A
  1. Foundation Architectures - Eg: TOGAF TRM
  2. Common Systems Architecture - Eg: TOGAF Integrated Information Infrastructure Reference Model (III-RM)
  3. Industry Architectures
  4. Organization-Specific Architectures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Solution Continuum parts

A
  1. Foundation Solutions - Eg: EDIFACT, ITIL, IT4IT
  2. Common Systems Solutions - Eg: SaaS
  3. Industry Solutions
  4. Organization-Specific Solutions
25
TOGAF ADM vs Enterprise Continuum
ADM uses foundational, common systems, industry architectures/solutions from Enterprise Continuum. Specific architectures and solutions that prove to be credible and effective will be generalized for re-use.
26
What is the need for Architecture Partitioning?
Allows for management of costs and complexity by dividing up the Enterprise and assigning appropriate roles and responsibilities to each partition. Managing Complexity, Managing conflicts, Managing parallel developments, Managing Re-use.
27
Steps for Architectural Partitioning
1. Determine the organization structure for architecture within the enterprise - various standing teams that will create the architecture should be identified. 2. Determine the responsibilities for each standing architecture team. 3. Determine the relationships between partitioned architectures.
28
Integration types for partitioned architecture
1. Integration across the architectural domains provides a cross-domain view of the state of a segment of the enterprise for a point in time. 2. Integration across the organizational scope of the business provides a cross-segment view of the enterprise. 3. The Architecture Vision provides an integrated summary of Architecture Definitions, which provide an integrated summary of Transition Architectures.
29
Architecture partitioning vs ADM
In Preliminary Phase, the Architecture Capability for the enterprise is established into architectural partitions, providing defined boundaries, governance, and ownership.
30
Classification of Solution Partitioning
Subject Matter (Breadth) - Its content, structure and function. Time - All solutions exist for a period of time Maturity/Volatility - The extent to which subject matter and environment of a solutions are likely to change over time.
31
Classification of Architecture Partitioning
Depth (Level of detail) - It is related to the stakeholder group interested. Less detail for executive stakeholders.
32
Enterprise Continuum vs Architecture governance
Arch. governance function decides which assets an enterprise considers part of its own Enterprise Continuum.
33
Architecture Repository vs ADM
TOGAF ADM has reminders on when to use assets from Arch. repository
34
Architecture building blocks (ABBs) specification
Defined during phase A, B, C and D Define fundamental functionality and attributes to be implemented Capture business and technical requirement Technology aware Interfaces, dependency on building blocks Mapped to some Business entities/policies ## Footnote Groupings at the functional level are ABBs
35
Solution Building Blocks (SBBs) specification
Real products or specific custom developments Functionality implemented Fulfil business and technical requirement Vendor aware Mapped to some IT entities
36
3 classes of Building Blocks
1. Reusable legacies 2. Newly develop 3. COTS products
37
Architecture Patterns
An idea that has been useful in one practical context and will probably be useful in others. Eg: Describe a Reusable solution to a problem
38
Architecture Compliance Terminology
Irrelevant - Arch. Specification & implementation has no common features. Consistent - Some arch. specifications are implemented in accordance with specification, but some are not. And many implementation features are not in specification. Complaint - Arch. specifications are implemented partially Conformant - Many extra implementation along with all arch. specification is implemented. Fully Conformant - Full arch. specification are implemented Non-conformant - Some arch. specification implemented is not in accordance with the specification + feature of consistent
39
Two main components of Tech TRM
1. A taxonomy that defines terminology and provides a coherent description of the components and conceptual structure of an information system 2. An associated TRM graphic that provide a visual representation as an aid to understanding
40
TRM : Application portability
Achieved via Application Platform interface, identifying the set of services that are to be made available in a standard way to applications via the platform
41
TRM: Interoperability
Achieved via the Communications Infrastructure Interface, identifying the set of Communications Infrastructure services that are to be built on in a standard way
42
TRM: Adaptibility criterias
1.Interoperability - Whether within or outside organization 2.Scalability - Ability of component to grow or shrink its performance or capacity appropriately to the demands of the environment in which it operates 3.Portability - Data, people, applications and components 4.Extensibility - Accept new functionality 5.Assessibility - Services in new paradigm such as object orientation
43
TRM: Usability
Ease of operation by users
44
TRM: Assurance criteria
1.Security - Protection of information from unauthorized access 2.Integrity - Assurance that the data has not been corrupted 3.Credibility - Level of trust in the integrity of the system and its data
45
TRM: 6 criteria of availability
1.Manageability - Ability to gather information about the state of something and to control it 2.Serviceability - Ability to identify problems and take corrective action such as to repair or upgrade a component in as running system 3.Performance - Ability of a component to perform its tasks in appropriate time 4.Reliability - Resistance to failure 5.Recoverability - Ability to restore a system to a working state after an interruption 6.Locatability- Ability of a system to be found when needed
46
TRM: Availability
The degree to which something is available for use.
47
Main components of III-RM
1. A taxonomy, which defines terminology, and provides a coherent description of the components and conceptual structure of an integrated information infrastructure 2. An associated III-RM graphic, which provides a visual representation of the taxonomy, and the inter-relationship of the components, as an aid to understanding.
48
III-RM graphic contains
1.Business Applications - Brokering Applications, Information Provide Applications, Information Consumer Applications 2.Infrastructure Applications - Development Tools, Management Utilities 3.Application Platform 4.Interfaces 5.Qualities
49
Brokering Application
Manage the requests from any number of clients to and across any number of Information Provider Applications.
50
Information Provider Applications
Provide responses to client requests and rudimentary access to data managed by a particular server.
51
Information Consumer Applications
Deliver content to the user of the system, and provide services to request access to information in the system on the user's behalf
52
Development Tools
To develop and deploy applications that require access to the integrated information infrastructure
53
Management Utilities
To understand, operate, tune, and manage the run-time system in order to meet the demands of an ever-changing business
54
Application Platform
Provides supporting services to all the applications and so provides the ability to locate, access and move information within the environment
55
Classification to Architecture partitioning
1.Solution Partitioning - subject matter (breadth), time, maturity/voltality 2.Architecture Partitioning - depth (level of detail)
56
Types of iteration
1.Iteration to develop a comprehensive architecture - ADM for strategic Architecture - partition to Segment Architecture from PhaseF and run ADM there - again it can be partitition to Capability Architecture where again ADM will run 2.Iteration within ADM i.Architecture Capability Iteration - Prelim + PhaseA ii.Architecture Development Iteration - PhaseB, C, D, E, F iii.Transition Planning Iteration - PhaseE & F iv.Architecture Governance Iteration - PhaseG and H
57
Baseline first approach to Architecture Development
An Assessment of the baseline landscape is used to identify problem areas and opportunities for improvement. Suitable for when baseline is complex or not clearly understood
58
Target first approach to Architecture Development
The solution is elaborated in detail and then mapped back to the baseline. Suitable for when target state is agreed at a high level and where the enterprise wishes to effectively transition to the target model.

TOGAF (6 decks)

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