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

Geoffrey Clemm

dblp:78/1742 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 2005
—ORCID · none

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

Software engineering, systems software and programming languages · 3 · 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
3 papers
Software maintenance and evolution · 73% Empirical software engineering · 22% Operating systems · 5%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
software configuration management
0.122005
Impact of software engineering research on the practice of software configuration management · ACM Trans. Softw. Eng. Methodol. 2005
Impact of the research community for the field of software configuration management · ICSE 2002
Empirical software engineering
mining software repositories
0.012002
Impact of the research community for the field of software configuration management · ICSE 2002
Operating systems › resource management › storage management
persistent object stores
0.011990
A Mechanism for Environment Integration · ACM Trans. Program. Lang. Syst. 1990
Software maintenance and evolution
software ecosystems
0.011990
A Mechanism for Environment Integration · ACM Trans. Program. Lang. Syst. 1990

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

publication history analysis · 0.1historical analysis · 0.0
YearPublicationVenuePosition
2005 Impact of software engineering research on the practice of software configuration management
abstract
Software Configuration Management (SCM) is an important discipline in professional software development and maintenance. The importance of SCM has increased as programs have become larger, more long lasting, and more mission and life critical. This article discusses the evolution of SCM technology from the early days of software development to the present, with a particular emphasis on the impact that university and industrial research has had along the way. Based on an analysis of the publication history and evolution in functionality of the available SCM systems, we trace the critical ideas in the field from their early inception to their eventual maturation in commercially and freely available SCM systems. In doing so, this article creates a detailed record of the critical value of SCM research and illustrates how research results have shaped the functionality of today's SCM systems.
Jacky Estublier, David B. Leblang, André van der Hoek, Reidar Conradi, Geoffrey Clemm, Walter F. Tichy, Darcy Wiborg Weber
ACM Trans. Softw. Eng. Methodol.5
2002 Impact of the research community for the field of software configuration management
abstract
Software configuration management (SCM) is an important discipline in professional software development and maintenance. The importance of SCM has increased as programs have become larger, more complex, and more mission/life-critical. This paper presents a brief summary of a full report that discusses the evolution of SCM technology from the early days of software development to present, and the specific impact university and industrial research has had along the way.
Jacky Estublier, David B. Leblang, Geoffrey Clemm, Reidar Conradi, André van der Hoek, Walter F. Tichy, Darcy Wiborg Weber
ICSE3
1990 A Mechanism for Environment Integration
abstract
This paper describes research associated with the development and evaluation of Odin-an environment integration system based on the idea that tools should be integrated around a centralized store of persistent software objects. The paper describes this idea in detail and then presents the Odin architecture, which features such notions as the typing of software objects, composing tools out of modular tool fragments, optimizing the storage and rederivation of software objects, and isolating tool interconnectivity information in a single centralized object. The paper then describes some projects that have used Odin to integrate tools on a large scale. Finally, it discusses the significance of this work and the conclusions that can be drawn about superior software environment architectures.
Geoffrey Clemm, Leon J. Osterweil
ACM Trans. Program. Lang. Syst.1