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

David R. Harris 0001

dblp:13/3472-1 · DBLP profile ↗
← Back
5ranked-venue papers
2as first author
0since 2021 · last 1998
—ORCID · none

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

Software engineering, systems software and programming languages · 5 · 2 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
3 papers
Software maintenance and evolution · 53% Requirements engineering and software design · 47%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
reverse engineering
0.031997
Design Recovery for Distributed Systems · IEEE Trans. Software Eng. 1997
Manipulating Recovered Software Architecture Views · ICSE 1997
Reverse Engineering to the Architectural Level · ICSE 1995
Requirements engineering and software design
software architecture
0.021997
Manipulating Recovered Software Architecture Views · ICSE 1997
Reverse Engineering to the Architectural Level · ICSE 1995
Requirements engineering and software design › software architecture › software architecture analysis
software architecture recovery
0.021997
Manipulating Recovered Software Architecture Views · ICSE 1997
Reverse Engineering to the Architectural Level · ICSE 1995
Software maintenance and evolution › reverse engineering
design recovery
0.011997
Design Recovery for Distributed Systems · IEEE Trans. Software Eng. 1997
Software maintenance and evolution
program comprehension
0.011995
Reverse Engineering to the Architectural Level · ICSE 1995

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

view simplification · 0.0view combination · 0.0task flow extraction · 0.0source code cross-referencing · 0.0design knowledge · 0.0code coverage metric · 0.0
YearPublicationVenuePosition
1998 Recovering Software Architecture from Multiple Source Code Analyses
abstract
We describe the experiences we have had in using ManSART - a software architecture recovery tool that we developed and are employing in the analysis of large scale legacy software systems. ManSART uses a battery of standard data flow, control flow, and program slicing capabilities to automatically recover architectural features from source code. This source code analysis is enabled by representations called analysis. Analysis modules describe the interfaces of each component in a multiple component system. ManSART uses these modules to focus source code analysis and to store the results.
Melissa P. Chase, Steven M. Christey, David R. Harris 0001, Alexander S. Yeh
PASTE3
1997 Manipulating Recovered Software Architecture Views
abstract
Automatically recovered (reverse engineered) architectural views of legacy software are valuable for carrying out many software engineering tasks.However, while directly recovered views provide some relevant information, they often are either too fragmented or complex to be really useful in practice.This paper describes methods for making views more useful.We automatically combine and/or simplify views to produce hierarchies, hybrids, and abstractions.The methods we use take advantage of the source code fragments underlying the views to cross-reference between parts from different views.
Alexander S. Yeh, David R. Harris 0001, Melissa P. Chase
ICSE2
1997 Design Recovery for Distributed Systems
abstract
Two factors limit the utility of reverse engineering technology for many distributed software systems. First, with the exception of tools that support Ada and its explicit tasking constructs, reverse engineering tools fail to capture information concerning the flow of information between tasks. Second, relatively few reverse engineering tools are available for programming languages in which many older legacy applications were written (e.g., Jovial, CMS-2, and various assembly languages). We describe approaches that were developed for overcoming these limitations. In particular, we have implemented an approach for automatically extracting task flow information from a command and control system written in CMS-2. Our approach takes advantage of a small amount of externally provided design knowledge in order to recover design information relevant to the distributed nature of the target system.
Lester J. Holtzblatt, Richard L. Piazza, Howard B. Reubenstein, Susan N. Roberts, David R. Harris 0001
IEEE Trans. Software Eng.5
1996 Extracting Architectural Features from Source Code
David R. Harris 0001, Alexander S. Yeh, Howard B. Reubenstein
Autom. Softw. Eng.1
1995 Reverse Engineering to the Architectural Level
abstract
Recovery of higher level "design" information and the ability to create dynamic, task adaptable software documentation is crucial to supporting a number of program understanding activities.This paper presents research that demonstrates that reverse engineering technology can be used to recover software architecture representations of source code.We have developed a framework that integrates reverse engineering technology and architectural style representations.Using the framework, analysts can recover custom, dynamic documentation to fit a variety of software analysis requirements.Our goal is to establish coherent abstractions appropriate for helping analysts to understand large software systems.We discuss a code coverage metric useful for assessing the degree of program understanding achieved.
David R. Harris 0001, Howard B. Reubenstein, Alexander S. Yeh
ICSE1