This definition doesn’t necessarily fit for applications. Software maintenance differs from hardware maintenance although software does wear out, but gets useful with age. Software may be delivered with flaws that were undiscovered. While software maintenance can be treated as a level of work activity, there are results on schedule, functionality, reliability, cost and quality which may be mitigated through the use of estimation methods.

Among the challenges is that the management of change management. It’s been estimated that the expense of change control can vary between 40 percent and 70 percent of their life cycle costs . Software engineers have expected that new procedure and new languages would reduce these numbers. This is because software is delivered with a number of defects. This article’s purpose is to present alternative approaches and to review the principles of software maintenance. An integral element to note is that management and development decisions can impact the maintenance costs and the cost.


First, watch this video below:

Activities include all work must be distinguished from block alterations which represent design and development effort and completed post-delivery and supersede a software package that is previously released. These maintenance activities can be diverse, and it will help to identify just what actions must be included in an estimate of maintenance effort.

Software maintenance differs from hardware maintenance since software does wear out, but software gets useful with age and it could be delivered with flaws that are undiscovered.

Along with the flaws that are undiscovered, it’s common that some number of defects pass to the care group from the development company. That’s why its also important not just to maintain but to upgrade your software. You don’t want 8 Ball Pool Hack Android ads to pop out in your website or software. Most especially, you don’t want virus attached in your software.

Maintenance is a complex and structured procedure. Estimating Software Intensive Systems, in his textbook, the software maintenance procedure that is normal is outlined by Richard Stuzke. It’s apparent that the procedure is more than writing code that is new.

The following checklist may be used to explore precision and the realism of maintenance requirements.

  • Which pieces of software is going to be maintained?
  • How long will the system must be maintained?
  • Are you incremental maintenance, or currently estimating the maintenance problem?
  • What level of care is necessary?
  • Is what is being called maintenance in reality a development project that is brand new?
  • Will the developer does organically it? Will there be a team that is different?
  • Will there be a different organization?
  • Will maintainers be using the very same tools?
  • Are any tools necessary for maintenance?

This will inflate cause shortfalls, or maintenance statistics if maintenance gets pushed. These questions can allow you to ask if maintenance is being represented. The reason behind this is that maintenance activities can be carried on rendering any rules that are life-cycle useless.

As we spend creating applications we spend about 2-3 times as much effort maintaining and improving applications.

Similar observations and this apply higher and at an organizational level, but not for a particular project. Any development group with a history is going to be embroiled in the tail ends of their projects that are deliveredneeding attention that is indefinite.

As in growth, a difference is made by the quantity of code that’s new versus. The size, in other words, the equal effort if of the work were code that is fresh, is the essential input for maintenance cost estimate and development.


All program estimation techniques must have the ability to simulate the theory and the likely real world outcome. The actual world situation is that over time, applications difficult to keep and less useful is made by the overlay of changes upon changes. Effort estimation techniques include the level of work process, through development practice modifications and thoughtful analysis in order to use data to project future demands.

The article’s conclusions are:
  1. Software maintenance can be modeled using a method that was simplistic but this technique has drawbacks.
  2. Management decisions can significantly affect Software maintenance costs throughout the process.
  3. Software maintenance can be estimated using procedures.
  4. When management and development decisions are combined with cost estimation methods, Software maintenance is modeled.