PMI-PBA Exam Dumps : PMI Professional in Business Analysis

A requirements traceability matrix (RTM) is a tool that helps to map and track the user requirements with the test cases, and to ensure that the requirements are met by the solution. A RTM can also include other attributes or characteristics of the requirements, such as priority, risk, complexity, source, owner, etc. One of these attributes can be the system and architectural stability, which reflects the degree of reliability, robustness, and resilience of the system and its architecture. By including this attribute in the RTM, the business analyst can ensure that the requirement meets the acceptance criteria for system and architectural stability, and that the test cases can verify and validate this attribute. A RTM can also help to identify any gaps, inconsistencies, or conflicts between the requirements and the test cases, and to manage any changes or issues that may arise during the development process. References: = 1, 2

 The business analyst should conduct a stakeholder analysis and balance requirements by understanding the relative power associated with each stakeholder group. This action will help the business analyst to identify and prioritize the needs and expectations of different stakeholders, and to manage any conflicts or trade-offs among them. The business analyst should also consider the alignment of the requirements with the project objectives and the business value. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 9; Business Analysis for Practitioners: A Practice Guide2, page 38.

 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.