A model is a simplified representation of a complex reality that is useful for understanding that reality and making decisions regarding it. A model can describe a situation or problem, define boundaries for the business domain, describe thought processes and action flows, and other aspects of the requirements. However, a model cannot define the resources that will be needed on the project team, as this is not part of the requirements but rather part of the pr oject management plan.  References :  BABOK Guide v3 , page 123;  CBAP/CCBA Study Guide , page 181.

 Crashing is a process of adding labor to a project to reduce the project duration. Crashing involves increasing the resources, such as staff, equipment, or materials, to accelerate the completion of critical activities. Crashing may also involve paying overtime, hiring consultants, or outsourcing some tasks. Crashing is usually done when the project is behind schedule or when there is a need to meet a deadline. Crashing may increase the project cost and risk, so it should be done carefully and only when necessary.

Forming, storming, and rolling wave planning are not related to the process of adding labor to a project. Forming and storming are stages of team development, where the team members get to know each o ther and resolve conflicts. Rolling wave planning is a technique of iterative planning, where the work to be done in the near term is planned in detail, while the work in the distant future is planned at a higher level.  References :

CBAP Certification Study Guide v3.0 , page 33

BABOK Guide v3 , page 16

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 3, Week 3, Video: “Project Management Concepts”

Risky requirements are those that have a high probability of causing problems or failures in the project. By addressing them early in the prioritization, the project team can identify and resolve any issues before they affec t the rest of the requirements or the project deliverables. This way, the project can avoid rework, delays, and cost overruns that may result from risky requirements.  References :  CBAP / CCBA Certified Business Analysis Study Guide , Chapter 6: Requirements Analysis, page 203.  Certified Business Analysis Pro fessional (CBAP®) Handbook , page 6.

 A process configuration is a type of flowchart that shows all the processes and the interfaces that interact with the project processes. A process configuration provides a visual overview of the project scope, boundaries, inputs, outputs, and dependencies. It helps the business analyst to understand the project context, identify the stakeholders, and def ine the requirements. A process configuration is different from a Pareto chart, which is a type of chart that shows the frequency and impact of problems or issues in a process. A Pareto chart helps the business analyst to prioritize the problems or issues and focus on the most significant ones. A process configuration is also different from a control chart, which is a type of chart that shows the variation and performance of a process over time. A control chart helps the business analyst to monitor and cont rol the process quality and identify the causes of variation. A process configuration is not a quality baseline, which is a document that defines the quality standards and criteria for the project or the solution. A quality baseline helps the business anal yst to measure and evaluate the quality of the requirements and the solution. A process configuration is not a RACI chart, which is a type of matrix that shows the roles and responsibilities of the stakeholders in a project or a process. A RACI chart helps the business analyst to clarify the expectations and accountabilities of the stakeholders and improve the communication and collaboration among them.  References :

[CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition], Chapter 6: Enterprise Analysis, page 217-218.

Business Analysis: Key Definitions & Strategy Analysis , paragraph 3

Business Analysis: Process Modeling , paragraph 1

Process Configuration - an overview | ScienceDirect Topics , paragraph 1

Process Configuration - Project Management Knowledge , paragraph 1

 An entity relationship diagram (ERD) is a graphical representation of how entities and relationships are organized in a database or a system. An ERD consists of three main components: entities, attributes, and relationships. Entities are the objects or concepts that store data, such as customers, products, or orders. Attributes are the properties or characteristics of entities, such as name, price, or quantity. Relation ships are the associations or connections between entities, such as one-to-one, one-to-many, or many-to-many. Forks are not a component of an ERD, but rather a symbol used to represent a relationship type. A fork indicates that a relationship is either one -to-many or many-to-many, depending on the direction of the fork. For example, a fork pointing from an entity A to an entity B means that one instance of A can be related to many instances of B, while a fork pointing from an entity B to an entity A means t hat many instances of B can be related to one instance of A.  References :

ER Diagram (ERD) - Definition & Overview | Lucidchart , paragraph 1-2

A Guide to the Entity Relationship Diagram (ERD) - Database Star , paragraph 1-2

ERD Templates | ER Diagram Examples | Moqups , paragraph 1

What is an Entity Relationship (ER) Diagram - Creately , paragraph 1

Components of an ER Diagram - TAE - Tutoria l And Example , paragraph 1-2

GAP analysis is a technique that involves determining and documenting the variance between business requirements and current capabilities. GAP analysis helps to identify the gaps or discrepancies between th e current state and the desired state of a system or a process. GAP analysis can also help to prioritize the requirements, define the scope, and plan the actions needed to close the gaps. GAP analysis is different from risk analysis, which is a technique t hat involves identifying, assessing, and managing the uncertainties and threats that may affect the project objectives. GAP analysis is also different from schedule analysis, which is a technique that involves estimating, monitoring, and controlling the ti me and resources needed to complete the project activities. GAP analysis is not a cost benefit analysis, which is a technique that involves comparing the costs and benefits of alternative solutions or courses of action.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 6: Enterprise Analysis, page 215-216.

Business Capability Analysis: How to analyze capabilities , paragraph 3

ProjectManagement.com - Varian ce Analysis , paragraph 1

Which of the following techniques involves determinin g and documenting … , paragraph 1

Business rules analysis is a business analysis technique that involves identifying, analyzing, and documenting the rules that govern how an organization operates and makes decisions. Business rules analysis can help an organization to adapt to the change economy, new technologies, and an increase in competition by ensuring that the rules are aligned with the organizational goals and objectives, and that they are consistent, transparent, and flexible. Business rules analysis can also help to identify any gaps, conflicts, or redundancies in the existing rules, and to propose new or revised rules that can improve the organizational performance and efficiency.  References :  BABOK Guide v3 , page 142;  CBAP / CCBA Certified Business Analysis Study Guide , page 191.

 Voting is a technique of requirements prioritization that involves asking the stakeholders to express their preferences for the requirements using various methods, such as ranking, rating, or allocating points or money. Voting helps to achieve consensus and alignment among the stakeholders and to identify the most important and valuable requirements. In this scenario, the business analyst is using a voting method that assigns play money to the requirements, which reflects the relative importance and benefit of each requirement. The requirements with the highest amount of play money are prioritized over the ones with lower amounts.

References :

BABOK® Guide , p. 55, 376-377

CBAP / CCBA Certified Business Analysis Study Guide , p. 165-166

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 2, Week 1, Video: “Requirements Prioritization”

 According to the BABOK® Guide, one of the tasks of defining the business need is to review the requirements stated documentation and ens ure that it reflects the actual business requirements, not a description of the solutions. This is important because the business need should be based on the underlying problem or opportunity, not on a predetermined solution. The other options are not rele vant to this task.  References :  BABOK® Guide , v3, p. 30;  CBAP / CCBA Certified Business Analysis Study Guide , 2nd Edition, p. 36.

 Surveys are a conduct stakeholder analysis technique that is useful for identifying shared characteristics of a stakeholder group. Surveys are structured questionnaires that are distributed to a large number of stakeholders to collect quantitative and qualitative data about their needs, expectations, preferences, and opinions. Surveys can help to identify common patterns, trends, and themes among the stakeholder group, as well as to measure the level of agreement, satisfaction, or importance of the requirements. Surveys can also be used to segment the stakeholder group based on their characteristics, such as roles, responsibilities, interests, or influence.

Scope modeling, brainstorming, and interviews are other conduct stakeholder analysis techniques, but they are not as effective as surveys for identifying shared characteristics of a stakeholder group. Scope modeling is a technique that defines the boundaries and context of the business domain and the solution. Brainstorming is a technique that generates a large number of ideas or solutions in a creative and colla borative way. Interviews are a technique that involves one-on-one or group discussions with the stakeholders to elicit detailed information about their needs, expectations, preferences, and opinions. These techniques are more suitable for exploring the spe cific and individual characteristics of the stakeholders, rather than the general and collective ones.  References :

BABOK® Guide , p. 104-105, 377-378

CBAP / CCBA Certified Business Analysis Study Guide , p. 49-50, 52

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 1, Week 3, Video: “Stakeholder Analysis”