One of the best parts in BABOK is its requirements classification schema. BABOK describes four types of requirements and that’s very useful in understanding the evolution of requirements in business analysis practice.
In this article, I am going to discuss about BABOK requirements classification schema with the help of examples.
Want to know what is inside BABOK? Read this introduction to BABOK version 3
What are the types of requirements as per BABOK
BABOK 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.
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, conceptualised and initiated by an organisation is meant to achieve a business goal like improving customer service, increasing revenue by 10% every month etc.
Business requirements are typically high level business goals and objectives.
An example of business requirement
A typical business requirement example is shown for a large private sector bank could be as shown below:
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’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 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 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).
Example of stakeholder requirements
In our Bank’s customer service management project, one of the stakeholders may state the following 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.
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 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 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.
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.
Transition requirements are short period requirements. Once these requirements are completed, these no longer exist.
Example of transition 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:
Techcanvass offers IT certification courses for professionals. We are an IIBA endorsed education provider (EEP), iSQI ATP (for Certified Agile Business Analyst Training) as well as Agile Testing alliance partner for CP-SAT certification training in Selenium.
Our ECBA Certification training program is a well structured course, which not only helps you in becoming a Business Analyst but also helps you in getting prepared for ECBA Certification.