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

John A. Lewis

dblp:24/3818 · DBLP profile ↗
← Back
3ranked-venue papers
2as first author
0since 2021 · last 1991
—ORCID · unresolved

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

Software engineering, systems software and programming languages · 3 · 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
1 paper
Empirical software engineering · 33% Software maintenance and evolution · 33% Programming languages and type systems · 33%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
controlled experiment
0.011991
An Empirical Study of the Object-Oriented Paradigm and Software Reuse · OOPSLA 1991
Programming languages and type systems
object-oriented programming
0.011991
An Empirical Study of the Object-Oriented Paradigm and Software Reuse · OOPSLA 1991
Software maintenance and evolution
software reuse
0.011991
An Empirical Study of the Object-Oriented Paradigm and Software Reuse · OOPSLA 1991

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

controlled experiment · 0.0
YearPublicationVenuePosition
1991 An Empirical Study of the Object-Oriented Paradigm and Software Reuse
abstract
Little or no empirical validation exists for many of software engineering's basic assumptions. While some of these assumptions are intuitive, the need for scientific experimentation remains clear. Several assumptions are made about the factors affecting software reuse, and in particular, the role of the object-oriented paradigm. This paper describes the preliminary results of a controlled experiment designed to evaluate the impact of the object-oriented paradigm on software reuse. The experiment concludes that (1) the object-oriented paradigm substantially improves productivity, although a significant part of this improvement is due to the effect of reuse, (2) reuse without regard to language paradigm improves productivity, (3) language differences are far more important when programmers reuse than when they do not, and (4) the object-oriented paradigm has a particular affinity to the reuse process.
John A. Lewis, Sallie M. Henry, Dennis G. Kafura, Robert S. Schulman
OOPSLA1
1990 Integrating metrics into a large-scale software development environment
Sallie M. Henry, John A. Lewis
J. Syst. Softw.2
1990 On the benefits and difficulties of a maintainability via metrics methodology
abstract
Abstract A metrics methodology can dramatically reduce the problems associated with software maintenance. However, several issues must be addressed in order to develop and use these techniques successfully. This paper defines a metrics methodology which is designed to deliberately integrate maintainability into software as it is being developed. The benefits of using this approach are discussed. Then several issues which complicate the development and use of the methodology are examined. Previous maintenance studies which incorporate the methodology into two different commercial environments are used to demonstrate the difficulties in implementation and contrast the differences in approach.
John A. Lewis, Sallie M. Henry
J. Softw. Maintenance Res. Pract.1