Q. Discuss the problems faced during software maintenance?

The most significant problem during maintenance is that before correcting or else modifying a program the programmer must first understand it. Subsequently the programmer must understand the impact of the intended change. Only some problems are discussed below. Habitually the program is written by another person or group of persons working over the years in isolation from each other. Habitually the program is changed by person who didn't understand it clearly resulting in a deterioration of the program's original organization. Program listing still those that are well organized aren't structured to support reading or comprehension. We usually read article or book straight through but with listing programmer rummages back and forth.

There is a high workforce turnover within information Technology industry. Because of this many systems are maintained by persons who are not the original authors. These persons mayn't have adequate knowledge about the system. This may denote that these persons may introduce changes to programs without being aware of their effects on other parts of the system -the ripple effect. This problem may be worsened by the absence of documentation. Even where it subsists it may be out of date or else inadequate.

A few problems merely become clearer when a system is operational. Several users know that they desire but lack the ability to express it in a variety understandable to programmers/analysts. This is primarily because of information gap.

Systems aren't designed for change. If there is barely any scope for change maintenance will be very difficult. So approach of development should be the production of maintainable software.