EDBT 2026 Demo / reviewers in the wild / expert
Frank E. McGarry
dblp:70/731
· DBLP profile ↗
7ranked-venue papers
1as first author
0since 2021 · last 2002
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 7 · 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
5 papers |
Software maintenance and evolution · 46% Requirements engineering and software design · 30% Empirical software engineering · 24% |
Topics — the 7 heaviest of 7, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
software process improvement |
0.0 | 2 | 2002 | Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory · ICSE 2002 The Software Engineering Laboratory: An Operational Software Experience Factory · ICSE 1992 |
Requirements engineering and software design › software process
software experience factory |
0.0 | 2 | 1997 | The Experience Factory: How to Build and Run One (Tutorial) · ICSE 1997 The Software Engineering Laboratory: An Operational Software Experience Factory · ICSE 1992 |
Empirical software engineering
software engineering practice |
0.0 | 2 | 2002 | Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory · ICSE 2002 Evaluating Software Engineering Technologies · IEEE Trans. Software Eng. 1987 |
Empirical software engineering
software engineering education |
0.0 | 1 | 1997 | The Experience Factory: How to Build and Run One (Tutorial) · ICSE 1997 |
Empirical software engineering › software evaluation
software technology evaluation |
0.0 | 1 | 1987 | Evaluating Software Engineering Technologies · IEEE Trans. Software Eng. 1987 |
Software maintenance and evolution
software modularization |
0.0 | 1 | 1985 | Criteria for Software Modularization · ICSE 1985 |
Requirements engineering and software design
modularity |
0.0 | 1 | 1985 | Criteria for Software Modularization · ICSE 1985 |
Methods — techniques the papers use, named apart from their topics
analysis of covariance · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2002 | Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratoryabstractFor 25 years the NASA/GSFC Software Engineering Laboratory (SEL) has been a major resource in software process improvement activities. But due to a changing climate at NASA, agency reorganization, and budget cuts, the SEL has lost much of its impact. In this paper we describe the history of the SEL and give some lessons learned on what we did right, what we did wrong, and what others can learn from our experiences. We briefly describe the research that was conducted by the SEL, describe how we evolved our understanding of software process improvement, and provide a set of lessons learned and hypotheses that should enable future groups to learn from and improve on our quarter century of experiences. Victor R. Basili, Frank E. McGarry, Rose Pajerski, Marvin V. Zelkowitz |
ICSE | 2 |
| 1997 | The Experience Factory: How to Build and Run One (Tutorial)abstractNo abstract available. Victor R. Basili, Frank E. McGarry |
ICSE | 2 |
| 1992 | The Software Engineering Laboratory: An Operational Software Experience FactoryabstractArticle Free Access Share on The software engineering laboratory: an operational software experience factory Authors: Victor Basili View Profile , Gianluigi Caldiera View Profile , Frank McGarry View Profile , Rose Pajerski View Profile , Gerald Page View Profile , Sharon Waligora View Profile Authors Info & Claims ICSE '92: Proceedings of the 14th international conference on Software engineeringJune 1992 Pages 370–381https://doi.org/10.1145/143062.143154Online:01 June 1992Publication History 50citation892DownloadsMetricsTotal Citations50Total Downloads892Last 12 Months30Last 6 weeks5 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF Victor R. Basili, Gianluigi Caldiera, Frank E. McGarry, Rose Pajerski, Gerald T. Page, Sharon Waligora |
ICSE | 3 |
| 1989 | Measuring Ada for software development in the Software Engineering Laboratory
Frank E. McGarry, William W. Agresti |
J. Syst. Softw. | 1 |
| 1989 | A summary of software measurement experiences in the Software Engineering Laboratory
Jon D. Valett, Frank E. McGarry |
J. Syst. Softw. | 2 |
| 1987 | Evaluating Software Engineering TechnologiesabstractMany new software development practices, tools, and techniques have been introduced in recent years. Few, however, have been empirically evaluated. The objectives of this study were to measure technology use in a production environment, develop a statistical model for evaluating the effectiveness of technologies, and evaluate the effects of some specific technologies on productivity and reliability. A carefully matched sample of 22 projects from the Software Engineering Laboratory database was studied using an analysis-of-covariance procedure. Limited use of the technologies considered in the analysis produced approximately a 30 percent increase in software reliability. These technologies did not demonstrate any direct effect on development productivity. David N. Card, Frank E. McGarry, Gerald T. Page |
IEEE Trans. Software Eng. | 2 |
| 1985 | Criteria for Software Modularization
David N. Card, Gerald T. Page, Frank E. McGarry |
ICSE | 3 |