Software maintenance

Software maintenance and evolution of systems was first addressed by Meir M. Lehman in 1969.

Software evolution is the term used in software engineering (specifically software maintenance) to refer to the process of developing software initially, then repeatedly updating it for various reasons.

Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes.

Software maintenance: refers to the activities required to provide cost-effective support after shipping the software product.

For example, very complex spaghetti code is quite difficult to maintain safely.

Spaghetti code is a pejorative phrase for unstructured and difficult-to-maintain source code.

Long-term support (LTS) is a product lifecycle management policy in which a stable release of computer software is maintained for a longer period of time than the standard edition.

In software engineering, these activities are known as software maintenance (cf.

Software archaeology or software archeology is the study of poorly documented or undocumented legacy software implementations, as part of software maintenance.

When porting the application to run on another OS, the functionality required by that application may be implemented differently by that OS (the names of functions, meaning of arguments, etc.) requiring the application to be adapted, changed, or otherwise maintained.

Software development is a process of writing and maintaining the source code, but in a broader sense, it includes all that is involved between the conception of the desired software through to the final manifestation of the software, sometimes in a planned and structured process.

Search techniques have been applied to other software engineering activities, for instance, requirements analysis, design, development, and maintenance.

A common perception of maintenance is that it merely involves fixing defects.

Software maintenance and evolution of systems was first addressed by Meir M. Lehman in 1969.

As they evolve, they grow more complex unless some action such as code refactoring is taken to reduce the complexity.

Key technical issues are: limited understanding, impact analysis, testing, maintainability measurement.

The browser is discontinued, but still maintained.

The software industry includes businesses for development, maintenance and publication of software that are using different business models, mainly either "license/maintenance based" (on-premises) or "Cloud based" (such as SaaS, PaaS, IaaS, MaaS, AaaS, etc.).

Application lifecycle management (ALM) is the product lifecycle management (governance, development, and maintenance) of computer programs.