CCBA Requirements Elicitation & Documentation

Question 1

What is the primary purpose of requirements elicitation?

Accepted Answer

To capture stakeholder needs and expectations

Answer

Requirements elicitation is the foundational process in business analysis where information is gathered from stakeholders. Its primary purpose is to accurately capture and understand the diverse needs, expectations, and underlying problems that a new solution must address. This ensures that the developed solution will be relevant and valuable to its users.

Question 2

Which technique is commonly used for eliciting requirements?

Accepted Answer

Interviews, surveys, and workshops

Answer

Interviews, surveys, and workshops are highly effective and commonly used techniques for eliciting requirements from stakeholders. Interviews allow for in-depth, one-on-one discussions, surveys can gather broad input from many stakeholders, and workshops facilitate collaborative discussions and consensus-building among groups. These methods help gather comprehensive and diverse perspectives.

Question 3

What is the purpose of documentation in requirements management?

Accepted Answer

To ensure proper approval and agreement of requirements

Answer

Documentation in requirements management serves as a formal record of all agreed-upon requirements, providing a single source of truth for the project. Its purpose is to ensure clarity, reduce ambiguity, and facilitate formal approval and agreement from all relevant stakeholders. This formal record is crucial for guiding development and preventing misunderstandings.

Question 4

What type of requirements document typically outlines the functionality of the system?

Accepted Answer

Functional requirements document

Answer

A Functional Requirements Document (FRD) is a key requirements document that specifically outlines the functionality and behavior of a system. It describes what the system must do, how it will respond to user input, and its various features from a user's perspective. This document focuses on the 'what' rather than the 'how' of the system's implementation.

Question 5

What is the role of a business analyst in requirements validation?

Accepted Answer

To validate that requirements align with business goals

Answer

In requirements validation, the business analyst's crucial role is to ensure that the gathered requirements are not only correct and complete but also directly align with the overarching business goals and objectives. This validation step confirms that the proposed solution will genuinely address the business problem and deliver the intended value. It prevents the development of features that do not contribute to strategic aims.

(CCBA) Certification of Capability in Business Analysis Practice Test

(CCBA) Certification of Capability in Business Analysis Practice Test

CCBA Requirements Elicitation & Documentation