Name: _____________________________________________ Score: _______________________
Section: ____________________________________________ Date: ________________________
.
Part 1: Multiple Choice:
INSTRUCTION: Encircle the letter of the correct answer.
1. Which of the following defines user requirements?
A) Detailed technical requirements in programming language
B) High-level statements written in natural language
C) System constraints in mathematical notation
D) Functional model requirements for programmers
2. What type of requirements are related to system services and functionalities?
A) Non-functional requirements
B) Functional requirements
C) Domain requirements
D) Process requirements
3. Which of the following is a non-functional requirement example?
A) The system must support 100 concurrent users.
B) The user shall be able to log in with an ID and password.
C) A user can submit requests via the form.
D) The system generates daily reports.
4. Requirements Elicitation is primarily focused on:
A) Testing system functionality
B) Gathering stakeholder needs and preferences
C) Writing programming code
D) Developing software prototypes
5. Which is NOT a step in the requirements engineering process?
A) Requirements elicitation
B) Requirements validation
C) Software development
D) Requirements management
6. Which stakeholders are typically involved in requirements discovery?
A) Only end-users
B) Only project managers
C) End-users, domain experts, and developers
D) System engineers only
7. In requirements management, traceability refers to:
A) Tracking errors in the code
B) Mapping requirements to system design and code
C) Managing user complaints
D) Documenting user needs in narrative form
Page 1 of 3
8. Agile methods for requirements engineering often use which of the following?
A) User stories
B) Extensive requirements documentation
C) Incremental development
D) Short release cycles
9. A scenario in requirements engineering often includes:
A) Source code
B) A description of the starting situation and flow of events
C) A description of all possible system errors
D) Only visual diagrams
10. Requirements validation ensures that:
A) Requirements meet the client’s needs and are feasible
B) Requirements are cost-effective
C) The project can be completed within budget
D) Requirements adhere to company policies
Part 2: Word Pool Identification
Instruction: Use the words in the word pool to fill in each blank with the most appropriate term. Each word
should be used only once, and not all words in the word pool will necessarily be used.
Functional Non-Functional Domain Requirements Requirements
Requirements Requirements Requirements Elicitation Validation
System Change
User Requirements Completeness Consistency
Requirements Management
System Test
Goal Use Case Traceability Stakeholders
Engineer
1. Requirements Elicitation is the process of discovering and documenting requirements.
2. Non-functional requirements are system properties like reliability, performance, and
security.
3. Requirements from the environment in which the system operates are called Domain
requirements
4. The end-users, clients, and engineers involved in a system are referred to as Stakeholders.
5. A Use Case is an interaction scenario in UML.
6. Requirements Validation ensures that all requirements are included and conflicts are
resolved.
7. The initial step in requirements gathering is called Requirements Elicitation.
8. User Requirements refers to the high-level statements of what the system should do.
9. A Functional requirements defines the specific services the system must provide.
10. Requirements Validation checks if requirements truly align with the client’s needs.
11. Requirements should aim for Consistency to avoid contradictory information.
12. Traceability involves connecting requirements to their source and impact in design.
Page 2 of 3
13. Change Management in requirements management deals with documenting and
controlling changes.
14. System Test Engineer uses the Requirement Document to create/develop validation tests
for the software system.
15. Goal describes an idealized intention, like "ease of use.
Part 3: True or False
Instruction: Draw a HEART (♥) if the statements are True and Draw a STAR (★) if the statements are
False.
1. _★_ Requirements should only focus on what the system should do, not on constraints or
limitations.
2. _★_ Functional requirements generally describe constraints like performance and reliability.
3. _♥_ A use case typically describes an interaction from a user’s perspective.
4. _♥_ Completeness in requirements means including descriptions of all required facilities.
5. _★_ Agile methods discourage all types of requirements documentation.
6. _★_ Requirements change management is unnecessary once the system is fully
developed.
7. _♥_ Requirements validation includes ensuring the feasibility of the requirements.
8. _★_ Traceability in requirements means mapping requirements to specific test cases only.
9. _♥_ The spiral model of requirements engineering allows iterative refinement of
requirements.
10. _★_ Goals are specific, measurable requirements.
Page 3 of 3
