Christopher J. Hetmanski

dblp:75/661 · DBLP profile ↗
← Back
3ranked-venue papers
0as first author
0since 2021 · last 1993
—ORCID · none

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

Software engineering, systems software and programming languages · 3

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
Empirical software engineering · 43% Software testing · 38% Requirements engineering and software design · 19%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › software defect prediction
fault-prone component identification
0.011993
Developing Interpretable Models with Optimized Set Reduction for Identifying High-Risk Software Components · IEEE Trans. Software Eng. 1993
Software testing
risk-based testing
0.011993
Developing Interpretable Models with Optimized Set Reduction for Identifying High-Risk Software Components · IEEE Trans. Software Eng. 1993
Requirements engineering and software design
risk management
0.011993
Modeling and Managing Risk Early in Software Development · ICSE 1993
Empirical software engineering
software defect prediction
0.011993
Developing Interpretable Models with Optimized Set Reduction for Identifying High-Risk Software Components · IEEE Trans. Software Eng. 1993
Software testing › test planning
test effort allocation
0.011993
Developing Interpretable Models with Optimized Set Reduction for Identifying High-Risk Software Components · IEEE Trans. Software Eng. 1993
Empirical software engineering
software project management
0.011993
Modeling and Managing Risk Early in Software Development · ICSE 1993

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

risk modeling · 0.0optimized set reduction · 0.0multivariate stochastic modeling · 0.0
YearPublicationVenuePosition
1993 Modeling and Managing Risk Early in Software Development
Lionel C. Briand, William M. Thomas, Christopher J. Hetmanski
ICSE3
1993 Developing Interpretable Models with Optimized Set Reduction for Identifying High-Risk Software Components
abstract
Applying equal testing and verification effort to all parts of a software system is not very efficient, especially when resources are tight. Therefore, one needs to low/high fault frequency components so that testing/verification effort can be concentrated where needed. Such a strategy is expected to detect more faults and thus improve the resulting reliability of the overall system. The authors present the optimized set reduction approach for constructing such models, which is intended to fulfill specific software engineering needs. The approach to classification is to measure the software system and build multivariate stochastic models for predicting high-risk system components. Experimental results obtained by classifying Ada components into two classes (is, or is not likely to generate faults during system and acceptance rest) are presented. The accuracy of the model and the insights it provides into the error-making process are evaluated.>
Lionel C. Briand, Victor R. Basili, Christopher J. Hetmanski
IEEE Trans. Software Eng.3
1992 Providing an empirical basis for optimizing the verification and testing phases of software development
abstract
Applying equal testing and verification effort to all parts of a software system is not very efficient, especially when resources are limited and scheduling is tight. Therefore, one needs to be able to differentiate low/high fault density components so that testing/verification effort can be concentrated where needed. Such a strategy is ejected to detect more faults and thus improve the resulting reliability of the overall system. The authors present an alternative approach for constructing such models that is intended to fulfil specific software engineering needs, (i.e. dealing with partial/incomplete information and creating models that are easy to interpret). The approach to classification is to: measure the software system to be considered; and to build multivariate stochastic models for prediction. The authors present experimental results obtained by classifying FORTRAN components into two fault density classes: low and high. They also evaluate the accuracy of the model and the insights it provides into the software process.>
Lionel C. Briand, Victor R. Basili, Christopher J. Hetmanski
ISSRE3