Proceedings. Conference on Software Maintenance 1991
DOI: 10.1109/icsm.1991.160325
|View full text |Cite
|
Sign up to set email alerts
|

Support for maintaining object-oriented programs

Abstract: Abstract-In this paper, we explain how inheritance and dynamic binding make object-oriented programs difficult to maintain, and we give a concrete example of the problems that arise. We show that the difficulty lies in the fact that conventional tools are poorly suited for work with object-oriented languages, and we argue that semantics-based tools are essential 'for effective maintenance of object-oriented programs.We then describe a system we have developed for working with C++ programs. This system comprise… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
19
0

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 23 publications
(19 citation statements)
references
References 11 publications
0
19
0
Order By: Relevance
“…The study by Wilde et al (Wilde et al, 1993) indicated that, to understand the behavior of a method, one has to trace inheritance dependencies, which may be considerably complicated due to dynamic binding. A similar point was made in (Leijter et al, 1992) about the understandability of programs in such languages as C++ that support dynamic binding.…”
Section: A Cognitive Modelmentioning
confidence: 89%
See 1 more Smart Citation
“…The study by Wilde et al (Wilde et al, 1993) indicated that, to understand the behavior of a method, one has to trace inheritance dependencies, which may be considerably complicated due to dynamic binding. A similar point was made in (Leijter et al, 1992) about the understandability of programs in such languages as C++ that support dynamic binding.…”
Section: A Cognitive Modelmentioning
confidence: 89%
“…That is, the complete description for a class D can only be assembled by examining D as well as each of D' s superclasses. Because different classes are described at different places in the source code of a program (often spread across several different files), there is no single place a programmer can turn to get a complete description of a class" (Leijter, Meyers, and Reiss, 1992). While this argument is stated in terms of source code, it is not difficult to generalize it to design documents.…”
Section: A Cognitive Modelmentioning
confidence: 99%
“…Support for code investigation and understanding was initially developed in the form of stand-alone lexical search tools (e.g., grep [Aho 1980]) and program databases (e.g., CIA [Chen et al 1990], XREFDB [Lejter et al 1992]). Basic program search and cross-referencing tools have also been provided as part of integrated development environments for many decades (e.g., in Interlisp [Sanella 1983], Smalltalk [Goldberg 1984], and Eclipse [Object Technology International, Inc. 2001]).…”
Section: Code Searching Techniquesmentioning
confidence: 99%
“…Tool support for program investigation and understanding was initially developed in the form of standalone lexical search tools (e.g., grep [1]) and program databases (e.g., CIA [2], and XREFDB [4]). Basic program search and cross-referencing tools have also been provided as part of integrated development environments for many decades (e.g., in Interlisp [9], Smalltalk [3], and Eclipse [5]).…”
Section: Related Workmentioning
confidence: 99%