Bob Hunt asked: AbstractThe The dictionary defines maintenance as, "The conservation work of something in order." Adequate, however, this definition is not necessarily suitable for software. Maintenance of software is different from hardware maintenance because software doesn 't consume physically, but often gets less useful with age. The software is typically delivered with no faults detected. Consequently, maintenance of software is: "The process of modifying existing operational software while leaving its primary functions intact." Maintenance typically exceeds fifty percent of the systems' cost of life cycle. While the maintenance of software can be treated as a level of effort, there are consequences on quality, functionality, reliability, cost and the program that may diminish with the use of the parametric evaluation techniques.1. INTRODUCTIONOne of the biggest challenges facing the Engineei Software is the administration of change control. It is estimated that the cost of monitoring the change may be between 40% and 70% of the life cycle. The Software Engineei have hoped that new languages and new process will significantly reduce these numbers, but this was not the case. This is basically because the software is still delivered with a significant number of defects. The capers Jones estimates that there are about 5 bugs per function point generated during development. Watt "found Humphrey; … even the experienced Software Engineei normally inject 100 or more defects per KSLOC. The capers Jones says, "A series of studies the defect density of software ranges from 49.5 to 94.5 errors per thousand lines of code. "The purpose of this article is to first examine the fundamentals of software maintenance and present alternative methods to assess the maintenance of software. A key element to note is that the development of and decisions taken during the development process can significantly affect the cost of construction and maintenance resulting costs.2. The activities of the SOFTWARE MAINTENANCEMaintenance include all post-delivery work, and should be distinguished from changes in the block representing the design and the significant development effort and substitute a package of previously released programs. These maintenance activities can be quite different and helps to identify exactly which assets of the post-delivery must be included in an estimate of maintenance effort. Maintenance activities, once defined, can be evaluated in a different light enough that when "simply called; maintenance. Maintenance of software is different from hardware maintenance because software doesn 't physically consumed, but the software often gets less useful with age and can be transported with the defects discovered. In addition to the defects discovered, it is common that a number of known defects is changed by the development team of maintenance. The exact evaluation of the effort required to make the software helps you transported from the decomposition of the general effort in the various activities that make the whole process.3. The AVVICINAMENTO MAINTENANCE ISSUEMaintenance is a complicated and structured process. In his manual, valutante systems dependent on logic, Richard Stuzke describes the typical process of software maintenance. It is apparent that the process is more of just writing the new code. The following checklist can be used to explore the realism and accuracy of requests for maintenance. ? Â that the software will be made? ? Â how long the system needs to be done? The? Â is that you evaluate the whole issue of maintenance, servicing or just incremental? ? Â that the level of maintenance is required? The? Â is what it is calling the maintenance in effect a new draft? ? Â Who does the maintenance? Will be done organically by the original developer? There will be a separate team? The? Â there will be a separate? The? Â maintainers will use the same tools used during development? Patented gear required for maintenance? ? Â How much Commercial-Off – Shelf (cot) is there? How closely linked are the interfaces? The? Â a continuation of development may be disguised as maintenance. This figure gonfierà or maintenance, or because the deficiency if the basic maintenance gets pushed aside. These questions will help to ask if the maintenance is honest rappresentanda. The? Â of the activity is really an incremental improvement? The? Â is healthy beautiful pieces of that original code is rewritten or variable? The? Â additional staff will be brought in to upgrade? ? Â is the effort of normal and reasonable maintenance plan, or it contains the recruitment of staff humps that look like news? 4th The scrutiny of health of mind CHECKSAlthough HEALTH OF MIND should be sought each year on a base, should not be attempted for the general development. The reason for this is that maintenance activities can be continued indefinitely, making the cycle of life rule not applicable. As an example, consider Grady (P. 17): Let about 2-3 times more effort to maintain and enhance the software as we spend creating new software. This and similar comments to make the application to an organizational level and higher, but not for a specific project. Any development group with a history will be involved in the conclusion of their long tail of many projects carried, still having need the indefinite. Here are some quick checks health of mind: The maintainer of? Â one may treat of about 10,000 lines a year. The general effort of the life cycle? Â is the development and maintenance of 60% to 40% in general. The costs of retaining? Â are on average one sixth of the annual costs of implementation. Systems? Â the successful are usually made for 10 – 20 years. Finally, as in the developing world, the amount of code that is new to make a difference amended. The effective size, ie, the equivalent effort if all the work were new code, is still the key input for the development is that the costs of maintaining estimation.5. FIVE ALTERNATIVE technical evaluation of software APPROACHESAll must be able to shape the theory and the likely outcome of the real world. The action plan of the real world is as time goes on that, the overlap of the changes on the changes the software makes it increasingly difficult to make and thus less useful. The technical evaluation of maintenance of effort varies by the level of simplistic method of effort, with the more caring and changes of practice development, the use of parametric models to use historical data to project the future level needs.5.1 of EffortAs is sometimes the case in the development, maintenance of software can be modeled as a level of effort. Since the category of repair and that show great variance, this method clearly has shortcomings. In this method, a level of effort to make the software is based on the format and level type.5.2 effort PlusStuzke proposed that maintenance of software begins with the level of effort basis (people had to have at least one jurisdiction center and then the basic staff of the center should be modified by assessing three additional factors, administration configuration, quality assurance and project management. The process has attracted a number of additional factors affecting the assessment of the cost of the change of FactorSoftware software maintenance maintenance.5.3 with COCOM II (Boehm 2000) proposes a deceivingly simple, but quite useful methodology for the determination of annual maintenance. Maintenance is one of the menu selections in the menu bar. In COCOM II includes maintenance the process of modifying existing operational software while leaving its primary functions intact. This process does not include: redesign of the greatest? Â and Reconstruction (new code more than 50%) of new software product performing substantially the same functions . drawing? Â and development (more than 20% of the installation source that contains the current product) of a software package that important connection requires relatively little redesigning of the current product. Runs the system of data of? Â, data entry and editing values in the database. The calculations of maintenance are based on the very factor of the change in maintenance (MCF) and the adjustment coefficient of maintenance (MAF). The MCF is similar to annual traffic of change in COCOMO81, except that the periods of maintenance except for one year may be used. The resulting formula for assessing maintenance effort is the same as the model for the development of architecture dell'alberino of COCOM II. As stated previously, three cost drivers for maintenance differ from development. Those cost drivers are software reliability, modern programming practices and programs. COCOM II assumes that increased investment in software reliability and use of modern programming practices during software development has a strong positive effect on the maintenance phase. The annual maintenance effort = (Annual Change Traffic) * (original effort of software development) effort to develop original software quantity refers to the total effort ( person-months or other unit of measure) consumed during development, although a multi-annual project. The annual traffic of the change in multiplier is the proportion of the overall software to be amended during the year. This is relatively easy to occur in the calculations engineering. The developers often make lists of change, or have a sense of proportional change to be requested even before the development is in keeping costs borne by the software complete.5.4 through technical and administrative decisions relating to development during the development when it is maintained, "a penny spent is a pound saved." Best practices in development (though more expensive) can significantly reduce the maintenance effort and reduce the cost of life generally. More effort has development, less maintenance required. As an example, the cost of software development and the program can be bumped significantly (reduction), leaving the number of defects transported develop. This reduction program and the cost is more than compensated by increasing
Create a video blog
