2.

1
Plan Business
Analysis Approach
2.2
Conduct
Stakeholder
Analysis
2.3
Plan BA Activities
2.4
Plan BA
Communication
2.5
Plan Rqmnt
Management
Process
2.6
Manage BA
Performance
3.1
Prepare for
Elicitation
3.2
Conduct Elicitation
Activity
3.3
Document
Elicitation Results
3.4
ConfirmElicitation
Results
4.1
Manage Solution
Scope
4.2
Manage
Requirement
Traceability
4.3
Maintain
Requirements for
Re-Use
4.4
Prepare
Requirements
Package
4.5
Communicate
Requirements
5.1
Define Business
Need
5.2
Assess Capability
Gaps
5.3
Determine
Solutions
Approach
5.4
Define Solution
Scope
5.5
Define Business
Case
6.1
Prioritise
Requirements
6.2
Organise
Requirements
6.3
Specify and Model
Requirements
6.4
Define
Assumptions and
Constraints
6.5
Verify Quality of
Requirements
6.6
Validate Rqmnts
Meet Stakeholders
Needs
7.1
Assess Proposed
Solution
7.2
Allocate
Requirements
7.3
Assess
Organaisation
Readiness
7.4
Define Transition
Requirements 7.5
Validate Solution
7.6
Evaluate Solution
Performance
BA Mentor
BA Management
Enterprise
Archi tect
Sol ution
Suppli er
(3) Business
Analysis
Approach
(11)
Business
Need
(14) Expert
J udgement
Organi sation Fi le
Reposi tory (18)
Organisation
al Process
Assets
(13)
Enterprise
Architecture
(44)
Stakeholder
list, roles &
responsibilities
(5) BA
Performance
Assessment
?????
Collect BA
Performance
Metrics
(6) BA
Performan
ce Metrics
(4) BA
Communic
ationPlan
(7) BA
Plan
(31) Rqmnts
Management
Plan
(16)
Organisational
Perfromance
Standards
(8) BA
Process
Assets
(9)
Business
Case (34)
Scheduled
Resources
(46)
Supporting
Materials
(40)
Solution
Scope
(12)
Elicitation
Results
(21) Rqmnts
(Stated,
Unconfirmed)
(42)
Stakeholder
Concerns
(Unconfirmed)
(22) Rqmnts
(Stated,
Confirmed)
(43)
Stakeholder
Concerns
(Confirmed)
(10) Business
Goals &
Objectives
Management
(20)
Required
Capabilities
(38) Solution
Performance
Assessment
(2)
Assumptions
&Constraints
(23) Rqmnts
(Traced)
(24) Rqmnts
(Communicat
ed)
(32) Rqmnts
Package
(29) Rqmnts
(All ocated)
(25) Rqmnts
(Approved)
(45)
Stakeholder or
Solution
Rqmnts
(47) Transition
Rqmnts
(33) Rqmnts
Structure
(30) Rqmnts
(Mai ntained &
Reusabl e)
(26) Rqmnts
Pri ori ti sed
(27) Rqmnts
(Veri fied
Qual ity of
Model s)
(28) Rqmnts
(Val i dated by
Stakehol der)
(37) Solution
Options
(1)
Assessment of
Proposed
Solution
(35) Solution
(Constructed,
deployed or
designed)
(19)
Organisational
Readiness
Assessment
(15) Identified
Defects
(16) Mitigating
Actions
(41) Solution
Validation
Assessment
(39) Solution
Performance
Metrics
IIBA BABOK v2 Level 2 Process Data Flows v0_02 (DRAFT)
(36)
Solution
Approach
IT System Test &
Operati ons???
Development &
Impl ementati on
Team???
Key
(ID)
Document
Name
Output
from
Input
to
(ID)
Unused
Output
from
A version of
Requirements
Document
BABOK L2 Ref
BABOK v2 Level 2
Process Name
External (Non
BA Process)
Source of
Document
Has input of Doc (18)
Organisational
Templates etc
???
BABOK Level 1 s2 =BA Planning&Monitoring
BABOK Level 1 s3 =Elicitation
BABOK Level 1 s4 =Requirements Management &Comms
BABOK Level 1 s5 =Enterprise Analysis
BABOK Level 1 s6 =Requirement Analysis
BABOK Level 1 s7 =Solution Assessment &Validation
4.4
Requirements Package can
have as input any Rqmnts
Version
This process (4.4) also uses
document (18) templates
2- BA Pl anni ng & Monitoring
2-1 PlanBusiness Analysis Approach
2-2 Conduct Stakeholder Analysis
2-3 PlanBA Activities
2-4 PlanBA Communication
2-5 PlanRequirements Management Process
2-6 Manage BA Performance
3- El i citation
3-1 Prepare for Elicitation
3-2 Conduct ElicitationActivity
3-3 Document Elicitation Results
3-4 ConfirmElicitation Results
5- Enterpri se Analysi s
5-1 Define Business Need
5-2 Assess Capability Gaps
5-3 Determine Solutions Approach
5-4 Define SolutionScope
5-5 Define Business Case
7- Soluti on Assessment & Val idati on
7-1 Assess Proposed Solution
7-2 Allocate Requirements
7-3 Assess Organisational Readiness
7-4 Define Transition Requirements
7-5 Validate Solution
7-6 Evaluate Solution Performance
6- Requi rements Analysis
6-1 Prioritise Requirements
6-2 Organise Requirements
6-3 Specify and Model Requirements
6-4 Define Assumptions and Constraints
6-5 Verify Requirements
6-6 Validate Requirements
4- Requi rements Management & Communi cation
4-1 Manage Solution Scope
4-2 Manage Requirements Traceability
4-3 MaintainRequirements for Re-use
4-4 Prepare Requirements Package (41,42)
4-5 Communicate Requirements
So many Processes
use this as input that
diagramwould be cluttered,
so highlighted process instead
Reverse Loop to FollowUp
Redundant Link???
Sol ution
Sel ection or
Design
Sol ution
Impl ementation