#Workdone company software software#
#Workdone company software code#

Transition: a controlled and coordinated sequence of activities during which a system is transferred progressively from the developer to the maintainer.

There are a number of processes, activities, and practices that are unique to maintainers, for example:

Finally, the last maintenance process, also an event which does not occur on a daily basis, is the retirement of a piece of software.

#Workdone company software software#

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. The migration process ( platform migration, for example) is exceptional, and is not part of daily maintenance tasks.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 process considering the implementation of the modification itself.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 problem and modification analysis process, which is executed once the application has become the responsibility of the maintenance group.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.This section describes the six software maintenance processes as: 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. 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. It should specify how users will request modifications or report problems. Software maintenance planning Īn integral part of software is maintenance, which requires an accurate maintenance plan to be constructed during the software development. Maintenance may span for 20 years, whereas development may be 1–2 years. The value can be enhanced by expanding the customer base, meeting additional requirements, becoming easier to use, more efficient and employing newer technology. The purpose is to preserve the value of software over the time. So any work done to change the software after it is in operation is considered to be maintenance work. Because change is inevitable, mechanisms must be developed for evaluation, controlling and making modifications. Software maintenance is a very broad activity that includes error correction, enhancements of capabilities, deletion of obsolete capabilities, and optimization. Key technical issues are: limited understanding, impact analysis, testing, maintainability measurement. Key management issues are: alignment with customer priorities, staffing, which organization does maintenance, estimating costs. The key software maintenance issues are both managerial and technical. 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. This is the main cause of any problem during software evolution and maintenance. Studies show that contribution of end users is crucial during the new requirement data gathering and analysis. Many subsequent studies suggest a similar problem magnitude. The survey showed that around 75% of the maintenance effort was on the first two types, and error correction consumed about 21%. 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.

#Workdone company software code#

As they evolve, they grow more complex unless some action such as code refactoring is taken to reduce the complexity. Lehman demonstrated that systems continue to evolve over time. 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. Over a period of twenty years, his research led to the formulation of Lehman's Laws (Lehman 1997). Software maintenance and evolution of systems was first addressed by Meir M.