Requirements Elicitation & Documentation Flashcards

What is the primary purpose of requirements elicitation?

Answer: To capture stakeholder needs and expectations

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.

Which technique is commonly used for eliciting requirements?

Answer: Interviews, surveys, and workshops

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.

What is the purpose of documentation in requirements management?

Answer: To ensure proper approval and agreement of requirements

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.

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

Answer: Functional requirements document

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.

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

Answer: To validate that requirements align with business goals

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.

Which is a critical aspect of requirements documentation?

Answer: Clarity, conciseness, and measurability

Critical aspects of requirements documentation include clarity, conciseness, and measurability. Clarity ensures that requirements are easily understood by all stakeholders, conciseness avoids unnecessary detail, and measurability allows for objective verification during testing and implementation. These qualities are essential for effective communication, accurate development, and successful project delivery.

Which stakeholder group should primarily review and approve requirements documents?

Answer: Project sponsors and key stakeholders

Project sponsors and key stakeholders are the primary group responsible for reviewing and approving requirements documents. As the ultimate owners of the business problem and vision, their approval ensures that the documented requirements accurately reflect their strategic objectives and expectations. Their sign-off provides legitimacy and direction for the development effort.

Why should requirements be prioritized?

Answer: To address the highest business value first

Requirements should be prioritized to ensure that the most critical features and functionalities, those delivering the highest business value, are addressed first. This strategic approach optimizes resource allocation, manages stakeholder expectations, and ensures that essential needs are met early in the project lifecycle. It allows for incremental delivery of value and adaptability.

How should changes to requirements be managed?

Answer: By formal change control processes

Changes to requirements must be managed through formal change control processes to maintain project stability and prevent uncontrolled scope creep. This involves a structured approach where proposed changes are documented, reviewed for impact, and formally approved by relevant stakeholders before implementation. This ensures that all changes are deliberate, understood, and aligned with project objectives.