Quiz 2 Flashcards
Is the main goal of prototypes and mockups to check the adequacy of requirements from direct user feedback?
- True
- False
True
Artifact-based elicitation techniques involve analyzing existing documents and artifacts to extract requirements
- True
- False
True
In artifact-based elicitation, the primary focus is on direct interactions with stakeholders.
- True
- False
False
Stakeholder-driven techniques are generally less time-consuming compared to artifact-based techniques
- True
- False
False
A product vision statement should be highly detailed, including specific features and technical specifications of the product.
- True
- False
False
Questionnaires are a requirements elicitation technique commonly used to gather detailed and in-depth information directly from stakeholders.
- True
- False
False
Inconsistencies among stakeholders in needs and expectations are common challenges in requirements elicitation
- True
- False
True
Stakeholders who know their needs but can’t express them represent a challenge in requirements elicitation.
- True
- False
True
Stakeholders frequently neglect attributes and constraints, which is a typical problem in requirements elicitation.
- True
- False
True
Storyboards are typically created to showcase a product within a certain context.
- True
- False
True
What is the definition of requirements elicitation in software development?
- The process of testing software to ensure it meets quality standards.
- The process of coding software to meet specific requirements.
- The process of documenting requirements after a project is completed.
- The process of seeking, capturing, and consolidating requirements from available sources.
The process of seeking, capturing, and consolidating requirements from available sources.
What is one of the advantages of paper prototypes?
- Durability
- Complexity
- Lightweight
- High fidelity
Lightweight
What is one pro of interviews as a requirements elicitation technique?
- Less time spent
- Higher frequency of contact
- More individuals involved
- Stronger contact
Stronger contact
What is one cons of observation as a requirements elicitation technique?
- Find hidden problems
- Contextualization of the acquired information
- Focus on the system-as-is
- It is slow and expensive
It is slow and expensive
Which of the following is an advantage of using mockups as a requirements elicitation technique?
- Automatically generates code from requirements
- Facilitates detailed documentation of requirements
- Allows for real-time user feedback
- Eliminates the need for user involvement
Allows for real-time user feedback
What is one key characteristic of an “ideal” RE process?
- Adheres to tradition and not innovation
- Open Collaboration
- None of the above
- Short feedback cycles
Short feedback cycles
Which of the following is NOT an artifact-based elicitation techniques
- Brainstorming
- Background studies
- Prototypes
- Observation
Brainstorming
Observation
What is a key difference between storyboards and prototypes in the context of requirements engineering?
- Storyboards provide a visual sequence of events, while prototypes demonstrate functional aspects.
- Prototypes focus on high-level requirements, while storyboards detail low-level requirements.
- Prototypes are static representations, while storyboards are interactive.
- Storyboards are used for code generation, while prototypes are not.
Storyboards provide a visual sequence of events, while prototypes demonstrate functional aspects.
Which principle of Requirements Engineering emphasizes that requirements should be systematically managed and continuously refined?
- Evolution
- Systematic Work
- Innovation
- Shared Understanding
Evolution
What is the primary purpose of stakeholder-driven elicitation techniques like interviews and workshops?
- To analyze historical project documents for requirement derivation
- To ensure complete specifications are developed before design decisions
- To generate detailed system designs before requirement documentation
- To collect qualitative insights directly from individuals involved in the system
To collect qualitative insights directly from individuals involved in the system
Which principle of Requirements Engineering highlights the importance of ensuring that all stakeholders have a consistent and agreed-upon understanding of system requirements?
- Validation
- Shared Understanding
- Problems, Requirements & Solutions
- Risk-based Prioritization
Shared Understanding
During a requirements elicitation process, a team decides to conduct structured workshops where different stakeholders contribute based on their expertise. What is a key advantage of this approach?
- It minimizes time spent on requirement gathering
- It ensures requirement prioritization is dictated solely by technical feasibility
- It fosters negotiation and resolution of conflicting stakeholder viewpoints
- It eliminates the need for further validation after documentation
It fosters negotiation and resolution of conflicting stakeholder viewpoints
Which principle of Requirements Engineering focuses on balancing business objectives, technical feasibility, and stakeholder needs to ensure that requirements add tangible value to the system?
- Problems, Requirements & Solutions
- Evolution
- Systematic Work
- Value-Orientation
Value-Orientation
What is a key challenge when using Observation as a Requirements Elicitation technique?
- It is ineffective for identifying usability issues
- It requires all stakeholders to be physically present
- It may not capture tacit knowledge that users take for granted
- It prevents the discovery of hidden problems in current workflows
It may not capture tacit knowledge that users take for granted
