Which type of maintenance activity involves keeping the software up to date and focuses on making the software work on new environment?
Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes.[1][2] Show
A common perception of maintenance is that it merely involves fixing defects. However, one study indicated that over 80% of maintenance effort is used for non-corrective actions.[3] This perception is perpetuated by users submitting problem reports that in reality are functionality enhancements to the system.[citation needed] More recent studies put the bug-fixing proportion closer to 21%.[4] History[edit]Software maintenance and evolution of systems was first addressed by Meir M. Lehman in 1969. Over a period of twenty years, his research led to the formulation of Lehman's Laws (Lehman 1997). Key findings of his research conclude that maintenance is really evolutionary development and that maintenance decisions are aided by understanding what happens to systems (and software) over time. Lehman demonstrated that systems continue to evolve over time. As they evolve, they grow more complex unless some action such as code refactoring is taken to reduce the complexity. In the late 1970s, a famous and widely cited survey study by Lientz and Swanson, exposed the very high fraction of life-cycle costs that were being expended on maintenance. The survey showed that around 75% of the maintenance effort was on the first two types, and error correction consumed about 21%. Many subsequent studies suggest a similar problem magnitude. Studies show that contribution of end users is crucial during the new requirement data gathering and analysis. This is the main cause of any problem during software evolution and maintenance. Software maintenance is important because it consumes a large part of the overall lifecycle costs and also the inability to change software quickly and reliably means that business opportunities are lost. [5] [6] [7] Importance of software maintenance[edit]The key software maintenance issues are both managerial and technical. Key management issues are: alignment with customer priorities, staffing, which organization does maintenance, estimating costs. Key technical issues are: limited understanding, impact analysis, testing, maintainability measurement. Software maintenance is a very broad activity that includes error correction, enhancements of capabilities, deletion of obsolete capabilities, and optimization. Because change is inevitable, mechanisms must be developed for evaluation, controlling and making modifications. So any work done to change the software after it is in operation is considered to be maintenance work. The purpose is to preserve the value of software over the time. The value can be enhanced by expanding the customer base, meeting additional requirements, becoming easier to use, more efficient and employing newer technology. Maintenance may span for 20 years,[citation needed] whereas development may be 1–2 years.[citation needed] Software maintenance planning[edit]An integral part of software is maintenance, which requires an accurate maintenance plan to be constructed during the software development. It should specify how users will request modifications or report problems. The budget should include resource and cost estimates, and a new decision should be addressed for the development of every new system feature and its quality objectives. The software maintenance, which can last for 5+ years (or even decades) after the development process, calls for an effective plan which can address the scope of software maintenance, the tailoring of the post delivery/deployment process, the designation of who will provide maintenance, and an estimate of the life-cycle costs. Software maintenance processes[edit]This section describes the six software maintenance processes as:
There are a number of processes, activities, and practices that are unique to maintainers, for example:
Categories of software maintenance[edit]E.B. Swanson initially identified three categories of maintenance: corrective, adaptive, and perfective.[8] The IEEE 1219 standard was superseded in June 2010 by P14764.[9] These have since been updated and ISO/IEC 14764 presents:
There is also a notion of pre-delivery/pre-release maintenance which is all the good things you do to lower the total cost of ownership of the software. Things like compliance with coding standards that includes software maintainability goals. The management of coupling and cohesion of the software. The attainment of software supportability goals (SAE JA1004, JA1005 and JA1006 for example). Some academic institutions[who?] are carrying out research to quantify the cost to ongoing software maintenance due to the lack of resources such as design documents and system/software comprehension training and resources (multiply costs by approx. 1.5-2.0 where there is no design data available). Maintenance factors[edit]Impact of key adjustment factors on maintenance (sorted in order of maximum positive impact)
Not only are error-prone modules troublesome, but many other factors can degrade performance too. For example, very complex spaghetti code is quite difficult to maintain safely. A very common situation which often degrades performance is lack of suitable maintenance tools, such as defect tracking software, change management software, and test library software. Below describe some of the factors and the range of impact on software maintenance. Impact of key adjustment factors on maintenance (sorted in order of maximum negative impact)
[10] Maintenance debt[edit]In a paper for the 27th International Conference on Software Quality Management in 2019,[11] John Estdale introduced the term “maintenance debt” for maintenance needs generated by an implementation’s dependence on external IT factors such as libraries, platforms and tools, that have become obsolescent.[12] The application continues to run, and the IT department forgets this theoretical liability, focussing on more urgent requirements and problems elsewhere. Such debt accumulates over time, silently eating away at the value of the software asset. Eventually something happens that makes system change unavoidable. The owner may then discover that the system can no longer be modified – it is literally unmaintainable. Less dramatically, it may take too long, or cost too much, for maintenance to solve the business problem, and an alternative solution must be found. The software has suddenly crashed to £0 value. Estdale defines "Maintenance Debt"[12] as: the gap between the current implementation state of an application and the ideal, using only functionality of external components that is fully maintained and supported. This debt is often hidden or not recognized. An application’s overall maintainability is dependent on the continuing obtainability of components of all sorts from other suppliers, including:
and of course
The complete disappearance of a component could make the application un-rebuildable, or imminently unmaintainable. See also[edit]
References[edit][13]
Further reading[edit]
External links[edit]
Which type of maintenance activity in was keeping the software up to date and focuses on making the software work on new environment?Adaptive Software Maintenance
Adaptive maintenance aims at updating and modifying the software when: The platform in which your software operates is changing (due to technology, laws, policies, rules, operating system,etc.)
Which type of maintenance activity involves keeping the software up to date?Adaptive Maintenance - This includes modifications and updations applied to keep the software product up-to date and tuned to the ever changing world of technology and business environment.
What are the 4 types of software maintenance?What are the 4 types of software maintenance?. Corrective Software Maintenance. Corrective software maintenance is the typical, classic form of maintenance (for software and anything else for that matter). ... . Preventative Software Maintenance. ... . Perfective Software Maintenance. ... . Adaptive Software Maintenance.. Which type of maintenance ensures the system to run on changing environment and also a new environment?Adaptive maintenance is concerned with the changes made to the software in order to make it adaptable to new environments, such as running it on a new operating system. The term "perfective maintenance" refers to the changes in the software that occur as a result of adding new features.
|