Software Requirements & Specification MCQs with Answers
Practice important Software Requirements & Specification MCQs with answers and explanations.
Multiple Choice Questions
Q61: What should functional requirements be like?
- A: Complete and consistent
- B: Ambiguous and flexible
- C: Irrelevant and minimal
- D: Untestable and vague
View Answer
A
Q62: Which of the following is a key characteristic of good software requirements?
- A: Feasible
- B: Invalid
- C: Unverifiable
- D: Unmodifiable
View Answer
A
Q63: Which of the following is NOT considered a software requirement?
- A: Functional requirements
- B: Non-functional requirements
- C: Design specifications
- D: Design implementations
View Answer
C
Q64: What does a design and implementation constraint do?
- A: Defines the desired functionality of the system
- B: Limits design and implementation options
- C: Describes the performance metrics
- D: Defines how the system will be tested
View Answer
B
Q65: Which of the following is an example of a functional requirement?
- A: The system shall be able to process payments
- B: The system shall not allow user errors
- C: The system shall be developed on open-source tools
- D: The system shall meet security standards
View Answer
A
Q66: What is the relationship between software processes and software engineering?
- A: Software processes are steps that help organize software development activities
- B: Software processes are just a series of random steps
- C: Software processes focus only on documentation
- D: Software processes involve only testing activities
View Answer
A
Q67: What is the role of the RE process in software development?
- A: To ensure that the system meets the defined requirements
- B: To write code for system features
- C: To test the system before deployment
- D: To design the system architecture
View Answer
A
Q68: Which of the following activities is NOT part of the Requirements Engineering process?
- A: Requirements management
- B: Requirements elicitation
- C: Requirements testing
- D: Requirements validation
View Answer
C
Q69: What is the purpose of Requirements Elicitation (RE)?
- A: To define system architecture
- B: To obtain stakeholder requirements
- C: To test system performance
- D: To implement system functionality
View Answer
B
Q70: Which of the following is a basic technique for Requirements Elicitation?
- A: Interviews
- B: Testing
- C: Debugging
- D: Coding
View Answer
A