This technique is used in a few different business analysis tasks in some knowledge areas in the BABOK® v3 guide. These tasks include the following:
|
Task |
The reason this technique is used |
|
Plan a business analysis approach |
To break down the business analysis deliverables and processes into smaller, more manageable concepts or activities to include in the business analysis approach. |
|
Trace the requirements |
To help break down high-level scope items into lower-level components. This is also used to help break down requirements into usable and trackable components. |
|
Maintain the requirements |
To help identify requirements that could be reused by breaking requirements down into useable components. |
|
Analyze the current state |
To help simplify concepts by breaking them down into smaller parts when analyzing the current state. |
|
Define the future state |
To help simplify concepts by breaking them down into smaller parts when defining the future state. |
|
Define the change strategy |
To break the solution down into smaller parts when defining the change strategy. |
|
Specify and model the requirements |
To model the requirements in a way that shows the different parts of a more complex business process or function. |
|
Define the requirements architecture |
To break down products, business functions, or other larger concepts into smaller logical components. |
This technique is a powerful way of breaking a complex topic or system down into smaller, understandable parts. It provides the framework for creating a common understanding of a potentially complex situation.
The next technique you need to include in your preparation is a glossary.