View TRAK:Requirement


Version & Date

7th September 2015

Configuration History

See change record for the TRAK metamodel at


One of the elements within the the TRAK metamodel and part of the Management Perspective.

An atomic requirement or constraint - a statement of need.

Covered by TRAK IPR and licenses

Tests For

  • atomic

Covered by TRAK IPR and licenses

Tests Against

Covered by TRAK IPR and licenses


  • requirement identifier
  • sequence identifier
  • requirement priority
  • compliance level required = Unknown, Desirable - Freedom, Desirable - Commitment or Mandatory
  • requirement paragraph (number e.g.. 1.2.33)
  • requirement owner (organisation)
  • requirement scope = Unknown, Enabling or Product
  • requirement text
  • requirement title
  • requirement type = Unknown, Commercial, Legal or Technical

+ Inherited Attributes Architecture Description Element


Covered by TRAK IPR and licenses

Implementation of TRAK Attribute Names and Values

The implementation of TRAK attributes in a tool is controlled by ‘TRAK. Implementation. Architecture Description Elements’ with respect to the case, spelling of attributes and format of values. See References section below.



Requirement participates in the following relationships:

  • Requirement traces to Architecture Description Element (including Requirement!)
  • Requirement derived from Requirement
  • Requirement governs Architecture Description Element
  • Requirement satisfies Architecture Description Element
  • Contract has part Requirement
  • Standard has part Requirement

Inherited relationships:

from Architecture Description Element:

  • Claim about Requirement
  • Concern about Requirement
  • Standard governs Requirement
  • Contract governs Requirement
  • Standard governs Requirement
  • Requirement satisfies Contract
  • Requirement satisfies Requirement
  • Requirement satisfies Standard
  • Requirement traces to Argument
  • Requirement traces to Document
  • Requirement traces to Requirement

Covered by TRAK IPR and licenses

Master Architecture View

Any Requirement used within an architecture description of the system-of-interest must appear on a MV-03 Requirements & Standards View for the architecture description.

The MV-03 is the Master Architecture View for Requirement.

Covered by TRAK IPR and licenses


It is NOT a requirements document. It is intended to represent a requirement - something that might be exported from a requirement management tool.

It can be associated with any architecture element inside the boxed area. This provides a mechanism to associate requirements in a tool with architectural models.

Covered by TRAK IPR and licenses


Other Frameworks

Neither MODAF nor the NATO Architecture Framework are able to represent Requirement within their metamodels. They make reference to this and alert the user to the danger that any requirements included might not be able to be exchanged:

p364 of APPENDIX 5 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework v3, CHAPTER 5

Full size:File:NAV requirements.jpg


Category:Metamodel -> Stereotype



© 2010 Eclectica Systems Ltd.