Types of requirements as per BABOK

Types of requirements as per BABOK v3

In this article, we are going to discuss about the types of requirements as per BABOK v3. Business analysis body of knowledge (BABOK) guide is published by IIBA.
BABOK guide is also the reference book for all the 4 levels of business analyst certification – ECBA, CCBA, CBAP ad CBATL. If you are looking to go for a business analyst certification, you would like to know – which is the right certification for you?

Which business analyst certification is right for me?


What are the types of requirements as per BABOK

BABOK v3 has described 4 types of requirements as shown below:

  • Business Requirements
  • Stakeholders Requirements
  • Solution Requirements
  • Transition Requirements

Business requirements represent business objectives, stated by the customer. Stakeholders requirements represent the requirements of individual stakeholders. Features and characteristics expected of developed software application represent solution requirements. The transition requirements are the requirements needed to implement the software application successfully. Let’s look at these types of requirements in details.

Business Requirements

As per BABOK guide, the business requirement is defined as:

Statements of goals, objectives, and outcomes that describe why a change has been initiated. They can apply to the whole of an enterprise, a business area, or a specific initiative.

Every software application, conceptualized and initiated by an organization is meant to achieve a business goal like automating customer relationship management, sales and marketing etc. Business requirements are typically high level business goals.

An example of business requirement

A typical business requirement example is as shown for a customer relationship management system.
We would like to automate our customer relationship management system so that we can offer better customer services to our existing customers and can also cross-sell and up-sell to improve revenue.

Stakeholder Requirements

Stakeholder requirements as per BABOK guide:

Describe the needs of stakeholders that must be met in order to achieve the business requirements.

Stakeholders requirements are more individualistic. They may serve as a bridge between business and solution requirements. Stakeholders may specify their requirements specific to the project as per their perception.

Example of stakeholder requirements

The customer service department head may ask for implementing the project in a phase wise manner.
The customer service manager may ask for a mechanism to monitor the response time for each and every customer support request on a daily basis in order to improve the response time.

Solution Requirements

These requirements refer to the expected features and behaviour of the system. Solution requirements as per BABOK guide:

Describe the capabilities and qualities of a solution that meets the stakeholder requirements. They provide the appropriate level of detail to allow for the development and implementation of the solution.

Solution requirements are the detailed set of requirements. These requirements will be used by the development team to develop the system.
Solution requirements are of two types:

  • Functional requirements: Functional requirements are the expected features of the system. Features like registering a user, making an online purchase etc.
  • Non-Functional requirements: Non-functional requirements are the requirements which are related to the behaviour of the system. Every page should load in 5 seconds is an example of non-functional requirement.

One of the important part of requirements gathering activity for every business analyst is to write the requirements well. Well written requirements should follow guidelines. We have discussed these guidelines in another post as shown below:

Transition Requirements

Transition requirements refer to the requirements to enable successful implementation of a project. As per BABOK,

Describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature.

Example of transition requirements

Transition requirements are specific period requirements. Examples of transition requirements are as follows:

  • The users must be trained to be able to use the system effectively
  • Previous years data must be migrated to the new system to generate comparative report

A small video explaining the types of requirements is as shown below:

Leave a Reply

Your email address will not be published. Required fields are marked *