Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Certification of Capability in Business Analysis (CCBA) · IIBA
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Explanation: A matrix documentation approach is useful when requirements share common attributes or characteristics—such as source, priority, status, or type. This allows the business analyst to efficiently organize and compare requirements in a structured table or matrix format. It’s especially valuable in large projects with many related requirements.
A matrix documentation approach (e.g., traceability matrix, prioritization matrix) requires requirements to share common characteristics (e.g., attributes like priority, source, status, or category) to structure the matrix effectively. These shared attributes allow the business analyst to organize, compare, and analyze requirements in a tabular format, highlighting relationships or gaps. BABOK Reference (Chapter 10: Techniques - Matrix Diagrams): Matrix models rely on common attributes to map relationships between requirements, stakeholders, or solution components. For example, a Requirements Traceability Matrix (RTM) links requirements to their sources, test cases, and business objectives.
C. The requirements must have the uniform structure.