Maybe there needs to be some formal guidance on when a software application is out of date and needs to be rewritten? The banking industries reliance on ancien

Maybe there needs to be some formal guidance on when a software application is out of date and needs to be rewritten? The banking industries reliance on ancient code written in Cobol has caused them (and everyone) numerous problems. If there continues to be massive churn in software design then there probably needs to be an expiration date for software as well. It can't be a specific time period like 10 years, it has to be based instead on the number and kind of problems caused by ancient software and the resources of the company using it. A cost-benefit analysis with a large variety of inputs. Perhaps computer science should do more work on the inherent difficulty of migrating software as well. Software that is expected to be long lived should be written differently than software expected to be thrown away in 5 or 10 years.