Insights / 05

Confidence is useful only when its basis, scope, contradiction, expiry, and relationship to the actual system are visible.

Independent software assuranceSM / 05.36

SecondMark position

Assurance converts evidence into a conclusion; it should never reverse that order by collecting support for a predetermined level of confidence.

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

    What evidence would change the conclusion?

  2. 02

    Which evidence is direct versus asserted?

  3. 03

    How are contradictions handled?

  4. 04

    When does the record become stale?

02

Evidence model

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

01

Explicit definitions

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

02

Reasoned assurance principles

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

03

Practical system implications

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

04

Boundaries and counterexamples

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

Intended outcome

A more disciplined relationship between technical evidence, uncertainty, and executive reliance.

A sharper decision frameQuestions for system stewardsPractical next steps
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.