Software maintenance in package engineering is that the modification of a product once delivery to correct faults, to enhance performance or different attributes.
A common perception of maintenance is that it just involves fixing defects. However, one study indicated that over eightieth of maintenance effort is employed for non-corrective actions.
An integral a part of package is that the maintenance one, which needs Associate in Nursing correct maintenance conceive to be ready throughout the package development. It ought to specify however users can request modifications or report issues. The budget ought to embrace resource and value estimates. a brand new call ought to be self-addressed for the developing of each new system feature and its quality objectives. The package maintenance, which may last for 5�6 years (or even decades) once the event method, requires an efficient arrange which may address the scope of package maintenance, the craft of the post delivery/deployment method, the designation of United Nations agency can offer maintenance, Associate in Nursingd an estimate of the life-cycle prices. the choice of correct social control of standards is that the difficult task right from early stage of package engineering that has not got definite importance by the involved stakeholders.
Software maintenance processes
- 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.
