Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Software maintenance”

Software Maintenance

H. Kopetz · 1976

The development of a system can be said to be complete as soon as it is taken over by the user after the acceptance test. Any work that must be performed on the system after acceptance to support a particular state of the software is known as software maintenance.

Cited by 0

Software Maintenance

National Cancer Institute · Definitions · 2020

Ope n Pe e r Re v ie w on Qe ios

Cited by 0Open access

Software Maintenance

Ms. Harpreet Kaur, Ms. Rinku Kalotra · Zenodo (CERN European Organization for Nuclear Research) · 2025

Software maintenance represents an essential stage of the software development life cycle (SDLC), ensuring that the software system remain dependable, secure and capable of adapting to changing user requirements. With rapid advancements in technology, maintaining software has become more challenging and now involves tasks such as fixing defects, enhancing performance, implementing adaptive updates and applying preventive improvements. The study categorises maintenance into corrective, adaptive, perfective and preventive activities, highlighting how each contributes to addressing defects, meeting evolving requirements, optimizing functionality and reducing future risks.

Cited by 0Open access

Software Maintenance

Erich Prem · Techné Research in Philosophy and Technology · 2025

The aim of this paper is to challenge and push back against the view that making and maintaining artefacts should be regarded an action where a maker’s intentions are imposed on matter. It addresses software maintenance and how to best conceptualize it to clarify aspects such as software’s formal nature, how it is conceived and produced, and its relation to users and their expectations. The paper diverges from a tradition in the philosophy of artefacts focused on maker’s intentions to clarify the ontological nature of artefacts and their maintenance. It starts from a conceptual analysis of software maintenance and identifies important differences of software to other artefacts including inherent faultiness and functional change. In discussing the ontology of software, the paper proposes a shift from maker’s intentions to functional and organisational criteria and on development processes involving interactions of users and designers to anticipate users’ future needs.

Cited by 0

Software Maintenance

Ms. Rinku Kalotra, Harpreet Kaur · Zenodo (CERN European Organization for Nuclear Research) · 2025

Software maintenance represents an essential stage of the software development life cycle (SDLC), ensuring that the software system remain dependable, secure and capable of adapting to changing user requirements. With rapid advancements in technology, maintaining software has become more challenging and now involves tasks such as fixing defects, enhancing performance, implementing adaptive updates and applying preventive improvements. The study categorises maintenance into corrective, adaptive, perfective and preventive activities, highlighting how each contributes to addressing defects, meeting evolving requirements, optimizing functionality and reducing future risks.

Cited by 0Open access

Software maintenance

Andréa Sabedra Bordin, Fabiane Barreto Vavassori Benitti · 2018

Software engineering has been consolidated in the last decades with the increasing production of software products and with the consequent increase in the demand for maintenance of these products, making evident the relevance of the so called maintenance phase in the life cycle of a product. However, it is observed that both academy and industry do not prioritize research and practices in this area. Based on the assumption that academic education promotes the application of best practices in the software industry and that industry practices provide subsidies to delineate what should be taught and researched in the academy, one believes it is important to analyze how software maintenance has been addressed in these two contexts. The goal of this paper is to identify if what is being taught is in accordance with the international and national curricular guidelines as well as to relate the contents recommended and taught with software maintenance practices of the industry. In order to achieve this goal, a document review was carried out on the curricular guidelines and syllabus that address software maintenance in software engineering undergraduate programs and a survey was applied in the industry to identify the practices in this area. The document review resulted in 21 topics, among which basic concepts, maintenance process, reengineering and refactoring are the most referenced topics. The comparative analysis between the academy and professional perspective revealed that the topics related to the maintenance process and reengineering are little applied in industry. On the other hand, particular aspects related to the legacy systems and the impact analysis area are a reality in companies, however little explored in the academy.

Cited by 3

Software Maintenance

Ms. Rinku Kalotra, Harpreet Kaur · Zenodo (CERN European Organization for Nuclear Research) · 2025

Software maintenance represents an essential stage of the software development life cycle (SDLC), ensuring that the software system remain dependable, secure and capable of adapting to changing user requirements. With rapid advancements in technology, maintaining software has become more challenging and now involves tasks such as fixing defects, enhancing performance, implementing adaptive updates and applying preventive improvements. The study categorises maintenance into corrective, adaptive, perfective and preventive activities, highlighting how each contributes to addressing defects, meeting evolving requirements, optimizing functionality and reducing future risks.

Cited by 0Open access