The document contains information about various business analysis knowledge areas and processes presented on single pages, including: 1. Business analysis planning and monitoring with key performance indicators. 2. Enterprise analysis with components like business needs, capability gaps, and solution scope. 3. Requirements elicitation process and template. 4. Requirements analysis template with components like prioritizing, organizing, specifying, and verifying requirements. 5. Requirements management and communication process and template.

1. iiBA Knowledge Area Visualisation

2. 1. Plan Business
Analysis Approach
2. Conduct
Stakeholder
Analysis
3. Plan BA
Activities
4. Plan BA
Communications
5. Plan
Requirements
Management
Process
6. Manage BA
Performance
Business Analysis Planning and Monitoring on a Page
Business Analysis
Performance
Complete deliverables
according to plan
Complete 99% must have and
should solution requirements
specifications on time as planned
95% Solution verification rated 4
and above for each requirement
catalogue, as per standards
Solution realises planned
outcomes
100% traceability to all process
improvement and business
outcomes (backward chain)
Gaps in business outcomes
identified and approved (forward
chain)
Role / Title Name Reporting Communication Context & Objective
Role / Title
Name
Reporting
Communication Context & Objective

3. 1. The business
Need
2. Capability Gaps
3. Solution Scope
4. solution
Approach
5. A Business
Case
Enterprise Analysis on a Page
Evaluate Options 0, 1, 2 & 3…
1. Realises Objective
2. Resolves Problem
3. Fulfils Product
4. Automates Process
5. Stores Data
6. Used by Organisation
Do Nothing
Cost Benefit
 Business objectives realised
= improvement $
 Obstacles eliminated
= savings $
Analysis
 Return on Investment
 Net Present Value
 Internal Rate of Return
Dimensions of Scope…
Item Description
Why Statement
States what is the problem and why the project must be undertaken in a sentence, e.g. The
Question Every Project Team Should Answer - MIT Sloan Management Review.
Business
Objectives
Sets the direction of the project, identifying the desired outcome of the project.
Obstacles
Identifies the business pain points that need to be addressed. How the pain points affect
the business, can be illustrated on the context diagram or business process model.
Context Diagram
Identifies external agents (organisation, system or process) with which the system must
interact. Any change to an external agent is outside the scope of the system.
Scope Statement A short paragraph to succinctly describes and communicates the project scope.
Scope Perspective
Identifies the processes, data, organisation, information flows and existing systems that are
included in the scope of the project. The health and priority of each dimension describes
the urgency of the change and provides the basis for partitioning requirements into project
releases.
Scope Inclusions
Identifies specific agreed items within the scope of the project that do not neatly fit with the
scope dimensions.
Scope Exclusions Identifies specific agreed items that are excluded from the scope of the system.

4. 1. Prepare for Elicitation
2. Conduct Elicitation
Activity
3. Document Elicitation
Results
4. Confirm Elicitation
Results
Elicitation on a Page

5. Criterion 5: Conformance to Standards
5  All the Use Case models and specifications conform to the naming and modelling standards
covering Use Case business rules, and data requirements.
4  Most of the Use Case models and specifications conform to the standards specified.
3  Over half the Use Case models and specifications conform to the standards specified.
2  Some of the Use Case models and specifications conform to the standards specified.
1  None of the Use Case models and specifications conform to the standards specified.
Verify Workshop
Scope
Develop Future
Business
Process
Determine Data
Requirements
Specify
Use Case
Requirements
Write up
Specifications
Verify & Validate
Outcome
1. Prioritise
Requirements
2. Organise
Requirements
3. Specify &
Model
Requirements
4. Define
Assumptions &
Constraints
5. Verify
Requirements
6. Validate
Requirements
Search Product
Catalogue
Requirements Analysis on a Page
Focus
Question
Search Product OfferingSearch Product Offering
File Edit Search Help ViewTool
Classify SpecificationDescribe Search
Fatigue* Search
Fatigue design assessment Add to Product Package
Fatigue Design Assessment is applied in addition to normal plan approval to obtain the necessary confidence level in fatigue performance
in the configuration and details of the structure. This enables identification of critical areas prone to fatigue at an early stage in the design
process, permitting just in time modification. It also helps identify critical Locations, in addition to those identified in the structural
design assessment, where construction needs to be more closely supervised, and attention paid during in-service surveys.
FDA Software Add to Product Package
The Fatigue Design Assessment (FDA) procedure provides a multi-level evaluation of the fatigue performance of structural details.
Whether you are a designer, builder, repairer or ship operator, you will find FDA to be of great benefit for both initial design and in-
service maintenance - helping to ensure fatigue durability at critical locations. Experience gained from FDA, together with the extensive
research programmes.
Structural Design Assessment Add to Product Package
CA Mining & quarrying of energy
CA11.1 Extraction of Crude Petrole
CA11.2 Service incidental to O&G ext
Family:Industry Sector Lifecycle StageAsset Type:
Certification
Classification
Consultancy
Floating Offshore
FPSO
FSO
Technical Search Options
Concept
Design
Build
Customer Search Options
Enterprise Analysis Scope:
Product Development Process
Workshop Workgroup

6. 1. Manage Solution
Requirements Scope
2. Manage
Requirements
Traceability
3. Maintain
Requirements
for Re-use
4. Prepare
Requirements
Package
5. Communicate
Requirements
Requirements Management & Communication on a Page
Process - Activity
Use Case
/User Story
Data Model
Business Objective - Measure uses
Business Logic
Modules
e-User Guides
Data Access Modules
/ Database
Presentation
Modules
Pain Points
Pattern
General ...  Traceability  … Specific
Product Development Package
− Design Product
+ Search Product Catalogue
+ Specify Product Offering
+ Find Product Usage
− Develop Product
+ Specify Package Composition
+ Publish Product

7. 1. Assess
Proposed
Solution
2. Allocate
Requirements
3. Assess
Organisation
Readiness
4. Define
Transition
Requirements
5. Validate
Solution
6. Evaluate
Solution
Performance
Solution Assessment & Validation on a Page
Identify Market Needs Promote ProductSunny
Scenario
Design Product Develop Product Launch Product
Product Manager
Campaign
Management
Finance
Product Master
Business Objective Metrics Average VolumeMore, quicker at less cost
CMS
+
+