CBAP Exam Dumps : Certified Business Analysis Professional

The approach that would help the BA to understand the functionality definition issues is to use a requirements traceability repository, as this is a technique that helps to track the origin, dependencies, and relationships of the requirements throughout the business analysis process. A requirements traceability repository can help the BA to identify the sources, owners, and stakeholders of the requirements, as well as the changes, impacts, and risks associated with them. By using a requirements traceability repository, the BA can avoid duplication, inconsistency, and ambiguity in the functionality definition, and ensure that the requirements are aligned with the business needs and objectives. References: The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 6: Requirements Life Cycle Management, p. 209-210; Chapter 10: Requirements Traceability, p. 348-351.

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Requirements Life Cycle Management, p. 99-100,

According to the CBAP competencies, one of the skills required for business analysis planning and monitoring is to guide practice in performing stakeholder analysis1. Stakeholder analysis is the process of identifying and assessing the needs, interests, and influence of stakeholders on a project or initiative2. One of the outputs of stakeholder analysis is a stakeholder list, which identifies the key stakeholders and their roles, responsibilities, and expectations3. A stakeholder list can also include information on the potential risks and issues that may arise from stakeholder involvement or lack thereof4. Therefore, developing a risk plan to anticipate negative behavior from the Director of Human Resources is a valid activity that is included in performing a stakeholder analysis. This can help the team to mitigate the impact of the Director’s bitterness and resistance on the project’s success.

The other options are not included in performing a stakeholder analysis. Comparing the expertise of the Director of Human Resources to other stakeholders is not relevant to the stakeholder analysis process, as it does not help to understand the Director’s needs, interests, or influence. Recommending excluding the Director of Human Resources as a stakeholder is not a good practice, as it may create more conflict and resentment, and ignore the Director’s legitimate role and authority in the project. Implementing all of the Director of Human Resources suggestions to relieve tension is not a realistic or effective strategy, as it may compromise the quality and feasibility of the project, and disregard the needs and interests of other stakeholders. References:

1: CBAP Competencies - International Institute of Business Analysis

2: BABOK Guide v3, Section 2.2.2: Conduct Stakeholder Analysis

3: BABOK Guide v3, Section 2.2.2.3: Outputs

4: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 3: Business Analysis Planning and Monitoring, p. 83

The HAZOP technique, which stands for Hazard and Operability Study, is a qualitative technique that involves a disciplined analysis of the event sequences that could transform a potential hazard into an accident. The HAZOP technique is a systematic and structured method of identifying and evaluating the possible deviations from the intended design, operation, or functionality of a system, process, or product. The HAZOP technique uses a set of guide words, such as no, more, less, as well as, part of, and reverse, to generate different scenarios of what could go wrong and why. The HAZOP technique helps to identify the causes, consequences, and safeguards of the deviations, and to recommend the appropriate actions or controls to prevent or mitigate the hazards12. A failure mode and effects criticality analysis (FMECA) is a qualitative technique that involves an extension of the failure mode and effects analysis (FMEA) by adding a criticality rating to each failure mode. A FMECA is a method of identifying and evaluating the potential failures of a system, process, or product, and their impacts on the performance, safety, or reliability of the system, process, or product. A FMECA helps to prioritize the failures based on their severity and frequency, and to determine the corrective actions or preventive measures to reduce or eliminate the failures13. A failure mode and effects analysis (FMEA) is a qualitative technique that involves a systematic analysis of the potential failures of a system, process, or product, and their effects on the performance, safety, or reliability of the system, process, or product. An FMEA is a method of identifying and evaluating the causes, modes, and consequences of the failures, and the existing or planned controls to detect or prevent the failures. An FMEA helps to improve the design, operation, or functionality of the system, process, or product, and to reduce the risk of failures14. A preliminary risk analysis (PRA) is a qualitative technique that involves a high-level assessment of the risks that may affect a project or a solution. A PRA is a method of identifying and evaluating the sources, events, and impacts of the risks, and the existing or planned responses to the risks. A PRA helps to determine the feasibility and viability of the project or the solution, and to establish the scope and objectives of the risk management process15. References:

CBAP® Handbook

HAZOP Technique - iiba.org

Failure Mode and Effects Criticality Analysis - iiba.org

Failure Mode and Effects Analysis - iiba.org

Preliminary Risk Analysis - iiba.org