Skip to content
Facebook (Opens in a new window) YouTube (Opens in a new window) Twitter (Opens in a new window) Flickr (Opens in a new window) LinkedIn (Opens in a new window) Instagram (Opens in a new window)
Systems Engineering for ITS
Retirement / Replacement ChecklistRetirement / Replacement Checklist

The Microsoft Word version of this checklist is an editable form that can be used to support process reviews.


Process Checklist
Are all the bases covered? Yes No Not Applicable Comments
Was a trade study done on the cost/benefit of upgrading the legacy system against the cost/benefit of developing or procuring a new system?        
Did the trade studies include the operations & maintenance costs of the current and replacement system?        
Is the replacement system well documented? Does it have a concept of operations, requirements, and documentation necessary to support operations and maintanence.        
Is there a replacement strategy to switch out the current system with the replacement?        
Have all of the affected stakeholders been involved in the replacement/retirement decision, and the planning and replacement strategy for the new system?        
  • High-level design documentation
        
  • Detailed design documentation
        
  • Verification plans
        
  • Support documentation on development, training, maintenance, and users' manuals
        
Is there a replacement strategy to switch out the current system with the replacement?        
Have all of the affected stakeholders been involved in the replacement/retirement decision, and the planning and replacement strategy for the new system?        
Have all of the affected stakeholders been involved in the replacement/retirement decision, and the planning and replacement strategy for the new system/subsystem?        
Back to top of page