Maintaining object-oriented software

descriptionPublicationkeyboard_double_arrow_right Article 01 Jan 1993Publisher:Institute of Electrical and Electronics Engineers (IEEE)Journal:IEEE Software, volume 10, pages 75-80 (issn: 0740-7459,

Copyright policy )

Authors: Norman Wilde; Paul Matthews; Ross Huitt;

doi: 10.1109/52.207232

Maintaining object-oriented software

- Summary
- Metrics

Abstract

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

Related Organizations

University of West Florida
United States

Impact byBIP!

	selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).	55
	popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.	Top 10%
	influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).	Top 1%
	impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.	Top 10%