WorksheetsRequirements Engineering Worksheet MCQs
Total questions: 40
Worksheet time: 20mins
Requirements Engineering is primarily concerned with
Coding the system
Defining and documenting requirements
Testing the software
Deploying the software
The main goal of Requirements Engineering is to ensure the system meets the needs of
Developers
Testers
Stakeholders
Network administrators
Requirements Engineering bridges the gap between
Users and hardware
What users want and what developers build
Testing and maintenance
Design and documentation
Before designing an ATM system, Requirements Engineering helps identify
Cash availability only
User interface colors
User expectations like withdrawal limits and security
The bank logo
Which of the following is NOT an outcome of good Requirements Engineering?
Reduced rework
Increased cost
Better communication
Stakeholder satisfaction
Which problem occurs due to unclear requirements?
Better design quality
Faster testing
Scope creep
Improved traceability
Requirements Engineering helps avoid
User feedback
Misunderstandings and budget overruns
Software installation
Code optimization
Requirements Engineering is performed during
Deployment phase
Early phase of SDLC
Testing phase
Maintenance phase
A major reason for project failure is
High-quality testing
Unclear or changing requirements
Over-documentation
Lack of coding standards
Business requirements describe
Low-level coding details
High-level organizational goals
Test procedures
User interfaces
User requirements are expressed from the viewpoint of
Developers
End-users
System analysts
Test engineers
Functional requirements define
How the system performs
What the system should do
The project budget
Testing conditions
Non-functional requirements define
Software features
How the system performs its functions
The developer’s role
Business models
System requirements specify
Only software algorithms
Hardware, software, and network details
User training materials
Business profits
Which of the following is a non-functional requirement?
The system shall allow login
The system shall process 500 requests per second
The user shall create an account
The system shall send an email
A functional requirement example is
The website should load within 2 seconds
The system shall authenticate the user
The system must be secure
The software must run on Linux
The first stage in the Requirements Engineering process is
Requirement Validation
Feasibility Study
Requirements Analysis
Requirements Specification
The purpose of feasibility study is to determine
Project deadlines
Technical and financial viability
Team size
Programming language
The main goal of Requirements Elicitation is to
Test software modules
Understand what stakeholders expect
Write code
Debug programs
Requirements Analysis focuses on
Testing performance
Detecting conflicts and priorities
Deploying the software
Fixing bugs
Requirements Specification results in
Feasibility report
SRS document
Test case report
Design document
Requirements Validation ensures
Code is written correctly
Documented requirements reflect user needs
Network is stable
Interface is colorful
Requirements Management deals with
Change control and traceability
User interface design
Code refactoring
Test automation
A tool often used in Requirements Analysis is
Compiler
Data Flow Diagram (DFD)
Version control system
Browser
Functional requirements are mainly derived from
Business strategies
User interactions and business rules
Testing documents
Marketing reports
Which of the following is NOT a functional requirement?
Generate report
Manage transactions
Encrypt password
Response time less than 2 seconds
Which diagram best represents functional requirements?
Sequence diagram
Class diagram
Use case diagram
Network diagram
A good functional requirement should be
Ambiguous
Verifiable
Incomplete
Unmeasurable
Non-functional requirements include
Performance, security, usability
Algorithms, loops, arrays
Coding syntax
Testing errors
The quality attribute "usability" refers to
Speed of processing
Ease of use and accessibility
Data storage
Cost of maintenance
"System shall have 99.9% uptime" refers to
Reliability requirement
Functional requirement
Design constraint
Interface requirement
"System shall encrypt all passwords" is a
Functional requirement
Security requirement (non-functional)
Business rule
Data requirement
Requirements Engineering is carried out mainly by
System analysts
End-users
Database designers
Testers only
Stakeholders include
Only developers
Clients, users, and customers
Testers only
Designers only
A Requirements Engineering document acts as a
Test case file
Contract between client and developer
Programming guideline
Deployment script
Traceability in Requirements Engineering means
Linking each requirement to design and testing stages
Tracking user login attempts
Monitoring code size
Tracing system logs
Requirements evolve because
Technology and user needs change
Software never changes
Teams refuse to communicate
Budgets remain constant
Poorly written requirements lead to
Improved documentation
Project delays and cost overrun
Faster release
More clarity
Requirement Validation can be done using
Reviews, prototypes, and test cases
Debuggers
IDE tools
Network sniffers
The final output of the Requirements Engineering process is
Software code
Software Requirements Specification (SRS)
Design prototype
Test report
