CBAP Exam Dumps - Certified Business Analysis Professional

The marketing department (AAC) is a key stakeholder for launching an existing product in another channel, as they are responsible for defining the requirements, confirming the elicitation results, and validating the solution. Therefore, they have a high influence on the project, as they can affect the decisions and outcomes of the project. They also have a high impact from the project, as they will be directly affected by the changes and benefits of the new channel. According to the stakeholder analysis technique, influence and impact are two dimensions that can be used to categorize and prioritize stakeholders12. A stakeholder with high influence and high impact is considered a primary stakeholder, who should be actively involved and engaged throughout the project

 A requirement attribute is a characteristic or property of a requirement that provides additional information about it. Requirement attributes can help to manage, prioritize, trace, and verify the requirements. Some common requirement attributes are source, priority, status, owner, version, etc. One of the qualities of a good requirement is that it should be unambiguous, which means that it should have only one possible interpretation and avoid any confusion or misunderstanding. An unambiguous requirement is clear, precise, and consistent, and it can be easily verified and validated. An ambiguous requirement, on the other hand, can lead to errors, defects, rework, and conflicts among the stakeholders. References:

• Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS) - Jama Software, under Qualities of Good Requirements
• The Four Attributes of High-Quality Requirements - ArgonDigital, paragraph 1
• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47

 The information architect is the role that helps assess the data requirements of a project, identifies data assets, and helps the project team complete data modeling requirements. The information architect is responsible for designing and organizing the data structures, relationships, and flows that support the business processes and objectives. The information architect also ensures that the data quality, security, and integrity are maintained throughout the project. The information architect works closely with the business analyst, the database analyst, the end user, and the subject matter expert to elicit, analyze, validate, and communicate the data requirements and models. References: CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 237; CBAP Sample Questions, question 231.

Risk analysis is the process of analyzing the areas of a project that are most affected by risk. It involves estimating the probability and impact of each identified risk, as well as assessing the quality and reliability of the available data. Risk analysis helps to prioritize the risks based on their severity and potential effect on the project objectives and deliverables. Risk analysis also helps to identify the root causes and triggers of the risks, as well as the interrelationships and dependencies among the risks. Risk analysis is the second step of risk management, which also includes risk identification, risk response, and risk monitoring and control. References: [IIBA BABOK Guide v3], section 11.2.2, page 387; CBAP / CCBA Certified Business Analysis Study Guide, chapter 5, page 231; CBAP Sample Questions, question 234.

 A cause-and-effect diagram, also known as an Ishikawa diagram, is a graphical tool that helps identify, sort, and display possible causes of a specific problem or quality characteristic. It can also be used to explore the root causes of a problem or a desired outcome. The diagram looks like the skeleton of a fish, hence the name fishbone diagram. The effect or problem is shown as the fish’s head, and the causes are shown as the bones along the spine. The diagram helps to organize the causes into categories, such as people, processes, equipment, materials, environment, etc. The diagram can be created by brainstorming the causes and grouping them into major categories. The diagram can then be analyzed to identify the most likely or significant causes of the problem or outcome.

Compromising is a conflict resolution technique that requires that all parties in the conflict must give up something in order to reach a mutually acceptable solution. Compromising involves finding a middle ground or a trade-off that satisfies some of the interests or needs of each party, but not all of them. Compromising is useful when the parties have equal power and the conflict is not very important or complex. However, compromising may also result in a suboptimal outcome that does not fully address the root cause of the conflict or create a lasting agreement. References: [IIBA BABOK Guide v3], section 2.2.2.5, page 26; CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 181; Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam, question 254.

Diagrams are visual representations of information that can be used to define boundaries for business domains, categorize and create a hierarchy of items, and show data sources and their relationships for specific audiences. Diagrams can include various types of models, such as context diagrams, class diagrams, data flow diagrams, entity relationship diagrams, use case diagrams, and swimlane diagrams. Diagrams can help the BA to communicate complex information in a clear and concise way, and to elicit, analyze, and validate requirements with stakeholders. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

A Pareto diagram is a type of chart that displays the frequency of problems or causes in a process in descending order by bars, and the cumulative percentage of the total number of problems or causes by a line. The Pareto diagram helps to identify the most significant defects or issues that need to be prioritized for improvement. It is based on the Pareto principle, which states that 80% of the problems are caused by 20% of the causes. A Pareto diagram is one of the seven basic quality tools that are widely used in quality management and process improvement. References:

• Pareto chart - Wikipedia
• What Are the 7 Basic Quality Tools? | Lucidchart Blog, under 7 quality tools
• What is a Pareto Chart? Analysis & Diagram | ASQ