Software Requirements & Specification MCQs with Answers
Practice important Software Requirements & Specification MCQs with answers and explanations.
Multiple Choice Questions
Q261: What does the responsibility diagram in KAOS help to generate for each agent?
- A: A list of requirements and expectations
- B: An operations plan
- C: An object model
- D: A set of goals
View Answer
A
Q262: In KAOS, the responsibility model is based on which of the following?
- A: Events and operations
- B: Requirements and expectations
- C: Objects and agents
- D: Goals and agents
View Answer
B
Q263: What is the input for building a responsibility diagram in KAOS?
- A: Operational model
- B: Goal model
- C: Behavioral model
- D: Agent model
View Answer
B
Q264: Which KAOS model defines static constraints and objects relevant to requirements?
- A: Goal model
- B: Operational model
- C: Object model
- D: Responsibility model
View Answer
C
Q265: Which type of object in the KAOS model represents independent, passive objects?
- A: Agents
- B: Entities
- C: Associations
- D: Objects
View Answer
B
Q266: Which KAOS model includes requirements patterns grown from organizational experience?
- A: Goal model
- B: Operational model
- C: Responsibility model
- D: Object model
View Answer
A
Q267: Which of the following is a reason for requirements changes in software development?
- A: Lack of domain knowledge at start
- B: Inconsistent requirements
- C: Change in customer prioritization
- D: All of the above
View Answer
D
Q268: Agile methodologies welcome ______ during the software development process.
- A: Change at the start
- B: Change after requirements are fixed
- C: Changes to coding standards
- D: Changes during development
View Answer
D
Q269: What is the main focus of the Agile Manifesto?
- A: Individuals and interactions over tools and processes
- B: Customer contract negotiation
- C: Formal documentation
- D: Heavy reliance on detailed planning
View Answer
A
Q270: Which of the following is NOT one of the rules of Extreme Programming (XP)?
- A: Small Releases
- B: Pair Programming
- C: Heavy Documentation
- D: Continuous Integration
View Answer
C