BS Software Engineering · Software Re-Engineering

Unit 3: Program Comprehension MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement most accurately characterizes Program Comprehension Concepts within Program Comprehension? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
  2. BIt is only a naming convention with no effect on engineering decisions.
  3. CIt automatically guarantees a defect-free product.
  4. DIt applies only after deployment and never during development.
Show answer
Answer: A. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Report a mistake

Q2. What is the primary purpose of Program Comprehension Concepts when practicing Software Re-Engineering? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt exists only to increase the number of project documents.
  2. BIt guarantees optimal performance without measurement.
  3. CIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  4. DIts main purpose is to remove the need for requirements.
Show answer
Answer: C. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.
Report a mistake

Q3. A software team is applying Program Comprehension Concepts during Program Comprehension. Which action is the most appropriate? Context: BS Software Engineering / Software Re-Engineering.

  1. AClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
  2. BSkip requirements and implement the first idea immediately.
  3. CChoose a technique solely because it is fashionable.
  4. DAvoid review because the technique itself guarantees correctness.
Show answer
Answer: A. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Report a mistake

Q4. Which statement correctly distinguishes sound use of Program Comprehension Concepts from a common misuse? Context: BS Software Engineering / Software Re-Engineering.

  1. ASound use means avoiding documentation and review.
  2. BMisuse cannot occur once a tool supports the technique.
  3. CSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  4. DAny use is sound if the software compiles.
Show answer
Answer: C. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
Report a mistake

Q5. Which criterion is most useful for evaluating the quality of Program Comprehension Concepts? Context: BS Software Engineering / Software Re-Engineering.

  1. AEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
  2. BCount only the number of pages or lines produced.
  3. CJudge quality solely by visual appearance.
  4. DAssume quality is high whenever the work was completed quickly.
Show answer
Answer: A. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Report a mistake

Q6. Which risk should be considered most carefully when applying Program Comprehension Concepts? Context: BS Software Engineering / Software Re-Engineering.

  1. AOnly the color scheme of the artifact can create risk.
  2. BRisk disappears if the team avoids documenting decisions.
  3. CUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  4. DThere are no meaningful risks once a standard tool is used.
Show answer
Answer: C. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
Report a mistake

Q7. Which sequence best reflects disciplined work with Program Comprehension Concepts? Context: BS Software Engineering / Software Re-Engineering.

  1. ADefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
  2. BImplement first, then decide what objective was intended.
  3. CIgnore constraints, skip review, and optimize immediately.
  4. DSelect an answer by preference and avoid collecting evidence.
Show answer
Answer: A. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.
Report a mistake

Q8. What evidence would best support the claim that Program Comprehension Concepts was applied correctly? Context: BS Software Engineering / Software Re-Engineering.

  1. AThe mere existence of source code, regardless of behavior.
  2. BA screenshot with no link to requirements, tests, or measurements.
  3. CA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  4. DA team member saying it looks correct without review.
Show answer
Answer: C. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
Report a mistake

Q9. When selecting an approach to Program Comprehension Concepts, which trade-off should be assessed? Context: BS Software Engineering / Software Re-Engineering.

  1. ACorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
  2. BOnly source-code length matters.
  3. CAlways maximize complexity because it shows sophistication.
  4. DIgnore maintainability and constraints whenever performance is discussed.
Show answer
Answer: A. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Report a mistake

Q10. Which example best demonstrates practical understanding of Program Comprehension Concepts? Context: BS Software Engineering / Software Re-Engineering.

  1. AApply it identically in every project regardless of context.
  2. BTreat it as a substitute for requirements, testing, and review.
  3. CUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  4. DMemorize the term but never use it in a project decision.
Show answer
Answer: C. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Software Re-Engineering → Program Comprehension → Program Comprehension Concepts, the correct choice follows a requirements-driven, reviewable engineering approach. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.
Report a mistake

Q11. Which statement most accurately characterizes Program Comprehension Techniques within Program Comprehension? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt automatically guarantees a defect-free product.
  2. BIt applies only after deployment and never during development.
  3. CIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
  4. DIt is only a naming convention with no effect on engineering decisions.
Show answer
Answer: C. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Report a mistake

Q12. What is the primary purpose of Program Comprehension Techniques when practicing Software Re-Engineering? Context: BS Software Engineering / Software Re-Engineering.

  1. AIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  2. BIts main purpose is to remove the need for requirements.
  3. CIt exists only to increase the number of project documents.
  4. DIt guarantees optimal performance without measurement.
Show answer
Answer: A. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.
Report a mistake

Q13. A software team is applying Program Comprehension Techniques during Program Comprehension. Which action is the most appropriate? Context: BS Software Engineering / Software Re-Engineering.

  1. AChoose a technique solely because it is fashionable.
  2. BAvoid review because the technique itself guarantees correctness.
  3. CClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
  4. DSkip requirements and implement the first idea immediately.
Show answer
Answer: C. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Report a mistake

Q14. Which statement correctly distinguishes sound use of Program Comprehension Techniques from a common misuse? Context: BS Software Engineering / Software Re-Engineering.

  1. ASound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  2. BAny use is sound if the software compiles.
  3. CSound use means avoiding documentation and review.
  4. DMisuse cannot occur once a tool supports the technique.
Show answer
Answer: A. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
Report a mistake

Q15. Which criterion is most useful for evaluating the quality of Program Comprehension Techniques? Context: BS Software Engineering / Software Re-Engineering.

  1. AJudge quality solely by visual appearance.
  2. BAssume quality is high whenever the work was completed quickly.
  3. CEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
  4. DCount only the number of pages or lines produced.
Show answer
Answer: C. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Report a mistake

Q16. Which risk should be considered most carefully when applying Program Comprehension Techniques? Context: BS Software Engineering / Software Re-Engineering.

  1. AUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  2. BThere are no meaningful risks once a standard tool is used.
  3. COnly the color scheme of the artifact can create risk.
  4. DRisk disappears if the team avoids documenting decisions.
Show answer
Answer: A. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
Report a mistake

Q17. Which sequence best reflects disciplined work with Program Comprehension Techniques? Context: BS Software Engineering / Software Re-Engineering.

  1. AIgnore constraints, skip review, and optimize immediately.
  2. BSelect an answer by preference and avoid collecting evidence.
  3. CDefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
  4. DImplement first, then decide what objective was intended.
Show answer
Answer: C. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.
Report a mistake

Q18. What evidence would best support the claim that Program Comprehension Techniques was applied correctly? Context: BS Software Engineering / Software Re-Engineering.

  1. AA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  2. BA team member saying it looks correct without review.
  3. CThe mere existence of source code, regardless of behavior.
  4. DA screenshot with no link to requirements, tests, or measurements.
Show answer
Answer: A. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
Report a mistake

Q19. When selecting an approach to Program Comprehension Techniques, which trade-off should be assessed? Context: BS Software Engineering / Software Re-Engineering.

  1. AAlways maximize complexity because it shows sophistication.
  2. BIgnore maintainability and constraints whenever performance is discussed.
  3. CCorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
  4. DOnly source-code length matters.
Show answer
Answer: C. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Report a mistake

Q20. Which example best demonstrates practical understanding of Program Comprehension Techniques? Context: BS Software Engineering / Software Re-Engineering.

  1. AUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  2. BMemorize the term but never use it in a project decision.
  3. CApply it identically in every project regardless of context.
  4. DTreat it as a substitute for requirements, testing, and review.
Show answer
Answer: A. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Software Re-Engineering → Program Comprehension → Program Comprehension Techniques, the correct choice follows a requirements-driven, reviewable engineering approach. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.
Report a mistake

Q21. Which statement most accurately characterizes Program Comprehension Modeling within Program Comprehension? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
  2. BIt is only a naming convention with no effect on engineering decisions.
  3. CIt automatically guarantees a defect-free product.
  4. DIt applies only after deployment and never during development.
Show answer
Answer: A. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Report a mistake

Q22. What is the primary purpose of Program Comprehension Modeling when practicing Software Re-Engineering? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt exists only to increase the number of project documents.
  2. BIt guarantees optimal performance without measurement.
  3. CIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  4. DIts main purpose is to remove the need for requirements.
Show answer
Answer: C. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.
Report a mistake

Q23. A software team is applying Program Comprehension Modeling during Program Comprehension. Which action is the most appropriate? Context: BS Software Engineering / Software Re-Engineering.

  1. AClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
  2. BSkip requirements and implement the first idea immediately.
  3. CChoose a technique solely because it is fashionable.
  4. DAvoid review because the technique itself guarantees correctness.
Show answer
Answer: A. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Report a mistake

Q24. Which statement correctly distinguishes sound use of Program Comprehension Modeling from a common misuse? Context: BS Software Engineering / Software Re-Engineering.

  1. ASound use means avoiding documentation and review.
  2. BMisuse cannot occur once a tool supports the technique.
  3. CSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  4. DAny use is sound if the software compiles.
Show answer
Answer: C. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
Report a mistake

Q25. Which criterion is most useful for evaluating the quality of Program Comprehension Modeling? Context: BS Software Engineering / Software Re-Engineering.

  1. AEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
  2. BCount only the number of pages or lines produced.
  3. CJudge quality solely by visual appearance.
  4. DAssume quality is high whenever the work was completed quickly.
Show answer
Answer: A. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Report a mistake

Q26. Which risk should be considered most carefully when applying Program Comprehension Modeling? Context: BS Software Engineering / Software Re-Engineering.

  1. AOnly the color scheme of the artifact can create risk.
  2. BRisk disappears if the team avoids documenting decisions.
  3. CUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  4. DThere are no meaningful risks once a standard tool is used.
Show answer
Answer: C. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
Report a mistake

Q27. Which sequence best reflects disciplined work with Program Comprehension Modeling? Context: BS Software Engineering / Software Re-Engineering.

  1. ADefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
  2. BImplement first, then decide what objective was intended.
  3. CIgnore constraints, skip review, and optimize immediately.
  4. DSelect an answer by preference and avoid collecting evidence.
Show answer
Answer: A. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.
Report a mistake

Q28. What evidence would best support the claim that Program Comprehension Modeling was applied correctly? Context: BS Software Engineering / Software Re-Engineering.

  1. AThe mere existence of source code, regardless of behavior.
  2. BA screenshot with no link to requirements, tests, or measurements.
  3. CA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  4. DA team member saying it looks correct without review.
Show answer
Answer: C. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
Report a mistake

Q29. When selecting an approach to Program Comprehension Modeling, which trade-off should be assessed? Context: BS Software Engineering / Software Re-Engineering.

  1. ACorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
  2. BOnly source-code length matters.
  3. CAlways maximize complexity because it shows sophistication.
  4. DIgnore maintainability and constraints whenever performance is discussed.
Show answer
Answer: A. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Report a mistake

Q30. Which example best demonstrates practical understanding of Program Comprehension Modeling? Context: BS Software Engineering / Software Re-Engineering.

  1. AApply it identically in every project regardless of context.
  2. BTreat it as a substitute for requirements, testing, and review.
  3. CUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  4. DMemorize the term but never use it in a project decision.
Show answer
Answer: C. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Software Re-Engineering → Program Comprehension → Program Comprehension Modeling, the correct choice follows a requirements-driven, reviewable engineering approach. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.
Report a mistake

Q31. Which statement most accurately characterizes Program Comprehension Evaluation within Program Comprehension? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt automatically guarantees a defect-free product.
  2. BIt applies only after deployment and never during development.
  3. CIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
  4. DIt is only a naming convention with no effect on engineering decisions.
Show answer
Answer: C. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Report a mistake

Q32. What is the primary purpose of Program Comprehension Evaluation when practicing Software Re-Engineering? Context: BS Software Engineering / Software Re-Engineering.

  1. AIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  2. BIts main purpose is to remove the need for requirements.
  3. CIt exists only to increase the number of project documents.
  4. DIt guarantees optimal performance without measurement.
Show answer
Answer: A. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.
Report a mistake

Q33. A software team is applying Program Comprehension Evaluation during Program Comprehension. Which action is the most appropriate? Context: BS Software Engineering / Software Re-Engineering.

  1. AChoose a technique solely because it is fashionable.
  2. BAvoid review because the technique itself guarantees correctness.
  3. CClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
  4. DSkip requirements and implement the first idea immediately.
Show answer
Answer: C. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Report a mistake

Q34. Which statement correctly distinguishes sound use of Program Comprehension Evaluation from a common misuse? Context: BS Software Engineering / Software Re-Engineering.

  1. ASound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  2. BAny use is sound if the software compiles.
  3. CSound use means avoiding documentation and review.
  4. DMisuse cannot occur once a tool supports the technique.
Show answer
Answer: A. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
Report a mistake

Q35. Which criterion is most useful for evaluating the quality of Program Comprehension Evaluation? Context: BS Software Engineering / Software Re-Engineering.

  1. AJudge quality solely by visual appearance.
  2. BAssume quality is high whenever the work was completed quickly.
  3. CEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
  4. DCount only the number of pages or lines produced.
Show answer
Answer: C. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Report a mistake

Q36. Which risk should be considered most carefully when applying Program Comprehension Evaluation? Context: BS Software Engineering / Software Re-Engineering.

  1. AUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  2. BThere are no meaningful risks once a standard tool is used.
  3. COnly the color scheme of the artifact can create risk.
  4. DRisk disappears if the team avoids documenting decisions.
Show answer
Answer: A. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
Report a mistake

Q37. Which sequence best reflects disciplined work with Program Comprehension Evaluation? Context: BS Software Engineering / Software Re-Engineering.

  1. AIgnore constraints, skip review, and optimize immediately.
  2. BSelect an answer by preference and avoid collecting evidence.
  3. CDefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
  4. DImplement first, then decide what objective was intended.
Show answer
Answer: C. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.
Report a mistake

Q38. What evidence would best support the claim that Program Comprehension Evaluation was applied correctly? Context: BS Software Engineering / Software Re-Engineering.

  1. AA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  2. BA team member saying it looks correct without review.
  3. CThe mere existence of source code, regardless of behavior.
  4. DA screenshot with no link to requirements, tests, or measurements.
Show answer
Answer: A. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
Report a mistake

Q39. When selecting an approach to Program Comprehension Evaluation, which trade-off should be assessed? Context: BS Software Engineering / Software Re-Engineering.

  1. AAlways maximize complexity because it shows sophistication.
  2. BIgnore maintainability and constraints whenever performance is discussed.
  3. CCorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
  4. DOnly source-code length matters.
Show answer
Answer: C. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Report a mistake

Q40. Which example best demonstrates practical understanding of Program Comprehension Evaluation? Context: BS Software Engineering / Software Re-Engineering.

  1. AUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  2. BMemorize the term but never use it in a project decision.
  3. CApply it identically in every project regardless of context.
  4. DTreat it as a substitute for requirements, testing, and review.
Show answer
Answer: A. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Software Re-Engineering → Program Comprehension → Program Comprehension Evaluation, the correct choice follows a requirements-driven, reviewable engineering approach. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.
Report a mistake

Q41. Which statement most accurately characterizes Program Comprehension Applications within Program Comprehension? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
  2. BIt is only a naming convention with no effect on engineering decisions.
  3. CIt automatically guarantees a defect-free product.
  4. DIt applies only after deployment and never during development.
Show answer
Answer: A. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Report a mistake

Q42. What is the primary purpose of Program Comprehension Applications when practicing Software Re-Engineering? Context: BS Software Engineering / Software Re-Engineering.

  1. AIt exists only to increase the number of project documents.
  2. BIt guarantees optimal performance without measurement.
  3. CIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  4. DIts main purpose is to remove the need for requirements.
Show answer
Answer: C. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.
Report a mistake

Q43. A software team is applying Program Comprehension Applications during Program Comprehension. Which action is the most appropriate? Context: BS Software Engineering / Software Re-Engineering.

  1. AClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
  2. BSkip requirements and implement the first idea immediately.
  3. CChoose a technique solely because it is fashionable.
  4. DAvoid review because the technique itself guarantees correctness.
Show answer
Answer: A. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Report a mistake

Q44. Which statement correctly distinguishes sound use of Program Comprehension Applications from a common misuse? Context: BS Software Engineering / Software Re-Engineering.

  1. ASound use means avoiding documentation and review.
  2. BMisuse cannot occur once a tool supports the technique.
  3. CSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  4. DAny use is sound if the software compiles.
Show answer
Answer: C. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
Report a mistake

Q45. Which criterion is most useful for evaluating the quality of Program Comprehension Applications? Context: BS Software Engineering / Software Re-Engineering.

  1. AEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
  2. BCount only the number of pages or lines produced.
  3. CJudge quality solely by visual appearance.
  4. DAssume quality is high whenever the work was completed quickly.
Show answer
Answer: A. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Report a mistake

Q46. Which risk should be considered most carefully when applying Program Comprehension Applications? Context: BS Software Engineering / Software Re-Engineering.

  1. AOnly the color scheme of the artifact can create risk.
  2. BRisk disappears if the team avoids documenting decisions.
  3. CUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  4. DThere are no meaningful risks once a standard tool is used.
Show answer
Answer: C. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
Report a mistake

Q47. Which sequence best reflects disciplined work with Program Comprehension Applications? Context: BS Software Engineering / Software Re-Engineering.

  1. ADefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
  2. BImplement first, then decide what objective was intended.
  3. CIgnore constraints, skip review, and optimize immediately.
  4. DSelect an answer by preference and avoid collecting evidence.
Show answer
Answer: A. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.
Report a mistake

Q48. What evidence would best support the claim that Program Comprehension Applications was applied correctly? Context: BS Software Engineering / Software Re-Engineering.

  1. AThe mere existence of source code, regardless of behavior.
  2. BA screenshot with no link to requirements, tests, or measurements.
  3. CA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  4. DA team member saying it looks correct without review.
Show answer
Answer: C. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
Report a mistake

Q49. When selecting an approach to Program Comprehension Applications, which trade-off should be assessed? Context: BS Software Engineering / Software Re-Engineering.

  1. ACorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
  2. BOnly source-code length matters.
  3. CAlways maximize complexity because it shows sophistication.
  4. DIgnore maintainability and constraints whenever performance is discussed.
Show answer
Answer: A. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Report a mistake

Q50. Which example best demonstrates practical understanding of Program Comprehension Applications? Context: BS Software Engineering / Software Re-Engineering.

  1. AApply it identically in every project regardless of context.
  2. BTreat it as a substitute for requirements, testing, and review.
  3. CUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  4. DMemorize the term but never use it in a project decision.
Show answer
Answer: C. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Software Re-Engineering → Program Comprehension → Program Comprehension Applications, the correct choice follows a requirements-driven, reviewable engineering approach. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.
Report a mistake