Wayground logo

Free Printable Worksheets

Font size

S
M
L
XL
Worksheets

SAD Prelim Term Quiz 2

Total questions: 24

Worksheet time: 5mins

Name
Class
Date
1.

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

a)

Focus Groups

b)

Observation

c)

Interviews

d)

Surveys

2.

What is the purpose of user interviews in requirements gathering?

a)

To conduct market research on competitors.

b)

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

c)

To evaluate the performance of existing software.

d)

To gather technical specifications from developers.

3.

How can surveys be effectively used to gather user requirements?

a)

Surveys should avoid any form of anonymity to ensure accountability.

b)

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

c)

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

d)

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

4.

What are the key components of requirements documentation?

a)

Team Roles

b)

Budget Estimates

c)

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

d)

Project Timeline

5.

How does prototyping aid in the requirements gathering process?

a)

Prototyping only serves to finalize the design without user input.

b)

Prototyping eliminates the need for user feedback entirely.

c)

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

d)

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

6.

What is the importance of feedback in the prototyping phase?

a)

Feedback is irrelevant to user satisfaction.

b)

Feedback slows down the prototyping process.

c)

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

d)

Feedback is only necessary for final products.

7.

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

a)

Focus groups are only effective for large-scale projects.

b)

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

c)

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

d)

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

8.

How can user stories enhance the requirements gathering process?

a)

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

b)

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

c)

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

d)

User stories provide a detailed technical specification for developers.

9.

What is the significance of acceptance criteria in requirements documentation?

a)

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

b)

Acceptance criteria define the budget and timeline for the project.

c)

Acceptance criteria are only necessary for final product delivery.

d)

Acceptance criteria are irrelevant to the development process.

10.

What is the role of stakeholder interviews in refining requirements?

a)

Stakeholder interviews are used to gather technical specifications from developers.

b)

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

c)

Stakeholder interviews are irrelevant to the requirements gathering process.

d)

Stakeholder interviews are primarily for testing prototypes.

11.

What is the primary goal of a focus group in requirement gathering?

a)

To conduct individual interviews with users

b)

To gather feedback from a group of users through guided discussion

c)

To test prototypes with a small group of stakeholders

d)

To document user workflows

12.

Which of these is a best practice when conducting workshops for gathering requirements?

a)

Skip brainstorming sessions to keep the workshop concise and focused.

b)

Involve only technical stakeholders to streamline the discussions.

c)

Use interactive techniques such as role-playing and process mapping to engage participants.

d)

Focus discussions exclusively on system constraints and technical limitations.

13.

Which of the following is an example of a user requirement?

a)

The system should allow users to search for products using keywords.

b)

The system must respond to all queries within a maximum of 1 second.

c)

The software should help the company achieve a 10% sales increase within 6 months.

d)

The system must be capable of supporting up to 10,000 concurrent users without failure.

14.

Why is stakeholder involvement crucial during requirement gathering?

a)

It reduces the need for prototypes.

b)

It ensures the project meets business needs and user expectations.

c)

It speeds up the implementation phase.

d)

It eliminates the need for testing.

15.

What is the main purpose of acceptance criteria in a requirement specification?

a)

To rank requirements based on their level of importance and urgency.

b)

To specify the conditions that must be met for a requirement to be considered fulfilled.

c)

To provide a basis for estimating project timelines and deliverables.

d)

To record and organize feedback received from stakeholders during the project.

16.

What is the purpose of a Feasibility Report in the requirement gathering phase?

a)

To identify potential challenges and assess project viability

b)

To document test cases for the system

c)

To finalize system architecture

d)

To track changes in requirements

17.

What is MoSCoW prioritization?

a)

A framework for categorizing requirements as Must Have, Should Have, Could Have, and Won’t Have.

b)

A method for organizing tasks into Must Do, Should Do, Can Do, and Won’t Do.

c)

A process for prioritizing features as Mandatory, Secondary, Conditional, and Optional.

d)

A technique for assigning priorities as Must Complete, Should Complete, Could Complete, and Would Complete.

18.

Which tool is commonly used for managing requirements?

a)

Google forms

b)

JIRA

c)

SurveyMonkey

d)

Visual Studio

19.

What characteristic of a good requirement ensures that it can be tested or verified?

a)

Clear and Unambiguous

b)

Specific and Concise

c)

Measurable and Testable

d)

Relevant

20.

Which technique gathers requirements by analyzing existing system documentation and reports?

a)

Document Analysis

b)

Observation

c)

Workshops

d)

Focus Groups

21.

Which technique is most suitable for gathering quantitative data from a large number of users?

a)

Interviews

b)

Surveys and Questionnaires

c)

Focus Groups

d)

Document Analysis

22.

Which of the following is a best practice for conducting interviews during requirement gathering?

a)

Avoid preparing detailed questions to keep the conversation flexible.

b)

Focus primarily on open-ended questions to encourage detailed responses.

c)

Involve various stakeholders to gather diverse and comprehensive insights.

d)

Conduct the interviews informally to make participants feel more comfortable.

23.

What is the main advantage of using prototypes during requirement gathering?

a)

They simplify the process by eliminating the need for extensive documentation.

b)

They help users visualize the system and provide valuable feedback on its design and functionality.

c)

They serve as a substitute for creating detailed functional requirements.

d)

They minimize the need for continuous involvement from stakeholders throughout the project.

24.

Which of the following is a challenge in gathering user requirements?

a)

Stakeholders clearly articulate all needs upfront.

b)

Requirements remain constant throughout the project.

c)

Communication barriers between stakeholders and developers.

d)

There is no need to prioritize requirements.