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.

John P. Stampfel

dblp:97/6653 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1991
—ORCID · none

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

Software engineering, systems software and programming languages · 2

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
Software testing · 100%

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

TopicWeightPapersLastEvidence papers
Software testing › software reliability
software reliability modeling
0.011990
Application of Software Reliability Modeling to Product Quality and Test Process · ICSE 1990
Software testing
test process
0.011990
Application of Software Reliability Modeling to Product Quality and Test Process · ICSE 1990

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

software reliability modeling · 0.0
YearPublicationVenuePosition
1991 How faults cause software failures: implications for software reliability engineering
abstract
Software systems typically contain design and code defects that manifest themselves as software failures at various points during program execution. These software faults can be viewed as causing failures to occur according to some chance mechanism that is often taken to be a Poisson process. Individual per-fault failure sequences (resulting from delayed fault detection and software correction) during test execution were analyzed to determine whether they satisfied Poisson process assumptions. The system analyzed, a large, complex, industrial software system, was executed under a defined operational profile corresponding to a controlled command and autonomous event mix characteristic of the system's actual usage. The failure events, defined as severe, system-wide affecting events attributed to software faults, typically occurred following many cycles of interacting system features in the expected user mode. Execution times between failure events were calculated and then statistically analyzed for conformance to Poisson process assumptions. The results indicated that first-time failure events conformed to the assumptions of a Poisson process and were consistent with a reliability growth Poisson model but that per-fault failure sequences attributed to specific faults tended to violate Poisson assumptions due to failure clustering.>
Willa K. Ehrlich, Anthony Iannino, Bala Prasanna, John P. Stampfel, Jar R. Wu
ISSRE4
1990 Application of Software Reliability Modeling to Product Quality and Test Process
Willa K. Ehrlich, John P. Stampfel, Jar R. Wu
ICSE2