Business Analysis

Fundamentals
Key Concepts to Learn before diving further
 Knowledge Areas
BABOK has divided entire business analysis in six knowledge areas, we will use
these as template for this course; 

1 Business Analysis Planning and Monitoring 

2 Elicitation & Collaboration 

3 Requirements Life Cycle Management 

4 Strategy Analysis 

5 Requirement Analysis & Design Definition (RADD) 

6 Solution Evaluation
BACCM or business analysis key concepts model is a conceptual framework for
the field of business analysis. It kind of defines the field of business analysis and
provide framework which is used to perform business analysis. It defines six
terms for the field of business analysis and these definitions remain same across
domain, organization or methodology. 

These terminologies are; 

1 Change 
2 Need 
3 Solution 
4 Stakeholder 
5 Value 
6 Context 
REQUIREMENT CLASSIFICATION SCHEMA

Types of Requirements;

Business Requirements- these are requirements or changes which a business

user need. These are business goals or changes that describe why a change is
needed. In the example of Typewriter to Computer Project, if the change was
initiated to meet business objectives and it was initiated at company level or
Team level by end users to satisfy company goal, it is business requirement. 
Stakeholders Requirements – stakeholder’s requirements are like bridge
between business & solution requirements. These requirements are the changes
required by stakeholders and features which a solution must have to achieve
business requirements. In the example of Typewriter to Computer change,
stakeholders are management, implementation team, user groups and some
other group which is directly or indirectly impacted by the change.

Now stakeholder may not directly be concerned about this change, but they may
put a condition to implement it. this condition will be in the form of requirements
like if we need to bring in computers, we need to bring the computer desk and
electric sockets to plugin computers.  

So essentially stakeholder requirements are requirements given by stakeholders

to meet their need. 
STAKEHOLDERS 
 
As you can guess, anybody and everybody who is involved in a project, is a
Stakeholder. These are individual or groups which are being impacted by the
project. I have used generic list of stakeholders from the BABOK guide, please
note it is generic and shouldn’t be treated as formal or complete, every project
will have its own list of stakeholders, this list is for example only; 
• Business analyst 
• Customer 
• Domain subject matter expert 
• End user 
• Implementation subject matter expert 
• Operational support 
• Project manager 
• Regulator 
• Sponsor 
• Supplier 
• Tester
Solution Requirement – these are requirements which a solution must have to
satisfy the stakeholders requirements. Solution requirements are one which are
finally designed & developed, so solution requirements should have enough design
details so that development team can implement them. Solution requirements are
further classified into 2 categories; 

• Functional requirements- these are those requirements which describes the

functionality aspect of the requirement. For example, a site having a button and
what that button should do when clicked. These deals with the functional
behavior and information. 
• Non-Functional Requirements or Quality of service requirements – these are
requirements which are not directly related to behavior or functional properties
but rather defines the condition under which the solution must behave. 

So, solution requirements are those requirements which a solution must have to
meet the solution standard or need. Continuing with the example of Typewriter to
Computer, computer is the solution and its feature are solution requirements. So,
before arriving on the conclusion that computer is the solution, we needed to look at
its features to know if it possesses enough functionalities to satisfy business
requirement.
Transition Requirement- transition requirements are the requirements which are
required to support transition from current state to future and are not required
once the future state is achieved. This is to support the transition and if not
needed, there may not be any transition requirement.

In case of typewriter to computer project, a workaround is developed which is

used while computers are installed, this workaround is transition requirement and
its role will end as soon as computers are implemented.