Editing Software maintenance (section)

==History==
In the early 1970s, companies began to separate out software maintenance with its own team of engineers to free up [[software development]] teams from support tasks.{{sfn|Tripathy |Naik|2014|p=25}} In 1972, R. G. Canning published "The Maintenance 'Iceberg{{'"}}, in which he contended that software maintenance was an extension of software development with an additional input: the existing system.{{sfn|Tripathy |Naik|2014|p=25}} The discipline of software maintenance has changed little since then.<ref name=Offutt>{{cite web |last1=Offutt |first1=Jeff |author1-link=Jeff Offutt |title=Overview of Software Maintenance and Evolution |url=https://cs.gmu.edu/~offutt/classes/437/maintessays/maintEvolutionOverview.html |website=[[George Mason University]] Department of Computer Science |access-date=5 May 2024 |date=January 2018}}</ref> One twenty-first century innovation has been companies deliberately releasing incomplete software and planning to finish it post-release. This type of change, and others that expand functionality, is often called [[software evolution]] instead of maintenance.<ref name=Offutt/>