Use the information gathered using BACCM to identify the project requirements, and classify them accordingly. This is how you will be able to trace any requirements regardless of what stage in the project you are in.
The Requirements Classification Schema in BABOK v3 organizes requirements into a hierarchy that can indeed be depicted as a pyramid.
This pyramid helps visualize the relationships and dependencies between different types of requirements, from high-level business needs down to specific, detailed requirements. Here's a breakdown of the schema:
- Business Requirements: These are at the top of the pyramid and represent the high-level needs of the organization, including goals and objectives. They provide the rationale for why a project is being undertaken.
- Stakeholder Requirements: These capture the needs and expectations of the stakeholders. They bridge the gap between business requirements and solution requirements.
- Solution Requirements: These are divided into two subcategories:
- Functional Requirements: Describe the capabilities the solution must have to meet the stakeholder and business requirements.
- Non-functional Requirements: Define the quality attributes, design, and constraints the solution must adhere to, such as performance, usability, and reliability.
- Transition Requirements: These requirements describe the conditions that must be met to transition from the current state to the future state. They are often temporary and help ensure a smooth implementation of the solution.
| Classification |
What information to elicit |
BACCM Alignment |
| Business Requirements |
- Business Goal/s |
|
-
Business Objective/s
-
Epic in Agile
Example: Increase sales (goal), increase sales of X product by 10% (objective) | Need
Context
Value |
| Stakeholder Requirements | - User Stories (broken down from Epic)
- Expected outcomes (e.g. User A must be able to send a message whenever he wants while using the system on his mobile device ) | Stakeholder
Need |
| Solution Requirements | - Functional requirements (Acceptance Criteria in Agile)
- Nonfunctional requirements | Solution |
| Transition Requirements | - User training materials, other transition requirements | Change |