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

Robert S. Arnold

dblp:07/2664 · DBLP profile ↗
← Back
5ranked-venue papers
5as first author
0since 2021 · last 1993
—ORCID · none

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

Software engineering, systems software and programming languages · 4 · 4 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 1 first-author

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
2 papers
Software maintenance and evolution · 100%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › software reengineering
software restructuring
0.011989
Software restructuring · Proc. IEEE 1989
Software maintenance and evolution
software maintenance
0.011982
The Dimensions of Healthy Maintenance · ICSE 1982

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

tutorial · 0.0
YearPublicationVenuePosition
1993 Reflections on Software Maintenance Progress 1983 - 1993
Robert S. Arnold
ICSM1
1993 Impact Analysis - Towards a Framework for Comparison
abstract
The term impact analysis is used with many meanings. A three-part framework for characterizing and comparing diverse impact analysis approaches is defined. The parts correspond to how an approach is used to accomplish impact analysis, how an approach does impact analysis internally, and the effectiveness of the impact analysis approach. To illustrate the framework's application, five impact analysis approaches are illustrated according to it.>
Robert S. Arnold, Shawn A. Bohner
ICSM1
1993 Do Design Records Really Benefit Software Malntenance?
Robert S. Arnold, Malcolm Slovin, Norman Wilde
ICSM1
1989 Software restructuring
abstract
The author provides a brief tutorial on software restructuring. He discusses what restructuring is, advantages and disadvantages of restructuring, tools and case studies, and future possibilities. The reader is assumed to have a general appreciation for building and maintaining software systems. The aim is to provide the reader with a feel for the strengths, weaknesses, and capabilities of software restructuring technology.>
Robert S. Arnold
Proc. IEEE1
1982 The Dimensions of Healthy Maintenance
Robert S. Arnold, D. A. Parker
ICSE1