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

Edward I. Cohen

dblp:61/6813 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1980
—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 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software testing › specification-based testing
domain testing
0.011980
A Domain Strategy for Computer Program Testing · IEEE Trans. Software Eng. 1980
Software testing
test adequacy
0.011980
A Domain Strategy for Computer Program Testing · IEEE Trans. Software Eng. 1980
Software testing › structural testing
control flow testing
0.011980
A Domain Strategy for Computer Program Testing · IEEE Trans. Software Eng. 1980

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

domain partitioning analysis · 0.0
YearPublicationVenuePosition
1980 A Domain Strategy for Computer Program Testing
abstract
This paper presents a testing strategy desiged to detect errors in the control flow of a computer program, and the conditions under which this strategy is reliable are given and characterized. The control flow statements in a computer progam partition the input space into a set of mutually exclusive domains, each of which corresponds to a particular program path and consists of input data points which cause that path to be executed. The testing strategy generates test points to examine the boundaries of a domain to detect whether a domain error has occurred, as either one or more of these boundaries will have shifted or else the corresponding predicate relational operator has changed. If test points can be chosen within e of each boundary, under the appropriate assumptions, the strategy is shown to be reliable in detecting domain errons of magnitude greater than ∈. Moreover, the number of test points required to test each domain grows only linearly with both the dimensionality of the input space and the number of predicates along the path being tested.
Lee J. White, Edward I. Cohen
IEEE Trans. Software Eng.2