View TRAK:Resource Interaction



5th September 2015


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

From the TRAK metamodel:

A formalised representation of the thing exchanged between Resource.

Covered by TRAK IPR and licenses

Tests For

  • something flows or is exchanged not part of the specification of the environment

Covered by TRAK IPR and licenses

Note that an energy flow has to be made in the context of what is needed e.g. a supply with a rated voltage and which is capable of being defined by a protocol - 440v, 3 phase, 110v AC supply

Tests Against

  • in realms of physics e.g. thermal flow
  • effect of/ on immediate environment e.g. EMC, vibration

Covered by TRAK IPR and licenses


  • resource interaction identifier
  • exchange type = Unknown, Data, Energy, Resource
  • interface authority (an Organisation)

Inherited Attributes:

Covered by TRAK IPR and licenses


Resource Interaction participates in:

Inherited relationships:

+ from Architecture Description Element:

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

Covered by TRAK IPR and licenses

Configuration History

  • 20th August 2011. Resource interaction identifier added.

See change record for the TRAK metamodel at

Master Architecture View

Any Resource Interaction used within an architecture description of the system-of-interest must appear on a SV-02 Solution Resource Interaction View for the architecture description.

The SV-02 is the Master Architecture View for Resource Interaction.

Covered by TRAK IPR and licenses


The exchange isn’t just information. It can be energy, data or resource (or ‘Unknown).

At some point or level almost anything can be rationalised as a resource interaction. There is a level below which, however, we’re either not interested or which it adds nothing. The natural environment is an example in point as almost everything will interact in some way - just saying it affects another unit via a thermal interface doesn’t help. There are better ways of managing these things than using an architecture description!!

Resource is a graphic path element - it is shown as a line on an Architecture View.

Other Frameworks





Category:Metamodel -> Stereotype



© 2010 Eclectica Systems Ltd.