BS Software Engineering · Programming Fundamentals

Unit 10: Program Design MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement most accurately characterizes Decomposition within Program Design? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt is only a naming convention with no effect on engineering decisions.
  2. BIt automatically guarantees a defect-free product.
  3. CIt applies only after deployment and never during development.
  4. DIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Show answer
Answer: D. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition when practicing Programming Fundamentals? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt guarantees optimal performance without measurement.
  2. BIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  3. CIts main purpose is to remove the need for requirements.
  4. DIt exists only to increase the number of project documents.
Show answer
Answer: B. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition during Program Design. Which action is the most appropriate? Context: BS Software Engineering / Programming Fundamentals.

  1. ASkip requirements and implement the first idea immediately.
  2. BChoose a technique solely because it is fashionable.
  3. CAvoid review because the technique itself guarantees correctness.
  4. DClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Show answer
Answer: D. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition from a common misuse? Context: BS Software Engineering / Programming Fundamentals.

  1. AMisuse cannot occur once a tool supports the technique.
  2. BSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  3. CAny use is sound if the software compiles.
  4. DSound use means avoiding documentation and review.
Show answer
Answer: B. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition? Context: BS Software Engineering / Programming Fundamentals.

  1. ACount only the number of pages or lines produced.
  2. BJudge quality solely by visual appearance.
  3. CAssume quality is high whenever the work was completed quickly.
  4. DEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Show answer
Answer: D. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition? Context: BS Software Engineering / Programming Fundamentals.

  1. ARisk disappears if the team avoids documenting decisions.
  2. BUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  3. CThere are no meaningful risks once a standard tool is used.
  4. DOnly the color scheme of the artifact can create risk.
Show answer
Answer: B. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition? Context: BS Software Engineering / Programming Fundamentals.

  1. AImplement first, then decide what objective was intended.
  2. BIgnore constraints, skip review, and optimize immediately.
  3. CSelect an answer by preference and avoid collecting evidence.
  4. DDefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
Show answer
Answer: D. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition was applied correctly? Context: BS Software Engineering / Programming Fundamentals.

  1. AA screenshot with no link to requirements, tests, or measurements.
  2. BA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  3. CA team member saying it looks correct without review.
  4. DThe mere existence of source code, regardless of behavior.
Show answer
Answer: B. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition, which trade-off should be assessed? Context: BS Software Engineering / Programming Fundamentals.

  1. AOnly source-code length matters.
  2. BAlways maximize complexity because it shows sophistication.
  3. CIgnore maintainability and constraints whenever performance is discussed.
  4. DCorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Show answer
Answer: D. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Programming Fundamentals → Program Design → Decomposition, 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 Decomposition? Context: BS Software Engineering / Programming Fundamentals.

  1. ATreat it as a substitute for requirements, testing, and review.
  2. BUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  3. CMemorize the term but never use it in a project decision.
  4. DApply it identically in every project regardless of context.
Show answer
Answer: B. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Programming Fundamentals → Program Design → Decomposition, 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 Modularity within Program Design? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt applies only after deployment and never during development.
  2. BIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
  3. CIt is only a naming convention with no effect on engineering decisions.
  4. DIt automatically guarantees a defect-free product.
Show answer
Answer: B. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Programming Fundamentals → Program Design → Modularity, 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 Modularity when practicing Programming Fundamentals? Context: BS Software Engineering / Programming Fundamentals.

  1. AIts main purpose is to remove the need for requirements.
  2. BIt exists only to increase the number of project documents.
  3. CIt guarantees optimal performance without measurement.
  4. DIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
Show answer
Answer: D. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Programming Fundamentals → Program Design → Modularity, 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 Modularity during Program Design. Which action is the most appropriate? Context: BS Software Engineering / Programming Fundamentals.

  1. AAvoid review because the technique itself guarantees correctness.
  2. BClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
  3. CSkip requirements and implement the first idea immediately.
  4. DChoose a technique solely because it is fashionable.
Show answer
Answer: B. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Programming Fundamentals → Program Design → Modularity, 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 Modularity from a common misuse? Context: BS Software Engineering / Programming Fundamentals.

  1. AAny use is sound if the software compiles.
  2. BSound use means avoiding documentation and review.
  3. CMisuse cannot occur once a tool supports the technique.
  4. DSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
Show answer
Answer: D. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Programming Fundamentals → Program Design → Modularity, 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 Modularity? Context: BS Software Engineering / Programming Fundamentals.

  1. AAssume quality is high whenever the work was completed quickly.
  2. BEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
  3. CCount only the number of pages or lines produced.
  4. DJudge quality solely by visual appearance.
Show answer
Answer: B. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Programming Fundamentals → Program Design → Modularity, 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 Modularity? Context: BS Software Engineering / Programming Fundamentals.

  1. AThere are no meaningful risks once a standard tool is used.
  2. BOnly the color scheme of the artifact can create risk.
  3. CRisk disappears if the team avoids documenting decisions.
  4. DUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
Show answer
Answer: D. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Programming Fundamentals → Program Design → Modularity, 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 Modularity? Context: BS Software Engineering / Programming Fundamentals.

  1. ASelect an answer by preference and avoid collecting evidence.
  2. BDefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
  3. CImplement first, then decide what objective was intended.
  4. DIgnore constraints, skip review, and optimize immediately.
Show answer
Answer: B. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Programming Fundamentals → Program Design → Modularity, 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 Modularity was applied correctly? Context: BS Software Engineering / Programming Fundamentals.

  1. AA team member saying it looks correct without review.
  2. BThe mere existence of source code, regardless of behavior.
  3. CA screenshot with no link to requirements, tests, or measurements.
  4. DA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
Show answer
Answer: D. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Programming Fundamentals → Program Design → Modularity, 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 Modularity, which trade-off should be assessed? Context: BS Software Engineering / Programming Fundamentals.

  1. AIgnore maintainability and constraints whenever performance is discussed.
  2. BCorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
  3. COnly source-code length matters.
  4. DAlways maximize complexity because it shows sophistication.
Show answer
Answer: B. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Programming Fundamentals → Program Design → Modularity, 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 Modularity? Context: BS Software Engineering / Programming Fundamentals.

  1. AMemorize the term but never use it in a project decision.
  2. BApply it identically in every project regardless of context.
  3. CTreat it as a substitute for requirements, testing, and review.
  4. DUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
Show answer
Answer: D. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Programming Fundamentals → Program Design → Modularity, 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 Readability within Program Design? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt is only a naming convention with no effect on engineering decisions.
  2. BIt automatically guarantees a defect-free product.
  3. CIt applies only after deployment and never during development.
  4. DIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Show answer
Answer: D. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Programming Fundamentals → Program Design → Readability, 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 Readability when practicing Programming Fundamentals? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt guarantees optimal performance without measurement.
  2. BIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  3. CIts main purpose is to remove the need for requirements.
  4. DIt exists only to increase the number of project documents.
Show answer
Answer: B. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Programming Fundamentals → Program Design → Readability, 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 Readability during Program Design. Which action is the most appropriate? Context: BS Software Engineering / Programming Fundamentals.

  1. ASkip requirements and implement the first idea immediately.
  2. BChoose a technique solely because it is fashionable.
  3. CAvoid review because the technique itself guarantees correctness.
  4. DClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Show answer
Answer: D. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Programming Fundamentals → Program Design → Readability, 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 Readability from a common misuse? Context: BS Software Engineering / Programming Fundamentals.

  1. AMisuse cannot occur once a tool supports the technique.
  2. BSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  3. CAny use is sound if the software compiles.
  4. DSound use means avoiding documentation and review.
Show answer
Answer: B. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Programming Fundamentals → Program Design → Readability, 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 Readability? Context: BS Software Engineering / Programming Fundamentals.

  1. ACount only the number of pages or lines produced.
  2. BJudge quality solely by visual appearance.
  3. CAssume quality is high whenever the work was completed quickly.
  4. DEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Show answer
Answer: D. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Programming Fundamentals → Program Design → Readability, 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 Readability? Context: BS Software Engineering / Programming Fundamentals.

  1. ARisk disappears if the team avoids documenting decisions.
  2. BUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  3. CThere are no meaningful risks once a standard tool is used.
  4. DOnly the color scheme of the artifact can create risk.
Show answer
Answer: B. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Programming Fundamentals → Program Design → Readability, 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 Readability? Context: BS Software Engineering / Programming Fundamentals.

  1. AImplement first, then decide what objective was intended.
  2. BIgnore constraints, skip review, and optimize immediately.
  3. CSelect an answer by preference and avoid collecting evidence.
  4. DDefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
Show answer
Answer: D. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Programming Fundamentals → Program Design → Readability, 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 Readability was applied correctly? Context: BS Software Engineering / Programming Fundamentals.

  1. AA screenshot with no link to requirements, tests, or measurements.
  2. BA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  3. CA team member saying it looks correct without review.
  4. DThe mere existence of source code, regardless of behavior.
Show answer
Answer: B. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Programming Fundamentals → Program Design → Readability, 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 Readability, which trade-off should be assessed? Context: BS Software Engineering / Programming Fundamentals.

  1. AOnly source-code length matters.
  2. BAlways maximize complexity because it shows sophistication.
  3. CIgnore maintainability and constraints whenever performance is discussed.
  4. DCorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Show answer
Answer: D. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Programming Fundamentals → Program Design → Readability, 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 Readability? Context: BS Software Engineering / Programming Fundamentals.

  1. ATreat it as a substitute for requirements, testing, and review.
  2. BUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  3. CMemorize the term but never use it in a project decision.
  4. DApply it identically in every project regardless of context.
Show answer
Answer: B. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Programming Fundamentals → Program Design → Readability, 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 Tracing within Program Design? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt applies only after deployment and never during development.
  2. BIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
  3. CIt is only a naming convention with no effect on engineering decisions.
  4. DIt automatically guarantees a defect-free product.
Show answer
Answer: B. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Programming Fundamentals → Program Design → Tracing, 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 Tracing when practicing Programming Fundamentals? Context: BS Software Engineering / Programming Fundamentals.

  1. AIts main purpose is to remove the need for requirements.
  2. BIt exists only to increase the number of project documents.
  3. CIt guarantees optimal performance without measurement.
  4. DIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
Show answer
Answer: D. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Programming Fundamentals → Program Design → Tracing, 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 Tracing during Program Design. Which action is the most appropriate? Context: BS Software Engineering / Programming Fundamentals.

  1. AAvoid review because the technique itself guarantees correctness.
  2. BClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
  3. CSkip requirements and implement the first idea immediately.
  4. DChoose a technique solely because it is fashionable.
Show answer
Answer: B. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Programming Fundamentals → Program Design → Tracing, 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 Tracing from a common misuse? Context: BS Software Engineering / Programming Fundamentals.

  1. AAny use is sound if the software compiles.
  2. BSound use means avoiding documentation and review.
  3. CMisuse cannot occur once a tool supports the technique.
  4. DSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
Show answer
Answer: D. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Programming Fundamentals → Program Design → Tracing, 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 Tracing? Context: BS Software Engineering / Programming Fundamentals.

  1. AAssume quality is high whenever the work was completed quickly.
  2. BEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
  3. CCount only the number of pages or lines produced.
  4. DJudge quality solely by visual appearance.
Show answer
Answer: B. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Programming Fundamentals → Program Design → Tracing, 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 Tracing? Context: BS Software Engineering / Programming Fundamentals.

  1. AThere are no meaningful risks once a standard tool is used.
  2. BOnly the color scheme of the artifact can create risk.
  3. CRisk disappears if the team avoids documenting decisions.
  4. DUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
Show answer
Answer: D. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Programming Fundamentals → Program Design → Tracing, 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 Tracing? Context: BS Software Engineering / Programming Fundamentals.

  1. ASelect an answer by preference and avoid collecting evidence.
  2. BDefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
  3. CImplement first, then decide what objective was intended.
  4. DIgnore constraints, skip review, and optimize immediately.
Show answer
Answer: B. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Programming Fundamentals → Program Design → Tracing, 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 Tracing was applied correctly? Context: BS Software Engineering / Programming Fundamentals.

  1. AA team member saying it looks correct without review.
  2. BThe mere existence of source code, regardless of behavior.
  3. CA screenshot with no link to requirements, tests, or measurements.
  4. DA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
Show answer
Answer: D. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Programming Fundamentals → Program Design → Tracing, 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 Tracing, which trade-off should be assessed? Context: BS Software Engineering / Programming Fundamentals.

  1. AIgnore maintainability and constraints whenever performance is discussed.
  2. BCorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
  3. COnly source-code length matters.
  4. DAlways maximize complexity because it shows sophistication.
Show answer
Answer: B. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Programming Fundamentals → Program Design → Tracing, 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 Tracing? Context: BS Software Engineering / Programming Fundamentals.

  1. AMemorize the term but never use it in a project decision.
  2. BApply it identically in every project regardless of context.
  3. CTreat it as a substitute for requirements, testing, and review.
  4. DUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
Show answer
Answer: D. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Programming Fundamentals → Program Design → Tracing, 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 Integrated Problems within Program Design? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt is only a naming convention with no effect on engineering decisions.
  2. BIt automatically guarantees a defect-free product.
  3. CIt applies only after deployment and never during development.
  4. DIt is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.
Show answer
Answer: D. It is understood by its role, rules, inputs, outputs, and constraints in the surrounding software process.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems when practicing Programming Fundamentals? Context: BS Software Engineering / Programming Fundamentals.

  1. AIt guarantees optimal performance without measurement.
  2. BIts purpose is to support a defined software-engineering objective while preserving correctness and traceability.
  3. CIts main purpose is to remove the need for requirements.
  4. DIt exists only to increase the number of project documents.
Show answer
Answer: B. Its purpose is to support a defined software-engineering objective while preserving correctness and traceability.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems during Program Design. Which action is the most appropriate? Context: BS Software Engineering / Programming Fundamentals.

  1. ASkip requirements and implement the first idea immediately.
  2. BChoose a technique solely because it is fashionable.
  3. CAvoid review because the technique itself guarantees correctness.
  4. DClarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.
Show answer
Answer: D. Clarify the requirement and constraints, apply the technique deliberately, and verify the resulting artifact or behavior.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems from a common misuse? Context: BS Software Engineering / Programming Fundamentals.

  1. AMisuse cannot occur once a tool supports the technique.
  2. BSound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.
  3. CAny use is sound if the software compiles.
  4. DSound use means avoiding documentation and review.
Show answer
Answer: B. Sound use follows explicit principles and context; misuse applies the idea mechanically without checking assumptions.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems? Context: BS Software Engineering / Programming Fundamentals.

  1. ACount only the number of pages or lines produced.
  2. BJudge quality solely by visual appearance.
  3. CAssume quality is high whenever the work was completed quickly.
  4. DEvaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.
Show answer
Answer: D. Evaluate whether it satisfies stated requirements and produces evidence that can be reviewed or tested.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems? Context: BS Software Engineering / Programming Fundamentals.

  1. ARisk disappears if the team avoids documenting decisions.
  2. BUnstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.
  3. CThere are no meaningful risks once a standard tool is used.
  4. DOnly the color scheme of the artifact can create risk.
Show answer
Answer: B. Unstated assumptions and poorly controlled changes can invalidate the result even when the technique appears correct.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems? Context: BS Software Engineering / Programming Fundamentals.

  1. AImplement first, then decide what objective was intended.
  2. BIgnore constraints, skip review, and optimize immediately.
  3. CSelect an answer by preference and avoid collecting evidence.
  4. DDefine the objective, identify constraints, apply the method, review the result, and revise from evidence.
Show answer
Answer: D. Define the objective, identify constraints, apply the method, review the result, and revise from evidence.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems was applied correctly? Context: BS Software Engineering / Programming Fundamentals.

  1. AA screenshot with no link to requirements, tests, or measurements.
  2. BA traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.
  3. CA team member saying it looks correct without review.
  4. DThe mere existence of source code, regardless of behavior.
Show answer
Answer: B. A traceable artifact, test, review, or measurement showing that the stated requirement or objective is satisfied.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems, which trade-off should be assessed? Context: BS Software Engineering / Programming Fundamentals.

  1. AOnly source-code length matters.
  2. BAlways maximize complexity because it shows sophistication.
  3. CIgnore maintainability and constraints whenever performance is discussed.
  4. DCorrectness and maintainability should be balanced with cost, performance, complexity, and project constraints.
Show answer
Answer: D. Correctness and maintainability should be balanced with cost, performance, complexity, and project constraints.For Programming Fundamentals → Program Design → Integrated Problems, 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 Integrated Problems? Context: BS Software Engineering / Programming Fundamentals.

  1. ATreat it as a substitute for requirements, testing, and review.
  2. BUse the concept in a realistic project decision and justify the result against requirements and measurable criteria.
  3. CMemorize the term but never use it in a project decision.
  4. DApply it identically in every project regardless of context.
Show answer
Answer: B. Use the concept in a realistic project decision and justify the result against requirements and measurable criteria.For Programming Fundamentals → Program Design → Integrated Problems, 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