View TRAK:Physical

TRAK_logo_60.jpg

Version & Date

28th January 2017

Configuration History

See change record for the TRAK metamodel at http://trakmetamodel.svn.sourceforge.net/viewvc/trakmetamodel/trunk/?view=log

Definition

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

From the TRAK metamodel:

A physical thing. Can represent an equipment (which can host Software), a building or civil item, train etc.

Covered by TRAK IPR and licenses

Tests For

  • bricks & mortar

Covered by TRAK IPR and licenses

Tests Against

  • a System - systems are almost always not purely physical. They may have an essential part that is the Physical container but the system itself is formed from the collection and behavioural interaction of its essential parts
  • the collection of people/resource (Organisation) that sits within the Physical (building) - often we give the same name to a headquarters building and to the organisation that is based within it.

Attributes

Inherited from:

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.

Relationships

Physical.jpg

Physical participates in:

  • Physical contains Physical
  • Physical contains System
  • Physical is attached to Physical
  • Physical has part Physical
  • Physical is a Resource
  • Physical physically depends on Physical
  • Physical physically supports Physical
  • Software is hosted on Physical
  • System is configured with Physical

Inherited relationships:

+ from Resource

from Architecture Description Element:

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

Covered by TRAK IPR and licenses

Note: Roles such as Design Authority, Manufacturer are defined using the SV-01 Solution Structure View  and the scope is defined using the extends to relationship between Resource and Role.

Configuration History

See change record for the TRAK metamodel at http://trakmetamodel.svn.sourceforge.net/viewvc/trakmetamodel/trunk/?view=log

Master Architecture View

Any Physical used within an architecture description of the system-of-interest must appear on a SV-01 Solution Structure View for the architecture description.

The SV-01 is the Master Architecture View for Physical.

Covered by TRAK IPR and licenses

Comments

Can represent an equipment (which can host Software), a building or civil item, train etc.

Care is needed to distinguish when loose language is used between, for example, a HQ or Station as a building (=Physical) and the Organisation that might have the same name.

Other Frameworks

References

 

Category:Metamodel -> Stereotype
Category:Solution
Category:Architecture Perspective -> Solution

Categories:

 

© 2010 Eclectica Systems Ltd.