Q1. Requirements Engineering is concerned with:
(A) Writing code
(B) Defining and managing requirements
(C) Installing software
(D) Selling products
Answer: (B) Defining and managing requirements
Q2. The first activity in Requirements Engineering is:
(A) Design
(B) Requirement Elicitation
(C) Testing
(D) Deployment
Answer: (B) Requirement Elicitation
Q3. Functional requirements describe:
(A) System behavior
(B) Development cost
(C) Hardware type
(D) Office location
Answer: (A) System behavior
Q4. Non-functional requirements describe:
(A) Features
(B) Quality attributes
(C) Code length
(D) Database name
Answer: (B) Quality attributes
Q5. SRS stands for:
(A) Software Requirement Specification
(B) System Run Setup
(C) Software Runtime Service
(D) System Requirement Setup
Answer: (A) Software Requirement Specification
Q6. Requirement elicitation involves:
(A) Gathering requirements from stakeholders
(B) Writing code
(C) Testing modules
(D) Installing OS
Answer: (A) Gathering requirements from stakeholders
Q7. Stakeholders are:
(A) Developers only
(B) People interested in the system
(C) Testers only
(D) Managers only
Answer: (B) People interested in the system
Q8. Interview is a technique of:
(A) Testing
(B) Requirement elicitation
(C) Deployment
(D) Coding
Answer: (B) Requirement elicitation
Q9. Questionnaire is useful when:
(A) Few stakeholders
(B) Many stakeholders
(C) No users
(D) No budget
Answer: (B) Many stakeholders
Q10. Observation technique is used to:
(A) Watch users perform tasks
(B) Write documentation
(C) Test system
(D) Install software
Answer: (A) Watch users perform tasks
Q11. Requirement analysis helps to:
(A) Clarify requirements
(B) Write code
(C) Deploy system
(D) Fix bugs
Answer: (A) Clarify requirements
Q12. Requirement validation ensures:
(A) Correct code
(B) Requirements are correct and complete
(C) Fast internet
(D) Hardware support
Answer: (B) Requirements are correct and complete
Q13. Ambiguous requirements are:
(A) Clear
(B) Unclear
(C) Complete
(D) Verified
Answer: (B) Unclear
Q14. A good requirement should be:
(A) Ambiguous
(B) Testable
(C) Complex
(D) Optional
Answer: (B) Testable
Q15. Requirement management deals with:
(A) Coding
(B) Controlling requirement changes
(C) Testing
(D) Marketing
Answer: (B) Controlling requirement changes
Q16. Traceability means:
(A) Tracking requirement changes
(B) Deleting requirements
(C) Coding faster
(D) Ignoring stakeholders
Answer: (A) Tracking requirement changes
Q17. Forward traceability links:
(A) Requirements to design and code
(B) Code to hardware
(C) Testing to deployment
(D) Budget to salary
Answer: (A) Requirements to design and code
Q18. Backward traceability links:
(A) Code to requirements
(B) Hardware to users
(C) Testing to maintenance
(D) Design to planning
Answer: (A) Code to requirements
Q19. Business requirements describe:
(A) Organizational goals
(B) Code syntax
(C) Database schema
(D) UI design
Answer: (A) Organizational goals
Q20. User requirements describe:
(A) User expectations
(B) Hardware type
(C) Coding language
(D) Network cables
Answer: (A) User expectations
Q21. System requirements describe:
(A) Detailed system functions
(B) Office rules
(C) Electricity
(D) Marketing plan
Answer: (A) Detailed system functions
Q22. Use case diagram is used to:
(A) Model user interactions
(B) Write code
(C) Test modules
(D) Deploy system
Answer: (A) Model user interactions
Q23. Prototyping helps in:
(A) Understanding requirements
(B) Deleting requirements
(C) Increasing cost
(D) Hardware design
Answer: (A) Understanding requirements
Q24. Requirement conflicts occur when:
(A) Stakeholders disagree
(B) Code runs fast
(C) Hardware fails
(D) Budget increases
Answer: (A) Stakeholders disagree
Q25. Requirement prioritization helps to:
(A) Decide important requirements
(B) Delete all requirements
(C) Ignore users
(D) Reduce testing
Answer: (A) Decide important requirements
Q26. Feasibility study checks:
(A) Technical and economic viability
(B) Code errors
(C) UI color
(D) Office space
Answer: (A) Technical and economic viability
Q27. Functional requirement example is:
(A) System shall generate report
(B) System shall be secure
(C) System shall be fast
(D) System shall be reliable
Answer: (A) System shall generate report
Q28. Performance requirement is a type of:
(A) Functional requirement
(B) Non-functional requirement
(C) Business requirement
(D) User requirement
Answer: (B) Non-functional requirement
Q29. Reliability is a:
(A) Functional requirement
(B) Non-functional requirement
(C) Code error
(D) Stakeholder
Answer: (B) Non-functional requirement
Q30. Requirement specification document should be:
(A) Clear and concise
(B) Ambiguous
(C) Incomplete
(D) Complex
Answer: (A) Clear and concise
Q31. Volatility in requirements means:
(A) Stability
(B) Frequent changes
(C) No changes
(D) Fixed budget
Answer: (B) Frequent changes
Q32. Brainstorming is used for:
(A) Generating ideas
(B) Testing
(C) Coding
(D) Deployment
Answer: (A) Generating ideas
Q33. JAD stands for:
(A) Joint Application Development
(B) Java Application Design
(C) Job Analysis Document
(D) Joint Analysis Data
Answer: (A) Joint Application Development
Q34. Requirement baseline means:
(A) Approved version of requirements
(B) Deleted requirements
(C) Draft version
(D) Random file
Answer: (A) Approved version of requirements
Q35. Change request is submitted when:
(A) New requirement arises
(B) Code runs well
(C) Testing completes
(D) Deployment finishes
Answer: (A) New requirement arises
Q36. Requirement review is done to:
(A) Detect errors
(B) Increase errors
(C) Delete documentation
(D) Ignore stakeholders
Answer: (A) Detect errors
Q37. Validation answers:
(A) Are we building the right product?
(B) Are we building the product right?
(C) Is hardware correct?
(D) Is budget enough?
Answer: (A) Are we building the right product?
Q38. Verification answers:
(A) Are we building the right product?
(B) Are we building the product right?
(C) Is hardware correct?
(D) Is network fast?
Answer: (B) Are we building the product right?
Q39. Domain requirements come from:
(A) Application domain
(B) Coding language
(C) Hardware vendor
(D) Office policy
Answer: (A) Application domain
Q40. Constraints in requirements may include:
(A) Legal restrictions
(B) Code comments
(C) UI colors
(D) Logo design
Answer: (A) Legal restrictions
Q41. SMART requirements are:
(A) Specific, Measurable, Achievable, Relevant, Time-bound
(B) Simple, Modern, Accurate, Real, Technical
(C) Small, Manual, Active, Random, Testable
(D) Secure, Manageable, Agile, Reliable, Traceable
Answer: (A) Specific, Measurable, Achievable, Relevant, Time-bound
Q42. Requirement elicitation techniques include:
(A) Interview and survey
(B) Coding and testing
(C) Deployment and maintenance
(D) Installation and setup
Answer: (A) Interview and survey
Q43. Incomplete requirements lead to:
(A) Project failure
(B) Faster coding
(C) Less cost
(D) Better quality
Answer: (A) Project failure
Q44. Requirements should be documented in:
(A) SRS
(B) Code file
(C) Test report
(D) User manual
Answer: (A) SRS
Q45. Requirement negotiation resolves:
(A) Conflicts
(B) Code errors
(C) Hardware faults
(D) Network issues
Answer: (A) Conflicts
Q46. Functional decomposition breaks system into:
(A) Smaller functions
(B) Larger modules
(C) Hardware parts
(D) Test cases
Answer: (A) Smaller functions
Q47. Use case scenario describes:
(A) Interaction steps
(B) Code structure
(C) Database schema
(D) Hardware layout
Answer: (A) Interaction steps
Q48. Requirement attributes include:
(A) Priority and status
(B) Screen size
(C) CPU speed
(D) Disk space
Answer: (A) Priority and status
Q49. Requirement engineering reduces:
(A) Development risk
(B) Hardware cost
(C) Electricity usage
(D) UI design
Answer: (A) Development risk
Q50. The ultimate goal of Requirements Engineering is:
(A) Deliver correct and complete requirements
(B) Increase documentation
(C) Reduce users
(D) Delete system
Answer: (A) Deliver correct and complete requirements
Q51. Requirement elicitation is primarily concerned with:
(A) Writing code
(B) Collecting stakeholder needs
(C) Testing modules
(D) Hardware installation
Answer: (B) Collecting stakeholder needs
Q52. Requirement ambiguity can cause:
(A) Misunderstanding and errors
(B) Faster development
(C) Lower cost
(D) Hardware efficiency
Answer: (A) Misunderstanding and errors
Q53. Prototyping is particularly useful for:
(A) Clarifying unclear requirements
(B) Coding only
(C) Deployment only
(D) Testing only
Answer: (A) Clarifying unclear requirements
Q54. Joint Application Development (JAD) involves:
(A) Stakeholders and developers working together
(B) Coding only
(C) Deployment planning
(D) Hardware installation
Answer: (A) Stakeholders and developers working together
Q55. Observation technique captures:
(A) Actual user behavior
(B) Code errors
(C) Hardware configuration
(D) Deployment logs
Answer: (A) Actual user behavior
Q56. Brainstorming in requirements helps:
(A) Generate multiple ideas
(B) Test code
(C) Deploy software
(D) Install OS
Answer: (A) Generate multiple ideas
Q57. A requirement is testable if:
(A) Its correctness can be verified
(B) It is ambiguous
(C) It is vague
(D) It is optional
Answer: (A) Its correctness can be verified
Q58. Requirement conflict occurs due to:
(A) Differing stakeholder goals
(B) Hardware malfunction
(C) Coding errors
(D) Network failure
Answer: (A) Differing stakeholder goals
Q59. Prioritization of requirements is needed to:
(A) Focus on high-value requirements
(B) Ignore some users
(C) Reduce coding
(D) Increase cost
Answer: (A) Focus on high-value requirements
Q60. Feasibility study ensures:
(A) Technical, operational, and economic viability
(B) Coding efficiency
(C) UI design
(D) Network optimization
Answer: (A) Technical, operational, and economic viability
Q61. Requirements baseline refers to:
(A) Approved set of requirements
(B) Draft version
(C) Deleted requirements
(D) Random code
Answer: (A) Approved set of requirements
Q62. Change management is needed to:
(A) Handle evolving requirements
(B) Install software
(C) Fix hardware
(D) Increase cost
Answer: (A) Handle evolving requirements
Q63. Requirement traceability ensures:
(A) Each requirement is linked to design and code
(B) Hardware is efficient
(C) Coding speed increases
(D) Network is reliable
Answer: (A) Each requirement is linked to design and code
Q64. Forward traceability tracks:
(A) Requirements → Design → Code
(B) Hardware → Software → Users
(C) Budget → Staff → Timeline
(D) Testing → Coding → Deployment
Answer: (A) Requirements → Design → Code
Q65. Backward traceability tracks:
(A) Code → Design → Requirements
(B) Users → Hardware → Network
(C) Budget → Timeline → Staff
(D) Deployment → Testing → Coding
Answer: (A) Code → Design → Requirements
Q66. Requirement volatility refers to:
(A) Frequency of changes in requirements
(B) Stability
(C) Code efficiency
(D) Hardware upgrades
Answer: (A) Frequency of changes in requirements
Q67. Business requirements define:
(A) Organizational objectives
(B) Code structure
(C) Testing plan
(D) Hardware configuration
Answer: (A) Organizational objectives
Q68. User requirements describe:
(A) Needs and expectations of users
(B) Hardware specs
(C) Deployment plan
(D) Coding standards
Answer: (A) Needs and expectations of users
Q69. System requirements include:
(A) Detailed specifications for the software system
(B) Office rules
(C) Marketing strategy
(D) Budget allocation
Answer: (A) Detailed specifications for the software system
Q70. Functional decomposition is used to:
(A) Break down system functions into smaller components
(B) Merge requirements
(C) Delete modules
(D) Install software
Answer: (A) Break down system functions into smaller components
Q71. Use case describes:
(A) Interaction between user and system
(B) Hardware configuration
(C) Coding style
(D) Deployment procedure
Answer: (A) Interaction between user and system
Q72. Requirement review helps to:
(A) Detect errors early
(B) Delay coding
(C) Increase bugs
(D) Reduce hardware cost
Answer: (A) Detect errors early
Q73. Validation of requirements answers:
(A) Are we building the right system?
(B) Are we building the system right?
(C) Is hardware correct?
(D) Is network fast?
Answer: (A) Are we building the right system?
Q74. Verification of requirements answers:
(A) Are we building the system right?
(B) Are we building the right system?
(C) Is budget enough?
(D) Is hardware compatible?
Answer: (A) Are we building the system right?
Q75. Domain requirements are derived from:
(A) Application domain rules
(B) Coding standards
(C) Hardware manuals
(D) Marketing policy
Answer: (A) Application domain rules
Q76. Constraints in requirements include:
(A) Legal, regulatory, and technology limits
(B) Code comments
(C) UI colors
(D) Office policies
Answer: (A) Legal, regulatory, and technology limits
Q77. Requirement elicitation errors can lead to:
(A) Project failure
(B) Faster deployment
(C) Lower cost
(D) Better performance
Answer: (A) Project failure
Q78. SMART requirements are:
(A) Specific, Measurable, Achievable, Relevant, Time-bound
(B) Simple, Modern, Accurate, Real, Technical
(C) Small, Manual, Agile, Random, Testable
(D) Secure, Manageable, Agile, Reliable, Traceable
Answer: (A) Specific, Measurable, Achievable, Relevant, Time-bound
Q79. Prototyping helps in:
(A) Early validation of requirements
(B) Deploying hardware
(C) Coding faster
(D) Marketing the software
Answer: (A) Early validation of requirements
Q80. Requirement negotiation resolves:
(A) Conflicts among stakeholders
(B) Coding errors
(C) Hardware issues
(D) Deployment delays
Answer: (A) Conflicts among stakeholders
Q81. Requirement documentation is critical for:
(A) Maintenance and traceability
(B) Faster coding
(C) Lower cost
(D) Hardware setup
Answer: (A) Maintenance and traceability
Q82. Functional requirement example:
(A) System shall generate monthly reports
(B) System shall be secure
(C) System shall have high performance
(D) System shall be reliable
Answer: (A) System shall generate monthly reports
Q83. Non-functional requirement example:
(A) System shall respond within 2 seconds
(B) System shall generate report
(C) System shall add new users
(D) System shall validate input
Answer: (A) System shall respond within 2 seconds
Q84. Requirement elicitation techniques include:
(A) Interview, Questionnaire, Observation
(B) Coding, Testing, Deployment
(C) Hardware installation, Networking, Marketing
(D) Design, Implementation, Maintenance
Answer: (A) Interview, Questionnaire, Observation
Q85. Requirement completeness means:
(A) All necessary requirements are included
(B) Code is error-free
(C) Hardware is installed
(D) Deployment is finished
Answer: (A) All necessary requirements are included
Q86. Requirement correctness means:
(A) Requirement reflects stakeholder intent
(B) Code runs correctly
(C) UI is designed
(D) Network is functional
Answer: (A) Requirement reflects stakeholder intent
Q87. Requirement consistency ensures:
(A) No conflicting requirements
(B) Faster coding
(C) Hardware compatibility
(D) Deployment readiness
Answer: (A) No conflicting requirements
Q88. Requirement traceability helps in:
(A) Linking requirements to design and tests
(B) Coding faster
(C) Hardware installation
(D) Marketing strategy
Answer: (A) Linking requirements to design and tests
Q89. Requirement management tools help to:
(A) Track changes and versions
(B) Code faster
(C) Deploy hardware
(D) Install OS
Answer: (A) Track changes and versions
Q90. Forward traceability ensures:
(A) Each requirement is implemented in design and code
(B) Hardware is compatible
(C) Network is fast
(D) Budget is sufficient
Answer: (A) Each requirement is implemented in design and code
Q91. Backward traceability ensures:
(A) Each code element maps to a requirement
(B) UI is attractive
(C) Hardware is installed
(D) Deployment is fast
Answer: (A) Each code element maps to a requirement
Q92. Requirement validation techniques include:
(A) Reviews, Prototyping, Test cases
(B) Coding, Debugging, Deployment
(C) Hardware testing, Network setup, Marketing
(D) UI design, Logo creation, Documentation
Answer: (A) Reviews, Prototyping, Test cases
Q93. Requirements engineering helps to:
(A) Reduce development risks
(B) Increase bugs
(C) Deploy hardware
(D) Install OS
Answer: (A) Reduce development risks
Q94. Requirement elicitation is iterative because:
(A) Stakeholder needs may change
(B) Coding is slow
(C) Testing is hard
(D) Deployment takes time
Answer: (A) Stakeholder needs may change
Q95. Requirement conflict resolution may involve:
(A) Negotiation among stakeholders
(B) Ignoring some stakeholders
(C) Deleting requirements
(D) Skipping design
Answer: (A) Negotiation among stakeholders
Q96. Requirement prioritization criteria include:
(A) Business value, Risk, Cost
(B) UI color, Font, Logo
(C) Hardware type, Disk, CPU
(D) Network speed, Bandwidth, Latency
Answer: (A) Business value, Risk, Cost
Q97. Requirement elicitation failures lead to:
(A) Cost overruns and delays
(B) Faster development
(C) Less documentation
(D) Hardware upgrade
Answer: (A) Cost overruns and delays
Q98. Requirement change control ensures:
(A) Controlled modifications to requirements
(B) Faster coding
(C) Hardware efficiency
(D) Network stability
Answer: (A) Controlled modifications to requirements
Q99. Requirements should be:
(A) Complete, Consistent, Correct, Feasible, Verifiable
(B) Ambiguous, Vague, Optional, Redundant
(C) Deleted, Ignored, Complex, Unclear
(D) Random, Optional, Technical, Impossible
Answer: (A) Complete, Consistent, Correct, Feasible, Verifiable
Q100. The ultimate goal of Requirements Engineering is:
(A) Deliver software that meets stakeholder needs
(B) Increase code length
(C) Install hardware
(D) Reduce budget
Answer: (A) Deliver software that meets stakeholder needs