RE UTHM FINAL REVISION

Which of the following is NOT a requirement elicitation technique?

• Interview
• Questionnaire
• Observation
• Guessing

Answer explanation

Guessing is not an elicitation technique.

What is the main purpose of requirements documentation?

• To make development easier
• To ensure clarity and consistency
• To track project progress
• To validate stakeholder opinions

Answer explanation

Documentation ensures clarity and consistency.

Which of the following is NOT a functional requirement?

• User authentication
• System login
• Database encryption
• Data processing speed

Answer explanation

Database encryption is a non-functional requirement.

What is the main purpose of the Kano Model in requirements engineering?

• To determine system speed
• To categorize requirements based on satisfaction
• To organize documentation
• To define system security levels

Answer explanation

Kano Model categorizes requirements based on satisfaction.

Which of the following is an example of a non-functional requirement?

• The system shall support 1000 concurrent users
• Login functionality
• The user interface must be responsive
• System should be user-friendly

Answer explanation

This is a performance-based non-functional requirement.

In MoSCoW prioritization, which category is considered essential for system success?

• Must-Have
• Should-Have
• Could-Have
• Won’t-Have

Answer explanation

Must-Have requirements are critical to system success.

What is one way to avoid ambiguity in natural language requirements?

• Use vague terms
• Define terms clearly
• Use active voice
• Use diagrams and models

Answer explanation

Defining terms reduces ambiguity.

Which technique is best for capturing user interactions with a system?

• Workshops
• Use Case Diagrams
• Prototyping
• Mind Mapping

Answer explanation

Use Case Diagrams capture interactions.

Which of the following best describes traceability in requirements documentation?

• Ensuring all features are documented
• Tracking requirements throughout the project
• Clarifying software constraints
• Ensuring software reliability

Answer explanation

Traceability ensures requirements are tracked.

Why is voting important in requirements engineering?

• It ensures fairness
• It speeds up decision making
• It ensures transparency
• It helps in ranking requirements

Answer explanation

Voting helps in fair decision-making.