The best action to take to ensure the design meets customer requirements is to create a system requirements verification matrix to trace the design to the technical requirements and include verification methods. A system requirements verification matrix is a document that maps the design elements to the system requirements, and specifies the methods and criteria for verifying that the design satisfies the requirements. Verification methods can include inspection, analysis, demonstration, or testing.A system requirements verification matrix can help the business analyst and the project team to ensure the quality and completeness of the design, and to avoid any errors, gaps, or inconsistencies.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 100.

Business rules are statements that define or constrain some aspect of the business, such as policies, standards, procedures, regulations, or constraints. Business rules can be uncovered by asking about the reasons for choosing a particular course of action when modeling processes or analyzing tasks. By asking why a certain decision is made, what criteria are used, what conditions are applied, or what consequences are expected, the business analyst can elicit the business rules that govern the behavior or outcome of the process or task.Asking about tasks that overlap with each other, work that may be performed out of sequence, or task transitions that hinder organizational performance may help to identify issues or opportunities for improvement in the process or task, but they may not reveal the business rules that underlie them.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.

A requirements baseline is a set of approved requirements that serves as the basis for further development and validation. A requirements baseline approval form is a document that records the formal acceptance of the requirements baseline by the customer and other stakeholders. Creating a requirements baseline approval form for the customer to review and approve is the best action to take to establish an approved requirements baseline with the customer. The other actions are not sufficient or appropriate for this purpose. A requirements traceability matrix is a tool that links the requirements to their sources, objectives, and deliverables, but it does not record the approval of the requirements. Requesting that the customer create a baseline of the requirements in the contract specification is not a proactive or collaborative approach. Performing a variance analysis on the design specification and reporting the results to the customer is not relevant to establishing an approved requirements baseline.Reference: PMI-PBA Examination Content Outline, page 13; PMI-PBA Reference List, page 1, BABOK Guide v3, page 39.

An organizational chart is a tool that helps to visualize the structure and hierarchy of an organization, as well as the roles and responsibilities of its members. It can also show the relationships and interactions between different units, departments, or teams within the organization. An organizational chart can help the business analyst to identify the missing project stakeholders by showing who are involved in or affected by the online ordering system, such as the purchasing department. A business case is a tool that helps to justify the need and value of a project or initiative, as well as the costs and benefits associated with it. It does not provide information about the project stakeholders. A business analysis plan is a tool that helps to define the scope, approach, activities, deliverables, and schedule of the business analysis work. It does not provide information about the project stakeholders. A business analyst communication plan is a tool that helps to determine the communication needs, methods, frequency, and channels for the business analysis work.It does not provide information about the project stakeholders.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, PMI Guide to Business Analysis2, Business Analysis for Practitioners: A Practice Guide3, Organizational Chart - What is an Organization Chart?Definition, Types, Tips, Tutorial, and Examples

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.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline3, page 18; Business Analysis for Practitioners: A Practice Guide4, page 92.