Software Requirements & Specification MCQs with Answers
Practice important Software Requirements & Specification MCQs with answers and explanations.
Multiple Choice Questions
Q281: Which of the following is NOT a tool used in Requirement Change Management?
- A: Spreadsheet
- B: Bug Tracking Tools
- C: Coding Standards Management Tools
- D: Word Processor
View Answer
C
Q282: The Agile change management process begins with ________.
- A: Defining detailed requirements
- B: Planning the iteration
- C: Selecting the highest priority requirement for implementation
- D:
View Answer
B
Q283: Which agile technique is best known for its emphasis on pair programming?
- A: Scrum
- B: Extreme Programming
- C: Kanban
- D: Waterfall
View Answer
B
Q284: Agile change management emphasizes ________ over strict adherence to a plan.
- A: Customer feedback and collaboration
- B: Comprehensive documentation
- C: Quality assurance
- D: Post-delivery testing
View Answer
A
Q285: In Agile development, changes to requirements are handled ________.
- A: Only at the beginning
- B: At the end of the project
- C: After every iteration
- D: During the whole project lifecycle
View Answer
D
Q286: The Rational Unified Process (RUP) tends to be ________ when responding to rapidly changing requirements.
- A: Highly adaptable
- B: Slow to adapt
- C: Very fast
- D: Very flexible
View Answer
B
Q287: Fill in the blank: The Agile Manifesto values individuals and interactions over ________.
- A: Tools and processes
- B: Documentation
- C: Contract negotiation
- D: Planning
View Answer
A
Q288: Fill in the blank: In the Agile change management process, the requirements stack is ________ as a result of updates after each iteration.
- A: Fixed
- B: Updated
- C: Constantly evaluated
- D: Reviewed
View Answer
C
Q289: Which of the following is NOT an activity performed in Scrum?
- A: Iterative planning
- B: Customer collaboration
- C: Heavy documentation
- D: Short development cycles
View Answer
C
Q290: What is the key difference between Agile and traditional approaches regarding requirement changes?
- A: Agile welcomes changes during development
- B: Traditional approaches welcome changes during development
- C: Agile doesn't allow any changes during development
- D: Traditional approaches encourage regular changes
View Answer
A