Scribd
Upload
70 views2 pages

Cbap Class Notes

This document discusses different business analysis techniques including work breakdown structure, high level and low level requirements, process modeling, scope modeling, context diagrams, communication approaches, and feasibility analysis.

Uploaded by

vaibhav26.vv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
70 views2 pages

Cbap Class Notes

This document discusses different business analysis techniques including work breakdown structure, high level and low level requirements, process modeling, scope modeling, context diagrams, communication approaches, and feasibility analysis.

Uploaded by

vaibhav26.vv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

https://drive.google.

com/drive/u/2/folders/1fEEJsa3CG3m8zz006Ofn9C8mTbetaHbO

https://www.iiba.org/certification/iiba-certifications/cbap/#get-started-intro
https://www.iiba.org/certification/exam-information/#next-steps

[email protected]

This element is based on work


break down structure principles i.e.,
breaking down the complex requirements
into granular or fragment level.

1. This helps to perform analysis in a more


structured and organised manner.
2. This helps to perform tracking,
monitoring and evaluation in a more
effective manner.
3. This also helps in task allocation and
team management.
4. Since, requirements are captured at
more granular level, it helps to avoid scope
creep and define in-scope requirements.

24-01-2023

Low level requirement

High level requirement

--------------------------

Summary, overview or
synopsis for the given set of
requirements can be classified as
high level requirements.
High level requirement need more
analysis. In-depth on HLR will
result into granular requirements
also known as LLR.

Process Modelling:
Foundation Level: Here, activity diagram needs to be captured. This diagram will
completely focus on sequential set of events and would help to create a flowchart.
This will just capture end to end process.
Advanced level: Here Swimlane needs to be captured. This diagram not only captures
end to end flow but also helps to perform impact analysis. This diagram has several
lanes that depict connected processes or the systems.
This helps to ensure that new process flow is not causing any adverse impact to the
parallelly running sub-process.

Scope Modeling: This helps to sketch the boundaries for any given requirement. It
helps to come up with:
1. In-scope requirements: Requirements components that lie within the
boundaries.
2. Out of Scope requirements: Components outside the boundaries.
These components will not be part of scope and will remain intact or untouched.

Context Diagram:
This diagram finds its relevance when requirements are related data analysis and
transformation.
This diagram helps in data transformation i.e. removes redundant and duplicate info

from the raw data and helps to store useful info in the document repository.

30-01-2023

Communication of business analysis information is part of BA deliverables. BA


deliverables have complete dependency
on the business analysis approach.
Business Analysis approach can be
1. Predictive or
2. Adaptive.
Case 1 Predictive: Here, comprehensive document like BRDs and formal ways of
communication through proper
communication channel along with involvement of decision makers is preferred and is
part of protocols.
Case 2 Adaptive: Here, lightweight documentation and informal ways of communication
have now replaced the
traditional ways of communication. Here, email exchange, presentation or even
verbal communication through
workshop may occur.

01-02-2023

Feasibility Analysis:
Analysis to ensure the future state defined for any solution/product is in line
with given technology and
it fits in given requirement architecture. Technical feasibility will help to
ensure that the solution or
the future state proposed by BA is technically feasible to implement or not.
Feasibility analysis is about applying system thinking and gauge/monitor the
capabilities considering the
technology related constraints.

Drive Link

https://drive.google.com/drive/u/2/folders/1fEEJsa3CG3m8zz006Ofn9C8mTbetaHbO

Raci Matrix
RACI Matrix: Responsible Accountable Consulted Informed Business Scenario:
Requirement Gathering and
Documentation Responsibility: BA must CRE here. Accountable: Project Manager
Consulting: 1. If it is about
domain related issues: DSME 2. If it is about technical aspects: ISME 3. If it is
about the test strategy :
Testers Informed: Rest other stakeholders .

You might also like