BS Computer Science · Software Engineering

Unit 4: Requirements MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. What is the most accurate description of Elicitation in the context of Software Engineering? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AIt guarantees that every implementation is optimal without testing.
  2. BIt removes the need to define requirements or constraints.
  3. CElicitation should be understood through its defined role, constraints, and effect on the surrounding system.
  4. DIt is mainly a physical hardware connector and is independent of software logic.
Show answer
Answer: C. Elicitation should be understood through its defined role, constraints, and effect on the surrounding system.BS Computer Science → Software Engineering → Requirements → Elicitation: Elicitation should be understood through its defined role, constraints, and effect on the surrounding system.
Report a mistake

Q2. Which statement best reflects a correct principle of Elicitation? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AIt makes verification and testing unnecessary.
  2. BCorrect use of Elicitation requires applying its rules consistently to the problem being solved.
  3. CIts behavior can be chosen arbitrarily because formal rules do not matter.
  4. DIt is useful only for naming files and folders.
Show answer
Answer: B. Correct use of Elicitation requires applying its rules consistently to the problem being solved.BS Computer Science → Software Engineering → Requirements → Elicitation: Correct use of Elicitation requires applying its rules consistently to the problem being solved.
Report a mistake

Q3. A BS Computer Science student is working on Elicitation. Which choice is conceptually appropriate? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AA suitable solution connects Elicitation to the stated inputs, outputs, requirements, and constraints.
  2. BThe best approach is to ignore inputs and focus only on formatting.
  3. CIt always requires the same implementation regardless of context.
  4. DIt is unrelated to correctness or program behavior.
Show answer
Answer: A. A suitable solution connects Elicitation to the stated inputs, outputs, requirements, and constraints.BS Computer Science → Software Engineering → Requirements → Elicitation: A suitable solution connects Elicitation to the stated inputs, outputs, requirements, and constraints.
Report a mistake

Q4. Which outcome is most directly associated with applying Elicitation correctly? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AIt should be applied without checking assumptions or edge cases.
  2. BIt automatically eliminates all resource constraints.
  3. CIt is primarily a user-interface color convention.
  4. DApplying Elicitation correctly should produce behavior that can be reasoned about and verified.
Show answer
Answer: D. Applying Elicitation correctly should produce behavior that can be reasoned about and verified.BS Computer Science → Software Engineering → Requirements → Elicitation: Applying Elicitation correctly should produce behavior that can be reasoned about and verified.
Report a mistake

Q5. Which statement would be the strongest starting point when reasoning about Elicitation? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AThe concept is valid only when no data is involved.
  2. BIt replaces the need for algorithms and design.
  3. CThe student should first identify the purpose and assumptions of Elicitation before selecting an implementation.
  4. DImplementation should begin before the problem is understood.
Show answer
Answer: C. The student should first identify the purpose and assumptions of Elicitation before selecting an implementation.BS Computer Science → Software Engineering → Requirements → Elicitation: The student should first identify the purpose and assumptions of Elicitation before selecting an implementation.
Report a mistake

Q6. In Software Engineering, which consideration is most relevant when evaluating Elicitation? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AIt should be selected solely by personal preference.
  2. BThe relevant tradeoffs of Elicitation should be evaluated against correctness, efficiency, and maintainability.
  3. COnly source-code length matters when evaluating it.
  4. DIt has no relationship to efficiency or maintainability.
Show answer
Answer: B. The relevant tradeoffs of Elicitation should be evaluated against correctness, efficiency, and maintainability.BS Computer Science → Software Engineering → Requirements → Elicitation: The relevant tradeoffs of Elicitation should be evaluated against correctness, efficiency, and maintainability.
Report a mistake

Q7. Which choice represents a sound use of Elicitation rather than a misconception? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AA sound use of Elicitation follows the concept's formal or established rules instead of relying on guesswork.
  2. BGuessing is preferable to following the concept's established rules.
  3. CThe concept applies only to computer hardware manufacturing.
  4. DCorrectness cannot be evaluated for this concept.
Show answer
Answer: A. A sound use of Elicitation follows the concept's formal or established rules instead of relying on guesswork.BS Computer Science → Software Engineering → Requirements → Elicitation: A sound use of Elicitation follows the concept's formal or established rules instead of relying on guesswork.
Report a mistake

Q8. Which statement about Elicitation would be most defensible in a technical review? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AA technical review should ignore side effects and assumptions.
  2. BThe concept is correct whenever the program compiles.
  3. COnly visual appearance determines whether it is used correctly.
  4. DA technical review should verify both the conceptual correctness and the consequences of using Elicitation.
Show answer
Answer: D. A technical review should verify both the conceptual correctness and the consequences of using Elicitation.BS Computer Science → Software Engineering → Requirements → Elicitation: A technical review should verify both the conceptual correctness and the consequences of using Elicitation.
Report a mistake

Q9. When solving a problem involving Elicitation, what should the student prioritize? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AConstraints can be ignored because they never affect solutions.
  2. BTesting is unnecessary when the concept is familiar.
  3. CThe student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
  4. DOptimization should always come before correctness.
Show answer
Answer: C. The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.BS Computer Science → Software Engineering → Requirements → Elicitation: The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
Report a mistake

Q10. Which observation best demonstrates understanding of Elicitation? Context: BS Computer Science / Software Engineering / Requirements / Elicitation.

  1. AIts meaning changes randomly between problems.
  2. BUnderstanding is demonstrated by being able to explain, apply, and test Elicitation in an appropriate scenario.
  3. CMemorizing the term without applying it is sufficient.
  4. DThe concept cannot be tested with examples or counterexamples.
Show answer
Answer: B. Understanding is demonstrated by being able to explain, apply, and test Elicitation in an appropriate scenario.BS Computer Science → Software Engineering → Requirements → Elicitation: Understanding is demonstrated by being able to explain, apply, and test Elicitation in an appropriate scenario.
Report a mistake

Q11. What is the most accurate description of Functional Requirements in the context of Software Engineering? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AFunctional Requirements should be understood through its defined role, constraints, and effect on the surrounding system.
  2. BIt is mainly a physical hardware connector and is independent of software logic.
  3. CIt guarantees that every implementation is optimal without testing.
  4. DIt removes the need to define requirements or constraints.
Show answer
Answer: A. Functional Requirements should be understood through its defined role, constraints, and effect on the surrounding system.BS Computer Science → Software Engineering → Requirements → Functional Requirements: Functional Requirements should be understood through its defined role, constraints, and effect on the surrounding system.
Report a mistake

Q12. Which statement best reflects a correct principle of Functional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AIts behavior can be chosen arbitrarily because formal rules do not matter.
  2. BIt is useful only for naming files and folders.
  3. CIt makes verification and testing unnecessary.
  4. DCorrect use of Functional Requirements requires applying its rules consistently to the problem being solved.
Show answer
Answer: D. Correct use of Functional Requirements requires applying its rules consistently to the problem being solved.BS Computer Science → Software Engineering → Requirements → Functional Requirements: Correct use of Functional Requirements requires applying its rules consistently to the problem being solved.
Report a mistake

Q13. A BS Computer Science student is working on Functional Requirements. Which choice is conceptually appropriate? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AIt always requires the same implementation regardless of context.
  2. BIt is unrelated to correctness or program behavior.
  3. CA suitable solution connects Functional Requirements to the stated inputs, outputs, requirements, and constraints.
  4. DThe best approach is to ignore inputs and focus only on formatting.
Show answer
Answer: C. A suitable solution connects Functional Requirements to the stated inputs, outputs, requirements, and constraints.BS Computer Science → Software Engineering → Requirements → Functional Requirements: A suitable solution connects Functional Requirements to the stated inputs, outputs, requirements, and constraints.
Report a mistake

Q14. Which outcome is most directly associated with applying Functional Requirements correctly? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AIt is primarily a user-interface color convention.
  2. BApplying Functional Requirements correctly should produce behavior that can be reasoned about and verified.
  3. CIt should be applied without checking assumptions or edge cases.
  4. DIt automatically eliminates all resource constraints.
Show answer
Answer: B. Applying Functional Requirements correctly should produce behavior that can be reasoned about and verified.BS Computer Science → Software Engineering → Requirements → Functional Requirements: Applying Functional Requirements correctly should produce behavior that can be reasoned about and verified.
Report a mistake

Q15. Which statement would be the strongest starting point when reasoning about Functional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AThe student should first identify the purpose and assumptions of Functional Requirements before selecting an implementation.
  2. BImplementation should begin before the problem is understood.
  3. CThe concept is valid only when no data is involved.
  4. DIt replaces the need for algorithms and design.
Show answer
Answer: A. The student should first identify the purpose and assumptions of Functional Requirements before selecting an implementation.BS Computer Science → Software Engineering → Requirements → Functional Requirements: The student should first identify the purpose and assumptions of Functional Requirements before selecting an implementation.
Report a mistake

Q16. In Software Engineering, which consideration is most relevant when evaluating Functional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AOnly source-code length matters when evaluating it.
  2. BIt has no relationship to efficiency or maintainability.
  3. CIt should be selected solely by personal preference.
  4. DThe relevant tradeoffs of Functional Requirements should be evaluated against correctness, efficiency, and maintainability.
Show answer
Answer: D. The relevant tradeoffs of Functional Requirements should be evaluated against correctness, efficiency, and maintainability.BS Computer Science → Software Engineering → Requirements → Functional Requirements: The relevant tradeoffs of Functional Requirements should be evaluated against correctness, efficiency, and maintainability.
Report a mistake

Q17. Which choice represents a sound use of Functional Requirements rather than a misconception? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AThe concept applies only to computer hardware manufacturing.
  2. BCorrectness cannot be evaluated for this concept.
  3. CA sound use of Functional Requirements follows the concept's formal or established rules instead of relying on guesswork.
  4. DGuessing is preferable to following the concept's established rules.
Show answer
Answer: C. A sound use of Functional Requirements follows the concept's formal or established rules instead of relying on guesswork.BS Computer Science → Software Engineering → Requirements → Functional Requirements: A sound use of Functional Requirements follows the concept's formal or established rules instead of relying on guesswork.
Report a mistake

Q18. Which statement about Functional Requirements would be most defensible in a technical review? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AOnly visual appearance determines whether it is used correctly.
  2. BA technical review should verify both the conceptual correctness and the consequences of using Functional Requirements.
  3. CA technical review should ignore side effects and assumptions.
  4. DThe concept is correct whenever the program compiles.
Show answer
Answer: B. A technical review should verify both the conceptual correctness and the consequences of using Functional Requirements.BS Computer Science → Software Engineering → Requirements → Functional Requirements: A technical review should verify both the conceptual correctness and the consequences of using Functional Requirements.
Report a mistake

Q19. When solving a problem involving Functional Requirements, what should the student prioritize? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AThe student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
  2. BOptimization should always come before correctness.
  3. CConstraints can be ignored because they never affect solutions.
  4. DTesting is unnecessary when the concept is familiar.
Show answer
Answer: A. The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.BS Computer Science → Software Engineering → Requirements → Functional Requirements: The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
Report a mistake

Q20. Which observation best demonstrates understanding of Functional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Functional Requirements.

  1. AMemorizing the term without applying it is sufficient.
  2. BThe concept cannot be tested with examples or counterexamples.
  3. CIts meaning changes randomly between problems.
  4. DUnderstanding is demonstrated by being able to explain, apply, and test Functional Requirements in an appropriate scenario.
Show answer
Answer: D. Understanding is demonstrated by being able to explain, apply, and test Functional Requirements in an appropriate scenario.BS Computer Science → Software Engineering → Requirements → Functional Requirements: Understanding is demonstrated by being able to explain, apply, and test Functional Requirements in an appropriate scenario.
Report a mistake

Q21. What is the most accurate description of Nonfunctional Requirements in the context of Software Engineering? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AIt guarantees that every implementation is optimal without testing.
  2. BIt removes the need to define requirements or constraints.
  3. CNonfunctional Requirements should be understood through its defined role, constraints, and effect on the surrounding system.
  4. DIt is mainly a physical hardware connector and is independent of software logic.
Show answer
Answer: C. Nonfunctional Requirements should be understood through its defined role, constraints, and effect on the surrounding system.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: Nonfunctional Requirements should be understood through its defined role, constraints, and effect on the surrounding system.
Report a mistake

Q22. Which statement best reflects a correct principle of Nonfunctional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AIt makes verification and testing unnecessary.
  2. BCorrect use of Nonfunctional Requirements requires applying its rules consistently to the problem being solved.
  3. CIts behavior can be chosen arbitrarily because formal rules do not matter.
  4. DIt is useful only for naming files and folders.
Show answer
Answer: B. Correct use of Nonfunctional Requirements requires applying its rules consistently to the problem being solved.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: Correct use of Nonfunctional Requirements requires applying its rules consistently to the problem being solved.
Report a mistake

Q23. A BS Computer Science student is working on Nonfunctional Requirements. Which choice is conceptually appropriate? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AA suitable solution connects Nonfunctional Requirements to the stated inputs, outputs, requirements, and constraints.
  2. BThe best approach is to ignore inputs and focus only on formatting.
  3. CIt always requires the same implementation regardless of context.
  4. DIt is unrelated to correctness or program behavior.
Show answer
Answer: A. A suitable solution connects Nonfunctional Requirements to the stated inputs, outputs, requirements, and constraints.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: A suitable solution connects Nonfunctional Requirements to the stated inputs, outputs, requirements, and constraints.
Report a mistake

Q24. Which outcome is most directly associated with applying Nonfunctional Requirements correctly? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AIt should be applied without checking assumptions or edge cases.
  2. BIt automatically eliminates all resource constraints.
  3. CIt is primarily a user-interface color convention.
  4. DApplying Nonfunctional Requirements correctly should produce behavior that can be reasoned about and verified.
Show answer
Answer: D. Applying Nonfunctional Requirements correctly should produce behavior that can be reasoned about and verified.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: Applying Nonfunctional Requirements correctly should produce behavior that can be reasoned about and verified.
Report a mistake

Q25. Which statement would be the strongest starting point when reasoning about Nonfunctional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AThe concept is valid only when no data is involved.
  2. BIt replaces the need for algorithms and design.
  3. CThe student should first identify the purpose and assumptions of Nonfunctional Requirements before selecting an implementation.
  4. DImplementation should begin before the problem is understood.
Show answer
Answer: C. The student should first identify the purpose and assumptions of Nonfunctional Requirements before selecting an implementation.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: The student should first identify the purpose and assumptions of Nonfunctional Requirements before selecting an implementation.
Report a mistake

Q26. In Software Engineering, which consideration is most relevant when evaluating Nonfunctional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AIt should be selected solely by personal preference.
  2. BThe relevant tradeoffs of Nonfunctional Requirements should be evaluated against correctness, efficiency, and maintainability.
  3. COnly source-code length matters when evaluating it.
  4. DIt has no relationship to efficiency or maintainability.
Show answer
Answer: B. The relevant tradeoffs of Nonfunctional Requirements should be evaluated against correctness, efficiency, and maintainability.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: The relevant tradeoffs of Nonfunctional Requirements should be evaluated against correctness, efficiency, and maintainability.
Report a mistake

Q27. Which choice represents a sound use of Nonfunctional Requirements rather than a misconception? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AA sound use of Nonfunctional Requirements follows the concept's formal or established rules instead of relying on guesswork.
  2. BGuessing is preferable to following the concept's established rules.
  3. CThe concept applies only to computer hardware manufacturing.
  4. DCorrectness cannot be evaluated for this concept.
Show answer
Answer: A. A sound use of Nonfunctional Requirements follows the concept's formal or established rules instead of relying on guesswork.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: A sound use of Nonfunctional Requirements follows the concept's formal or established rules instead of relying on guesswork.
Report a mistake

Q28. Which statement about Nonfunctional Requirements would be most defensible in a technical review? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AA technical review should ignore side effects and assumptions.
  2. BThe concept is correct whenever the program compiles.
  3. COnly visual appearance determines whether it is used correctly.
  4. DA technical review should verify both the conceptual correctness and the consequences of using Nonfunctional Requirements.
Show answer
Answer: D. A technical review should verify both the conceptual correctness and the consequences of using Nonfunctional Requirements.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: A technical review should verify both the conceptual correctness and the consequences of using Nonfunctional Requirements.
Report a mistake

Q29. When solving a problem involving Nonfunctional Requirements, what should the student prioritize? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AConstraints can be ignored because they never affect solutions.
  2. BTesting is unnecessary when the concept is familiar.
  3. CThe student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
  4. DOptimization should always come before correctness.
Show answer
Answer: C. The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
Report a mistake

Q30. Which observation best demonstrates understanding of Nonfunctional Requirements? Context: BS Computer Science / Software Engineering / Requirements / Nonfunctional Requirements.

  1. AIts meaning changes randomly between problems.
  2. BUnderstanding is demonstrated by being able to explain, apply, and test Nonfunctional Requirements in an appropriate scenario.
  3. CMemorizing the term without applying it is sufficient.
  4. DThe concept cannot be tested with examples or counterexamples.
Show answer
Answer: B. Understanding is demonstrated by being able to explain, apply, and test Nonfunctional Requirements in an appropriate scenario.BS Computer Science → Software Engineering → Requirements → Nonfunctional Requirements: Understanding is demonstrated by being able to explain, apply, and test Nonfunctional Requirements in an appropriate scenario.
Report a mistake

Q31. What is the most accurate description of Use Cases in the context of Software Engineering? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AUse Cases should be understood through its defined role, constraints, and effect on the surrounding system.
  2. BIt is mainly a physical hardware connector and is independent of software logic.
  3. CIt guarantees that every implementation is optimal without testing.
  4. DIt removes the need to define requirements or constraints.
Show answer
Answer: A. Use Cases should be understood through its defined role, constraints, and effect on the surrounding system.BS Computer Science → Software Engineering → Requirements → Use Cases: Use Cases should be understood through its defined role, constraints, and effect on the surrounding system.
Report a mistake

Q32. Which statement best reflects a correct principle of Use Cases? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AIts behavior can be chosen arbitrarily because formal rules do not matter.
  2. BIt is useful only for naming files and folders.
  3. CIt makes verification and testing unnecessary.
  4. DCorrect use of Use Cases requires applying its rules consistently to the problem being solved.
Show answer
Answer: D. Correct use of Use Cases requires applying its rules consistently to the problem being solved.BS Computer Science → Software Engineering → Requirements → Use Cases: Correct use of Use Cases requires applying its rules consistently to the problem being solved.
Report a mistake

Q33. A BS Computer Science student is working on Use Cases. Which choice is conceptually appropriate? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AIt always requires the same implementation regardless of context.
  2. BIt is unrelated to correctness or program behavior.
  3. CA suitable solution connects Use Cases to the stated inputs, outputs, requirements, and constraints.
  4. DThe best approach is to ignore inputs and focus only on formatting.
Show answer
Answer: C. A suitable solution connects Use Cases to the stated inputs, outputs, requirements, and constraints.BS Computer Science → Software Engineering → Requirements → Use Cases: A suitable solution connects Use Cases to the stated inputs, outputs, requirements, and constraints.
Report a mistake

Q34. Which outcome is most directly associated with applying Use Cases correctly? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AIt is primarily a user-interface color convention.
  2. BApplying Use Cases correctly should produce behavior that can be reasoned about and verified.
  3. CIt should be applied without checking assumptions or edge cases.
  4. DIt automatically eliminates all resource constraints.
Show answer
Answer: B. Applying Use Cases correctly should produce behavior that can be reasoned about and verified.BS Computer Science → Software Engineering → Requirements → Use Cases: Applying Use Cases correctly should produce behavior that can be reasoned about and verified.
Report a mistake

Q35. Which statement would be the strongest starting point when reasoning about Use Cases? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AThe student should first identify the purpose and assumptions of Use Cases before selecting an implementation.
  2. BImplementation should begin before the problem is understood.
  3. CThe concept is valid only when no data is involved.
  4. DIt replaces the need for algorithms and design.
Show answer
Answer: A. The student should first identify the purpose and assumptions of Use Cases before selecting an implementation.BS Computer Science → Software Engineering → Requirements → Use Cases: The student should first identify the purpose and assumptions of Use Cases before selecting an implementation.
Report a mistake

Q36. In Software Engineering, which consideration is most relevant when evaluating Use Cases? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AOnly source-code length matters when evaluating it.
  2. BIt has no relationship to efficiency or maintainability.
  3. CIt should be selected solely by personal preference.
  4. DThe relevant tradeoffs of Use Cases should be evaluated against correctness, efficiency, and maintainability.
Show answer
Answer: D. The relevant tradeoffs of Use Cases should be evaluated against correctness, efficiency, and maintainability.BS Computer Science → Software Engineering → Requirements → Use Cases: The relevant tradeoffs of Use Cases should be evaluated against correctness, efficiency, and maintainability.
Report a mistake

Q37. Which choice represents a sound use of Use Cases rather than a misconception? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AThe concept applies only to computer hardware manufacturing.
  2. BCorrectness cannot be evaluated for this concept.
  3. CA sound use of Use Cases follows the concept's formal or established rules instead of relying on guesswork.
  4. DGuessing is preferable to following the concept's established rules.
Show answer
Answer: C. A sound use of Use Cases follows the concept's formal or established rules instead of relying on guesswork.BS Computer Science → Software Engineering → Requirements → Use Cases: A sound use of Use Cases follows the concept's formal or established rules instead of relying on guesswork.
Report a mistake

Q38. Which statement about Use Cases would be most defensible in a technical review? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AOnly visual appearance determines whether it is used correctly.
  2. BA technical review should verify both the conceptual correctness and the consequences of using Use Cases.
  3. CA technical review should ignore side effects and assumptions.
  4. DThe concept is correct whenever the program compiles.
Show answer
Answer: B. A technical review should verify both the conceptual correctness and the consequences of using Use Cases.BS Computer Science → Software Engineering → Requirements → Use Cases: A technical review should verify both the conceptual correctness and the consequences of using Use Cases.
Report a mistake

Q39. When solving a problem involving Use Cases, what should the student prioritize? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AThe student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
  2. BOptimization should always come before correctness.
  3. CConstraints can be ignored because they never affect solutions.
  4. DTesting is unnecessary when the concept is familiar.
Show answer
Answer: A. The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.BS Computer Science → Software Engineering → Requirements → Use Cases: The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
Report a mistake

Q40. Which observation best demonstrates understanding of Use Cases? Context: BS Computer Science / Software Engineering / Requirements / Use Cases.

  1. AMemorizing the term without applying it is sufficient.
  2. BThe concept cannot be tested with examples or counterexamples.
  3. CIts meaning changes randomly between problems.
  4. DUnderstanding is demonstrated by being able to explain, apply, and test Use Cases in an appropriate scenario.
Show answer
Answer: D. Understanding is demonstrated by being able to explain, apply, and test Use Cases in an appropriate scenario.BS Computer Science → Software Engineering → Requirements → Use Cases: Understanding is demonstrated by being able to explain, apply, and test Use Cases in an appropriate scenario.
Report a mistake

Q41. What is the most accurate description of Validation in the context of Software Engineering? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AIt guarantees that every implementation is optimal without testing.
  2. BIt removes the need to define requirements or constraints.
  3. CValidation should be understood through its defined role, constraints, and effect on the surrounding system.
  4. DIt is mainly a physical hardware connector and is independent of software logic.
Show answer
Answer: C. Validation should be understood through its defined role, constraints, and effect on the surrounding system.BS Computer Science → Software Engineering → Requirements → Validation: Validation should be understood through its defined role, constraints, and effect on the surrounding system.
Report a mistake

Q42. Which statement best reflects a correct principle of Validation? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AIt makes verification and testing unnecessary.
  2. BCorrect use of Validation requires applying its rules consistently to the problem being solved.
  3. CIts behavior can be chosen arbitrarily because formal rules do not matter.
  4. DIt is useful only for naming files and folders.
Show answer
Answer: B. Correct use of Validation requires applying its rules consistently to the problem being solved.BS Computer Science → Software Engineering → Requirements → Validation: Correct use of Validation requires applying its rules consistently to the problem being solved.
Report a mistake

Q43. A BS Computer Science student is working on Validation. Which choice is conceptually appropriate? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AA suitable solution connects Validation to the stated inputs, outputs, requirements, and constraints.
  2. BThe best approach is to ignore inputs and focus only on formatting.
  3. CIt always requires the same implementation regardless of context.
  4. DIt is unrelated to correctness or program behavior.
Show answer
Answer: A. A suitable solution connects Validation to the stated inputs, outputs, requirements, and constraints.BS Computer Science → Software Engineering → Requirements → Validation: A suitable solution connects Validation to the stated inputs, outputs, requirements, and constraints.
Report a mistake

Q44. Which outcome is most directly associated with applying Validation correctly? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AIt should be applied without checking assumptions or edge cases.
  2. BIt automatically eliminates all resource constraints.
  3. CIt is primarily a user-interface color convention.
  4. DApplying Validation correctly should produce behavior that can be reasoned about and verified.
Show answer
Answer: D. Applying Validation correctly should produce behavior that can be reasoned about and verified.BS Computer Science → Software Engineering → Requirements → Validation: Applying Validation correctly should produce behavior that can be reasoned about and verified.
Report a mistake

Q45. Which statement would be the strongest starting point when reasoning about Validation? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AThe concept is valid only when no data is involved.
  2. BIt replaces the need for algorithms and design.
  3. CThe student should first identify the purpose and assumptions of Validation before selecting an implementation.
  4. DImplementation should begin before the problem is understood.
Show answer
Answer: C. The student should first identify the purpose and assumptions of Validation before selecting an implementation.BS Computer Science → Software Engineering → Requirements → Validation: The student should first identify the purpose and assumptions of Validation before selecting an implementation.
Report a mistake

Q46. In Software Engineering, which consideration is most relevant when evaluating Validation? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AIt should be selected solely by personal preference.
  2. BThe relevant tradeoffs of Validation should be evaluated against correctness, efficiency, and maintainability.
  3. COnly source-code length matters when evaluating it.
  4. DIt has no relationship to efficiency or maintainability.
Show answer
Answer: B. The relevant tradeoffs of Validation should be evaluated against correctness, efficiency, and maintainability.BS Computer Science → Software Engineering → Requirements → Validation: The relevant tradeoffs of Validation should be evaluated against correctness, efficiency, and maintainability.
Report a mistake

Q47. Which choice represents a sound use of Validation rather than a misconception? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AA sound use of Validation follows the concept's formal or established rules instead of relying on guesswork.
  2. BGuessing is preferable to following the concept's established rules.
  3. CThe concept applies only to computer hardware manufacturing.
  4. DCorrectness cannot be evaluated for this concept.
Show answer
Answer: A. A sound use of Validation follows the concept's formal or established rules instead of relying on guesswork.BS Computer Science → Software Engineering → Requirements → Validation: A sound use of Validation follows the concept's formal or established rules instead of relying on guesswork.
Report a mistake

Q48. Which statement about Validation would be most defensible in a technical review? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AA technical review should ignore side effects and assumptions.
  2. BThe concept is correct whenever the program compiles.
  3. COnly visual appearance determines whether it is used correctly.
  4. DA technical review should verify both the conceptual correctness and the consequences of using Validation.
Show answer
Answer: D. A technical review should verify both the conceptual correctness and the consequences of using Validation.BS Computer Science → Software Engineering → Requirements → Validation: A technical review should verify both the conceptual correctness and the consequences of using Validation.
Report a mistake

Q49. When solving a problem involving Validation, what should the student prioritize? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AConstraints can be ignored because they never affect solutions.
  2. BTesting is unnecessary when the concept is familiar.
  3. CThe student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
  4. DOptimization should always come before correctness.
Show answer
Answer: C. The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.BS Computer Science → Software Engineering → Requirements → Validation: The student should prioritize correctness first, then evaluate complexity, clarity, and applicable constraints.
Report a mistake

Q50. Which observation best demonstrates understanding of Validation? Context: BS Computer Science / Software Engineering / Requirements / Validation.

  1. AIts meaning changes randomly between problems.
  2. BUnderstanding is demonstrated by being able to explain, apply, and test Validation in an appropriate scenario.
  3. CMemorizing the term without applying it is sufficient.
  4. DThe concept cannot be tested with examples or counterexamples.
Show answer
Answer: B. Understanding is demonstrated by being able to explain, apply, and test Validation in an appropriate scenario.BS Computer Science → Software Engineering → Requirements → Validation: Understanding is demonstrated by being able to explain, apply, and test Validation in an appropriate scenario.
Report a mistake