Brainscape's Knowledge GenomeTM

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


See full index

TOGAF > Architecture Development Method > Flashcards

Architecture Development Method Flashcards

Describes the TOGAF Architecture Development Method (ADM)

1
Q

4 Architecture domains

A

Business Architecture
Data Architecture
Application Architecture
Technology Architecture

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

Business Architecture

A

A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business
views and strategies, products, policies, initiatives, and stakeholders.

It relates business elements to business goals and elements of other
domains.

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

Data Architecture

A

A description of the structure and interaction of the enterprise’s major types and sources of data,
logical data assets, physical data assets, and data management resources.

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

Application Architecture

A

A description of the structure and interaction of the applications as groups of capabilities that
provide key business functions and manage the data assets.

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

Technology Architecture

A

A description of the structure and interaction of the technology services and technology
components.

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

Architectural principle

A

A qualitative statement of intent that should be met by the architecture.

Rules and guidelines that say how enterprise fulfils its mission

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

Defining Architecture Principles

A

Why - it provides a framework for decision making.
Who - Enterprise Architects, with stakeholders.

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

TOGAF template for Principles

A

Name (essence of generic rule), Statement (explain fundamental rule), Rationale (Business benefit and relation to other principles), Implications (Business impact & consequences)

Eg: Primacy of Principles, Maximize Benefit to the Enterprise, Complaince with the Law

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

Five Qualities of Principles

A
  1. Understandable - Intent is clear and unambiguous
  2. Robust - Enable good decisions about architectures and plans, enable enforceable policies and standards to be created.
  3. Complete - They cover every situation perceived.
  4. Consistent - Principles should allow a balance of interpretations and should not be contradictory
  5. Stable - Must be enduring and able to accommodate change.

Established amendment process for changing principles.

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

Principles vs Metamodel

A

Principles should be aligned to the metamodel concepts of drivers, goals, objectives.

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

Principles Catalog

A

The principles Catalog captures principles of the business and Architecture Principles that describe what a “good” solution or architecture looks like.
Contains metamodel entity - Principle.

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

Business Scenarios

A

Business scenarios help us to identify and understand business requirements that the architecture development must address.
Used prominently in Phase A, and iteratively in Phase B.

Business requirement is referred throughout ADM

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

What does Business scenarios describe?

A

Business process, application, or set of applications that can ebe enabled by the architecture; Business and technology environment; Actors who execute it; desired outcome of proper execution.

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

Developing a Business Scenario

A
  1. Problem
  2. Environment
  3. Objectives
  4. Human Actors
  5. Computer Actors
  6. Roles & Responsibility
  7. Refine
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Method within a method

A

TOGAF Series Guide: Business Scenarios defines a method for developing Business Scenarios.

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

Preliminary Phase: Objectives

A
  1. Determine the Architecture Capability desired by the organization
  2. Establish the Architecture Capability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Preliminary Phase: Inputs

A
  1. Reference Materials External to the Enterprise - TOGAF library, Architecture frameworks
  2. Non-Architectural Inputs - Business goals, drivers, governance and legal frameworks
  3. Architectural Inputs - Pre-existing models for operating an Enterprise Architecture Capability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Preliminary Phase: Steps

A

1.Scope the enterprise organizations impacted
2.Confirm governance and support frameworks
3.Define and establish Enterprise Architecture team
4.Identify Architecture Principles
5.Tailor TOGAF or other architecture framework (Terminology/Process/Content Tailoring)
6.Develop a strategy and implementation plan for tools and techniques

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

Preliminary Phase: Outputs

A
  1. Organizational Model for Enterprise Architecture
  2. Tailored Architecture Framework + Architecture principles
  3. Initial Architecture Repository
  4. Restatement of business principles, business goals, and business drivers
  5. Request for Architecture Work
  6. Architecture Governance Framework
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Preliminary Phase: Artifacts

A

Principles catalog

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

Preliminary Phase: Approach

A

1.Defining the enterprise
2.Identifying key drivers and elements in the organizational context
3.Defining the requirements for architecture work
4.Defining the Architecture Principles that will inform any architecture work
5.Defining the framework to be used
6.Defining the relationships between management frameworks
7.Evaluating the Enterprise Architecture maturity

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

Phase A: Architecture Vision: Objectives

A

1.Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture
2.Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision

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

Phase A: Architecture Vision: Input

A

1.Reference Materials External to the Enterprise
2.Non-Architectural Inputs - Request for Architecture Work (from Business), Business principles, business goals, and business drivers (from Sponsor)
3.Architectural Inputs - Organizational Model for Enterprise Architecture (from Prelim), Tailored Architecture Framework including Arch. principles (from Prelim), Populated Architecture Repository (from previous enterprise work)

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

Phase A: Architecture Vision: Steps

A

1.Establish the architecture project
2.Identify stakeholders, concerns, and business requirements
3.Confirm and elaborate business goals, business drivers, and constraints
4.Evaluate capabilities
5.Assess readiness for business transformation
6.Define scope
7.Confirm and elaborate Architecture Principles, including business principles
8.Develop Architecture Vision
9.Define the Target Architecture value propositions and KPIs
10.Identify the business transformation risks and mitigation activities
11.Develop Statement of Architecture Work; secure approval

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

Phase A: Architecture Vision: Artifacts

A

Stakeholder Map Matrix
Value Chain Diag
Solution Concept Diag

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

Phase A: Architecture Vision: Outputs

A

1.Approved Statement of Architecture Work
2.Refined statements of business principles, business goals, and business drivers
3.Architecture Principles
4.Capability Assessment
5.Tailored Architecture Framework
6.Architecture Vision
7.Draft Architecture Definition Document - Baseline & target BDAT architecture
8.Communications Plan
9.Additional content populating the Architecture Repository

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

Phase A: Architecture Vision: Approach

A

1.Phase A defines what is in and what is outside of the acrchitecture effort, and the constraints
2.COnstarints are informed by principles, business goals and strategic drivers
3.Creates the Architecture Vision document

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

Phase B: Business Architecture: Objectives

A

1.Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns
2.Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures

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

Phase B: Business Architecture: Approach

A

1.Knowledge of Business Architecture (taken from owner of Business)
2.Business strategy defines what to achieve
3.Business Architecture describes how to achieve it
4.Required to demonstrate business value of subsequent work to key stakeholders.
5.Scope depends on existing strategy and planning. If none exist then process definition will require detailed work.
6.Identify key business objectives and processes.

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

Phase B: Business Architecture: Input

A

1.Reference Materials External to the Enterprise
2.Non-Architectural Inputs - Request for Architecture Work, Business principles, business goals, and business drivers, Capability Assessment (from phaseA), Communications Plan (from phaseA)
3.Architectural Inputs - Organizational Model for Enterprise Architecture (from Prelim), Tailored Architecture Framework (from Prelim), Approved Statement of Architecture Work (from phaseA), Architecture Principles (from phaseA/Prelim), Enterprise Continuum (all previous arch work by Enterprise), Architecture Repository (all previous arch work by Enterprise), Architecture Vision (from phaseA), Draft Architecture Definition Document (from phaseA)

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

Phase B: Business Architecture: Steps

A

1.Select reference models, viewpoints, and tools
2.Develop Baseline Business Architecture Description
3.Develop Target Business Architecture Description
4.Perform gap analysis
5.Define candidate roadmap components
6.Resolve impacts across the Architecture Landscape
7.Conduct formal stakeholder review
8.Finalize the Business Architecture
9.Create the Architecture Definition Document

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

Phase B: Business Architecture: Outputs

A

1.Statement of Architecture Work
2.Validated business principles, goals and drivers
3.Refined and updated Business Architecture Principles
4.Draft Architecture Definition Document (started in phaseA, here detailed)
5.Draft Architecture Requirements Specifications (started in phaseA with high level requirement, here detailed)
6.Business Architecture components of an Architecture Roadmap (gap analysis result)

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

Business Architecture: Modelling Process techniques

A

Capability Mapping
Organization Mapping
Value stream Mapping
Structured Analysis
Use-Case Analysis
Process Modelling

34
Q

Business Architecture: Business Capability Mapping

A

identifies, categorizes, and decomposes the business capabilities required for the business to have the ability to deliver value to one or more stakeholders

35
Q

Business Architecture: Organization Mapping

A

representation of the organizational structure of the business (including third-party domains), depicting business units, the decomposition of those units into lower-level functions, and organizational relationships (unit-to-unit and mapping to business capabilities, locations, and other attributes)

36
Q

Business Architecture: Value stream Mapping

A

the breakdown of activities that an organization performs to create the value being exchanged with stakeholders

37
Q

Business Architecture: Structured Analysis

A

identifies the key business functions within the scope of the architecture, and maps those functions onto the organizational units within the business

38
Q

Business Architecture: Use-Case Analysis

A

the breakdown of business-level functions across actors and organizations allows the actors in a function to be identified and permits a breakdown into services supporting/delivering that functional capability

39
Q

Business Architecture: Process Modelling

A

the breakdown of a function or business service through process modeling allows the elements of the process to be identified, and permits the identification of lower-level business services or functions.

40
Q

Business Architecture: Artifacts

A

Organization/Actor Catalog, Role Catalog, Business Service/Function Catalog, Location Catalog, Value Stream Catalog, Business Capabilities Catalog, Value Stream Stages Catalog, Process/Event/Control/Product Catalog, Driver/Goal/Objective Catalog, Contract/Measure Catalog, Business Interaction Matrix, Actor/Role Matrix, Value Stream/Capability Matrix, Strategy/Capability Matrix, Capability/Organization Matrix, Business Footprint Diag, Business Service/Information Diag, Functional Decomposition Diag, Product Lifecycle Diag, Business Model Diag, Business Capability Map, Value Stream Map, Organization Map, Goal/Objective/Service Diag, Business Use-case Diag, Organization Decomposition Diag, Process Flow Diag, Event Diag

41
Q

Phase E: Opportunities & Solutions: Objectives

A

1.Generate the initial complete version of the Architecture Roadmap, based upon the gap
analysis and candidate Architecture Roadmap components from Phases B, C, and D
2.Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
3.Define the overall solution building blocks to finalize the Target Architecture based on the
Architecture Building Blocks (ABBs)

42
Q

Phase E: Opportunities & Solutions: Approach

A

1.Take into account the complete set of gaps between Target & Baseline arch. in BDAT domains
2.Logically group changes into work packages
3.Build best-fit roadmap

43
Q

Phase E: Opportunities & Solutions: Inputs

A
  1. Reference Materials External to the Enterprise
    i. Architecture reference materials
    ii. Product information (COTS/ERP etc)
  2. Non-Architectural Inputs
    i. Request for Architecture Work (from Prelim)
    ii. Capability Assessment (Prelim + PhaseA)
    iii. Communications Plan (PhaseA)
    iv. Planning methodologies (PhaseA)
  3. Architectural Inputs
    i. Organizational Model for Enterprise Architecture (Prelim)
    ii. Governance models and frameworks (Prelim)
    iii. Tailored Architecture Framework (Prelim)
    iv. Statement of Architecture Work (PhaseA)
    v. Architecture Vision (PhaseA)
    vi. Architecture Repository (prelim)
    vii. Draft Architecture
    Definition Document (PhaseA,B,C,D)
    viii. Draft Architecture Requirements Specification (PhaseA,B,C,D)
    ix. Change Requests for existing business programs and projects (PhaseB,C,D)
    x. Candidate Architecture Roadmap components (PhaseB,C,D)
44
Q

Phase E: Opportunities & Solutions: Steps

A

1.Determine/confirm key corporate change attributes
2.Determine business constraints for implementation
3.Review and consolidate gap analysis results from Phases B to D
4.Review consolidated requirements across related business functions
5.Consolidate and reconcile interoperability requirements
6.Refine and validate dependencies
7.Confirm readiness and risk for business transformation
8.Formulate Implementation and Migration Strategy
9.Identify and group major work packages
10.Identify Transition Architectures
11.Create the Architecture Roadmap & Implementation and Migration Plan

45
Q

Phase E: Opportunities & Solutions: Outputs

A

1.Statement of Architecture Work
2.Architecture Vision
3.Draft Architecture Definition Document
4.Draft Architecture Requirements Specification
5.Capability Assessment
6.Architecture Roadmap
7.Implementation & Mitigation Plan (outline)

46
Q

Phase E: Opportunities & Solutions: Artifacts

A

1.Project Context Diagram
2.Benefits Diagram

47
Q

Phase C: Information systems Architecture: Objectives

A

1.Develop the Target Data/Application Architecture
2.Identify candidate Architecture Roadmap components based on gap analysis

48
Q

Phase C: Approach: Top-down design Bottom-up implementation

A

Design: BDAT architecture
Implementation: BADT architecture

49
Q

Phase C: Approach: Data-Driven Sequence implementation

A
  1. Implement application systems that create data
  2. Applications that process data
  3. Applications that archive data
50
Q

Retail industry reference Data architecture model

A

ARTS

51
Q

Petrotechnical industry reference Data architecture model

A

Energistics Data Exchange Standards

52
Q

Telecommunications industry reference Application architecture model

A

TM Forum

53
Q

Healthcare, Transportation, Finance industry reference Application architecture model

A

OMG software models

54
Q

Consideration for Data architecture

A

Data Management, Data Migration, Data Governance

55
Q

Phase C: Information systems Architecture & Phase D: Technology systems Architecture: Inputs

A

1.Reference Materials External to the Enterprise
i. Architecture reference materials
2.Non-Architectural Inputs
i.Request for Architecture Work
ii.Capability Assessment
iii.Communications Plan
3.Architectural Inputs
i.Organizational Model for Enterprise Architecture
ii.Tailored Architecture Framework
iii.Data & Applications /Technology principles
iv.Statement of Architecture Work
v.Architecture Vision
vi.Architecture Repository
vii.Draft Architecture Definition Document
viii.Draft Architecture Requirements Specification
ix.Business Architecture components of an Architecture Roadmap

56
Q

Phase C: Data /Application Architecture & Phase D: Technology Architecture: Steps

A

1.Select reference models, viewpoints, and tools
2.Develop Baseline Data /Application /Technology Architecture Description
3.Develop Target Data /Application /Technology Architecture Description
4.Perform gap analysis
5.Define candidate roadmap components
6.Resolve impacts across the Architecture Landscape
7.Conduct formal stakeholder review
8.Finalize the Data /Application /Technology Architecture
9.Create the Architecture Definition Document

57
Q

Phase C: Data Architecture: Artifacts

A
  1. Catalog:
    Data Entity/Data Component Catalog
  2. Matrices:
    i.Data Entity/Business Function matrix
    ii.Application/Data matrix
    3.Diagrams:
    i.Conceptual Data diagram
    ii.Logical Data diagram
    iii.Data Dissemination diagram
    iv.Data Security diagram
    v.Data Migration diagram
    vi.Data Lifecycle diagram
58
Q

Phase C: Data /Application Architecture & Phase D: Technology Architecture Outputs

A

1.Statement of Architecture Work
2.Validated or new Data /Application / Tehcnology principles
3.Draft Architecture Definition Document
i.Baseline Data /Application / Technology Architecture
ii.Target Data /Application /Technology Architecture
iii.Views corresponding to the selected viewpoints addressing key stakeholder concerns
4.Draft Architecture Requirements Specification
i.Gap analysis results
ii.Data interoperability requirements
5.Data/ Application / Technology Architecture components of an Architecture Roadmap

59
Q

Phase C: Application Architecture: Artifacts

A

1.Catalogs:
i.Application Portfolio catalog
ii.Interface catalog
2.Matrices:
i.Application/Organization matrix
ii.Role/Application matrix
iii.Application/Function matrix
iv.Application Interaction matrix
3.Diagrams:
i.Application Communication diagram
ii.Application and User Location diagram
iii.Application Use-Case diagram
iv.Enterprise Manageability diagram
v.Process/Application Realization diagram
vi.Software Engineering diagram
vii.Application Migration diagram
viii.Software Distribution diagram

60
Q

Phase D: Technology Architecture: Artifacts

A
  1. Catalogs:
    i.Technology Standards catalog
    ii.Technology Portfolio catalog
    2.Matrices:
    i.Application/Technology matrix
    3.Diagrams:
    i.Environments and Locations diagram
    ii.Platform Decomposition diagram
    iii.Processing diagram
    iv.Networked Computing/Hardware diagram
    v.Network and Communications diagram
61
Q

Phase F: Migration Planning: Objectives

A

1.Finalize the Architecture Roadmap & supporting Implementation and Migration Plan
2.Ensure Implementation and Migration Plan is co-ordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio
3.Ensure business value and cost of work packages & Transition Architectures is understood by key stakeholders

62
Q

Phase F: Migration Planning: Approach

A

1.Focus on creation of an Implementation and Migration Plan in co-operation with the project and portfolio managers
2.Assessing dependencies, costs, & benefits of the various migration
projects within the context of the enterprise’s other activity.

63
Q

Phase F: Migration Planning: Inputs

A

1.Reference Materials External to the Enterprise
2.Non-Architectural Inputs
i.Request for Architecture Work
ii.Capability Assessment
iii.Communications Plan
3.Architectural Inputs
i.Organizational Model for Enterprise Architecture
ii.Governance models and frameworks
iii.Tailored Architecture Framework
iv.Statement of Architecture Work
v.Architecture Vision
vi.Architecture Repository
vii.Draft Architecture Definition Document
viii.Draft Architecture Requirements Specification
ix.Change Requests for existing business programs and projects
x.Architecture Roadmap
xi.Capability Assessment
xii.Implementation and Migration Plan (outline)

64
Q

Phase F: Migration Planning: Steps

A

1.Confirm management framework interactions for Implementation and Migration Plan
2.Assign a business value to each work package
3.Estimate resource requirements, project timings, and availability/delivery vehicle
4.Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation
5.Confirm Architecture Roadmap and update Architecture Definition Document
6.Complete the Implementation and Migration Plan
7.Complete the architecture development cycle and document lessons learned

65
Q

Phase F: Migration Planning: Output

A

1.Implementation and Migration Plan - Implementation and Migration Strategy, Project and portfolio breakdown of the implementation, Project charters
2.Finalized Architecture Definition Document
3.Finalized Architecture Requirements Specification
4.Finalized Architecture Roadmap
5.Re-Usable Architecture Building Blocks
6.Requests for Architecture Work
7.Implementation Governance Model
8.Change Requests for the Architecture Capability

66
Q

Phase G: Implementation Governance: Objectives

A

1.Ensure conformance with the Target Architecture by implementation projects
2.Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests

67
Q

Phase G: Implementation Governance: Inputs

A

1.Reference Materials External to the Enterprise
2.Non-Architectural Inputs
i.Request for Architecture Work
ii.Capability Assessment
3.Architectural Inputs
i.Organizational Model for Enterprise Architecture
ii.Tailored Architecture Framework
iii.Statement of Architecture Work
iv.Architecture Vision
v.Architecture Repository
vi.Architecture Definition Document
vii.Architecture Requirements Specification
viii.Architecture Roadmap
ix.Implementation Governance Model
x.Architecture Contract (standard)
xi.Request for Architecture Work
xii.Implementation and Migration Plan

68
Q

Phase G: Implementation Governance: Steps

A

1.Confirm scope and priorities for deployment with development management
2.Identify deployment resources and skills
3.Guide development of solutions deployment
4.Perform Enterprise Architecture Compliance reviews
5.Implement business and IT operations
6.Perform post-implementation review & close the implementation

69
Q

Phase G: Implementation Governance: Outputs

A

1.Architecture Contract (signed)
2.Compliance Assessments
3.Change Requests
4.Architecture-compliant solutions deployed

70
Q

Phase G: Implementation Governance: Approach

A

1.Establish an implementation program that will enable the delivery of the Transition
Architectures agreed for implementation during the Migration Planning phase
2.Adopt a phased deployment schedule that reflects the business priorities embodied in the
Architecture Roadmap
3.Follow the organization’s standard for corporate, IT, & Architecture Governance
4.Use the organization’s established portfolio /program management approach, where this exists
5.Define an operations framework to ensure the effective long life of the deployed solution

71
Q

Phase H: Architecture Change Management: Objectives

A

1.Ensure architecture lifecycle is maintained
2.Ensure Architecture Governance Framework is executed
3.Ensure Enterprise Architecture Capability meets current requirements

72
Q

Phase H: Architecture Change Management: Inputs

A

1.Reference Materials External to the Enterprise
2.Non-Architectural Inputs
i.Request for Architecture Work
3.Architectural Inputs
i.Organizational Model for Enterprise Architecture
ii.Tailored Architecture Framework
iii.Statement of Architecture Work
iv.Architecture Vision
v.Architecture Repository
vi.Architecture Definition Document
vii.Architecture Requirements Specification
viii.Architecture Roadmap
ix.Change request technology changes/ request business changes/ lessons learned
x.Implementation Governance Model
xi.Architecture Contract (signed)
xii.Compliance Assessments
xiii.Implementation and Migration Plan

73
Q

Phase H: Architecture Change Management: Approach

A

1.Ensure that the architecture achieves its original target business value.
2.Ensure changes to the architecture are managed properly and dynamic architecture is supported
3.Determine circumstances under which architecture may be changed and process for this

74
Q

Phase H: Architecture Change Management: Outputs

A

1.Architecture updates (for maintenance changes)
2.Changes to architecture framework and principles (for maintenance changes)
3.New Request for Architecture Work, to move to another cycle
(for major changes)
4.Statement of Architecture Work (updated if needed)
5.Architecture Contract (updated if needed)
6.Compliance Assessments

75
Q

3 main categories of architectural change

A

1.Simplification change: can normally be handled via change management techniques
2.Incremental change: may be capable of being handled via change
management techniques, or it may require partial re-architecting, depending on the nature of the change
3.Re-architecting change: requires putting the whole architecture through the architecture development cycle again

76
Q

Determination of category of architectural change

A

1.Register all events that may impact the architecture
2. Allocate resource & management for architecture tasks
3. The process or role responsible for architecture resources has to make assessment of what should be done
4. Evaluation of impact

77
Q

Guidelines for Maintenance vs Architecture Redesign

A

1.change impacts two stakeholders or more -REDESIGN
2.change impacts only one stakeholder-MAINTENANCE
3.change can be allowed under a dispensation-MAINTENANCE

78
Q

ADM Architecture Requirements Management Phase: Objectives

A

1.Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases
2.Manage architecture requirements identified during any execution of the ADM cycle or a phase
3.Ensure that relevant architecture requirements are available for use by each phase as the
phase is executed

79
Q

ADM Architecture Requirements Management Phase: Inputs

A

1.Architectural Inputs
i.Populated Architecture Repository
ii.Organizational Model for Enterprise Architecture
iii.Tailored Architecture Framework
iv.Statement of Architecture Work
v.Architecture Vision
v.Requirements Impact Assessment

80
Q

ADM Architecture Requirements Management Phase: Steps

A

1.Identify/document requirements - Business use case
2.Baseline requirements
3.Monitor Baseline requirements
4.Identify changed requirement
5.Identify changed requirement and record priorities
6.Assess impact of change
7.Implement changes arising from PhaseH
8.Update the Architecture Requirements Repository with information relating to the changes requested, including stakeholder views affected.
9.Implement change in the current phase
10.Assess and revise gap analysis for past phases

81
Q

ADM Architecture Requirements Management Phase: Outputs

A

1.Update Architecture Requirements Specification
2.Requirements Impact Statement

82
Q

Phase H: Architecture Change Management: Steps

A

1.Establish value realization process
2.Deploy monitoring tools
3.Manage risks
Provide analysis for architecture change management
4.Develop change requirements to meet performance targets
5.Manage governance process
6.Activate the process to implement change

TOGAF (6 decks)

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