Explanation
The rationale for each requirement is the justification or explanation of why the requirement is needed and how it supports the business objectives. It should include the reasons and assumptions behind the requirement, as well as any constraints or dependencies that affect it. The product vision and operational relationships are part of the business case, not the rationale. The stakeholder impact and design decisions are part of the analysis and solution evaluation, not the rationale. The functional relationships and work breakdown structure code are part of the solution scope and architecture, not the rationale. References: PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline, page 17; Business Analysis for Practitioners: A Practice Guide, page 113.

Explanation
Team peer review is a technique that is used to identify ambiguous or unverifiable requirements. Team peer review is a technique that involves having a group of peers or experts examine and evaluate the requirements for quality, completeness, correctness, clarity, consistency, and testability. Team peer review can help to identify any ambiguous or unverifiable requirements that may cause confusion, misunderstanding, or errors in the project. Team peer review can also provide feedback and suggestions for improvement or resolution of any issues or defects in the requirements. Fishbone analysis is not a technique that is used to identify ambiguous or unverifiable requirements. Fishbone analysis is a technique that is used to identify the root causes of a problem or an effect by analyzing its contributing factors and their relationships. Fishbone analysis can help to understand why a problem exists or why an effect occurs, but it does not directly examine or evaluate the quality of the requirements. Resource checklist is not a technique that is used to identify ambiguous or unverifiable requirements. Resource checklist is a tool that is used to identify and document the resources needed to perform business analysis activities, such as people, tools, facilities, equipment, etc. Resource checklist can help to plan and manage the resources required for business analysis work, but it does not assess or verify the quality of the requirements. Traceability matrix is not a technique that is used to identify ambiguous or unverifiable requirements. Traceability matrix is a tool that is used to track and document the relationships and dependencies among requirements and other project elements, such as design, test cases, risks, issues, etc. Traceability matrix can help to monitor and control changes to requirements and ensure alignment with project objectives and stakeholder needs, but it does not measure or validate the quality of the requirements. References: Business Analysis for Practitioners: A Practice Guide 1, page 162-163; PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline 2, page 19-20.

Explanation
A modeling tool integrated into a version control feature that ensures that team knowledge is captured is a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding. A modeling tool is a tool that allows the business analyst to create visual representations of the product needs, such as diagrams, charts, graphs, or mockups. These models can help the stakeholders to comprehend and verify the requirements more easily than textual descriptions. A version control feature is a tool that allows the business analyst to track and manage changes to the models and ensure that they are consistent and accurate. A version control feature also enables collaboration and knowledge sharing among the team members and stakeholders. A requirements management tool that documents requirements and their properties and relationships is not a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding, as it does not provide visual or graphical representations of the product needs. A document management system and a relationship matrix that groups all related documents is not a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding, as it does not create or display models of the product needs. A workflow management tool that documents the flow of information is not a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding, as it only focuses on one aspect of the product needs and does not capture other dimensions such as functionality, quality, or value. References: Business Analysis for Practitioners: A Practice Guide 1, page 77-78; PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline 2, page 16.

Explanation
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.

Explanation
Asking stakeholders to vote on the requirements is a technique that the business analyst can employ to rectify the issue of not having enough resources to deliver all the requirements. Voting is a method of prioritizing requirements by asking stakeholders to rank or rate them according to their importance, urgency, value, or risk. Voting can help to identify the most critical or essential requirements that should be delivered first or within the available resources. Voting can also help to resolve conflicts or disagreements among stakeholders and reach a consensus on the priority of the requirements. Holding a brainstorming workshop to build the rationale for the requirements is not an effective technique to rectify the issue, as it does not address the resource constraint or the priority of the requirements. Brainstorming is a method of generating ideas or solutions by encouraging free and creative thinking from participants. Brainstorming can help to elicit or analyze requirements, but not prioritize them. Performing traceability to find out where the requirements originated is not a useful technique to rectify the issue, as it does not indicate the importance or value of the requirements. Traceability is a process of tracking the relationship between requirements and other project artifacts, such as design, test cases, or deliverables. Traceability can help to ensure completeness, consistency, and quality of the requirements, but not prioritize them. Surveying stakeholders on their likes and dislikes about the requirements is not a viable technique to rectify the issue, as it does not provide a clear or objective way of prioritizing the requirements. Surveying is a method of collecting feedback from stakeholders by asking them questions about their satisfaction, preferences, expectations, needs, problems, or suggestions. Surveying can help to validate or evaluate the requirements, but not prioritize them. References:
PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline1, page 15; Business
Analysis for Practitioners: A Practice Guide2, page 95.