View TRAK:System


Version & Date

30th September 2011

Configuration History

See change record for the TRAK metamodel at


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

From the TRAK metamodel:

A System is something that has complex and emergent behaviour or properties. It is also therefore classically more than the sum of its parts. It may be a soft system (touchy-feely people for example - something you can’t touch) or it may be a classic hard system expressed as hardware.

A composite structure representing the physical, software and human resources (and their interactions) in an enterprise.

Covered by TRAK IPR and licenses

Tests For

Tests Against

Not a System if any of the following apply

  • the function(s) of the System can be purely described by the sum of the functions of the Resource with which the System is configured with i.e. no emergent behaviour
  • configured with purely Physical - not 100% but you would normally only expect behaviour from a combination of Physical and either Software or Human Resource i.e. not a pile of bricks or inanimate structure


Inherited Attributes:

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.



TRAK::System has the following relationships with other TRAK metamodel elements:

Inherited relationships:

Covered by TRAK IPR and licenses

Note: Roles such as System Authority, 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

Master Architecture View

Any System 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 System.

Covered by TRAK IPR and licenses


Part of the Solution Perspective.

The current INCOSE Systems Engineering Handbook defines a system as:

an integrated set of elements, subsystems, or assemblies that accomplish a defined objective. These elements include products (hardware, software, firmware), processes, people, information, techniques, facilities, services, and other support elements.

This is why TRAK::System is defined as it is and why MODAF::System cannot be used in this sense.

A System need not be configured with anything - initially you might not have information to be able to describe the components. In this case it is a high level outline description and the components of the system can be defined later on.

A System could consist of purely Human Resource with no Physical or Software. In this case it would be a soft system.

Note: TRAK::System is quite different in definition from MODAF::System. This is why the TRAK and MODAF namespace prefixes (TRAK:: and MODAF::) are used here.

Other Frameworks




Category:Metamodel -> Stereotype



© 2010 Eclectica Systems Ltd.