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

Ray W. Wolverton

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

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

Software engineering, systems software and programming languages · 2Systems, architecture and hardware · 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
2 papers
Software testing · 73% Empirical software engineering · 21% Requirements engineering and software design · 6%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Performance modeling and evaluation · 100%

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

TopicWeightPapersLastEvidence papers
Software testing
software reliability
0.011978
An Analysis of Competing Software Reliability Models · IEEE Trans. Software Eng. 1978
Software testing › software reliability
software reliability modeling
0.011978
An Analysis of Competing Software Reliability Models · IEEE Trans. Software Eng. 1978
Empirical software engineering
software effort estimation
0.011974
The Cost of Developing Large-Scale Software · IEEE Trans. Computers 1974
Requirements engineering and software design › software process
project planning
0.011974
The Cost of Developing Large-Scale Software · IEEE Trans. Computers 1974

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

probability distribution modeling · 0.0econometric analysis · 0.0case study · 0.0
YearPublicationVenuePosition
1980 Software cost modeling: Some lessons learned
Barry W. Boehm, Ray W. Wolverton
J. Syst. Softw.2
1978 An Analysis of Competing Software Reliability Models
abstract
This paper examines the most widely used reliability models. The models discussed fall into two categories, the data domain and the time domain. Besides tracing the historical development of the various models their advantages and disadvantages are analyzed. This includes models based on discrete as weil as continuous probability distributions. How well a given model performs its purpose in a specific economic environment will determine the usefulness of the model. Each of the models is examined with actual data as to the applicability of the error fmding process.
George J. Schick, Ray W. Wolverton
IEEE Trans. Software Eng.2
1974 The Cost of Developing Large-Scale Software
abstract
The work of software cost forecasting falls into two parts. First we make what we call structural forecasts, and then we calculate the absolute dollar-volume forecasts. Structural forecasts describe the technology and function of a software project, but not its size. We allocate resources (costs) over the project's life cycle from the structural forecasts. Judgment, technical knowledge, and econometric research should combine in making the structural forecasts. A methodology based on a 25 X 7 structural forecast matrix that has been used by TRW with good results over the past few years is presented in this paper. With the structural forecast in hand, we go on to calculate the absolute dollar-volume forecasts. The general logic followed in "absolute" cost estimating can be based on either a mental process or an explicit algorithm. A cost estimating algorithm is presented and five tradition methods of software cost forecasting are described: top-down estimating, similarities and differences estimating, ratio estimating, standards estimating, and bottom-up estimating. All forecasting methods suffer from the need for a valid cost data base for many estimating situations. Software information elements that experience has shown to be useful in establishing such a data base are given in the body of the paper. Major pricing pitfalls are identified. Two case studies are presented that illustrate the software cost forecasting methodology and historical results. Topics for further work and study are suggested.
Ray W. Wolverton
IEEE Trans. Computers1