Contents

---

Introduction

The TRAK.xml file is a bare bones UML profile for a UML modelling tool. It provides a set of UML/SysML node and connector elements to construct TRAK architecture views. The UML/SysML elements extend base UML metaclasses and SysML stereotypes (SysML v 1.X is itself based on UML metaclasses).

The UML and SysML profiles are intended to be used with a UML modelling tool. Note that there is a separate set of profiles encapsulated into a single plugin for Sparx Systems Enterprise Architect - MDG for TRAK hosted on a separate SourceForge project site at https://mdgfortrak.sourceforge.io.

The SysML UML profile for TRAK extends the base UML profile for TRAK - it references and then specialises some of the UML stereotypes in the UML profile. For the SysML profile to work therefore both the UML and the SysML UML profiles for TRAK have to be loaded into a modelling tool.

Node and connector elements represented form part of the metamodel for the open source TRAK architecture framework. Note that individual elements do not define a metamodel - it is the set of triples formed from them that defines a metamodel.

It is an implementation of the logical definition of TRAK and as such may include limitations of the architecture description languages, UML and the SysML, used to represent TRAK (in addition to any errors).

As an implementation it is governed by the specification 'TRAK. Implementation. Architecture Description Elements' which specifies the names, values in enumerated lists

Defining TRAK Documents

TRAK is defined by 3 documents.

The top level TRAK definition is at https://trak.sourceforge.io. This describes important ideas, choice of architecture description language, colour rules, bye laws, conformance with TRAK and the minimal modelling process. It invokes the following 2 documents:

• The specifications for TRAK architecture views (architecture viewpoints) are available at https://trakviewpoints.sourceforge.io

• The TRAK metamodel is available at https://trakmetamodel.sourceforge.io. This defines the architecture description elements, their properties, property values and triples.

Informative Documents

• TRAK-on-a-page.pdf provides a very short 4 page introductory guide to TRAK including the metamodel diagrams.

Implementation of TRAK in Tools

• TRAK. Implementation Architecture Descriptions Elements. https://sourceforge.net/projects/trak/files/Implement%20TRAK/ (defines how the logical definition of TRAK is to be implemented in any tool)

This release - Version 31

25th August 2025

Entities

• Architecture Description. Removed 'views' attribute - use 'Architecture Description has part Architecture View' triple. TRAK Metamodel 2025-04-30
• Architecture Description Element. pm marking - Added 'OFFICIAL' enumerated value . pm descriptor' - added 'LEGAL' enumerated value, changed MANAGEMENT' to 'HR / MANAGEMENT' , deleted 'PERSONAL'. TRAK Metamodel 2025-06-25
• Architecture Description Tuple. Deleted (doesn't appear in any TRAK architecture view - internal management of TRAK only
• Architecture Framework. Deleted (doesn't appear in any TRAK architecture view - internal management of TRAK only
• Architecture Metamodel. Deleted (doesn't appear in any TRAK architecture view - internal management of TRAK only
• Architecture Perspective. Deleted (doesn't appear in any TRAK architecture view - internal management of TRAK only
• Architecture Task. Removed 'sponsor' and 'stakeholders' attributes - use 'Role extends to Architecture Task' triple.TRAK Metamodel 2025-04-30
• Architecture Viewpoint. Deleted (doesn't appear in any TRAK architecture view - internal management of TRAK only)
• DCMI Artefact. Changed 'url' to 'artefact url'. TRAK Metamodel 2024-09-23.
• Event. Added 'event identifier'. Changed 'likelihood' to 'probability'. TRAK Metamodel 2025-04-30
• Safety Monitored Element. 'safety integrity level' - changed 'Not Applicable' enumerated value to 'N/A'

• Requirement. 'compliance level required'. Changed 'Desirable - Obligation' enumerated value to 'Desirable - Intent'. TRAK Metamodel 2025-06-25 'requirement scope' - added 'N/A' and 'requirement type' - added 'N/A - Heading'. TRAK Metamodel 2023-09-09

• deleted stereotypedrelationships and metaconstraints - proprietary / non-standard UML used by Sparx EA.

Relationships

• added: 'is party to' connector (Dependency)TRAK Metamodel 2025-04-30

For the detail please see revisions.txt file.

Support

On the SourceForge project site (https://sf.net/p/trakumlprofile) there is a Tracker where you can submit bugs.

TRAK on the Internet

See also:

• TRAK Architecture Framework Group on LinkedIn
• TRAK Group on Facebook
• TRAK_AF on Mastodon
• TRAK_AF on Twitter

Implementations of TRAK

• UML profile for TRAK. Provides a set of UML and SysML node and connector elements for any UML modelling tool.
• UML / SysML with TRAK. Provides bare profiles (any UML modelling tool) and an MDG for Sparx Systems Enterprise Architect for those wanting to annotate standard UML / SysML Class, Use Case and State Machine diagrams with TRAK elements.
• MDG Technology for TRAK. Provides the views, toolbox palettes of UML and SysML elements, custom searches and context-sensitive linking for Sparx Systems' Enterprise Architect UML modelling tool.(Nic Plum, Eclectica Systems Ltd.)
• TRAK MooD 2010 Template. Provides a template through which TRAK architecture views can be created using Salamander MooD modelling tool and is constrained to use node and connector elements from the TRAK metamodel.(Brian Cliff, VEGA)
• OmniGraffle Stencil for TRAK. A stencil that provides the metamodel node and connector elements for OmniGroup's OmniGraffle ( a Visio-like tool for Mac and iOS).
• TRAK Visio Template. This similarly provides a set of node and connector elements.