Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Ross Huitt

dblp:98/6627 · DBLP profile ↗
← Back
4ranked-venue papers
0as first author
0since 2021 · last 1992
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 46% Programming languages and type systems · 46% Program analysis · 7%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Programming languages and type systems › object-oriented programming
inheritance and polymorphism
0.011992
Maintenance Support for Object-Oriented Programs · IEEE Trans. Software Eng. 1992
Programming languages and type systems › object-oriented programming
object-oriented language features
0.011992
Maintenance Support for Object-Oriented Programs · IEEE Trans. Software Eng. 1992
Software maintenance and evolution › software maintenance
object-oriented program maintenance
0.011992
Maintenance Support for Object-Oriented Programs · IEEE Trans. Software Eng. 1992
Software maintenance and evolution
program comprehension
0.011992
Maintenance Support for Object-Oriented Programs · IEEE Trans. Software Eng. 1992
Program analysis
dynamic analysis
0.011992
Maintenance Support for Object-Oriented Programs · IEEE Trans. Software Eng. 1992

Methods — techniques the papers use, named apart from their topics

case study · 0.0
YearPublicationVenuePosition
1992 Maintenance Support for Object-Oriented Programs
abstract
This paper describes some of the difficulties that may be expected in the maintenance of software developed using the new object oriented languages. The concepts of inheritance and of polymorphism provide the great strengths of these languages, but they also introduce difficulties in program analysis and understanding. The paper analyzes problems of dynamic binding, object dependencies, dispersed program structure, control of polymorphism, high-level understanding, and detailed code understanding. Examples are presented based on code from a PC Smalltalk environment and from studies of two systems under development at Bell Communications Research
Norman Wilde, Ross Huitt
IEEE Trans. Software Eng.2
1991 Maintenance support for object oriented programs
abstract
Some of the difficulties that may be expected in the maintenance of software developed using the new object oriented languages are described. The concepts of inheritance and of polymorphism provide the great strengths of these languages but they also introduce difficulties in program analysis and understanding. The authors analyze problems of dynamic binding, object dependencies, dispersed program structure, control of polymorphism, high level understanding and detailed code understanding. Examples are presented based on code from the Smalltalk V environment. Recommendations are made for possible tool support, particularly using the concepts of dependency analysis, external dependency graphs, and clustering methodologies. Some suggestions are made concerning maintenance in firefighting situations, when a failed system must be brought back into service with a minimum of lost time.>
Norman Wilde, Ross Huitt
ICSM2
1991 A reusable toolset for software dependency analysis
Norman Wilde, Ross Huitt
J. Syst. Softw.2
1989 Dependency analysis tools: reusable components for software maintenance
abstract
A general-purpose toolset that is being developed to capture and analyze software dependencies is described. The tools are designed to serve as reusable components. They can be used not only to aid programmers directly in understanding programs but also as a basis from which other specialized tools can be constructed. The tools use the concept of a dependency graph as a basic abstraction to simplify the understanding of software relationships. Definitional, calling, functional and data-flow dependencies are analyzed. An external dependency graph for each function is developed to encapsulate the effects of function cells.>
Norman Wilde, Ross Huitt, Scott Huitt
ICSM2