Topic · software metrics

Software metrics

Gist

Software metrics on this hop are three thresholds on the requirement set, not velocity. Proof runs proof gaps specs/system --check metrics. Waydev still owns cycle time. DX still owns the quality list. Jama still authors.

proof gaps specs/system --check metrics

Keep DORA if you already track lead time. Keep cyclomatic if you already lint McCabe. Proof will not count a dashboard as spec-set health.

Request demo Last DORA board vs this score

01 · The missed spine

The pipeline is green. repo,server owns 61 shalls.

A health score is a rollup of advisory findings. It never blocks a stage.

Wikipedia, GeeksforGeeks, and Waydev will give you software metrics: size, defect density, velocity, MTTR. That is not this URL. Proof's slice counts active requirements per component, how many shalls share one output variable, and whether each shall has a verified_by trace. The health score is 1 - (violations / measured items), bounded 0-100. No audit check consumes it.

The motivating miss is mechanical. repo,server grew to 61 live shalls. Coverage, lint, and the test runner are green. Metrics still emits component_complexity at the 50-requirement threshold. Nobody split the component. Nobody retired the superseded rows. The next agent treats the dashboard as proof the spec is reviewable. It is not.

Three honest exits, in order: decompose and reassign component; retire or supersede what is end of life; or accept the count when the component really is one job. Relabelling shalls across folders to push each count under 50 is how the number went green while ownership got worse.

proof gaps specs/system --check metrics
proof spec show --component repo,server
proof req edit SYS-REQ-010 --component repo,auth

The first command is the three categories. The show is who owns the pile. The edit is a real split, not a rename. A green DORA board next to 61 shalls in one component is how the spec stayed unreviewable.

02 · The exhibit

Same repo. A DORA board, or this score.

Velocity is green. The spec set is not. Click the tabs.

The run

Ask Waydev / DX / velocity / MTTR
Exit 0 if the board is green
Why the board does not count shalls

Board green

This hop

No metrics slice. repo,server still holds 61 active shalls.

No score

The run

Keep the board. It still owns cycle time. That is not this hop.

Keep DORA

Proof

Ask component count, fan-out, verified_by ratio
Out recommended / info, health 0-100, never a gate

A green board is not a score

Same repo. A DORA board, or this score. Click the tabs.

Surface	What they do	What Proof does	What we lose
Waydev / DX	Velocity, cycle time, defect density, MTTR.	Three thresholds on the spec set. Advisory only.	Not DORA. Keep the board if you already track delivery.
component_complexity	McCabe / Sonar on functions.	More than 50 active shalls on one component. Severity recommended.	Not cyclomatic. Not a gate. Accept the count when the job is one job.
variable_fanout	Shared outputs in a data model.	More than 10 shalls on one output. Severity info.	A shared error output is expected. Info is not a defect.
test_coverage_ratio	Line coverage on the Go.	Each shall needs a `verified_by` trace. Ratio 1.0.	A nearest-test link is a false claim. Coverage threshold.
Jama	The authoring programme. Charts if you put them there.	Count the files. Name the component that grew.	Not Jama's dashboard. Jama still authors.

The teaching graph is still a green delivery board next to 61 shalls in repo,server. Decompose if the component grew two jobs. Retire what is end of life. Accept the count when the component is one cohesive pile. Do not relabel folders to make the number drop.

proof gaps specs/system --check metrics
proof gaps specs/system --check metrics --format json
proof req retire SYS-REQ-010 --reason "superseded by SYS-REQ-040" --by CHG-010

The check is optional. It never fails a stage. The thresholds are fixed constants. There is no dial. See coverage threshold if the missing object is a percent on the Go, not a verified_by row. See documentation coverage if the missing object is a comment on a public symbol. See requirements quality if the missing object is rationale on a shall. See Proof vs Jama if the missing object is the authoring programme.

03 · The honest loss

Proof names the pile. It does not split the component.

A health score is not a proof of the Go. Jama still authors.

Proof does not implement DORA, Waydev, DX quality lists, McCabe cyclomatic dashboards, or LOC. It does not track velocity or MTTR. A metrics finding never blocks a stage. A component that legitimately holds 55 cohesive shalls should keep reporting one recommended finding. We have not scored this slice against a frozen DORA or ISO 25010 corpus. The loss is named, not scored. Attaching the nearest test to lift the ratio converts a visible gap into an invisible claim.

Coverage on the Go stays on coverage threshold. Comments on public symbols stay on documentation coverage. Jama still authors.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What are software metrics? Same question. Same URL.

What are software quality metrics? Same cluster in Proof. The Google result is often DX or defect density. That is not this hop.

What is metrics analysis? Investopedia and marketing dashboards. Proof's command is the spec-set slice, not a KPI workbook.

What is cyclomatic complexity? McCabe on functions. Not this hop. Sonar still owns that number.

Is Proof a Waydev alternative? No. Keep the delivery board. Proof vs SonarQube if the missing object is a quality gate on the Go.

Is Proof a Jama alternative for metrics? No. Jama still authors. Proof vs Jama.