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

Watts S. Humphrey

dblp:63/1672 · DBLP profile ↗
← Back
7ranked-venue papers
6as first author
0since 2021 · last 2008
—ORCID · none

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

Software engineering, systems software and programming languages · 6 · 5 first-authorHuman-computer interaction and ubiquitous computing · 1 · 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
Requirements engineering and software design · 52% Empirical software engineering · 32% Software maintenance and evolution · 16%
Interdisciplinary, comprehensive, and emerging computing
1 paper
Computing education · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software process
personal software process
0.011997
The Personal Software Process (PSP): A Full-Day Tutorial · ICSE 1997
Software maintenance and evolution › software process improvement
software process maturity
0.011991
A Comparison of U.S. and Japanese Software Process Maturity · ICSE 1991
Empirical software engineering
software engineering practice
0.011989
The State of Software Engineering Practice: A Preliminary Report · ICSE 1989
Requirements engineering and software design › software process
software process modeling
0.011989
Software Process Modeling: Principles of Entity Process Models · ICSE 1989
Computing education
software engineering education
0.011997
The Personal Software Process (PSP): A Full-Day Tutorial · ICSE 1997
Empirical software engineering
software metrics
0.011991
Predicting (Individual) Software Productivity · IEEE Trans. Software Eng. 1991
Requirements engineering and software design
software process
0.011991
A Comparison of U.S. and Japanese Software Process Maturity · ICSE 1991

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

prediction intervals · 0.0integrated moving average · 0.0exponential smoothing · 0.0
YearPublicationVenuePosition
2008 Preparing students for industry's software engineering needs
abstract
No abstract available.
Watts S. Humphrey, Robert Musson, Rafael Salazar
SIGCSE1
2008 Teaching disciplined software development
H. Dieter Rombach, Jürgen Münch, Alexis Ocampo, Watts S. Humphrey, Dan Burton
J. Syst. Softw.4
1997 The Personal Software Process (PSP): A Full-Day Tutorial
abstract
No abstract available.
Watts S. Humphrey, James W. Over
ICSE1
1991 A Comparison of U.S. and Japanese Software Process Maturity
Watts S. Humphrey, David H. Kitson, Julia Gale
ICSE1
1991 Predicting (Individual) Software Productivity
abstract
A method for projecting software productivity with reasonable accuracy which uses the statistical techniques of time series analysis is described. The measure of productivity is the development time required per line of code. In making productivity projections, the key issue is the need to achieve a balance between forecasting stability and responsiveness to changing conditions. An integrated moving average process of order one, using exponential smoothing of all the previous observations, is judged appropriate for software productivity analysis, particularly where there are limited data available or where conditions are sufficiently varied to make much of the available data inapplicable. Empirical evidence suggests that most commonly encountered time series can be reasonably well described by such methods. The methods for computing the weights used for exponential smoothing are described, as are the means for determining prediction intervals, or measures of forecast uncertainty. This data analytic approach uses historical data alone, unlike structural methods where learning curves as well as prior data are used to define the predictive process.>
Watts S. Humphrey, Nozer D. Singpurwalla
IEEE Trans. Software Eng.1
1989 Software Process Modeling: Principles of Entity Process Models
abstract
A defined software process is needed to provide organizations with a consistent framework for performing their work and im- proving the way they do it. An overall framework for modeling simplifies the task of producing process models, permits them to be tailored to individual needs, and facilitates process evolution. This paper outlines the principles of entity process, models and suggests ways in which they can help to address some of the problems with more conventional approaches to modeling software processes.
Watts S. Humphrey, Marc I. Kellner
ICSE1
1989 The State of Software Engineering Practice: A Preliminary Report
Watts S. Humphrey, David H. Kitson, Tim C. Kasse
ICSE1