Understanding Software Requirements

What is the primary goal of requirements elicitation?

• To gather and understand stakeholder needs and expectations.

• To define the budget for the project.

• To create a project timeline.

• To assign tasks to team members.

Name two common techniques used in requirements elicitation.

• Brainstorming Sessions

• Interviews, Surveys

• Document Analysis

• Focus Groups

What is a user story in the context of software development?

• A user story is a description of a software feature from the end user's perspective.

• A user story is a technical specification for developers.

• A user story is a detailed project plan for software development.

• A user story is a list of programming tasks to be completed.

How do use cases differ from user stories?

• Use cases are always shorter than user stories.

• Use cases focus on technical requirements, while user stories focus on business goals.

• User stories are detailed and scenario-based, while use cases are brief and user-focused.

• Use cases are detailed and scenario-based, while user stories are brief and user-focused.

What is the purpose of stakeholder interviews in requirements gathering?

• To finalize the project budget and timeline

• To evaluate team performance during the project

• To conduct market research for competitors

• The purpose of stakeholder interviews in requirements gathering is to collect insights and expectations to inform project requirements.

Describe the role of prototyping in requirements elicitation.

• Prototyping is only useful for testing software performance.

• Prototyping is primarily used for coding the final product.

• Prototyping eliminates the need for user feedback entirely.

• Prototyping helps clarify and refine requirements by providing a visual and interactive representation of the system.

What are acceptance criteria in user stories?

• Acceptance criteria are the same as user stories.

• Acceptance criteria are only for testing purposes.

• Acceptance criteria define the conditions for a user story to be accepted as complete.

• Acceptance criteria are optional for user stories.

How can brainstorming sessions aid in requirements gathering?

• They create a rigid structure for ideas.

• Brainstorming sessions aid in requirements gathering by facilitating collaboration, encouraging diverse perspectives, and fostering creativity to uncover and clarify project needs.

• They focus solely on individual contributions.

• They limit discussion to a single perspective.

What is the significance of the 'As a [user], I want [goal]' format in user stories?

• It is a method for tracking project budgets.

• It focuses solely on technical specifications.

• It eliminates the need for user feedback.

• It provides clarity on user needs and goals, guiding development efforts.

Explain the importance of validating requirements with stakeholders.

• Stakeholders should not be involved in the requirements process.

• Validation is primarily for technical teams, not stakeholders.

• Validating requirements with stakeholders is crucial for ensuring alignment with their needs, identifying misunderstandings early, and fostering satisfaction.

• Validating requirements is only necessary for large projects.