Method / 02

The connection of each material claim to direct, derived, contradictory, missing, and contextual evidence.

Independent software assuranceSM / 02.13

SecondMark position

Evidence volume is not evidence strength. Mapping reveals whether a conclusion rests on observation, assertion, inference, or an unexamined assumption.

The examination is bounded to defined claims, a versioned system, and evidence that can be traced to the state under review. Any material exclusion or uncertainty remains visible in the conclusion.

01

Core questions

What the examination needs to establish.

  1. 01

    Which evidence directly supports the claim?

  2. 02

    Can the evidence be traced to its source?

  3. 03

    What contradictory evidence exists?

  4. 04

    Where does the record depend on inference?

02

Evidence model

Evidence is assembled around the claim—not the folder structure.

01

Defined claims and decision context

Collected, attributed, challenged, and connected to the exact system boundary under examination.

02

Versioned system and dependency record

Collected, attributed, challenged, and connected to the exact system boundary under examination.

03

Direct observations and reproducible tests

Collected, attributed, challenged, and connected to the exact system boundary under examination.

04

Contradictory, missing, and residual evidence

Collected, attributed, challenged, and connected to the exact system boundary under examination.

Intended outcome

A navigable evidence model that makes the basis and weakness of every material conclusion inspectable.

Recorded reasoning chainFindings linked to evidenceConditions for continuing validity
03

Professional boundary

What an opinion does—and does not—mean.

It provides

A traceable independent conclusion on defined claims, grounded in the evidence and system state examined.

It does not provide

A guarantee that failure is impossible, a permanent certification, or a conclusion beyond the stated scope and validity conditions.