Proof. Request demo

Compare · Jama Connect

Proof vs Jama Connect

Jama Connect stores the links a person asserted. Proof re-reads the code on every commit and fails CI when those links are no longer true in the binary. IBM DOORS, Polarion, and codeBeamer sit on this page.

proof audit --check spec_lint_ac_subset_of_satisfies

Not a Jama alternative. Keep the ALM for programme authoring. Proof does not ingest your Jama project.

Request demo How they compare

01 · Answers

How Proof compares to Jama Connect

The comparison, as a list. The exhibit below is the same split as a table.

  1. How does Proof compare to Jama Connect? Jama is the programme ALM: author, review, baseline, impact. Proof is a CI gate on one component. A green Jama cell is what someone last typed. A green Proof check is that the running code still keeps the requirement.
  2. Is Proof a Jama Connect alternative? No. Keep Jama. Proof does not ingest the Jama project, does not run reviews, and does not replace programme-scale authoring.
  3. What does Jama still win? Many authors, review states, baselines across a large corpus. Proof does not do that job.
  4. What about IBM DOORS, Polarion, or codeBeamer? Same cluster. They store asserted links. They do not re-read the function. No twin pages.
  5. Is there a service that audits whether my code matches its requirements? Yes. That is Proof. Jama stores the links; it does not re-read the function.

02 · The distinction

A requirements database is not the code keeping the requirement.

Jama Connect is a real ALM. Teams author, review, and trace requirements there because that is the programme layer. Proof does not ingest your Jama project. It holds signed requirements for one component against the source, and it re-runs that check in CI.

When an engineer types a Jama link from STK-REQ-004 to session.go:74, the cell is true that day. Forty commits later the function moved. Jama still shows green, because the database only stores what it was last told. Proof's check reads the satisfies back-link and the code. If they disagree, the gate is non-zero.

The same miss exists in IBM DOORS, Polarion, and codeBeamer. They are requirements databases. None of them re-derive the link from the source on every commit.

03 · The exhibit

What Jama keeps. What the audit re-checks.

Jama is the programme layer. Proof is the check that the running code still keeps the requirement.

Jama Connect

  • Link STK-REQ-004 → session.go:74
Cell is true

Proof

  • satisfies matches the source
Check green

Jama Connect

The function moved. The cell was never re-typed. Jama still shows green.

Still green

Proof

The back-link and the code disagree. CI is red until they match.

Stale satisfies

Same link. Two moments. Click the tabs.

Axis Jama Connect Proof
What it is Requirements ALM. Author, review, baseline, impact across a programme. Signed requirements in the repo for one component. Re-checked in CI. The audit is what makes that more than a database.
What a link means A person asserted requirement ↔ test ↔ change. The cell stays until someone edits it. A path re-derived from the spec and the source. Stale satisfies fails the check.
When the function moves The Jama cell stays green. CI is red until the back-link matches the code that shipped.
What you keep The Jama project, workflows, and reviewers. Keep it. Requirements as files in the repo, and a CI gate.
Where they win Many authors, review states, programme-scale authoring. Proof does not replace that. One component, held to signed requirements, on every commit.

The check is this lint: every SYS-REQ cited in a stakeholder acceptance criterion must also appear in that child's traces.satisfies. When the two sides disagree, the matrix you would export from an ALM is already a lie.

proof audit --check spec_lint_ac_subset_of_satisfies \
            --check spec_lint_ac_inverse_coverage
spec_lint_ac_subset_of_satisfies
  specs/stakeholder/requirements/STK-REQ-003.req.yaml:41
  STK-REQ-003 AC-001 cites SYS-REQ-374 which back-links to
  STK-REQ-015 instead of STK-REQ-003.

04 · The honest loss

Proof does not replace Jama.

Jama still wins at the work it was built for: a requirements database, many authors, review workflow.

Jama can trace requirements. So can DOORS, Polarion, and codeBeamer. The miss is treating a green cell in the ALM as proof the running code still keeps the promise. Proof holds signed requirements for one component against the source, in CI. It is not Jama for the enterprise corpus.

A re-derived matrix still cannot invent the requirement nobody wrote. On the public jsonparser audit, a defect shipped in code that carried full structural coverage because the case that broke was never a requirement. Unspecified partitions are not in any check's denominator.

Request demo The matrix, as a check