Q.1 What is the primary goal of requirements engineering?
To design the software architecture
To gather and define what the system should do
To implement the software code
To test the software system
Explanation - Requirements engineering focuses on identifying, documenting, and maintaining the needs and expectations of stakeholders for a system.
Correct answer is: To gather and define what the system should do
Q.2 Which type of requirement defines the functions the system must perform?
Functional requirement
Non-functional requirement
User requirement
Design requirement
Explanation - Functional requirements describe specific behaviors, functions, or services that the system must provide.
Correct answer is: Functional requirement
Q.3 Non-functional requirements usually describe:
What the system should do
How the system performs its functions
The database schema
Programming languages to use
Explanation - Non-functional requirements define quality attributes like performance, reliability, security, and usability.
Correct answer is: How the system performs its functions
Q.4 Which activity is NOT part of requirements engineering?
Requirements elicitation
Requirements validation
Code optimization
Requirements specification
Explanation - Requirements engineering focuses on defining and validating requirements, not on code-level optimization.
Correct answer is: Code optimization
Q.5 Which technique is commonly used for requirements elicitation?
Interviews with stakeholders
Writing code modules
Load testing
Compiling the system
Explanation - Elicitation involves gathering information from users, clients, and other stakeholders using interviews, questionnaires, observation, and workshops.
Correct answer is: Interviews with stakeholders
Q.6 A use case primarily describes:
Hardware requirements
User interactions with the system
Database normalization
Code debugging procedures
Explanation - Use cases are used to model system behavior by describing interactions between users (actors) and the system to achieve specific goals.
Correct answer is: User interactions with the system
Q.7 Requirements validation ensures that:
The system meets stakeholder needs
The system code is optimized
The database is normalized
The network is secure
Explanation - Validation checks that the documented requirements accurately reflect the stakeholders' intentions and are feasible.
Correct answer is: The system meets stakeholder needs
Q.8 Which document formally records software requirements?
Software Requirements Specification (SRS)
Design Document
Test Plan
User Manual
Explanation - The SRS defines functional and non-functional requirements and serves as a reference throughout the development process.
Correct answer is: Software Requirements Specification (SRS)
Q.9 Ambiguous requirements are problematic because:
They are too detailed
Different people may interpret them differently
They are easy to implement
They reduce system security
Explanation - Ambiguity can lead to misunderstandings and errors in system design and implementation.
Correct answer is: Different people may interpret them differently
Q.10 Stakeholder analysis is important in requirements engineering because:
It identifies who provides and who uses requirements
It defines the system architecture
It optimizes algorithms
It helps in writing test cases
Explanation - Understanding stakeholders ensures that all relevant requirements are captured from the right sources.
Correct answer is: It identifies who provides and who uses requirements
Q.11 Which is a key challenge in requirements engineering?
Changing requirements during development
Writing unit tests
Optimizing code execution
Configuring the IDE
Explanation - Requirements often evolve due to changing business needs, and managing these changes is a major challenge.
Correct answer is: Changing requirements during development
Q.12 Requirements traceability refers to:
Tracking the origin and status of requirements throughout development
Tracking bugs in the code
Monitoring server performance
Documenting test results
Explanation - Traceability ensures that each requirement is implemented, tested, and validated correctly.
Correct answer is: Tracking the origin and status of requirements throughout development
Q.13 A requirement that describes system performance expectations is:
Functional requirement
Non-functional requirement
Business requirement
Interface requirement
Explanation - Performance, reliability, scalability, and security are examples of non-functional requirements.
Correct answer is: Non-functional requirement
Q.14 Which of the following is NOT a requirement elicitation technique?
Prototyping
Observation
Algorithm optimization
Workshops
Explanation - Algorithm optimization is related to implementation, not requirements elicitation.
Correct answer is: Algorithm optimization
Q.15 A requirement that cannot be directly verified by testing is usually:
Functional requirement
Non-functional requirement
Design requirement
Implementation requirement
Explanation - Some non-functional requirements, like maintainability or usability, may need subjective evaluation rather than direct testing.
Correct answer is: Non-functional requirement
Q.16 Which of the following is a business requirement?
The system shall process 1000 transactions per minute
The system shall support multiple user roles
The company wants to increase customer satisfaction
The system shall encrypt sensitive data
Explanation - Business requirements express high-level goals and objectives of the organization, not technical specifications.
Correct answer is: The company wants to increase customer satisfaction
Q.17 The process of analyzing requirements to identify conflicts, ambiguities, or missing information is called:
Requirements elicitation
Requirements analysis
Requirements validation
Requirements implementation
Explanation - Analysis ensures that requirements are complete, consistent, and clear before implementation begins.
Correct answer is: Requirements analysis
Q.18 A use case diagram is used to:
Visualize interactions between users and the system
Document database tables
Define software architecture
List all code modules
Explanation - Use case diagrams help in understanding functional requirements from the perspective of the user.
Correct answer is: Visualize interactions between users and the system
Q.19 Requirements prioritization is necessary because:
Not all requirements can be implemented due to resource constraints
All requirements are mandatory
Testing does not depend on requirements
Design is independent of requirements
Explanation - Prioritization helps in focusing on the most important requirements for successful project delivery.
Correct answer is: Not all requirements can be implemented due to resource constraints
Q.20 Which of the following represents a SMART requirement?
The system should be fast
The system shall process 500 orders per hour within 3 months
The system should have good security
The system shall look modern
Explanation - SMART requirements are Specific, Measurable, Achievable, Relevant, and Time-bound.
Correct answer is: The system shall process 500 orders per hour within 3 months
Q.21 Requirements elicitation should involve:
Only developers
Stakeholders, users, and domain experts
Only testers
Only project managers
Explanation - Involving all relevant parties ensures that all perspectives are captured and requirements are comprehensive.
Correct answer is: Stakeholders, users, and domain experts
Q.22 A requirement conflict occurs when:
Two requirements contradict each other
Requirements are well-defined
Requirements are too general
Requirements are non-functional
Explanation - Conflicting requirements can lead to design and implementation issues and must be resolved during analysis.
Correct answer is: Two requirements contradict each other
Q.23 Traceability matrix is used to:
Link requirements to design, code, and tests
Store user passwords
Monitor server logs
Document team meetings
Explanation - A traceability matrix ensures that each requirement is implemented and verified throughout the development lifecycle.
Correct answer is: Link requirements to design, code, and tests
Q.24 Which of the following is an example of a functional requirement?
The system shall allow users to log in using email and password
The system shall respond within 2 seconds
The system shall be easy to use
The system shall encrypt all sensitive data
Explanation - Functional requirements define specific functions or features that the system must provide.
Correct answer is: The system shall allow users to log in using email and password
Q.25 Requirements evolution refers to:
Changes to requirements during the software lifecycle
Testing new software features
Writing code modules
Creating UML diagrams
Explanation - Requirements may evolve due to changing business needs, technology, or stakeholder expectations, and this must be managed carefully.
Correct answer is: Changes to requirements during the software lifecycle