Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes. PDF Printer Version. Document issued on January 11, 2002. This document supersedes the draft document, General Principles of Software Validation, Version. Software Testing Types. Given below are few types of Software Testing. Alpha Testing. It is the most common type of testing used in software industry. The Software Maintenance knowledge area KA is related to all other aspects of software engineering. Therefore, this KA description is linked to all other software. Types Of Software Maintenance' title='3 Types Of Software Maintenance' />Software maintenance Wikipedia. Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes. A common perception of maintenance is that it merely involves fixing defects. However, one study indicated that over 8. This perception is perpetuated by users submitting problem reports that in reality are functionality enhancements to the system. More recent studies put the bug fixing proportion closer to 2. HistoryeditSoftware maintenance and evolution of systems was first addressed by Meir M. Lehman in 1. 96. 9. Crack Delta Force 2 Extreme on this page. Over a period of twenty years, his research led to the formulation of Lehmans Laws Lehman 1. Free software download,The biggest software directory for freeware and shareware download at brothersoft. Omnext white paper 2014 Omnext BV How to save on software maintenance costs 3 Figure 2 Analyzing is almost 50 of the total maintenance. Key findings of his research include 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 1. 97. Lientz and Swanson, exposed the very high fraction of life cycle costs that were being expended on maintenance. They categorized maintenance activities into four classes Adaptive modifying the system to cope with changes in the software environment DBMS, OS 4Perfective implementing new or changed user requirements which concern functional enhancements to the software. So you want to be a 3D artist, but you dont know which software to choose Whether youre a newcomer to art programs or incredibly experienced, here are the. Online tests and testing for certification, practice tests, test making tools, medical testing and more. ManagerPlus Desktop Benefits. ManagerPlus Desktop is a true maintenance management system that will allow you to track your assets, and streamline your workflow like. Corrective diagnosing and fixing errors, possibly ones found by users 4Preventive increasing software maintainability or reliability to prevent problems in the future 4The survey showed that around 7. Many subsequent studies suggest a similar magnitude of the problem. Studies show that contribution of end user is crucial during the new requirement data gathering and analysis. And this is the main cause of any problem during software evolution and maintenance. So 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. Importance of software maintenanceeditThe 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 2. Software maintenance planningeditAn integral part of software is the maintenance one, which requires an accurate maintenance plan to be prepared during the software development. It should specify how users will request modifications or report problems. The budget should include resource and cost estimates. A new decision should be addressed for the developing of every new system feature and its quality objectives. The software maintenance, which can last for 56 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 deliverydeployment process, the designation of who will provide maintenance, and an estimate of the life cycle costs. The selection of proper enforcement of standards is the challenging task right from early stage of software engineering which has not got definite importance by the concerned stakeholders. Software maintenance processeseditThis section describes the six software maintenance processes as The implementation process contains software preparation and transition activities, such as the conception and creation of the maintenance plan the preparation for handling problems identified during development and the follow up on product configuration management. The problem and modification analysis process, which is executed once the application has become the responsibility of the maintenance group. The maintenance programmer must analyze each request, confirm it by reproducing the situation and check its validity, investigate it and propose a solution, document the request and the solution proposal, and finally, obtain all the required authorizations to apply the modifications. The process considering the implementation of the modification itself. The process acceptance of the modification, by confirming the modified work with the individual who submitted the request in order to make sure the modification provided a solution. The migration process platform migration, for example is exceptional, and is not part of daily maintenance tasks. If the software must be ported to another platform without any change in functionality, this process will be used and a maintenance project team is likely to be assigned to this task. Finally, the last maintenance process, also an event which does not occur on a daily basis, is the retirement of a piece of software. There are a number of processes, activities and practices that are unique to maintainers, for example Transition a controlled and coordinated sequence of activities during which a system is transferred progressively from the developer to the maintainer Service Level Agreements SLAs and specialized domain specific maintenance contracts negotiated by maintainers Modification Request and Problem Report Help Desk a problem handling process used by maintainers to prioritize, documents and route the requests they receive Categories of maintenance in ISOIEC 1. E. B. Swanson initially identified three categories of maintenance corrective, adaptive, and perfective. The IEEE 1. June 2. P1. These have since been updated and ISOIEC 1. Corrective maintenance Reactive modification of a software product performed after delivery to correct discovered problems. Adaptive maintenance Modification of a software product performed after delivery to keep a software product usable in a changed or changing environment. Perfective maintenance Modification of a software product after delivery to improve performance or maintainability. Preventive maintenance Modification of a software product after delivery to detect and correct latent faults in the software product before they become effective faults. There is also a notion of pre deliverypre 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 JA1. JA1. 00. 5 and JA1.