Question: 740 Which of the following is the most effective way to ensure that a requirement is testable? A. Use vague terms to allow flexibility B. Define it in natural language without metrics C. Specify acceptance criteria and measurable outcomes D. Keep it at a high level to avoid complexity E. Rely on developer intuition for implementation Answer: C Explanation: Specifying acceptance criteria and measurable outcomes ensures that the requirement can be objectively validated during testing. Question: 741 What is the primary purpose of a requirements traceability matrix (RTM)? A. To document design decisions B. To track changes in project scope C. To manage project timelines D. To ensure each requirement is addressed in the final product E. To allocate resources Answer: D Explanation: An RTM ensures that each requirement is accounted for throughout the project lifecycle, linking requirements to their corresponding design, implementation, and testing artifacts. Question: 742 In a requirements gathering session, a stakeholder suggests a feature that is technically complex and outside the current scopE) What is the best approach to handle this suggestion? A. Document the suggestion for future consideration B. Reject the suggestion outright C. Immediately escalate it to upper management D. Analyze the technical complexity and present findings E. Ask the stakeholder to provide a detailed proposal Answer: A Explanation: Documenting the suggestion allows for future evaluation without dismissing potentially valuable ideas, fostering an inclusive atmosphere for stakeholders. Question: 743 When should requirements traceability be established in a project? A. After the testing phase B. Only if there is time available C. At the end of the project D. During the requirements elicitation phase Answer: D Explanation: Requirements traceability should be established during the requirements elicitation phase to ensure all requirements can be tracked throughout the project lifecycle. Question: 744 Which two benefits does prototyping provide in the requirements engineering process? A. It eliminates the need for requirements documentation. B. It helps validate requirements with users and stakeholders. C. It reduces development time significantly. D. It facilitates early detection of misunderstandings. Answer: B, D Explanation: Prototyping validates requirements and facilitates early detection of misunderstandings, improving stakeholder engagement and satisfaction. Question: 745 You are tasked with documenting requirements for a new system. Which of the following practices should be avoided to maintain clarity? A. Using clear and concise language. B. Writing ambiguous statements to cover multiple interpretations. C. Including diagrams and visual aids. D. Ensuring that all stakeholders review the requirements document. Answer: B Explanation: Writing ambiguous statements can lead to misinterpretation and confusion, undermining the clarity and effectiveness of the requirements documentation. Question: 746 Which of the following statements about use cases is correct? A. They are only useful for functional requirements. B. They provide a detailed technical specification. C. They focus on user interactions with the system. D. They replace the need for other requirement documents. E. They are primarily used for non-functional requirements. Answer: C Explanation: Use cases focus on user interactions with the system, detailing the steps taken by users to achieve specific goals, making them valuable for functional requirements. Question: 747 In the context of requirements documentation, which two characteristics indicate a high-quality requirement? A. It is vague and open to interpretation. B. It is clear, concise, and unambiguous. C. It is documented in lengthy and complex language. D. It is testable and verifiable. Answer: B, D Explanation: High-quality requirements are clear, concise, unambiguous, and testable, ensuring they can be understood and verified effectively. Question: 748 A project manager asks you to prioritize requirements based on return on investment (ROI). Which method should you use? A. MoSCoW method B. Cost-benefit analysis C. Kano model D. User story mapping Answer: B Explanation: A cost-benefit analysis is appropriate for prioritizing requirements based on ROI, as it evaluates the potential financial returns against implementation costs. Question: 749 You are analyzing the requirements for a new software application. A stakeholder mentions that a feature should be "user-friendly." Which of the following approaches is best to clarify and refine this ambiguous requirement? A. Create a requirements traceability matrix B. Conduct a SWOT analysis C. Use a prototyping approach D. Develop a state machine diagram E. Implement a waterfall model Answer: C Explanation: Prototyping allows stakeholders to visualize and interact with the software early in the development process, helping to clarify ambiguous terms like "user-friendly." Question: 750 What is the primary benefit of using a user acceptance test (UAT) in the requirements engineering process? A. To ensure that requirements are technically feasible. B. To validate that the system meets the needs of the users and stakeholders. C. To document all requirements in detail. D. To prioritize requirements based on stakeholder input. Answer: B Explanation: UAT is conducted to ensure the final product fulfills the requirements and expectations of users, validating that it is ready for deployment. Question: 751 Which two types of requirements are typically included in a Software Requirements Specification (SRS)? A. Business requirements B. Technical specifications C. Non-functional requirements D. Marketing strategies Answer: A, C Explanation: An SRS typically includes business requirements and non-functional requirements, focusing on what the software must achieve. Question: 752 Which of the following best describes the purpose of a feasibility study in the context of requirements engineering? A. To identify all possible requirements for the system. B. To assess the viability of the project in terms of technical, financial, and operational aspects. C. To finalize the project timeline and budget. D. To eliminate all risks associated with the project. Answer: B Explanation: A feasibility study assesses whether a project is viable by examining its technical, financial, and operational aspects, guiding decision-making. Question: 753 What role does a requirements traceability matrix play in the requirements engineering process? A. It simplifies the coding process B. It helps in tracking requirements throughout the project lifecycle C. It eliminates the need for stakeholder input D. It guarantees that all requirements will be implemented Answer: B Explanation: A requirements traceability matrix is a tool that helps track requirements throughout the project lifecycle, ensuring that all requirements are addressed and tested. Question: 754 Which two characteristics are most critical for writing effective and clear requirement statements? (Choose two) A. Ambiguity B. Testability C. Lengthy descriptions D. Specificity E. Technical jargon Answer: B, D Explanation: Testability ensures that requirements can be verified through testing, while specificity provides clear, detailed information on what is expected, reducing ambiguity and misunderstandings during development. Question: 755 Which of the following is NOT a characteristic of a well-defined requirement? A. Unambiguous B. Vague C. Comprehensive D. Testable E. Feasible Answer: B Explanation: A well-defined requirement must be unambiguous, meaning it should clearly convey its intention without room for misinterpretation. Question: 756 A requirement states, "The system should be user-friendly." What is the primary issue with this requirement? A. It is a business requirement B. It is not aligned with stakeholder needs C. It is too technical D. It is subjective and lacks measurable criteria Answer: D Explanation: The term "user-friendly" is subjective and can vary widely in interpretation. Good requirements should be specific and measurable to ensure clarity and testability. Question: 757 How should requirements be prioritized to ensure alignment with stakeholder value? A. Use a value-based approach to prioritize requirements according to their impact on business objectives. B. Prioritize based on technical complexity. C. All requirements should be treated equally, regardless of value. D. Prioritize based on the preferences of the most vocal stakeholders. Answer: A Explanation: A value-based prioritization approach ensures that requirements are aligned with strategic business goals, maximizing the value delivered by the system. Question: 758 What approach should be taken to manage conflicting requirements from different stakeholders? A. Ignore conflicting requirements as they will resolve themselves. B. Accept the requirements from the most senior stakeholder only. C. Facilitate discussions among stakeholders to negotiate and prioritize conflicting requirements. D. Document all conflicting requirements without addressing them. Answer: C Explanation: Facilitating discussions allows stakeholders to negotiate and find common ground, leading to more effective prioritization and resolution of conflicts. Question: 759 In the context of requirements verification, which two statements are true? (Choose two) A. Verification checks if the product meets user needs and requirements. B. It is an ongoing process conducted throughout the development lifecycle. C. Verification is solely concerned with the correctness of requirements documentation. D. Reviews and inspections are common techniques for verification. Answer: B, D Explanation: Verification is an ongoing process ensuring that requirements are met, typically using reviews and inspections to confirm correctness. Question: 760 Which practice is essential for effective requirements communication among stakeholders? A. Using complex technical language B. Relying solely on written documentation C. Engaging stakeholders through workshops and discussions D. Limiting communication to formal meetings Answer: C Explanation: Engaging stakeholders through workshops and discussions fosters effective communication, ensuring that all parties understand and agree on the requirements. Question: 761 A project manager wants to understand the feasibility of a proposed feature that requires significant resources. Which technique is best suited for a preliminary feasibility analysis? A. Cost-benefit analysis B. Use case analysis C. Requirements prioritization D. Stakeholder analysis E. Risk assessment Answer: A Explanation: A cost-benefit analysis helps to evaluate whether the benefits of implementing the feature outweigh the costs, providing a clear indication of its feasibility. Question: 762 Which two methods can help in achieving a shared understanding of requirements among stakeholders? (Choose two) A. Creating visual models to represent requirements. B. Relying solely on written documentation. C. Conducting regular review sessions to gather feedback. D. Limiting stakeholder involvement to only key individuals. Answer: A, C Explanation: Visual models enhance comprehension, and regular reviews facilitate feedback, promoting a shared understanding among all stakeholders.