Requirements Classification Schema

Requirements Classification Schema

Requirements Classification Schema (BABOK)  describe four important requirements that is very useful in understanding the evolution of requirements in business practice.

This Blog helps give a clear understanding on BABOK requirements and schema


BABOK has described four types of requirements as discussed below

  • Business Requirements
  • Stakeholder Requirements
  • Solution Requirements
  • Transition Requirements

Business Requirements represent business objectives, Stated by a customer

Stakeholder Requirements represent the requirements of individual Stakeholders.

Features and Characteristics expected of the developed software application represent solution Requirement.

The Transition Requirements are requirements that are needed to implement the software successfully.

Let’s look at the types of requirements in detail.

Business Requirements.


As per BABOK the business requirement can be defined as Statements of goals, objectives and outcomes that describe why a change has been initiated. They can apply to a 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 improving Customer Service, increasing revenue by 10% every month etc.

Business Requirements are typically high-level goals and objectives

One of the best Examples of Business requirement:

We would like to automate our customer relationship management system so that we can offer better customer services so that the customer response time improves by 70% in the next 6 months.

It is important that business requirements objectively state the objectives of what the Business needs

Business requirements takes needs as input to describe requirements. Business Requirements does not include details about screens or business Rules

It’s important that business requirements objectively state the objectives of what does the business need?

Business requirement takes needs as input to describe the business requirements. Business requirements does not include details about screens or business rules.

Stakeholder Requirements.

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

Stakeholders requirements are more individualistic. They serve as a bridge between business and solution requirements.

Stakeholders may specify their requirements specific to the project as per their needs (the division or business unit they represent).

One of the best Examples of Stakeholders requirement:

We would like to have 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. The report should be generated daily, monthly or on on-demand basis.

A comparative report will be needed to see the trend.


Solution Requirements.

Solution requirements refer to expected features and behavior 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 represent the requirements of a solution. 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 behavior of the system. Every page should load in 5 seconds is an example of non-functional requirement.

One of the most important part of requirement gathering is for every business analyst is to draft down the perfect requirements.


Transition Requirements:

Transition requirements refer to the requirements to enable successful implementation of a project.


As per BABOK, Transition Requirements 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.

i.e.: They are short period requirements and once these requirements are completed, they no longer exist.

One of the best Examples of Business requirement:

  • 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











About Satya Sai Srinivas Kondamuri

Check Also

Explain SRS and Its Key Elements

Introduction: Clear and concise communication is the cornerstone of successful software development projects. Software Requirement …

Leave a Reply

Watch Dragon ball super