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.

Paul Piwowarski

dblp:20/4693 · DBLP profile ↗
← Back
2ranked-venue papers
1as 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 · 2 · 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
1 paper
Software testing · 100%

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

TopicWeightPapersLastEvidence papers
Software testing
test coverage
0.011993
Coverage Measurement Experience During Function Test · ICSE 1993
Software testing › black-box testing
functional testing
0.011993
Coverage Measurement Experience During Function Test · ICSE 1993

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

coverage measurement · 0.0
YearPublicationVenuePosition
1993 Coverage Measurement Experience During Function Test
Paul Piwowarski, Mitsuru Ohba, Joseph M. Caruso
ICSE1
1993 Test Manager: A Regression Testing Tool
abstract
CWRU has participated in a joint project with IBM in developing an internal regression testing tool called Test Manager. The objective of Test Manager is to aid in regression testing at the unit testing, integration testing, or function testing levels and also to produce a reduced regression test set to verify the software changes indicated by the user. A conceptual basis for the tool, called a firewall, and a description of the factors which influenced the design of the tool are given. The tool utilizes a Prolog database; a set of experiments that determined how that database should best be structured is described. Timing and space requirements and future work and enhancements to the tool are discussed.>
Lee J. White, Venkatasubramaniam Narayanswamy, Ted Friedman, Marc Kirschenbaum, Paul Piwowarski, Mitsuru Oha
ICSM5