RE 3

Which of the following is a key aspect of requirements engineering?

• Defining and managing system requirements
• Writing program code
• Testing the software
• Deploying the system

Which of these is NOT a requirements elicitation technique?

• Interview
• Brainstorming
• Regression Testing
• Observation

Which requirement type describes what the system should do?

• Functional
• Non-functional
• Legal
• Usability

What is the purpose of a use case in requirements documentation?

• To describe user interactions with the system
• To test system performance
• To write system code
• To manage deployment

Why is stakeholder involvement critical in requirements engineering?

• To ensure the system meets business and user needs
• To help with system deployment
• To perform system testing
• To write technical documentation

Which of the following best defines requirements validation?

• Checking that the documented requirements are correct
• Ensuring system security
• Testing the system
• Optimizing the database

Which of these helps to avoid ambiguity in requirement documentation?

• Using clear and precise terminology
• Writing long descriptions
• Avoiding diagrams
• Skipping documentation

Which type of requirement focuses on usability, security, and performance?

• Non-functional
• Functional
• User
• Mandatory

What is the primary goal of requirement prioritization?

• To determine the most critical requirements
• To remove unnecessary features
• To validate system architecture
• To define user roles

Which of the following is a key challenge in requirement elicitation?

• Conflicting stakeholder needs
• Lack of system testing
• Insufficient programming knowledge
• Too much documentation