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 |
Conduct elicitation |
To help understand the relationship between entities, which often also highlights business rules that exist between entities |
Maintain requirements |
To identify a potential data structure that is similar across an organization, with the intention to reuse it |
Specify and model requirements |
To model requirements in a way that shows how data will be used in a business or solution |
Define the requirements architecture |
To describe the requirements structure of an initiative in relation to the data |
This technique is a consistent way of analyzing and documenting data and the relationships that exist between data entities. There is flexibility in the level of detail that is included and it can be used as a communication tool between both business and technical stakeholder groups.
The next technique you need to include in your preparation is decision analysis.