Maintaining object-oriented software

The maintenance requirements of object-oriented software, including the ability to make changes easily and an in-depth understanding of the software's structure and behavior, are discussed. The problems encountered by a maintainer trying to understand object-oriented software by reading and statically analyzing it are described. The problems caused by dynamic binding, polymorphism, and cooperating object classes in object-oriented software maintenance are reviewed.<<ETX>>

[1]  E. B. Swanson,et al.  Software maintenance management , 1980 .

[2]  Grady Booch,et al.  Object-oriented development , 1986, IEEE Transactions on Software Engineering.

[3]  Elliot Soloway,et al.  Designing documentation to compensate for delocalized plans , 1988, CACM.

[4]  Karl J. Lieberherr,et al.  Assuring good style for object-oriented programs , 1989, IEEE Software.

[5]  D. Mancl,et al.  A study of the impact of C++ on software maintenance , 1990, Proceedings. Conference on Software Maintenance 1990.

[6]  Norman Wilde,et al.  Maintenance support for object oriented programs , 1991, Proceedings. Conference on Software Maintenance 1991.

[7]  Norman Wilde,et al.  A reusable toolset for software dependency analysis , 1991, J. Syst. Softw..