Verifications
Verification confirms that system behavior, implementation evidence, or operational evidence satisfies the capabilities and requirements it is linked to. Reqvire keeps those verification links inside the same semantic graph as requirements, refinements, and implementation artifacts.
Verification Types
verification-objective
Mandatory planning or grouping parent for concrete verification work through derivedFrom. It does not verify capabilities or requirements and must not have satisfiedBy evidence.
test-verification
Formal or automated testing with documented expected outcomes. This is evidence-backed and must have satisfiedBy links to test implementations or reports.
formal-proof-verification
Proof, model checking, theorem proving, generated fixtures, or proof reports. This is evidence-backed and must have satisfiedBy proof evidence.
analysis-verification
Systematic analysis, calculation, simulation, or review of documentation or code. It does not require satisfiedBy evidence.
inspection-verification
Formal examination of documentation, code, design, or physical components. It does not require satisfiedBy evidence.
demonstration-verification
Showing the capability or requirement behavior in an operational-like environment. It does not require satisfiedBy evidence.
Two-Level Evidence Model
Capabilities and requirements link to concrete verification elements with verifiedBy. Each concrete verification must derive from a verification-objective parent. Evidence-backed concrete verification elements then link to concrete test or proof artifacts with satisfiedBy.
### Response Time Requirement The system shall process data within 500ms. #### Relations * verifiedBy: [Performance Test](Verifications.md#performance-test) --- ### Performance Verification Objective #### Metadata * type: verification-objective --- ### Performance Test #### Metadata * type: test-verification #### Relations * derivedFrom: [Performance Verification Objective](#performance-verification-objective) * verify: [Response Time Requirement](Requirements.md#response-time-requirement) * satisfiedBy: [test_performance.sh](../../tests/test-performance/test_performance.sh)
Coverage Philosophy
- Verification objectives are mandatory parents for concrete verifications and are excluded from concrete verification coverage counts.
- Leaf requirements are the preferred verification targets because they represent concrete testable obligations.
- Parent requirement coverage rolls up through the requirement hierarchy when leaf requirements are verified.
- Capabilities may be directly verified, and capability coverage can also roll up from the requirements that specify them.
- One verification may verify multiple leaf requirements when a single test or proof covers a coherent behavior.
Coverage Command
The coverage report includes verification coverage for leaf requirements plus evidence satisfaction status for test and formal proof verifications.
reqvire coverage reqvire coverage --json
What Gets Flagged
Verified leaf requirements
Leaf requirements with verifiedBy relations to verification elements.
Unsatisfied test verifications
test-verification elements that are missing satisfiedBy links to test implementations or evidence.
Unsatisfied formal proofs
formal-proof-verification elements that are missing satisfiedBy links to proof artifacts, generated fixtures, or reports.
Analysis, inspection, and demonstration
These verification methods are considered satisfied by the verification element itself and do not require satisfiedBy evidence.