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

B. D. Szablak

dblp:84/6124 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1997
—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
Software testing · 100%

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

TopicWeightPapersLastEvidence papers
Software testing › test coverage
code coverage
0.011997
Applying Design of Experiments to Software Testing (Experience Report) · ICSE 1997
Software testing
combinatorial testing
0.011997
Applying Design of Experiments to Software Testing (Experience Report) · ICSE 1997
Software testing
test coverage
0.011997
Applying Design of Experiments to Software Testing (Experience Report) · ICSE 1997
Software testing › test process
test design
0.011997
Applying Design of Experiments to Software Testing (Experience Report) · ICSE 1997

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

pairwise testing · 0.0design of experiments · 0.0
YearPublicationVenuePosition
1997 Applying Design of Experiments to Software Testing (Experience Report)
abstract
Recently, a class of experimental designs has been devised that guarantee input domain coverage up to all combinations of k test factors taken t at a time.With such designs, all pairwise combinations (or triplets or quadruplets, etc.) are selected at least once.To evaluate their applicability to software testing, we analyzed the extent to which software coverage (i.e., code execution) achieved by these designs for t=1, ... ,k is representative of that achieved by exhaustively testing all factor combinations.The block coverage obtained for t;5;2 was comparable with that achieved by exhaustively testing all factor combinations but higher-order values of t were required for path coverage.Implications of these results for software testing are discussed.
I. S. Dunietz, Willa K. Ehrlich, B. D. Szablak, Colin L. Mallows, Anthony Iannino
ICSE3