WorksheetsChapter 1 – Introduction to Requirements Engineering
Total questions: 25
Worksheet time: 13mins
What is the main goal of Requirements Engineering?
Coding
Testing
Understanding user needs
Debugging
A requirement must be agreed by:
Developers only
Users only
All stakeholders
Testers
Which of the following is a functional requirement?
Response time
Security level
Login feature
Availability
Which of the following is NOT a stakeholder?
User
Manager
Compiler
Developer
Elicitation in Requirements Engineering means:
Writing code
Testing the system
Gathering requirements
Managing the budget
Which activity is NOT part of the Requirements Engineering process?
Elicitation
Documentation
Validation & Negotiation
Coding
Why is it difficult to discover requirements directly from users?
Users refuse interviews
Users may not clearly express what they need
Users are not experts
Users only want technical details
Which requirement focuses on usability, performance, and reliability?
Functional requirement
Business requirement
Non-functional (quality) requirement
User requirement
Which of the following is a constraint?
The system shall allow user registration
The system shall calculate turbine stress
The system shall run on Windows and Mac OS
The system shall generate reports
Which is an example of a verifiable non-functional requirement?
The system should be user-friendly
The system should look modern
Users shall complete training within 2 hours
The system should be easy to learn
Why should requirements be documented early?
To increase development cost
To reduce testing
To save time and reduce rework later
To replace user interviews
Who is the primary source of real user requirements?
Developers
Testers
Users
System architects
Which of the following describes a functional requirement correctly?
How fast the system runs
What services the system provides
How secure the system is
How reliable the system is
Which obstacle to RE is related to overconfidence by developers?
Users cannot express needs
Developers think they already know user needs
Lack of documentation tools
Tight deadlines
Which quality attribute can be measured using “mean time to failure”?
Usability
Reliability
Portability
Size
Requirements Engineering is done after coding.
True
False
Stakeholders include users and managers.
True
False
Non-functional requirements describe system behaviour in detail.
True
False
“Easy to use” is a measurable requirement.
True
False
Documentation helps reduce rework.
True
False
Functional requirements describe system services.
True
False
Users always know exactly what they want.
True
False
Validation checks the correctness of requirements.
True
False
Requirements Engineering is not important for small systems.
True
False
Poor requirements increase project risk.
True
False
