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

Philip N. Papaccio

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

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

Software engineering, systems software and programming languages · 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 · 100%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
software economics
0.011988
Understanding and Controlling Software Costs · IEEE Trans. Software Eng. 1988
Empirical software engineering
software effort estimation
0.011988
Understanding and Controlling Software Costs · IEEE Trans. Software Eng. 1988
Empirical software engineering › software economics
software productivity
0.011988
Understanding and Controlling Software Costs · IEEE Trans. Software Eng. 1988

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

value chain analysis · 0.0cost modeling · 0.0
YearPublicationVenuePosition
1988 Understanding and Controlling Software Costs
abstract
A discussion is presented of the two primary ways of understanding software costs. The black-box or influence-function approach provides useful experimental and observational insights on the relative software productivity and quality leverage of various management, technical, environmental, and personnel options. The glass-box or cost distribution approach helps identify strategies for integrated software productivity and quality improvement programs using such structures as the value chain and the software productivity opportunity tree. The individual strategies for improving software productivity are identified. Issues related to software costs and controlling them are examined and discussed. It is pointed out that a good framework of techniques exists for controlling software budgets, schedules, and work completed, but that a great deal of further progress is needed to provide an overall set of planning and control techniques covering software product qualities and end-user system objectives.>
Barry W. Boehm, Philip N. Papaccio
IEEE Trans. Software Eng.2