Proceedings of ICECCS '96: 2nd IEEE International Conference on Engineering of Complex Computer Systems (Held Jointly With 6th
DOI: 10.1109/iceccs.1996.558517
|View full text |Cite
|
Sign up to set email alerts
|

A knowledge-based approach to object-oriented legacy code reuse

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 7 publications
0
2
0
Order By: Relevance
“…The necessity for informal tokens in program understanding. (Etzkorn, Davis, Bowen, Etzkorn, Lewis, Vinz and Wolf 1996;Davis 1996, 1997). This is true since object-oriented code is organized in classes, with everything required to implement a class at least mentioned (if not defined) in the class definition.…”
Section: Object-oriented Program Understanding Approachmentioning
confidence: 99%
See 1 more Smart Citation
“…The necessity for informal tokens in program understanding. (Etzkorn, Davis, Bowen, Etzkorn, Lewis, Vinz and Wolf 1996;Davis 1996, 1997). This is true since object-oriented code is organized in classes, with everything required to implement a class at least mentioned (if not defined) in the class definition.…”
Section: Object-oriented Program Understanding Approachmentioning
confidence: 99%
“…For object-oriented code, more so than for functionally-oriented code, much understanding can be performed by simply looking at comment and identifier names (Etzkorn, Davis, Bowen, Etzkorn, Lewis, Vinz, Wolf 1996;Etzkorn and Davis 1997). This is true since object-oriented code is organized in classes, with everything required to implement a class at least mentioned (if not defined) in the class definition.…”
Section: Object-oriented Program Understanding Approachmentioning
confidence: 99%