ADM Guidelines and Techniques Flashcards

1
Q

ADM + ADM Guidelines and Techniques

A
  • G+T is resources, guidelines, templates, techniques- G+T directly support the use of the ADM- Separated from the ADM to reduce clutter- E.g., Iteration, security, gap analysis, principles list
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

ADM + Enterprise Continuum + Architecture Repository

A
  • Continuum categorizes entities created using the ADM
  • Repository stores work created using the ADM
  • Repository has reference architectures, models, patterns
  • ADM phase dictates the types of assets used
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

ADM + Foundation Architecture

A
  • ADM populates Foundation Architecture with- Reusable common models, policy, governance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Briefly describe guidelines vs techniques

A
  • Guidelines document how to adapt the ADM- Techniques are used when applying the ADM
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Characteristics of a good business scenario (5)

A
  • S: Specific: Defines what needs to be done- M: Measurable: Clear metrics for success- A: Actionable: Provides the solution- R: Realistic: Within time and cost constraints- T: Time bound: When the opportunity expires
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Characteristics of Architecture Principles

A
  • A set of rules and guidelines for architecture
  • Seldom amended
  • Guides the way mission is accomplished
  • Guides values, actions, results
  • Initial output of Preliminary phase
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Define Business Architecture

A
  • Description of structure and interaction between- strategy, organization, functions, processes, needs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Define Business Governance

A
  • Ensuring business processes deliver outcomes- And adhere to regulations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Define Capability

A
  • Ability of organization, system, person- Requires org, people, processes, technology- E.g., telemarketing dept
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Define Concerns

A
  • Interests important to stakeholders- Determine acceptability of a solution- E.g., performance, reliability, security
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Define Constraint

A
  • External factor that prevents an approach or goal- E.g., Customer data is not consistent
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Define Data Architecture

A
  • Logical and physical data assets- Structure and interaction- Data management resources.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Define Deliverable

A
  • Work contractually specified- Reviewed, agreed, signed off by stakeholders- Archived or stored in an Architecture Repository- Can be: Reference model, standard, or snapshot
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Define Enterprise

A
  • Collection of organizations with common goals- Highest organizational level- Covers all missions and functions- Can extend to partners, suppliers, customers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Define Gap

A
  • Difference between two states- E.g., Baseline vs Target Architecture
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Define Governance

A
  • Monitoring, managing, steering a business- Enforces delivery of required business outcome
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Define IT (4 definitions)

A
  1. Lifecycle management of info + technology2. Umbrella including computer industry areas3. Department assigned to provision IT areas4. Information Services; Information Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Define Logical Architecture

A
  • Implementation-independent definition- Logical grouping of related physical entities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Define Reference Model (RM)

A
  • Abstract framework of entities and relations- Based on small number of unifying concepts- Common semantics across implementations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Define Repository

A
  • System that manages data in an enterprise- Includes data, processes, other information
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Define Segment Architecture

A
  • Formal description of areas within enterprise- E.g., program or portfolio level
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Define Solution Architecture

A
  • Descr of a discrete and focused business operation- Applies to a single project, release, solution
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Define Solution Building Block (SBB)

A
  • A concrete, physical Building block- Conforms to an Architectural building block
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Define Solutions Continuum

A
  • Part of the Enterprise Continuum- Implementations of Architecture Continuum- Reusable solutions for future implementations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Define Stakeholder
- Individual, team, or organization- Interests in or concerns about an architecture
26
Define Strategic Architecture
- Formal summary of an entire enterprise- Framework for operational activity- Executive level, long term view
27
Describe Business Transformation Readiness Assessment
- Technique to understand readiness to accept change- Identifies issues and solutions in Migration Plan- Based on Canadian Government BTEP E=Enablement
28
Describe Capability Based Planning
- Business driven: Focuses on business outcomes- Combines efforts of business lines to achieve- Useful when a latent capability needed (DR)
29
Describe IT interoperability in the 4 domains:
- Business: Common look/feel, portal - Data: Identity, common ontology, shared services - Application: Common components, reuse - Technical: Shared methods, systems, services
30
Describe the 2 domains of principles
- Enterprise principles * Guides and harmonizes decision making * Includes principles for business units (HR) - Architecture principles * Reflect enterprise architecture consensus * Govern architecture process and its use
31
Dimensions for limiting architecture scope:
- Breadth: Enterprise, segment, capability - Depth: Level of detail (simple = shallow) - Time period: Resources vs time, transitions - Domains: (Business, data, app, tech) vs subset
32
Guidelines vs techniques
- Guidelines: How to adapt ADM, e.g., iteration - Techniques: Support specific tasks, e.g. gap analysis
33
How does TOGAF work with other architectures
- TOGAF can include the use of other frameworks- ADM is framework agnostic
34
How is Capability based planning related to the ADM
- A: Corporate strategic plan - B-D: Define corporate projects and ABBs - E,F: Define transition architectures (increments)
35
In what ADM phases is Bus Transformation Readiness Assessment used
- A: Initial assessment readiness/CMM- E,F: Selection and implementation
36
In what ADM phases is interoperability considered
- A: Nature and security of information exchange - B-D: Defined for each domain - E: Actual solutions are selected - (Make/Buy) - F: Logical interoperability
37
In what phases is Gap Analysis used
- B, C, D, and E
38
Key ADM points
- ADM is iterative - Decisions are made at each iteration - Reuse from: Previous ADM iterations or other models
39
List 3 categories of interoperability
- Operational/business: Shared processes - Information: Shared information - Technical: Sharing or connection of services
40
List 4 items included in the guidelines (adapt ADM)
- Ways to apply iteration to the ADM - Applying ADM at different levels in enterprise - Security considerations - Using TOGAF to define SOAs
41
List 7 steps used to create business scenarios
- Problem: Identify, document, and rank - Environment: Business and technical - Objectives: Successful outcomes - Human actors: Positions and roles - Computer actors: Elements and roles - Roles and responsibilities: For each actor - Refine: If neces
42
List ADM iteration levels (3)
- Around: Cycle through the phases in order- Between: E.g., return to B Business from D Tech- Within: Repeated execution of a phase activities
43
List ADM Phase B-D steps needed per each domain (BDAT) (9)
- 1. Select reference models, viewpoints, tools- 2. Develop baseline __ Architecture Description- 3. Develop target __ Architecture Description- 4. Perform gap analysis (target vs baseline)- 5. Define candidate roadmap components- 6. Resolve imp
44
List some business domain gaps
* - People: cross training * - Process: inefficiencies * - Tools: duplicate or missing * - Information * - Measurement * - Financial * - Facilities: buildings, office space
45
List some business modeling tools-techniques
- Business process models (activity models)- Use case models- Class models- Node connectivity diagrams- Information exchange matrices
46
List some data domain gaps
- Not current - Not located where needed - Wrong data - Not created - Not consumed - Relationship gaps
47
List the TOGAF principles template elements (4)
- Name: Descriptively names the principle- Statement: Communicates the fundamental rule- Rationale: Business benefits, precedence- Implications: Resources, activities, tasks, impact
48
Process for managing risk (5 steps)
- Risk classification- Risk identification- Initial risk assessment- Mitigation and residual risk assessment- Risk monitoring
49
Purpose of Tailored architecture framework
- TOGAF needs to be tailored- Integration with project and process frameworks- Customization of technology, presentation, tools- Tailoring for specific projects- Selection of artifacts and deliverables
50
Reasons to adapt the ADM to fit your enterprise
- Change phase order based on org's maturity - Change order based on fixed/dictated constraints - Tailor ADM to use another framework - Reflect dependencies of other processes - Adapt ADM to match a vendor/customer's process - Smaller enterprise migh
51
Reasons to scope (constrain) architecture activity
- Limits in organizational authority - Objectives/concerns addressed within architecture - Resource availability (staff, funds) - In summary - feasibility
52
Steps to creating a Gap Analysis
- Matrix of ABBs: vertical=baseline; Horiz: Target- Add final row: New ABBs"
53
What 5 criteria make an architecture principle good
- Understandability: Easily grasped, unambiguous- Robustness: Precise for consistent decisions- Completeness: Cover every situation- Consistency: Does not contradict other principles- Stability: Enduring, accommodates change
54
What are the 2 levels of risk for Risk Management
- Initial: Prior to implementing mitigation - Residual: After implementing mitigation
55
What does a business scenario describe
- Business process, application, or applications - Business and technology environment - Actors (people and components) involved - Desired outcome
56
What information areas are in Governance Repository
- Reference data: Other repo info; e.g., ITIL - Process status: e.g., compliance assessments - Audit info: A record of completed governance actions
57
What is Gap Analysis
- Shortfall between baseline and target architectures- Validates an architecture being developed- Considers what is forgotten or missing- Lists stakeholder concerns not addressed- Lists ABBs added, updated, deleted
58
When is Business Transformation readiness Assessment done?
Phase A, E and F
59
Where are business scenarios used in the ADM
- A: Architecture Vision - build requirements- B: Business Architecture - derive BA- Referenced in all phases - validate reqs
60
Where is Risk Management used in the ADM
A-E-F
61
Why do we need integration of architecture domains
- Need a consistent frame of reference- So integrations can be considered as a group
62
- G+T is resources, guidelines, templates, techniques- G+T directly support the use of the ADM- Separated from the ADM to reduce clutter- E.g., Iteration, security, gap analysis, principles list
ADM + ADM Guidelines and Techniques
63
- Continuum categorizes entities created using the ADM - Repository stores work created using the ADM - Repository has reference architectures, models, patterns - ADM phase dictates the types of assets used
ADM + Enterprise Continuum + Architecture Repository
64
- ADM populates Foundation Architecture with- Reusable common models, policy, governance
ADM + Foundation Architecture
65
- Guidelines document how to adapt the ADM- Techniques are used when applying the ADM
Briefly describe guidelines vs techniques
66
- S: Specific: Defines what needs to be done- M: Measurable: Clear metrics for success- A: Actionable: Provides the solution- R: Realistic: Within time and cost constraints- T: Time bound: When the opportunity expires
Characteristics of a good business scenario (5)
67
- A set of rules and guidelines for architecture - Seldom amended - Guides the way mission is accomplished - Guides values, actions, results - Initial output of Preliminary phase
Characteristics of Architecture Principles
68
- Description of structure and interaction between- strategy, organization, functions, processes, needs
Define Business Architecture
69
- Ensuring business processes deliver outcomes- And adhere to regulations
Define Business Governance
70
- Ability of organization, system, person- Requires org, people, processes, technology- E.g., telemarketing dept
Define Capability
71
- Interests important to stakeholders- Determine acceptability of a solution- E.g., performance, reliability, security
Define Concerns
72
- External factor that prevents an approach or goal- E.g., Customer data is not consistent
Define Constraint
73
- Logical and physical data assets- Structure and interaction- Data management resources.
Define Data Architecture
74
- Work contractually specified- Reviewed, agreed, signed off by stakeholders- Archived or stored in an Architecture Repository- Can be: Reference model, standard, or snapshot
Define Deliverable
75
- Collection of organizations with common goals- Highest organizational level- Covers all missions and functions- Can extend to partners, suppliers, customers
Define Enterprise
76
- Difference between two states- E.g., Baseline vs Target Architecture
Define Gap
77
- Monitoring, managing, steering a business- Enforces delivery of required business outcome
Define Governance
78
1. Lifecycle management of info + technology2. Umbrella including computer industry areas3. Department assigned to provision IT areas4. Information Services; Information Management
Define IT (4 definitions)
79
- Implementation-independent definition- Logical grouping of related physical entities
Define Logical Architecture
80
- Abstract framework of entities and relations- Based on small number of unifying concepts- Common semantics across implementations
Define Reference Model (RM)
81
- System that manages data in an enterprise- Includes data, processes, other information
Define Repository
82
- Formal description of areas within enterprise- E.g., program or portfolio level
Define Segment Architecture
83
- Descr of a discrete and focused business operation- Applies to a single project, release, solution
Define Solution Architecture
84
- A concrete, physical Building block- Conforms to an Architectural building block
Define Solution Building Block (SBB)
85
- Part of the Enterprise Continuum- Implementations of Architecture Continuum- Reusable solutions for future implementations
Define Solutions Continuum
86
- Individual, team, or organization- Interests in or concerns about an architecture
Define Stakeholder
87
- Formal summary of an entire enterprise- Framework for operational activity- Executive level, long term view
Define Strategic Architecture
88
- Technique to understand readiness to accept change- Identifies issues and solutions in Migration Plan- Based on Canadian Government BTEP E=Enablement
Describe Business Transformation Readiness Assessment
89
- Business driven: Focuses on business outcomes- Combines efforts of business lines to achieve- Useful when a latent capability needed (DR)
Describe Capability Based Planning
90
- Business: Common look/feel, portal - Data: Identity, common ontology, shared services - Application: Common components, reuse - Technical: Shared methods, systems, services
Describe IT interoperability in the 4 domains:
91
- Enterprise principles * Guides and harmonizes decision making * Includes principles for business units (HR) - Architecture principles * Reflect enterprise architecture consensus * Govern architecture process and its use
Describe the 2 domains of principles
92
- Breadth: Enterprise, segment, capability - Depth: Level of detail (simple = shallow) - Time period: Resources vs time, transitions - Domains: (Business, data, app, tech) vs subset
Dimensions for limiting architecture scope:
93
- Guidelines: How to adapt ADM, e.g., iteration - Techniques: Support specific tasks, e.g. gap analysis
Guidelines vs techniques
94
- TOGAF can include the use of other frameworks- ADM is framework agnostic
How does TOGAF work with other architectures
95
- A: Corporate strategic plan - B-D: Define corporate projects and ABBs - E,F: Define transition architectures (increments)
How is Capability based planning related to the ADM
96
- A: Initial assessment readiness/CMM- E,F: Selection and implementation
In what ADM phases is Bus Transformation Readiness Assessment used
97
- A: Nature and security of information exchange - B-D: Defined for each domain - E: Actual solutions are selected - (Make/Buy) - F: Logical interoperability
In what ADM phases is interoperability considered
98
- B, C, D, and E
In what phases is Gap Analysis used
99
- ADM is iterative - Decisions are made at each iteration - Reuse from: Previous ADM iterations or other models
Key ADM points
100
- Operational/business: Shared processes - Information: Shared information - Technical: Sharing or connection of services
List 3 categories of interoperability
101
- Ways to apply iteration to the ADM - Applying ADM at different levels in enterprise - Security considerations - Using TOGAF to define SOAs
List 4 items included in the guidelines (adapt ADM)
102
- Problem: Identify, document, and rank - Environment: Business and technical - Objectives: Successful outcomes - Human actors: Positions and roles - Computer actors: Elements and roles - Roles and responsibilities: For each actor - Refine: If neces
List 7 steps used to create business scenarios
103
- Around: Cycle through the phases in order- Between: E.g., return to B Business from D Tech- Within: Repeated execution of a phase activities
List ADM iteration levels (3)
104
- 1. Select reference models, viewpoints, tools- 2. Develop baseline __ Architecture Description- 3. Develop target __ Architecture Description- 4. Perform gap analysis (target vs baseline)- 5. Define candidate roadmap components- 6. Resolve imp
List ADM Phase B-D steps needed per each domain (BDAT) (9)
105
* - People: cross training * - Process: inefficiencies * - Tools: duplicate or missing * - Information * - Measurement * - Financial * - Facilities: buildings, office space
List some business domain gaps
106
- Business process models (activity models)- Use case models- Class models- Node connectivity diagrams- Information exchange matrices
List some business modeling tools-techniques
107
- Not current - Not located where needed - Wrong data - Not created - Not consumed - Relationship gaps
List some data domain gaps
108
- Name: Descriptively names the principle- Statement: Communicates the fundamental rule- Rationale: Business benefits, precedence- Implications: Resources, activities, tasks, impact
List the TOGAF principles template elements (4)
109
- Risk classification- Risk identification- Initial risk assessment- Mitigation and residual risk assessment- Risk monitoring
Process for managing risk (5 steps)
110
- TOGAF needs to be tailored- Integration with project and process frameworks- Customization of technology, presentation, tools- Tailoring for specific projects- Selection of artifacts and deliverables
Purpose of Tailored architecture framework
111
- Change phase order based on org's maturity - Change order based on fixed/dictated constraints - Tailor ADM to use another framework - Reflect dependencies of other processes - Adapt ADM to match a vendor/customer's process - Smaller enterprise migh
Reasons to adapt the ADM to fit your enterprise
112
- Limits in organizational authority - Objectives/concerns addressed within architecture - Resource availability (staff, funds) - In summary - feasibility
Reasons to scope (constrain) architecture activity
113
- Matrix of ABBs: vertical=baseline; Horiz: Target- Add final row: New ABBs"
Steps to creating a Gap Analysis
114
- Understandability: Easily grasped, unambiguous- Robustness: Precise for consistent decisions- Completeness: Cover every situation- Consistency: Does not contradict other principles- Stability: Enduring, accommodates change
What 5 criteria make an architecture principle good
115
- Initial: Prior to implementing mitigation - Residual: After implementing mitigation
What are the 2 levels of risk for Risk Management
116
- Business process, application, or applications - Business and technology environment - Actors (people and components) involved - Desired outcome
What does a business scenario describe
117
- Reference data: Other repo info; e.g., ITIL - Process status: e.g., compliance assessments - Audit info: A record of completed governance actions
What information areas are in Governance Repository
118
- Shortfall between baseline and target architectures- Validates an architecture being developed- Considers what is forgotten or missing- Lists stakeholder concerns not addressed- Lists ABBs added, updated, deleted
What is Gap Analysis
119
Phase A, E and F
When is Business Transformation readiness Assessment done?
120
- A: Architecture Vision - build requirements- B: Business Architecture - derive BA- Referenced in all phases - validate reqs
Where are business scenarios used in the ADM
121
A-E-F
Where is Risk Management used in the ADM
122
- Need a consistent frame of reference- So integrations can be considered as a group
Why do we need integration of architecture domains