Application Demo

Yahoo Messenger

     

    Please do not hesitate to contact us for more information.

     

     

Contact Us

     

    Please do not hesitate to contact us for more information.

     

  •  

    Untung

    +62813 1150 7231

    +62878 8745 8682

    untung@awscenter.net

     

  •  

    Abdul Gopur

    +62815 1010 9234

    +62818 0755 2980

    abdul.gopur@awscenter.net

     

  •  

    Ferry Gunawan

    +62877 9018 9717

    ferry@autoworksys.com

     

  •  

    Immanuel G. Souhoka

    +62888 0162 0296

    emil.souhoka@gmail.com

     

Application Maintenance

 

Application Maintenance

 

Application 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 the majority, over 80%, of the maintenance effort is used for non-corrective actions (Pigosky 1997). This perception is perpetuated by users submitting problem reports that in reality are functionality enhancements to the system[citation needed].

Software maintenance and evolution of systems was first addressed by Meir M. Lehman in 1969. Over a period of twenty years, his research led to the formulation of Lehman's Laws (Lehman 1997). 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.

The 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.