View TRAK:MVp-04 Assurance Viewpoint



MVp-04 Assurance Viewpoint




8th December 2017


The MVp-04 - Assurance Viewpoint is part of the Management Perspective and one of the 24 TRAK Architecture Viewpoints.

The MVp-04 Architecture Assurance Viewpoint provides a way of describing and structuring one or more claims together with supporting or opposing arguments and evidence.

It is the specification for the TRAK::MV-04 Assurance view.

Stakeholders Addressed

  • Developer
  • Acquirer
  • Operator
  • Builder
  • Regulator
  • Maintainer
  • Auditor
  • Owner
  • User

Full size:File:mvp04 stakeholderConcern.pdf

Covered by TRAK IPR and licenses

The roles may apply to the Architecture Task, Enterprise, Concept, solution in terms of the design of a product or organisation or TRAK:Project.

Concerns Addressed

What are the claims made?

What is the basis of the claim?

Is the claim supported by evidence?

Covered by TRAK IPR and licenses


Describes a claim made about any other element with supporting (or opposing) arguments and evidence to establish how and whether a claim is proved or disproved. (as a result of the assessed evidence).

Typical claims for solutions include that a system is safe, fit for purpose and meets its requirements.

Covered by TRAK IPR and licenses

Declared Tuples


Identification of Claim / Forming Argument

  • Claim about Architecture Description Element
  • Claim has part Claim
  • Claim supports Claim
  • Claim opposes Claim (a counter-claim)
  • Argument supports Claim
  • Argument opposes Claim
  • Argument opposes Argument (a counter-argument)
  • Argument has part Argument
  • Architecture Description Element traces to Argument [where architecture of system of interest forms basis of Argument]
  • Organisation makes Claim
  • Role makes Claim

Verification of Claim / Argument

As identification +

  • Evidence proves Claim
  • Evidence disproves Claim
  • Evidence supports Argument
  • Evidence opposes Argument
  • Evidence has part Evidence

Covered by TRAK IPR and licenses

Optional Tuples

Context - Roles:


If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.

Covered by TRAK IPR and licenses


A MV-04 shall contain:

  • at least one Claim (the subject of the view)
  • every Claim is connected to the object of the claim (not itself) (about) or another Claim (has part)
  • at least one Argument is connected to at least one Claim (supports / opposes)
  • every Argument is connected to a Claim (supports / opposes) or another Argument (has part)
  • at least one Evidence is connected to:
    • at least one Argument (supports / opposes)
    • and only then that same Evidence may be connected to a Claim (proves / disproves)
  • every Evidence is directly connected to an Argument (supports / opposes) or indirectly connected to an Argument as part of another Evidence

Covered by TRAK IPR and licenses



Design verification of a requirement - the claim is that the design meets the requirement.

Example 1 - Verification of a Requirement


Example 2 - Safety


Example 3 - Safety (from the Supplier’s Perspective)


Full size - File:mv04 assuranceExample example supplier.pdf

Covered by TRAK IPR and licenses

Views Needed to Construct

Since the object of the Claim (Claim about [any TRAK metamodel element]) has to be shown the Master Architecture View for that object will be needed before the MV-04 can be drawn.

See Minimum Allowed View Sets|Minimum Allowed Architecture View Sets|Minimum Allowed View Sets

Covered by TRAK IPR and licenses

Consistency Rules


The Claim, Argument, Evidence (CAE) construct is an increasingly common construct used for safety assurance. It forms the basis of Adelard’s Safety Case Development (ASCAD) manual and underpins their ASCE tool. It has also been incorporated into the OMG Software Assurance Evidence Metamodel / Structured Assurance Case Metamodel (SACM).

One of the significant benefits that TRAK now provides is being able to link the safety argument structure to the description of the design / architecture of the design for which the case is being made within the same environment. This is one of the ways in which TRAK supports an integrated design approach as is an example of Model-Based Systems Engineering (MBSE).

Configuration History

The TRAK Viewpoints project on Sourceforge ( maintains a version-controlled repository. The change record is at



Other Frameworks


Category:Framework -> Viewpoint
Category:Architecture Perspective -> Management
Category:Framework -> Specification


  • Management

    © 2010 Eclectica Systems Ltd.