volume_mute

Use Case - Emergency Fix Trade-Off

publish date: 2026/06/24 21:38:15.282926 UTC

volume_mute

A live e-commerce checkout system suddenly starts rejecting valid customer payments due to a newly discovered software fault. The engineering team applies a quick direct code fix within two hours to restore checkout, without first updating the requirements or design documentation. Three weeks later, no one has gone back to update the documentation or refactor the patch. What risk has this scenario created?

The emergency fix automatically updated all documentation without any manual effort

The system is now completely safe from any future faults of any kind

There is no risk at all since checkout is now working again

The requirements, design, and code may now be inconsistent with each other, and the patch may accelerate software ageing if never revisited

Correct Answer

The requirements, design, and code may now be inconsistent with each other, and the patch may accelerate software ageing if never revisited

Explanation

This illustrates the classic emergency repair risk: an urgent fix is applied directly to the code to restore service quickly, bypassing documentation updates. If the patch is never revisited, documentation drifts out of sync with the code, and quick-fix code that prioritized speed over structure tends to accelerate software ageing, making future changes harder.

Reference

Software Engineering, Ian Sommerville, 10th edition

Quizzes you can take where this question appears

Software Evolution - Use Case Scenarios