RE 2

What is the purpose of requirements engineering?

• To define, document, and manage system requirements
• To develop software code
• To perform system testing
• To deploy the system

Which of the following is NOT a source of requirements?

• Stakeholders
• Previous Systems
• Random Online Articles
• Documents

Which requirement type focuses on system constraints and attributes?

• Functional
• Non-functional
• Performance
• Usability

What does the 'SDP' mnemonic stand for in requirements elicitation?

• Stakeholders, Documents, Previous Systems
• Software, Design, Planning
• Systematic Data Processing
• Structured Development Process

In the Kano Model, which category includes features that delight users unexpectedly?

• Must-Have
• Performance Needs
• Excitement Needs
• Optional Features

Which requirement prioritization method uses categories like Must-Have, Should-Have, Could-Have, and Won't-Have?

• Kano Model
• MoSCoW Method
• Requirement Voting
• Negotiation Strategy

What is a key benefit of using goal diagrams in requirements engineering?

• Helps structure and link system goals
• Makes testing easier
• Avoids the need for documentation
• Replaces user stories

Which of the following is NOT a technique for avoiding ambiguity in documentation?

• Using precise terminology
• Standardized templates
• Avoiding diagrams
• Diagrams & Models

What does the 'CUBD' mnemonic stand for in successful negotiation?

• Communicate, Use structure, Be thorough, Do reviews
• Create, Update, Build, Deliver
• Communicate, Understand, Break conflicts, Document
• Clarify, Use Brainstorming, Define needs

What is the first activity in the requirements engineering process?

• Elicitation
• Negotiation
• Validation
• Prioritization