Explanation/Reference:

A matrix is a tool that can be used to record, organize, and track the requirements throughout the lifecycle of the project. A matrix can help the business analyst to identify the sources, dependencies, relationships, and attributes of the requirements, as well as to monitor their status, changes, and traceability. A matrix can also facilitate the communication, verification, and validation of the requirements with the stakeholders, and ensure their alignment with the business needs and objectives. A matrix can be updated and reviewed regularly to reflect the current state of the requirements and the solution, and to obtain the approval and acceptance from the stakeholders. A common example of a matrix is the Requirements Traceability Matrix (RTM), which is a tool that links the requirements to the project scope, objectives, deliverables, and test cases12. References: PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline3, page 18; Business Analysis for Practitioners: A Practice Guide4, page 92.

Problem tracking is a technique that helps the business analyst to manage and resolve issues identified by stakeholders with requirements. It involves creating a clear and concise record of each issue with its description, impact, priority, data, owner, status, and any other relevant information. It also involves tracking and managing the recorded issues until they are resolved. Problem tracking helps to ensure that issues are not neglected or abandoned, and that they are addressed in a timely and effective manner. Problem tracking also exposes the root causes of issues and helps to prevent recurrence of similar problems in the future. References: = PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, page 19.

According to the PMI Guide to Business Analysis, a data dictionary is a tool that defines and describes the data elements and their attributes in a consistent and standardized way. A data dictionary can help to minimize the risk of misunderstanding or misinterpreting data items mentioned in the requirements documents, as it provides a common language and reference for all stakeholders involved in the project. A data dictionary can also help to ensure the quality, accuracy, and completeness of the data requirements. Planning a peer review, asking for a formal acceptance, or holding a workshop are other ways to improve the clarity and understanding of the requirements specification, but they do not address the specific issue of defining and describing the data items. References: PMI Guide to Business Analysis, page 169-170.

According to the PMI Guide to Business Analysis, planning the requirements change process involves defining how requirement changes will be identified, analyzed, approved, and communicated throughout the project life cycle. Communication is a key aspect of managing requirement changes, as it ensures that all stakeholders are aware of the status, impact, and rationale of the changes, and that they can provide their feedback and input. How requirement changes will impact the requirements baseline, how they will be implemented, and how they will impact the validation plan are all important considerations, but they are not part of planning the requirements change process. They are part of executing, monitoring, and controlling the requirements change process. References: PMI Guide to Business Analysis, page 286-287.