Verifying and Validating Software Requirements and Design Specifications¶
Boehm, B. W. (1984). Verifying and Validating Software Requirements and Design Specifications. IEEE Software, 1(1), 75-88.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Validation
- Validation answers "are we building the right thing?" — it is fundamentally a fitness-for-purpose assessment, distinct from verification (specification correctness: "are we building the thing right?") and falsification (logical refutation: "is this claim disprovable?"), a distinction Boehm (1984) crisply articulated.
This sourceIntroduces the V&V slogan "are we building the product right" (verification) versus "are we building the right product" (validation), and surveys techniques for catching specification and design defects early in the software life cycle.
- Validation answers "are we building the right thing?" — it is fundamentally a fitness-for-purpose assessment, distinct from verification (specification correctness: "are we building the thing right?") and falsification (logical refutation: "is this claim disprovable?"), a distinction Boehm (1984) crisply articulated.
- Verification
- The object can be a manufactured part, a software artifact, a mathematical derivation, a scientific result, or an institutional practice; the specification is whatever fixed criterion has been declared to govern it; the procedure is the test, audit, proof-check, measurement, or inspection that produces evidence; and the verdict closes the loop.
This sourceIntroduces the V&V slogan "are we building the product right" (verification) versus "are we building the right product" (validation), and surveys techniques for catching specification and design defects early in the software life cycle.
- The object can be a manufactured part, a software artifact, a mathematical derivation, a scientific result, or an institutional practice; the specification is whatever fixed criterion has been declared to govern it; the procedure is the test, audit, proof-check, measurement, or inspection that produces evidence; and the verdict closes the loop.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:833ebccd29ec · see in the full table