✓ Correct Answer: b) Design
Explanation: Design is part of the software development process that comes after requirements engineering. RE focuses on understanding and documenting WHAT needs to be built, while design focuses on HOW to build it. The main steps of RE are: Inception, Elicitation, Analysis, Specification, Validation, and Management.
✓ Correct Answer: d) Algorithm for software implementation
Explanation: A good SRS document should focus on WHAT the system should do, not HOW it should be implemented. Algorithms are design and implementation details that should not be included in the requirements document. The SRS should include functional requirements, non-functional requirements, and goals, but not specific implementation details.
✓ Correct Answer: b) Waterfall model
Explanation: When requirements are well understood and stable from the beginning, the waterfall model is most suitable as it follows a sequential approach. For unclear or changing requirements, iterative models like spiral or prototyping would be more appropriate.
✓ Correct Answer: a) Software requirement specification
Explanation: The Software Requirements Specification (SRS) is the document that contains all the requirements collected and analyzed from stakeholders. It serves as a formal agreement between stakeholders and developers about what the system will do.
✓ Correct Answer: b) Ambiguous
Explanation: A good SRS should be unambiguous, not ambiguous. Ambiguity leads to different interpretations of requirements by different stakeholders. A good SRS should be verifiable, complete, traceable, consistent, correct, feasible, necessary, and prioritized.
✓ Correct Answer: b) Requirements Inception
Explanation: Inception is the first step where the process starts with identifying the business need, market opportunity, establishing business case, feasibility study, system scope, and risks. This is followed by elicitation, analysis, specification, validation, and management.
✓ Correct Answer: c) 40-50 percent
Explanation: Requirements errors account for 40 to 50 percent of all defects found in software products, making it the largest source of defects. Moreover, 82% of the effort to fix defects is spent on requirements-related issues, highlighting the critical importance of getting requirements right.
✓ Correct Answer: c) The flight search results should load within 5 seconds
Explanation: This is a performance requirement (quality attribute) that specifies HOW WELL the system performs a task. Options a, b, and d are functional requirements that describe WHAT the system should do. Non-functional requirements include quality attributes like performance, security, usability, reliability, etc.
✓ Correct Answer: c) User involvement
Explanation: User involvement is the #1 success factor for software projects. This aligns with Truth #5: "Customer involvement is the most critical contributor to software quality." Without proper user involvement, projects are likely to miss important requirements or build the wrong solution.
✓ Correct Answer: b) Business requirements
Explanation: Business requirements describe WHY the system is being implemented - the business goals and objectives. Example: "Airline wants to reduce airport counter staff costs by 25 percent." User requirements describe WHAT users need to do, functional requirements describe HOW the system behaves, and system requirements describe requirements for multi-component systems.
✓ Correct Answer: False
Explanation: An actor in a use case is not always a person. An actor represents any external entity that interacts with the system, which can be a person, another system, hardware device, or even time (for scheduled tasks). For example, a payment gateway system or an email server can be actors.
✓ Correct Answer: False
Explanation: A stakeholder is anyone who has an interest in or is affected by the project, not just purchasers. Stakeholders include users, developers, project managers, domain experts, testers, lawyers, auditors, customers, clients, and many others who have a stake in the system's success.
✓ Correct Answer: True
Explanation: Conflicting requirements are indeed common in RE. Different stakeholders often have different perspectives and priorities, leading to conflicting requirements. This is one of the challenges in the requirements process, and it's addressed during requirements analysis and negotiation.
✓ Correct Answer: False
Explanation: RE is not a discrete activity but a continuous process that occurs throughout the project lifecycle. Truth #3 states "Change happens," and requirements management continues throughout the project. RE activities may be performed iteratively and requirements evolve as stakeholders gain better understanding of their needs.