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

Alan P. Sheng

dblp:21/5853 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1984
—ORCID · none

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

Databases, data management, data science and information retrieval · 1

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 · 77% Software maintenance and evolution · 23%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
software quality and productivity
0.011984
Building-In Quality and Productivity to a Large Software System · ICDE 1984

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

metric analysis · 0.0
YearPublicationVenuePosition
1984 Building-In Quality and Productivity to a Large Software System
abstract
The ever-increasing demand for more and larger software systems requires that new and more effective ways of developing software be developed to increase the levels of quality and productivity. Experience with the 5ESS1" switching system development at Bell Laboratories showed that simultaneous gains in productivity and quality were made by improving the methodology and the environment surrounding the development. This paper describes the key aspects of the management approach and the development methodology that directly contributed to those improvements in the software quality and project productivity. In addition, efforts for further improvements, including the implementation of productivity and quality circles, data and metric analysis, etc., are discussed. Although these experiences resulted from the development of a very large project, the basic ideas and techniques can still be applied to most software projects involving more than a small group of programmers.
Edward M. Prell, Alan P. Sheng
ICDE2