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

Johnny Martin

dblp:88/5908 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1992
—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
Requirements engineering and software design · 33% Software testing · 33% Empirical software engineering · 33%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
controlled experiment
0.011992
An Experimental Study of Fault Detection In User Requirements Documents · ACM Trans. Softw. Eng. Methodol. 1992
Software testing
fault detection
0.011992
An Experimental Study of Fault Detection In User Requirements Documents · ACM Trans. Softw. Eng. Methodol. 1992
Requirements engineering and software design › requirements validation
requirements inspection
0.011992
An Experimental Study of Fault Detection In User Requirements Documents · ACM Trans. Softw. Eng. Methodol. 1992

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

n-fold inspection · 0.0controlled experiment · 0.0
YearPublicationVenuePosition
1992 An Experimental Study of Fault Detection In User Requirements Documents
abstract
This paper describes a software engineering experiment designed to confirm results from an earlier project which measured fault detection rates in user requirements documents (URD). The experiment described in this paper involves the creation of a standardized URD with a known number of injected faults of specific type. Nine independent inspection teams were given this URD with instructions to locate as many faults as possible using the N-fold requirements inspection technique developed by the authors. Results obtained from this experiment confirm earlier conclusions about the low rate of fault detection in requirements documents using formal inspections and the advantages to be gained using the N-fold inspection method. The experiment also provides new results concerning variability in inspection team performance and the relative difficulty of locating different classes of URD faults.
G. Michael Schneider, Johnny Martin, Wei-Tek Tsai
ACM Trans. Softw. Eng. Methodol.2