Skip to main content

Software Requirements & Specification MCQs with Answers

Practice important Software Requirements & Specification MCQs with answers and explanations.

Chapter: 3
Q61:
What should functional requirements be like?
A. Complete and consistent
B. Ambiguous and flexible
C. Irrelevant and minimal
D. Untestable and vague
Correct Answer: A
Chapter: 3
Q62:
Which of the following is a key characteristic of good software requirements?
A. Feasible
B. Invalid
C. Unverifiable
D. Unmodifiable
Correct Answer: A
Chapter: 3
Q63:
Which of the following is NOT considered a software requirement?
A. Functional requirements
B. Non-functional requirements
C. Design specifications
D. Design implementations
Correct Answer: C
Chapter: 3
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
Correct Answer: B
Chapter: 3
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
Correct Answer: A
Chapter: 3
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
Correct Answer: A
Chapter: 3
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
Correct Answer: A
Chapter: 3
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
Correct Answer: C
Chapter: 4
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
Correct Answer: B
Chapter: 4
Q70:
Which of the following is a basic technique for Requirements Elicitation?
A. Interviews
B. Testing
C. Debugging
D. Coding
Correct Answer: A
Chapter: 4
Q71:
Which technique is described as "most employed" for Requirements Elicitation?
A. Interviews
B. Prototyping
C. Ethnography
D. Brainstorming
Correct Answer: A
Chapter: 4
Q72:
In semi-structured interviews, what is a major drawback?
A. No biasing
B. Interviewee may be uncomfortable
C. Low time consumption
D. No new ideas generated
Correct Answer: B
Chapter: 4
Q73:
What is the primary advantage of using unstructured interviews?
A. Provides consistency
B. Generates new ideas and opinions
C. Quick and easy to conduct
D. Produces quantitative data
Correct Answer: B
Chapter: 4
Q74:
Which technique involves analyzing existing documents to gather requirements?
A. Document Analysis
B. Prototyping
C. Brainstorming
D. Observation
Correct Answer: A
Chapter: 4
Q75:
The main disadvantage of document analysis is:
A. High cost
B. Time-consuming to find information
C. Lack of historical data
D. Data is too general
Correct Answer: B
Chapter: 4
Q76:
What is a major advantage of using questionnaires/surveys in elicitation?
A. Low cost
B. Limited reach
C. Clarification on ambiguous questions
D. Time-consuming to conduct
Correct Answer: A
Chapter: 4
Q77:
Which of the following is true regarding questionnaires/surveys?
A. They provide immediate feedback
B. They are only useful for large groups
C. They require face-to-face interaction
D. They are costly to implement
Correct Answer: B
Chapter: 4
Q78:
Which technique is best for gathering information from a large, distributed group?
A. Interviews
B. Questionnaires/Surveys
C. Observation
D. Ethnography
Correct Answer: B
Chapter: 4
Q79:
Requirements Elicitation is a part of the ________ phase.
A. Design
B. Testing
C. Development
D. Requirements Engineering
Correct Answer: D
Chapter: 4
Q80:
What is the main goal of Requirements Elicitation?
A. To develop system architecture
B. To understand stakeholder needs
C. To implement system functionality
D. To evaluate system performance
Correct Answer: B

Test Your Knowledge

Take a timed quiz on Software Requirements & Specification

🚀 Start Quiz Now