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.

Type

Journal article

Intellectual base

Primary research

Year

1984

Link

https://doi.org/10.1109/ms.1984.233702matched

Cited from

engineering_design, statistics_experimental_design

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.

• 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.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Registry ID ref:833ebccd29ec · see in the full table