SAD Prelim Term Quiz 2

Which among the choices is the most common technique used for gathering requirements?

• Focus Groups

• Observation

• Interviews

• Surveys

What is the purpose of user interviews in requirements gathering?

• To conduct market research on competitors.

• The purpose of user interviews in requirements gathering is to understand user needs and preferences.

• To evaluate the performance of existing software.

• To gather technical specifications from developers.

How can surveys be effectively used to gather user requirements?

• Surveys should avoid any form of anonymity to ensure accountability.

• Surveys are most effective when sent to a small group of users.

• Surveys can gather user requirements by asking targeted questions to a representative sample, ensuring clarity and anonymity, and analyzing the results for actionable insights.

• Surveys should only include open-ended questions for detailed feedback.

What are the key components of requirements documentation?

• Team Roles

• Budget Estimates

• Introduction, Stakeholder Requirements, Functional Requirements, Non-Functional Requirements, Use Cases, Acceptance Criteria

• Project Timeline

How does prototyping aid in the requirements gathering process?

• Prototyping only serves to finalize the design without user input.

• Prototyping eliminates the need for user feedback entirely.

• Prototyping aids in requirements gathering by providing a visual and interactive representation of the product, facilitating feedback and clarification of user needs.

• Prototyping is solely focused on technical specifications rather than user needs.

What is the importance of feedback in the prototyping phase?

• Feedback is irrelevant to user satisfaction.

• Feedback slows down the prototyping process.

• Feedback is essential for improving design, validating user needs, and refining functionality in the prototyping phase.

• Feedback is only necessary for final products.

What role do focus groups play in the requirements gathering process?

• Focus groups are only effective for large-scale projects.

• Focus groups are used to finalize the product design without user input.

• Focus groups help in gathering diverse user perspectives and identifying common needs through group discussions.

• Focus groups are primarily for testing prototypes rather than gathering requirements.

How can user stories enhance the requirements gathering process?

• User stories focus solely on the business goals rather than user needs.

• User stories help in capturing user needs in a simple, understandable format that guides development.

• User stories are only useful after the requirements have been finalized.

• User stories provide a detailed technical specification for developers.

What is the significance of acceptance criteria in requirements documentation?

• Acceptance criteria outline the conditions under which a product is considered complete and acceptable to stakeholders.

• Acceptance criteria define the budget and timeline for the project.

• Acceptance criteria are only necessary for final product delivery.

• Acceptance criteria are irrelevant to the development process.

What is the role of stakeholder interviews in refining requirements?

• Stakeholder interviews are used to gather technical specifications from developers.

• Stakeholder interviews help in understanding the broader business context and specific user needs.

• Stakeholder interviews are irrelevant to the requirements gathering process.

• Stakeholder interviews are primarily for testing prototypes.