Pass the IIBA Certified Business Analysis Professional CBAP Questions and answers with ValidTests

A data dictionary is a model that defines the name of the data, data aliases, and description of system data. A data dictionary is a collection of metadata that provides information about the data elements and structures in a system or a database. A data dictionary can include the following information for each data element: name, alias, description, data type, size, format, domain, constraints, default value, source, owner, and usage. A data dictionary can help the business analyst to understand the data requirements, design the data model, and ensure the data quality and consistency. A data dictionary is different from a class model, which is a model that defines the classes, attributes, operations, and relationships in an object-oriented system. A data dictionary is also different from an entity relationship model, which is a model that defines the entities, attributes, relationships, and cardinalities in a relational database. A data dictionary is not a CRUD matrix, which is a model that defines the create, read, update, and delete operations for each data element and user role in a system. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Requirements Analysis, page 288-289.

Data Dictionary - Tutorialspoint, paragraph 1-2

What is a Data Dictionary? | Definition and How To, paragraph 1-2

Data Dictionary - Project Management Knowledge, paragraph 1

 A requirements management plan is a business analysis plan that defines and describes the process to be followed in managing the solution scope and requirements. It includes the following items12:

The requirements structure and traceability

The requirements prioritization and approval process

The requirements change control process

The requirements communication and reporting process

The requirements validation and verification process

The requirements configuration management process

The requirements reuse and disposal process

A requirements management plan is an important component of the business analysis plan, as it helps to ensure that the requirements are aligned with the business needs and objectives, and that they are delivered and maintained in a consistent and effective way. References:

Requirements Management Plan - IIBA®

Requirements Management Plan Template

 A business analysis communications plan is a document that describes how the business analysis information will be communicated to the stakeholders, including the format, frequency, content, and recipients of the communication. A business analysis communications plan can help to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis work, and that the business analysis deliverables are validated and approved. A business analysis communications plan is part of the business analysis plan, which is a comprehensive document that covers all aspects of the business analysis approach, activities, and deliverables. References: BABOK Guide v3, page 37; CBAP / CCBA Certified Business Analysis Study Guide, page 75.

 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 collaborative 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 specific 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”

The Delphi technique is a type of requirements elicitation technique that is based on a survey method. The Delphi technique involves sending a series of questionnaires to a group of experts who have knowledge or experience in the domain of the project or the solution. The questionnaires are designed to elicit opinions, ideas, or feedback on the requirements or the issues related to the project or the solution. The responses from the experts are collected and analyzed by a facilitator, who then provides a summary of the results and the areas of agreement or disagreement to the experts. The facilitator also prepares a new questionnaire based on the feedback and sends it back to the experts for another round of responses. This process is repeated until a consensus is reached or a sufficient level of information is obtained. The Delphi technique is useful for gathering requirements from a large and diverse group of stakeholders who are geographically dispersed or have conflicting views. The Delphi technique also helps to reduce the influence of dominant or biased individuals and to encourage honest and independent opinions. The Delphi technique is different from a workshop, which is a type of requirements elicitation technique that involves bringing together a group of stakeholders in a face-to-face or virtual setting to collaborate and exchange information on the requirements or the issues related to the project or the solution. The workshop is facilitated by a moderator, who guides the discussion and ensures the participation and contribution of all the attendees. The workshop is useful for generating a large number of ideas and finding solutions for a specific problem in a short time. The workshop also helps to build rapport and trust among the stakeholders and to resolve conflicts or misunderstandings. The Delphi technique is also different from a round table, which is a type of requirements elicitation technique that involves inviting a group of stakeholders to a formal or informal meeting to share their perspectives and insights on the requirements or the issues related to the project or the solution. The round table is moderated by a leader, who introduces the topic and encourages the dialogue and debate among the participants. The round table is useful for exploring different viewpoints and opinions and for gaining a deeper understanding of the problem and the context. The round table also helps to foster a sense of involvement and ownership among the stakeholders and to identify the areas of agreement or disagreement. The Delphi technique is not a prototyping, which is a type of requirements elicitation technique that involves creating a simplified or partial version of the solution or a component of the solution and presenting it to the stakeholders for feedback. The prototype can be either low-fidelity or high-fidelity, depending on the level of detail and functionality. The prototype is useful for validating and verifying the requirements and for demonstrating the feasibility and usability of the solution. The prototype also helps to reduce the ambiguity and uncertainty of the requirements and to increase the satisfaction and acceptance of the solution. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 180-181.

Top 10 Most Common Requirements Elicitation Techniques, paragraph 9

Software Engineering | Requirements Elicitation - GeeksforGeeks, paragraph 6

Delphi Method Forecasting Definition and How It’s Used - Investopedia, paragraph 1

The Delphi Technique - Students 4 Best Evidence, paragraph 1

 A request for proposal (RFP) is a type of procurement document used to request proposals from prospective sellers of products or services. An RFP describes the problem or need, the desired solution, the evaluation criteria, and the contractual terms and conditions. An RFP invites sellers to submit a detailed proposal that explains how they will meet the buyer’s requirements and expectations. An RFP is used when the buyer has a complex or high-value problem or need, and wants to compare different approaches and solutions from various sellers. A request for quote (RFQ) is a type of procurement document used to request price quotations from prospective sellers of products or services. An RFQ describes the specifications, quantity, quality, and delivery schedule of the products or services. An RFQ invites sellers to submit a fixed-price quotation that indicates the cost of providing the products or services. An RFQ is used when the buyer has a well-defined or standard problem or need, and wants to compare the prices and terms from various sellers. A request for information (RFI) is a type of procurement document used to request general information from prospective sellers of products or services. An RFI describes the problem or need, the objectives, and the scope of the project. An RFI invites sellers to provide information about their capabilities, experience, references, and feedback. An RFI is used when the buyer has a vague or unclear problem or need, and wants to gather more information and knowledge from various sellers. A request for bid (RFB) is a type of procurement document used to request bids from prospective sellers of products or services. An RFB describes the specifications, quantity, quality, and delivery schedule of the products or services. An RFB invites sellers to submit a sealed bid that indicates the cost of providing the products or services. An RFB is used when the buyer has a well-defined or standard problem or need, and wants to select the lowest bidder among the qualified sellers. References: CBAP® Handbook, CBAP® Exam Prep Study Guide, Project Management Institute

According to the BABOK Guide, the business analyst must ensure that any information captured on a whiteboard or other temporary medium is transferred to a more permanent medium before it is lost or erased. This is part of the documentation and communication of the elicitation results. The other options are not required by the BABOK Guide, though they may be useful in some situations. References: BABOK Guide, Version 3, Section 4.4.6, p. 121; Certified Business Analysis Professional (CBAP) Handbook, p. 6.

 Preparing for elicitation is a process of planning and arranging the elicitation activities that will be used to gather information from the stakeholders. Preparing for elicitation involves clarifying the scope of the selected elicitation technique, gathering any supporting materials, and scheduling all the people and resources that are needed for conducting the elicitation activities. Preparing for elicitation can help to ensure that the elicitation is effective, efficient, and collaborative, and that the desired outcomes are achieved. References: Prepare for Elicitation, page 1; 3 Steps to Preparing for an Elicitation Session.

Work breakdown structure creation is a technique that can be used to plan and manage the business analysis work, but it is not a technique to specify or model requirements. Organization modeling, data modeling, and state diagrams are all techniques that can be used to describe different aspects of the requirements, such as the stakeholders, the data, and the behavior of the solution. References:

CBAP Handbook, page 6, Exam Blueprint, Knowledge Area 4: Requirements Analysis and Design Definition

BABOK Guide, Chapter 10: Techniques, Section 10.1: Acceptance and Evaluation Criteria Definition, Section 10.8: Data Modeling, Section 10.34: State Modeling, Section 10.37: Work Breakdown Structure

 Enterprise architecture is not an input for the conduct stakeholder analysis task. Enterprise architecture is a description of the structure, behavior, and governance of an organization and its information systems. Enterprise architecture may be an output of the business analysis process, but it is not an input for identifying and analyzing the stakeholders. The inputs for the conduct stakeholder analysis task are enterprise environmental factors, organizational process assets, and business need. Enterprise environmental factors are the internal and external factors that may influence the business analysis activities, such as the organizational culture, structure, policies, processes, and systems. Organizational process assets are the existing resources, standards, and guidelines that can be used to perform the business analysis activities, such as templates, tools, methodologies, and best practices. Business need is the problem or opportunity that the organization is facing and that requires a solution. References:

BABOK® Guide, p. 29, 104

CBAP / CCBA Certified Business Analysis Study Guide, p. 45, 49

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