cbap babok diagrams

8/19/2019 CBAP Babok Diagrams

1/80

Certified Business Analysis

Professional (CBAP)Task NotesBasma Gamal

12/29/2014


2/80

1

Contents

Chapter 1 Introduction .......................................................................................................................... 3

Chapter 2 Business Analysis Planning & Monitoring ........................................................................... 5

TASK 1- PLAN BUSINESS ANALYSIS APPROACH ........................................................................................... 6

TASK 2- CONDUCT STAKEHOLDER ANALYSIS ............................................................................................... 8

TASK 3- PLAN BA ACTIVITIES .................................................................................................................. 10

TASK 4- PLAN BA COMMUNICATION ....................................................................................................... 12

TASK 5- PLAN REQUIREMENTS MANAGEMENT PROCESS ........................................................................... 14

TASK 6- MANAGE BA PERFORMANCE ...................................................................................................... 16

Chapter 3 Elicitation ............................................................................................................................ 19

TASK 1- PREPARE FOR ELICITATION.......................................................................................................... 20

TASK 2- CONDUCT ELICITATION ACTIVITY ................................................................................................. 22TASK 3- DOCUMENT ELICITATION RESULTS .............................................................................................. 24

TASK 4- CONFIRM ELICITATION RESULTS .................................................................................................. 26

Chapter 4 Requirements Management and Communication ............................................................ 29

TASK 1- MANAGE SOLUTION SCOPE & REQUIREMENTS ............................................................................ 30

TASK 2- MANAGE REQUIREMENTS TRACEABILITY ..................................................................................... 32

TASK 3- MAINTAIN REQUIREMENTS FOR RE-USE ...................................................................................... 34

TASK 4- PREPARE REQUIREMENTS PACKAGE ............................................................................................ 36

TASK 5- COMMUNICATE REQUIREMENTS ................................................................................................. 38

Chapter 5 Enterprise Analysis ............................................................................................................. 41

TASK 1- DEFINE BUSINESS NEED .............................................................................................................. 42

TASK 2- ASSESS CAPABILITY GAPS ........................................................................................................... 44

TASK 3- DETERMINE SOLUTION APPROACH .............................................................................................. 46

TASK 4- DEFINE SOLUTION SCOPE ........................................................................................................... 48

TASK 5- DEFINE BUSINESS CASE .............................................................................................................. 50

Chapter 6 Requirements Analysis ....................................................................................................... 53

TASK 1- PRIORITIZE REQUIREMENTS ........................................................................................................ 54

TASK 2- ORGANIZE REQUIREMENTS ......................................................................................................... 56

TASK 3- SPECIFY AND MODEL REQUIREMENTS ......................................................................................... 58

TASK 4- DEFINE ASSUMPTIONS AND CONSTRAINTS ................................................................................... 60

TASK 5- VERIFY REQUIREMENTS .............................................................................................................. 62


3/80

2

TASK 6- VALIDATE REQUIREMENTS .......................................................................................................... 64

Chapter 7 Solution Assessment and Validation ................................................................................. 67

TASK 1- ASSESS PROPOSED SOLUTION ..................................................................................................... 68

TASK 2- ALLOCATE REQUIREMENTS ......................................................................................................... 70

TASK 3- ASSESS ORGANIZATION READINESS ............................................................................................. 72

TASK 4- DEFINE TRANSITION REQUIREMENTS ........................................................................................... 74

TASK 5- VALIDATE SOLUTION .................................................................................................................. 76

TASK 6- EVALUATE SOLUTION PERFORMANCE .......................................................................................... 78


4/80


5/80

4

Chapter 2 Business Analysis Planning & Monitoring

Task 1- Plan Business Analysis Approach

Task 2- Conduct Stakeholder analysis

Task 3- Plan BA Activities

Task 4- Plan BA Communication

Task 5- Plan Requirements Management Process

Task 6- Manage BA Performance

Chapter 3 Elicitation

Task 1- Prepare for Elicitation

Task 2- Conduct Elicitation Activity

Task 3- Document Elicitation Results

Task 4- Confirm Elicitation Results

Chapter 4 Requirements Management and Communication

Task 1- Manage Solution Scope & Requirements

Task 2- Manage Requirements Traceability

Task 3- Maintain Requirements for Re-use

Task 4- Prepare Requirements Package

Task 5- Communicate Requirements

Chapter 5 Enterprise Analysis

Task 1- Define Business Need

Task 2- Assess Capability Gaps

Task 3- Determine Solution Approach

Task 4- Define Solution Scope

Task 5- Define Business Case

Chapter 6 Requirements Analysis

Task 1- Prioritize Requirements

Task 2- Organize Requirements

Task 3- Specify and Model Requirements

Task 4- Define Assumptions and Constraints

Task 5- Verify Requirements

Chapter 7 Solution Assessment and Validation

Task 1- Assess Proposed Solution

Task 2- Allocate Requirements

Task 3- Assess Organization Readiness

Task 4- Define Transition Requirements

Task 5- Validate Solution


6/80

5

Chapter 2 Business Analysis Planning & Monitoring


7/80

6

Task 1-

PLAN BUSINESS ANALYSIS APPROACH


8/80

7

Input

1.

Business Need

2.

Expert Judgment

3.

Organizational Process Assets

Output

Business Analysis Approach

Tasks using this Output

1.

(2.3) Plan BA Activities

2.

(2.5) Plan Requirements Management Process

Elements

1.

Timing of Business Analysis Work

2.

Formality And Level Of Detail Of Business Analysis Deliverables

3.

Requirements Prioritization

4.

Change Management

5.

Business Analysis Planning Process6.

Communication With Stakeholders

7.

Requirements Analysis and Management Tools

8.

Project Complexity

Techniques

1.

Decision Analysis

2.

Process Modeling

3.

Structured Walkthrough

Stakeholders

1.

Customer, Domain SME, End User or Supplier

2.

Implementation SME3.

Project Manager

4.

Tester

5.

Regulator

6.

Sponsor


9/80

8

Task 2-

CONDUCT STAKEHOLDER ANALYSIS


10/80

9

Input

1. Business Need

2. Enterprise Architecture

3. Organizational Process Assets

Output

Stakeholder List, Roles, and Responsibilities


1. (2.3) Plan BA Activities

2. (2.4) Plan BA Communication

3. (3.1) Prepare for Elicitation

4. (4.1) Manage Solution Scope & Requirements

5. (6.1) Prioritize Requirements

Elements

1. Identification

2. Complexity of Stakeholder Group

Number and variety of direct end users

Number of interfacing business processes and automated systems

3.

Attitude and Influence Attitude towards business analysis

Attitude towards collaboration

Attitude towards the sponsor

Attitude towards team members

Influence on the project

Influence in the organization

Influence needed for the good of the project

Influence with other stakeholders

4. Authority Levels For Business Analysis Work

Techniques

1.

General Techniques

Acceptance and Evaluation Criteria Definition

Brainstorming

Interviews

Organization Modeling

Process Modeling

Requirements Workshops

Risk Analysis

Scenarios and Use Cases and User Stories

Scope Modeling

Survey/Questionnaire

2. RACI Matrix (Responsible , Accountable , Consulted , Informed)

3. Stakeholders Map

Stakeholders

1. Domain SME

2. Implementation SME

3. Project Manager

4. Tester

5. Regulator

6. Sponsor


11/80

10

Task 3-

PLAN BA ACTIVITIES


12/80

11

Input

1.


2.

Business Analysis Performance Assessment

3.


4.


Output

Business Analysis Plan(s)


1.

(2.4) Plan BA Communication

2.

(2.5) Plan Requirements Management Process

3.

(2.6) Manage BA Performance

4.

Elicitation

5.

Requirements Management and Communication

6.

Enterprise Analysis

7.

Requirements Analysis

8.

Solution Assessment and Validation

Elements

1.

Geographic Distribution of Stakeholders

Collocated

Dispersed

2.

Type of Project or Initiative

3.

Business Analysis Deliverables

4.

Determine Business Analysis Activities

Unique Number

Activity description

Assumptions Dependencies

Milestones

Techniques

1.

Estimation

2.

Functional Decomposition

3.

Risk Analysis

Stakeholders

1.

Customer, Domain SME, End User, and Supplier

2.

Implementation SME

3.

Operational Support4.

Project Manager

5.

Tester

6.

Sponsor


13/80

12

Task 4-

PLAN BA COMMUNICATION


14/80

13

Input

1.


2.

Business Analysis Plan

3.


4.


Output

Business Analysis Communication Plan


1.

(4.4) Prepare Requirements Package

2.

(4.5) Communicate Requirements

Elements

1.

Geography

2.

Culture

Relationship to time Relationship to task completion

Relationship to contracts

Relationship to formal and informal authority

3.

Project Type

4.

Communication Frequency

5.

Communication Formality

Techniques

1.


Stakeholders

1.

Customer and Supplier2.

Domain SME

3.

End User

4.

Implementation SME

5.

Project Manager

6.

Tester

7.

Regulator

8.

Sponsor


15/80

14

Task 5-

PLAN REQUIREMENTS MANAGEMENT PROCESS


16/80

15

Input

1. Business Analysis Approach

2. Business Analysis Plan(s)

3. Organizational Process Assets

Output

Requirements Management PlanTasks using this Output

1. (2.6) Manage BA Performance

2. (3.2) Conduct Elicitation Activity

3. (4.1) Manage Solution Scope & Requirements

4. (4.2) Manage Requirements Traceability

5. (6.1) Prioritize Requirements

Elements

1. Repository

2. Traceability

3. Select Requirements Attributes

Absolute reference

Author of the requirement

Complexity

Ownership

Priority

Risks

Source of the requirement

Stability

Status

Urgency

4. Requirements Prioritization Process

5. Change Management

Cost and time estimates of change

Benefits and risks of the change

Recommended course of action for change

6. Tailoring the Requirements Management Process

Organizational culture

Stakeholder preferences

Complexity of project, project phase, or product (product, service, or result)

Organizational maturity

Availability of resources

Techniques

1. Decision Analysis

2. Problem Tracking

3.

Risk AnalysisStakeholders

1. Domain SME

2. End User

3. Implementation SME

4. Operational Support

5. Project Manager

6. Tester

7. Sponsor


17/80

16

Task 6-

MANAGE BA PERFORMANCE


18/80

17

Input

1.

Business Analysis Performance Metrics

2.

Business Analysis Plan(s)

3.

Organizational Performance Standards

4.

Requirements Management Plan

Output

1.

Business Analysis Performance Assessment

2.

Business Analysis Process Assets


1.

(2.3) Plan BA Activities

2.

Organization Process Assets

Elements

1.

Performance Measures

2.

Performance Reporting

3.

Preventive And Corrective ActionTechniques

1.

General Techniques

Interviews

Lessons Learned Process.

Metrics and Key Performance Indicators

Problem Tracking

Process Modeling

Root Cause Analysis


2.

Variance Analysis

Stakeholders

1.

Domain SME and End User

2.

Implementation SME, Operational Support, and Tester

3.

Project Manager

4.

Sponsor


19/80

18


20/80

19

Chapter 3 Elicitation


21/80

20

Task 1-

PREPARE FOR ELICITATION


22/80

21

Input

1.

Business Need

2.

Solution Scope and Business Case

3.


Output

1.

Scheduled Resources

2.

Supporting Materials


1.

(3.2) Conduct Elicitation Activity

Elements

1.

Clarify the specific scope for the selected elicitation technique and gathers any necessary supporting

materials.

2.

Schedule all resources (people, facilities, equipment).

3.

Notify appropriate parties of the plan

Techniques

1.

General Techniques

Brainstorming

Document Analysis

Focus Groups

Interface Analysis

Interviews

Observation

Prototyping



Stakeholders

1.

All Stakeholders

2.

Project Manager


23/80

22

Task 2-

CONDUCT ELICITATION ACTIVITY


24/80

23

Input

1.

Business Need

2.


3.


4.

Scheduled Resources

5.

Solution Scope and Business Case6.

Supporting Materials

Output

1.

Elicitation Results


1.

(3.3) Document Elicitation Results

Elements

1.

Tracing requirements

2.

Capturing requirement attributes

3.

MetricsTechniques

1.

Data Dictionary and Glossary

2.

General Techniques

Brainstorming

Document Analysis

Focus Groups

Interface Analysis

Interviews

Observation

Prototyping



Stakeholders

1.

Customer, Domain SME, End User, Supplier and Sponsor

2.

Implementation SME, Operational Support, Project Manager, Supplier and Tester

3.

Regulator


25/80

24

Task 3-

DOCUMENT ELICITATION RESULTS


26/80

25

Input

1.

Elicitation Results

Output

1.

Requirements [Stated]

2.

Stakeholder Concerns


Tasks using Requirements [Stated]

1.

(3.4) Confirm Elicitation Results

2.

(5.1) Define Business Need

3.

(6.1) Prioritize Requirements

4.

(6.4) Specify and Model Requirements

5.

(7.4) Define Transition Requirements

Tasks using Stakeholder Concerns

1.

(3.4) Confirm Elicitation Results

2.

(5.5) Define Business Case

3.

(6.5) Define Assumptions and Constraints

4.

(7.3) Assess Org. Readiness

Elements

Documentation can take a number of forms, including:

Written documents describing the outcomes, such as meeting minute

Visual or audio recordings

Whiteboards (either actual or virtual) where notes are retained until they are transferred to

another medium.

Techniques

1.

General Techniques

Brainstorming

Document Analysis

Focus Groups

Interface Analysis

Interviews

Observation

Problem Tracking

Prototyping



Stakeholders

Business Analyst


27/80

26

Task 4-

CONFIRM ELICITATION RESULTS


28/80

27

Input

1.

Requirements [Stated, Unconfirmed]

2.

Stakeholder Concerns [Unconfirmed]

Output

1.

Requirements [Stated, Confirmed]

2.

Stakeholder Concerns [Confirmed]


Tasks using Requirements [Stated, Confirmed]

1.

(5.1) Define Business Need

2.


3.


4.


Tasks using Stakeholder Concerns[Confirmed]1.


2.

(6.5) Define Assumptions and Constraints

3.


Elements

Refer to the description of the relevant technique for unique aspects of confirming the results of the

Interview and Observation techniques.

Techniques

1.

General Techniques

Interviews Observation

Stakeholders

Any stakeholder who has participated in other elicitation tasks may participate in this task.


29/80

28


30/80


31/80

30

Task 1-

MANAGE SOLUTION SCOPE & REQUIREMENTS


32/80

31

Input 1.


2.

Solution Scope

3.


4.

Stakeholder, Solution, or Transition Requirements [Communicated or Traced]

Output Requirements [Approved] Tasks using this Output

1.

Maintain Requirements For Re-Use

2.

Assess Proposed Solution

3.

Allocate Requirements

Elements 1.

Solution Scope Management

2.

Conflict and Issue Management

3.

Presenting Requirements For Review

4.

Approval

Techniques 1.

General techniques (Problem Tracking)

2.

Baselining

3.

Sign Off

Stakeholders

1.

Domain SME2.

Implementation SME

3.

Project Manager

4.

Sponsor


33/80

32

Task 2-

MANAGE REQUIREMENTS TRACEABILITY


34/80

33

Input 1.

Requirements

2.


Output

Requirements [Traced]

Tasks using this Output 1.

(4.1) Manage Solution Scope and Requirements

Elements 1.

Relationships

Necessity

Effort

Subset

Cover

Value

2.

Impact Analysis3.

Configuration Management System

Techniques 1.

Coverage Matrix

Stakeholders 1.

Implementation SME

2.

Project Manager

3.

Tester


35/80

34

Task 3-

MAINTAIN REQUIREMENTS FOR RE-USE


36/80

35

Input 1.


2.

Requirements

Output

Requirements [Maintained and Reusable]


Enterprise Architecture

2.

Future Initiatives

Elements 1.

Ongoing Requirements

2.

Satisfied Requirements

Techniques None

Stakeholders 1.

Business Analyst

2.

Domain SME

3.

Implementation SME


37/80

36

Task 4-

PREPARE REQUIREMENTS PACKAGE


38/80

37

Input 1.


2.


3.

Requirements

4.

Requirements Structure

Output Requirements Package


(4.5) Communicate Requirements

Elements 1.

Work Product and Deliverables

Meeting agendas and minutes

Interview questions and notes

Facilitation session agendas and notes

Issues log

Work plan, status reports

Presentation slides used during the project

Traceability matrices

2.

Format

Techniques 1.

Requirements Documentation

2.

Requirements for Vendor Selection

Stakeholders 1.

Domain SMEs and End Users

2.

Implementation SMEs3.

Project Managers

4.

Regulators

5.

Sponsors

6.

Testers


39/80

38

Task 5-

COMMUNICATE REQUIREMENTS


40/80

39

Input 1.


2.

Requirements

3.

Requirements Package

Output Communicated Requirements


(4.1) MANAGE Solution Scope and Requirements

Elements 1.

General Communication

Enterprise Analysis Tasks

Elicitation Tasks

Requirements Analysis Tasks

Solution Assessment and Validation Tasks2.

Presentations

Formal Presentation

Informal Presentation

Techniques 1.


2.


Stakeholders 1.

All


41/80

40


42/80

41

Chapter 5 Enterprise Analysis


43/80

42

Task 1-

DEFINE BUSINESS NEED


44/80

43

Input 1.

Business Goals and Objectives

2.


Output Business Need


(2.1) Plan Business Analysis Approach

2.

(2.2) Conduct Stakeholder Analysis

3.

(3.1) Prepare for Elicitation

4.

(3.2)Conduct Elicitation Activity

5.

(5.2) Assess Capability Gaps

6.

(5.3) Determine Solution Approach

7.

(5.4) Define Solution Scope

8.


9.

(6.1) Prioritize Requirements10.

(6.5) Verify Requirements

11.

Requirements Mgt. and Communication

Elements 1.

Business Goals and Objectives

Specific

Measurable

Achievable

Relevant

Time-bounded

2.

Business Problem or Opportunity

3.

Desired Outcome

Techniques 1.

Benchmarking

2.

Brainstorming

3.

Business Rules Analysis

4.

Focus Groups

5.


6.

Root Cause Analysis

Stakeholders 1.

Customer or Supplier

2.

Domain SME and End User

3.

Implementation SME

4.

Regulator

5.

Sponsor


45/80

44

Task 2-

ASSESS CAPABILITY GAPS


46/80

45

Input 1.

Business Need

2.


3.

Solution Performance Assessment

Output Required Capabilities


(5.3) Determine Solution Approach

2.


3.


4.


5.


Elements 1.

Current Capability Analysis

2.

Assessment of New Capability Requirements3.

Assumptions

Techniques 1.

Document Analysis

2.

SWOT Analysis

Stakeholders 1.

Customer and Supplier

2.

Domain SME, End User, Implementation SME, and Sponsor


47/80

46

Task 3-

DETERMINE SOLUTION APPROACH


48/80


49/80

48

Task 4-

DEFINE SOLUTION SCOPE


50/80

49

Input 1.

Assumptions and Constraints

2.

Business Need

3.

Required Capabilities

4.

Solution Approach

Output Solution Scope



2.


3.


4.


5.

(6.2) Organize Requirements

6.


7.

(7.2) Allocate Requirements

8.


9.


Elements 1.

Solution Scope Definition

2.

Implementation Approach

3.

Dependencies

Techniques 1.

General Techniques


Interface Analysis Scope Modeling

User Stories

2.

Problem or Vision Statement

Stakeholders 1.

Domain SME

2.

Implementation SME

3.

Project Manager

4.

Sponsor


51/80

50

Task 5-

DEFINE BUSINESS CASE


52/80

51

Input 1.


2.

Business Need

3.

Solution Scope

4.


Output Business Case



2.


3.


4.


5.

(6.2) Organize Requirements

6.


7.


8.


9.


Elements 1.

Benefits

2.

Costs

3.

Risk Assessment

4.

Results Measurement

Techniques 1.

Decision Analysis

2.

Estimation3.


4.

Risk Analysis

5.

SWOT Analysis

6.

Vendor Assessment

Stakeholders 1.

Sponsor

2.

Domain SME

3.

Implementation SME

4.

Project Manager


53/80

52


54/80

53

Chapter 6 Requirements Analysis


55/80

54

Task 1-

PRIORITIZE REQUIREMENTS


56/80

55

Input

1. Business Case

2.

Business Need

3. Requirements

4. Requirements Management Plan

5.


Output

Requirements [Prioritized]


1. (7.1) Assess Proposed Solution

2.


3. (7.5) Validate Solution

4. Requirements Mgt. and Communication

Elements

1. Basis for Prioritization

Business Value

Business or Technical Risk

Implementation Difficulty

Likelihood of Success

Regulatory or Policy Compliance

Relationship to Other Requirements

Stakeholder Agreement

Urgency

2. Challenges

Non-negotiable Demands

Unrealistic Tradeoffs

Techniques

1. General Techniques

Decision Analysis

Risk Analysis

2.

MoSCoW Analysis

Must

Should

Could

Won’t

3. Time boxing/ Budgeting

All In

All Out

Selective

4.

Voting

Stakeholders

1.

Domain SME

2.

Implementation SME

3. Project Manager

4. Sponsor


57/80

56

Task 2-

ORGANIZE REQUIREMENTS


58/80

57

Input

1.


2.


3.

Solution Scope

Output Requirements Structure


1.

(4.4) Prepare Requirements Package

2.


Elements

1.

Levels of Abstraction

2.

Model Selection

User Classes, Profiles, or Roles

Concepts and Relationships

Events

Processes.

Rules

Techniques

1.


2.

Data Flow Diagrams

3.

Data Modeling

4.


5.


6.

Process Modeling

7.

Scenarios and Use Cases8.

Scope Modeling

9.

User Stories

Stakeholders

1.

Domain SME, End User, Implementation SME, and Sponsor

2.

Project Manager


59/80

58

Task 3-

SPECIFY AND MODEL REQUIREMENTS


60/80

59

Input

1.


2.

Requirements Structure

Output

Requirements [Analyzed]


1.


2.


3.


Elements

1.

Text

2.

Matrix Documentation

3.

Models

4.

Capture Requirements Attributes5.

Improvement Opportunities

Automate Or Simplify The Work People Perform

Improve Access To Information

Reduce Complexity Of Interfaces

Increase Consistency Of Behavior

Eliminate Redundancy

Techniques

1.

General Techniques



Data Dictionary and Glossary

Data Flow Diagrams

Data Modeling


Interface Analysis


Non-functional Requirements Analysis


Process Modeling

Prototyping

Scenarios and Use Cases Sequence Diagrams

State Diagrams

User Stories

Stakeholders

Any Stakeholder


61/80

60

Task 4-

DEFINE ASSUMPTIONS AND CONSTRAINTS


62/80

61

Input

1.


Output



1.


2.


3.

(7.1) Assess Proposed Solution

4.


Elements

1.

Assumptions

2.

Business Constraints

3.

Technical Constraints

Techniques

1.

Problem Tracking

2.

Risk Analysis

Stakeholders

1.

Implementation SME

2.

Project Manager

3.

All Stakeholders


63/80

62

Task 5-

VERIFY REQUIREMENTS


64/80

63

Input

1.

Requirements [Any Except Stated]

Output

Requirements [Verified]


1.

(6.6) Validate Requirements

2.


Elements

1.

Characteristics of Requirements Quality

Cohesive

Complete

Consistent

Correct

Feasible

Modifiable

Unambiguous

Testable

2.

Verification Activities

Techniques

1.

General Techniques


Problem Tracking


2.

Checklists

Stakeholders

All Stakeholders


65/80

64

Task 6-

VALIDATE REQUIREMENTS


66/80

65

Input

1.

Business Case

2.

Stakeholder, Solution, or Transition Requirements [Verified]

Output

Requirements [Validated]


1.

(7.5) Validate Solution

2.


Elements

1.

Identify Assumptions

2.

Define Measurable Evaluation Criteria

3.

Determine Business Value

4.

Determine Dependencies for Benefits Realization

5.

Evaluate Alignment with Business Case and Opportunity Cost

Techniques

1.


2.


3.

Prototyping

4.

Risk Analysis

5.


Stakeholders

All Stakeholders


67/80

66


68/80

67

Chapter 7 Solution Assessment and Validation


69/80

68

Task 1-

ASSESS PROPOSED SOLUTION


70/80

69

Input

1.


2.

Requirements [Prioritized and Approved]

3.

Solution Option(s)

Output

Assessment of Proposed Solution


1.

Solution Selection or Design

Elements

1.

Ranking of Solution Options

2.

Identification of Additional Potential Capabilities

Techniques

1.


2.

Decision Analysis3.

Vendor Assessment

Stakeholders

1.

Domain SME

2.

Implementation SME

3.

Operational Support

4.

Project Manager

5.

Supplier

6.

Sponsor


71/80

70

Task 2-

ALLOCATE REQUIREMENTS


72/80

71

Input

1.

Requirements [Prioritized and Approved]

2.

Solution [Designed]

3.

Solution Scope

Output

Requirements [Allocated]


1.


2.

Solution Selection or Design

Elements

1.

Solution Components

Available resources

Constraints on the solution

Dependencies between requirements

2.

Release Planning

Techniques

1.


2.


3.

Decision Analysis

4.


5.

Process Modeling

6.

Scenarios and Use Cases

Stakeholders

1.

Customers and Suppliers

2.

Domain SME3.

End User

4.

Implementation SME

5.

Operational Support

6.

Project Manager

7.

Tester

8.

Sponsor


73/80

72

Task 3-

ASSESS ORGANIZATION READINESS


74/80

73

Input

1.


2.

Solution Scope

3.

Solution [Designed]

4.


Output

Organizational Readiness Assessment


1.


Elements

1.

Cultural Assessment

2.

Operational or Technical Assessment

3.

Stakeholder Impact Analysis

Functions

Location Tasks

Concerns

Techniques

1.

General Techniques


Data Flow Diagrams and Process Models

Focus Groups , Interviews and Survey/Questionnaire


Problem Tracking

Risk Analysis

SWOT Analysis

2.

Force Field Analysis

Stakeholders

1.

Domain SME

2.

Implementation SME

3.

Operational Support

4.

Project Manager

5.

Sponsor


75/80

74

Task 4-

DEFINE TRANSITION REQUIREMENTS


76/80

75

Input

1.

Organizational Readiness Assessment

2.


3.

Solution [Deployed]

4.

Solution [Designed]

Output

Transition Requirements


1.


2.


3.


Elements

1.

Data

2.

Ongoing Work

3.

Organizational Change

Techniques

1.


2.

Data Flow Diagrams , Process Modeling and Organization Modeling

3.

Data Modeling

Stakeholders

1.

Customer

2.

Domain SME

3.

End User

4.

Implementation SME

5.

Operational Support6.

Project Manager

7.

Regulator

8.

Tester

9.

Sponsor


77/80

76

Task 5-

VALIDATE SOLUTION


78/80

77

Input

1.

Solution [Constructed]

2.

Requirements [Prioritized and Validated]

Output

1.

Identified Defects2.

Mitigating Actions

3.

Solution Validation Assessment


1.

(7.6) Evaluate Solution Performance

2.

Solution Implementation

Elements

1.

Investigate Defective Solution Outputs

2.

Assess Defects and Issues

Techniques

1.


2.

Root Cause Analysis

3.

Problem Tracking

Stakeholders

1.

Domain SME

2.

End User

3.

Implementation SME

4.

Operational Support

5.

Project Manager

6.

Tester

7.

Regulator8.

Sponsor


79/80

78

Task 6-

EVALUATE SOLUTION PERFORMANCE


80/80

Input

1.

Business Requirements

2.

Identified Defects

3.

Solution Performance Metrics

4.

Solution [Deployed]

Output

1.

Solution Performance Assessment


1.

(5.2) Assess Capability Gaps

Elements

1.

Understand Value Delivered By Solution

2.

Validate Solution Metrics

3.

Solution Replacement or Elimination

Ongoing Cost versus Initial Investment

Opportunity Cost Necessity

Sunk Cost

Techniques

1.

Decision Analysis

2.

Focus Groups

3.

Observation

4.


Stakeholders

1.

Customer, Domain SME, and Supplier.

2.

End User.3.

Operational Support

4.

Regulator

5.

Sponsor

cbap babok diagrams

Documents