Topic · software verification report

Software verification report

Gist

A software verification report here is the completeness dump from this graph this commit, not last quarter's V&V PDF. Proof prints it with proof doc generate verification-report. NIST still hosts SP 500-234. Jama still authors.

proof doc generate verification-report --output docs/verification.html

Keep the Word pack if the DER asked for one. Keep IEEE 1012 if you need an IV&V office. A generated table is not a proof of the function, and Proof does not sign a V&V certificate.

Request demo Last NIST PDF vs this dump

01 · The PDF that outlived the graph

A signed V&V pack is not this commit.

The merge stayed green because nobody asked whether the rows in last quarter's report still match the traces on disk.

On this install SYS-REQ-007 still said verified in the Word pack. Kind2 never ran. There was no review record. Reviewers argued about the PDF. There was no dump whose rows could fail.

proof doc generate verification-report prints, from loaded project data, per-requirement verification status, formalization, realizability, consistency, vacuity, review status, trace coverage, and obligations met versus required at each assurance level. It is HTML or Markdown. PDF output still fails until chromedp ships. The generator does not invent missing evidence. It reports what the graph currently holds.

The plan-before-the-code H1 lives on software verification plan as proof verify-plan status. The pack-after-the-fact H1 lives on software accomplishment summary. The NASA assurance-standard H1 lives on NASA-STD-8739.8. This URL is the dump from this graph, kept regenerable in CI.

proof doc generate verification-report --output docs/verification.html
proof doc generate verification-report --format md --spec specs/system
proof audit --fail-level warn

On this install the teaching miss is a stale pack: the PDF still named Kind2 on SYS-REQ-007, and CI never regenerated the table after the lemma was dropped.

02 · The exhibit

Same shall. A stale PDF, or a dump from this commit.

The last V&V pack still said verified. Kind2 is gone. Click the tabs.

This push

pack V&V report, Q2
row SYS-REQ-007 verified
graph no Kind2, no review

Merge stayed green

Finding

No dump from this commit. Reviewers argued about a PDF the graph no longer matches.

Stale pack

This push

Still last week's Go. The generator will not invent Kind2. Restore the lemma, or the row stays incomplete.

Keep the YAML

Proof

Ask proof doc generate verification-report
Kind SYS-REQ-007 Kind2 missing

incomplete row

Same shall. A stale PDF, or a dump from this commit. Click the tabs.

Invariant	What they do	What Proof does
NIST SP 500-234	A V&V report that records unit, integration, and system tests as a document.	Not that PDF. Proof prints a completeness table from the current graph. It does not certify the tests.
EUMETSAT / Word V&V	A signed programme pack. Reviewers argue about last quarter's file.	Not a certificate. Proof does not sign a V&V pack for a satellite or a DER.
Wikipedia V&V	Verification asks whether we built X. Validation asks whether X was the right thing.	This dump is verification status from traces. It is not validation of the product in the field.
Software verification plan	How each shall will be substantiated, written before the code exists.	software verification plan as `proof verify-plan status`. The plan is not this dump. Not this H1.
Software accomplishment summary	The pack after the work, for a gate.	software accomplishment summary. Different artefact. Not this H1.
NASA-STD-8739.8	Software assurance, software safety, and IV&V as an agency standard.	NASA-STD-8739.8 owns the standard. This URL owns the dump that standard would re-read.
Jama / DOORS	A verification-method field on an object that still says last quarter's result.	Jama still authors. IBM DOORS stays a mention on Proof vs Jama. Proof prints from the repo.
A dump is a proof	A regenerated HTML file means the function is correct.	The table reports what the graph currently holds. Incomplete rows stay incomplete. It is not a proof of the Go.

Regenerate the dump in CI after the graph changes. Preview with proof doc preview verification-report --format md when you do not want a file. Filter with --spec specs/system when the project has more than one spec. Unknown templates fail before render. PDF still fails until chromedp ships.

proof doc preview verification-report --format md
proof doc generate verification-report --spec specs/system --output docs/verification.html
proof audit --fail-level warn

We have not run NIST 500-234, IEEE 1012, and Proof on the same frozen corpus, and we have not claimed this dump is a signed V&V certificate or a proof of the Go. The loss is named, not scored.

03 · The honest loss

A dump is not a V&V certificate.

Proof prints the current graph. It does not author the programme V&V pack, run IV&V, or prove the code. Jama still authors.

The command does not write the plan. That H1 lives on software verification plan. It does not write the accomplishment summary. That H1 lives on software accomplishment summary. It does not replace NASA OSMA. That H1 lives on NASA-STD-8739.8. It does not generate an IEEE 829 software test report. That template does not exist.

A green dump can still be incomplete. A missing Kind2 row is a graph problem, not a renderer problem. Jama still authors.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is a software verification report? NIST 500-234 owns that SERP as a V&V document. Same cluster as this URL only when the rows come from a repo graph. Not a twin for a signed satellite pack.

What is a verification report? KYC and identity-check SERPs. Not this H1.

What is a software verification plan? How each shall will be substantiated before the code exists. software verification plan as proof verify-plan status.

What is a software accomplishment summary? The pack after the work. software accomplishment summary.

What is NASA-STD-8739.8? Software assurance, software safety, IV&V. NASA-STD-8739.8 owns the standard. This page is the dump that standard would re-read.

What is a software test report? IEEE 829 / TestRail. Proof does not generate that document. The shall-derived cases live on requirements based testing.

Is Proof a Jama alternative? No. Jama still authors. Proof prints from the graph. IBM DOORS stays a mention on Proof vs Jama.