Task-Specific BABOK Techniques for the CBAP Exam: Part 3

Coverage Matrix, Requirements for Vendor Selection, Requirements Documentation

Picking up where I left off on BABOK techniques, let’s cover three more task-specific techniques. Or, what might be considered outputs, or have been combined with other techniques. But, I’m editorializing again. 🙂

Coverage Matrix

Somewhere along the line, the good old fashioned traceability matrix was renamed as a Coverage Matrix. You didn’t get the memo, you say? Neither did I. But, it illustrates an important point about preparing for the CBAP exam: use the BABOK terminology even if it disagrees with what you are familiar with.

A coverage matrix does for all intents and purposes what a traceability matrix does. It is a table that cross-references requirements with attributes to be traced. Examples are: who supplied a requirement, who owns it, the status, dependencies, how it is allocated, etc. Here is an example:

This technique is from task 4.2- Manage Requirements Traceability.

Requirements for Vendor Selection

Requirements must frequently be packaged in a form that can assist in selecting a vendor for all or part of a solution. The BABOK mentions RFI, RFQ, and RFP as the three types. Below is a table that explains each.




RFI Request for Information It requests information from vendors about potential solutions to a given need.
RFQ Request for Quotation Used to request bids on a specific solution from a number of potential vendors.
RFP Request for Proposal Used to request proposals to solve a specified business need typically from a small number of potential vendors.

 The BABOK mentions several details regarding these, which I won’t repeat. If you are preparing for the CBAP exam, you should know the meanings of the three, when each would be used, and that they are common ways to package and communicate requirements.

This technique supports BABOK task 4.4- Prepare Requirements Package.

Requirements Documentation

Now, this is another output that is listed instead as a technique. Curious. Granted, there are multiple formats of requirements documentation that business analysts use. I get that. But, it’s kind of odd that this is listed as a technique.

What you need to know are that BAs frequently use templates for documentation, and that various types of documentation styles exist, including Business Requirements Document, Product Roadmap, Software Requirements Specification, and Supplementary Requirements Specification.

You could refer to task 4.4- Prepare Requirements Package, but you won’t need to.

To recap, these are all important techniques, even if I editorialize about whether they should be outputs or not. If you are studying for the CBAP exam, you should be familiar with them all, at least at a high level. My guess is you will be tested on at least one of them.


To learn more…

1) Get a copy of the BABOK by downloading it from the IIBA.

2) Read about all the task-specific techniques in our CBAP Certification Study Guide.

3) Take our CBAP Certification Preparation training course.

4) Studying for the CCBA exam? Our CBAP products are just what you need. Contact us for more information.

Leave a Reply

Your email address will not be published. Required fields are marked *