The later in the development life cycle a fault is discovered, the more expensive it is to fix. Why?

Question

BlackTom AI · Accepted Answer

A defect left undetected gets propagated into subsequent artifacts and work products, so fixing it later requires undoing and redoing more than just code.

1. Relevant knowledge points and concepts
- Fault propagation: a requirement/design/code fault typically becomes embedded in downstream artifacts (design diagrams, multiple code modules, tests, documentation).
- Rework and ripple effect: later fixes require changing multiple artifacts and retesting affected areas.
- Cost drivers: additional design, coding, integration, regression testing, deployment, and possibly customer support/patching increase effort and cost.

2. Step-by-step reasoning
- If a fault is found during requirements: correct the requirement document and align stakeholders — minimal engineering effort.
- If found during design: you must revise requirements/design documents, update designs, update any impacted modules, and then implement and test the changes.
- If found during coding or integration: code changes, rebuild, integration testing, and regression testing are required across affected modules.
- If found in production: emergency fixes, customer notifications, possible rollbacks, patches, legal/contractual penalties and support costs are added on top of development rework.

3. Calculation illustration (intermediate steps)
- Assume baseline fix cost at requirements stage = $100.
- Design-stage multiplier (rework + testing) = ×5 → $100 × 5 = $500.
- Production-stage multiplier (deployment, support, reputation) = ×50 → $100 × 50 = $5,000.
- These hypothetical steps show how effort and cost escalate as more artifacts and stakeholders are involved.

4. Why the correct answer is correct
- The correct option states the fault is built into each stage as it proceeds. That captures the propagation and amplification effect: a single missed defect multiplies effort because every subsequent stage consumes and potentially spreads that defect.

5. Why other options are incorrect
- “None of the options” is wrong because a valid, common explanation exists.
- “IT developers salaries keep increasing” is irrelevant to why an individual fault’s fix cost rises across the lifecycle.
- “Poor documentation” can make fixes harder but is a contributory factor, not the primary systemic reason; propagation across stages is the core cause.

6. Conclusion
- Therefore, the correct answer is: "The fault gets built into each stage of the development life cycle as it proceeds," which matches the provided answer.

The later in the development life cycle a fault is discovered, the more expensive it is to fix. Why?单项选择题

类似问题

Which of the following are examples of useful context for an engineering AI task?

What is the best way to prevent design flaws in software?

信息系统解决方案的开发是基于问题解决过程的。

Which statement best describes software engineering?

Which of the following best describes a software development methodology ?

Question at position 3 The steps of the systems development life cycle can only be viewed as a linear process. TrueFalse

A city government’s smart parking app project has used 65% of the budget at the halfway point because extra developers were hired to catch up. Which of the following is a preventive (proactive) action rather than a corrective (reactive) one?

更多留学生实用工具

智能学习助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单