Architecture Development Method

Question 1

4 Architecture domains

Answer 1

Business Architecture
Data Architecture
Application Architecture
Technology Architecture

Question 2

Business Architecture

Answer 2

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.

Question 3

Data Architecture

Answer 3

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.

Question 4

Application Architecture

Answer 4

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

Question 5

Technology Architecture

Answer 5

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

Question 6

Architectural principle

Answer 6

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

Rules and guidelines that say how enterprise fulfils its mission

Question 7

Defining Architecture Principles

Answer 7

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

Question 8

TOGAF template for Principles

Answer 8

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

Question 9

Five Qualities of Principles

Answer 9

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.

Question 10

Principles vs Metamodel

Answer 10

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

Question 11

Principles Catalog

Answer 11

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.

Question 12

Business Scenarios

Answer 12

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

Question 13

What does Business scenarios describe?

Answer 13

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.

Question 14

Developing a Business Scenario

Answer 14

1. Problem
2. Environment
3. Objectives
4. Human Actors
5. Computer Actors
6. Roles & Responsibility
7. Refine

Question 15

Method within a method

Answer 15

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

Question 16

Preliminary Phase: Objectives

Answer 16

1. Determine the Architecture Capability desired by the organization
2. Establish the Architecture Capability

Question 17

Preliminary Phase: Inputs

Answer 17

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

Question 18

Preliminary Phase: Steps

Answer 18

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

Question 19

Preliminary Phase: Outputs

Answer 19

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

Question 20

Preliminary Phase: Artifacts

Answer 20

Principles catalog

Question 21

Preliminary Phase: Approach

Answer 21

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

Question 22

Phase A: Architecture Vision: Objectives

Answer 22

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

Question 23

Phase A: Architecture Vision: Input

Answer 23

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)

Question 24

Phase A: Architecture Vision: Steps

Answer 24

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

Question 25

Phase A: Architecture Vision: Artifacts

Answer 25

Stakeholder Map Matrix Value Chain Diag Solution Concept Diag

Question 26

Phase A: Architecture Vision: Outputs

Answer 26

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

Question 27

Phase A: Architecture Vision: Approach

Answer 27

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

Question 28

Phase B: Business Architecture: Objectives

Answer 28

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

Question 29

Phase B: Business Architecture: Approach

Answer 29

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.

Question 30

Phase B: Business Architecture: Input

Answer 30

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)

Question 31

Phase B: Business Architecture: Steps

Answer 31

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

Question 32

Phase B: Business Architecture: Outputs

Answer 32

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)

Question 33

Business Architecture: Modelling Process techniques

Answer 33

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

Question 34

Business Architecture: Business Capability Mapping

Answer 34

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

Question 35

Business Architecture: Organization Mapping

Answer 35

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)

Question 36

Business Architecture: Value stream Mapping

Answer 36

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

Question 37

Business Architecture: Structured Analysis

Answer 37

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

Question 38

Business Architecture: Use-Case Analysis

Answer 38

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

Question 39

Business Architecture: Process Modelling

Answer 39

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.

Question 40

Business Architecture: Artifacts

Answer 40

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

Question 41

Phase E: Opportunities & Solutions: Objectives

Answer 41

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)

Question 42

Phase E: Opportunities & Solutions: Approach

Answer 42

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

Question 43

Phase E: Opportunities & Solutions: Inputs

Answer 43

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)

Question 44

Phase E: Opportunities & Solutions: Steps

Answer 44

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

Question 45

Phase E: Opportunities & Solutions: Outputs

Answer 45

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)

Question 46

Phase E: Opportunities & Solutions: Artifacts

Answer 46

1.Project Context Diagram 2.Benefits Diagram

Question 47

Phase C: Information systems Architecture: Objectives

Answer 47

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

Question 48

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

Answer 48

Design: BDAT architecture Implementation: BADT architecture

Question 49

Phase C: Approach: Data-Driven Sequence implementation

Answer 49

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

Question 50

Retail industry reference Data architecture model

Answer 50

ARTS

Question 51

Petrotechnical industry reference Data architecture model

Answer 51

Energistics Data Exchange Standards

Question 52

Telecommunications industry reference Application architecture model

Answer 52

TM Forum

Question 53

Healthcare, Transportation, Finance industry reference Application architecture model

Answer 53

OMG software models

Question 54

Consideration for Data architecture

Answer 54

Data Management, Data Migration, Data Governance

Question 55

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

Answer 55

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

Question 56

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

Answer 56

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

Question 57

Phase C: Data Architecture: Artifacts

Answer 57

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

Question 58

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

Answer 58

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

Question 59

Phase C: Application Architecture: Artifacts

Answer 59

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

Question 60

Phase D: Technology Architecture: Artifacts

Answer 60

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

Question 61

Phase F: Migration Planning: Objectives

Answer 61

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

Question 62

Phase F: Migration Planning: Approach

Answer 62

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.

Question 63

Phase F: Migration Planning: Inputs

Answer 63

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)

Question 64

Phase F: Migration Planning: Steps

Answer 64

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

Question 65

Phase F: Migration Planning: Output

Answer 65

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

Question 66

Phase G: Implementation Governance: Objectives

Answer 66

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

Question 67

Phase G: Implementation Governance: Inputs

Answer 67

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

Question 68

Phase G: Implementation Governance: Steps

Answer 68

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

Question 69

Phase G: Implementation Governance: Outputs

Answer 69

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

Question 70

Phase G: Implementation Governance: Approach

Answer 70

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

Question 71

Phase H: Architecture Change Management: Objectives

Answer 71

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

Question 72

Phase H: Architecture Change Management: Inputs

Answer 72

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

Question 73

Phase H: Architecture Change Management: Approach

Answer 73

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

Question 74

Phase H: Architecture Change Management: Outputs

Answer 74

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

Question 75

3 main categories of architectural change

Answer 75

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

Question 76

Determination of category of architectural change

Answer 76

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

Question 77

Guidelines for Maintenance vs Architecture Redesign

Answer 77

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

Question 78

ADM Architecture Requirements Management Phase: Objectives

Answer 78

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

Question 79

ADM Architecture Requirements Management Phase: Inputs

Answer 79

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

Question 80

ADM Architecture Requirements Management Phase: Steps

Answer 80

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

Question 81

ADM Architecture Requirements Management Phase: Outputs

Answer 81

1.Update Architecture Requirements Specification 2.Requirements Impact Statement

Question 82

Phase H: Architecture Change Management: Steps

Answer 82

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