volume_mute
Matching Strategic Options to Scenarios
publish date: 2026/06/24 21:04:2.734673 UTC
volume_muteMatch each described scenario to the most appropriate strategic option for legacy system management.
To complete the line match
- Click on an item in the first group
- Click on the match in the second group
To delete a match, double click on a line
Scenario
A payroll system that business processes no longer use because operations moved entirely to a third-party cloud payroll provider
An order processing system that works well and receives only occasional minor change requests
A customer database system that is heavily relied upon but whose code has become very difficult and costly to modify after years of patches
An inventory system running on hardware that the manufacturer has discontinued and can no longer be supported
Option
Replace the system
Leave unchanged with regular maintenance
Scrap the system completely
Reengineer the system
Correct Answer
(1) A payroll system that business processes no longer use because operations moved entirely to a third-party cloud payroll provider,Scrap the system completely
(2) An order processing system that works well and receives only occasional minor change requests,Leave unchanged with regular maintenance
(3) A customer database system that is heavily relied upon but whose code has become very difficult and costly to modify after years of patches,Reengineer the system
(4) An inventory system running on hardware that the manufacturer has discontinued and can no longer be supported,Replace the system
Explanation
Each scenario maps to a different strategic response: a system no longer contributing to business processes should be scrapped; a stable system with few requests should be left with regular maintenance; a heavily relied-upon but degraded system should be reengineered; and a system constrained by unsupportable hardware should be replaced.
Reference
Software Engineering, Ian Sommerville, 10th edition