Explanation
According to the PMI Guide to Business Analysis, one of the best strategies to define appropriate acceptance criteria is to clearly define the performance measures and targets for the solution, such as accuracy, reliability, availability, efficiency, etc. These measures and targets help to evaluate how well the solution meets the stakeholder needs and expectations, and how it contributes to the business value. In this case, since the operations manager is concerned about the accuracy of the new measurement system, a good strategy would be to clearly define the maximum acceptable error rate for the new system, which would indicate how accurate the system should be in order to be accepted by the stakeholder. Quantifying the risks associated with measurement errors, asking for a formal acceptance of requirements documents, or planning a training session for the new system are not effective strategies to define appropriate acceptance criteria, as they do not specify how the performance of the solution will be measured or evaluated. References: PMI Guide to Business Analysis, page 316-317.

Explanation
This situation could have been avoided if a change control process for requirements and their statuses was followed. A change control process is a set of procedures and tools that helps the business analyst to manage changes to the requirements, and to document and communicate the impact and approval of the changes. A change control process also helps to maintain the traceability and quality of the requirements, and to ensure that they are aligned with the business needs and the project scope. References: PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline1, page 23; Business Analysis for Practitioners: A Practice Guide2, page 131.

Explanation
A requirements traceability matrix (RTM) is a tool that helps to track the relationship between the requirements and the product features. It can be used to determine the scope of a change request by identifying which requirements and test cases are affected by the modification of an existing feature. A project schedule and cost baseline are not directly related to the product features, but rather to the project management aspects.
A requirements attributes table is a tool that helps to classify and prioritize the requirements, but it does not show the link between the requirements and the product features. A sequence diagram is a tool that helps to illustrate the interactions between the components of the product, but it does not show the traceability of the requirements. References: PMI Professional in Business Analysis (PMI-PBA)
Examination Content
Outline1, PMI Guide to Business Analysis2, Business Analysis for Practitioners: A Practice Guide

Explanation
Requirements status during the project development cycle is the information that should be reported to the stakeholder who wants to know how the implementation of new features in the development of a product is progressing. The requirements status shows how many requirements are in each stage of the development cycle, such as analysis, design, development, testing, or deployment. This information can help the stakeholder understand the progress and quality of the product development and identify any issues or risks that may affect the delivery of the new features. Distribution of project changes is not relevant to the implementation of new features, as it shows how many changes have been requested, approved, or rejected for the project scope, schedule, cost, or quality. Number of requirements approved vs. number of requirements rejected is not relevant to the implementation of new features, as it shows how many requirements have been accepted or discarded by the stakeholders during the requirements analysis phase. Number of requirements tested and approved is not sufficient to report the implementation of new features, as it only shows how many requirements have passed the verification and validation process, but not how many are still in development or deployment stages. References: Business Analysis for Practitioners: A Practice Guide, page 161-162; PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline, page 19.

Explanation
The business analyst should trace the requirements and measure the impact of the requested changes on the existing delivery date. Tracing the requirements means identifying the source, dependencies, and relationships of the requirements, and ensuring their alignment with the business needs, objectives, and expectations.
Measuring the impact of the changes means assessing how the changes will affect the scope, schedule, cost, quality, and risk of the project. These actions can help the business analyst and the project team to evaluate the feasibility and priority of the changes, and to communicate the implications and alternatives to the customer and other stakeholders. References: PMI Professional in Business Analysis (PMI-PBA)
Examination
Content Outline1, page 23; Business Analysis for Practitioners: A Practice Guide2, page 131.