volume_mute

Emergency Changes Model

publish date: 2026/06/06 23:08:31.973877 UTC

volume_mute

Suggest a process model for making emergency software changes while keeping requirements and implementation consistent. Which of the following is the most critical principle for such a model?

Allow verbal approval of changes without any written record

Reject all emergency change requests and wait for the next planned release

Implement the emergency change in code, then as soon as possible update the requirements document and maintain a traceability link between the code change and the updated requirement

Skip all documentation when making emergency changes to save time

Correct Answer

Implement the emergency change in code, then as soon as possible update the requirements document and maintain a traceability link between the code change and the updated requirement

Explanation

For genuine emergencies, implementing the code change first is pragmatic — waiting for full requirements approval may not be feasible. However, the requirements document MUST be updated as soon as possible afterward, with a traceability link maintained. This minimizes the risk of the requirements and implementation getting permanently out of step.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears

Applied Requirements Engineering - Exercises