RE 5 Elicitation

What is the primary goal of requirements elicitation?

• To gather and understand system requirements
• To write software code
• To perform system testing
• To document system bugs

Which of the following is a requirements elicitation technique?

• Interviews
• Debugging
• Deployment
• Regression Testing

Which technique involves directly speaking with stakeholders to gather requirements?

• Interviews
• Observation
• Prototyping
• Workshops

What is a major limitation of using questionnaires for requirements elicitation?

• Lack of interaction and clarification
• Takes too much time
• Does not work for small teams
• It is not scalable

Which elicitation technique is best suited for identifying implicit requirements?

• Observation
• Surveys
• Brainstorming
• Prototyping

Which technique gathers requirements from multiple stakeholders in a structured meeting?

• Workshops
• Questionnaires
• Interviews
• Regression Testing

What is an advantage of using prototyping in elicitation?

• It helps stakeholders visualize system functionality
• It replaces written documentation
• It speeds up the development process
• It reduces system testing efforts

Which of these is NOT a valid source of requirements?

• Stakeholders
• Existing System
• Project Documentation
• Random Internet Articles

Which stakeholder is usually responsible for defining business requirements?

• Clients or End-Users
• Software Testers
• System Architects
• Developers

Which of the following is a functional requirement?

• The system shall allow users to log in
• The system must respond in under 2 seconds
• The system should be available 99.9% of the time
• The application should support 1 million users