TRAK Enterprise Architecture UML Profile

• SourceForge Project Summary

trakumlprofile Project

• Introduction
• Features
• Open Source
• Download
• Get Support / Join
• Report Bug
• Support Request
• Keep Informed

TRAK SourceForge Projects

Definition

• TRAK
• TRAK Metamodel
• TRAK Viewpoints

Implementation

• Implementations of TRAK
• UML Profile for TRAK
• Rail Symbols
• MDG Technology for TRAK (Sparx Enterprise Architect)
• TRAK MooD 2010 Template
• TRAK OmniGraffle Stencil
• TRAK Visio Template

TRAK Information

• TRAK - Important Ideas
• TRAK FAQs (SF - trak project)
• Projects Using TRAK
• Demo Model
• Supporting Links
• Blog - "The Residual World"
• TRAK Community Wiki
• Community Discussion Forums

 

 

 

 

 

 

 

 

 

 

Home > TRAK UML Profile> Introduction

TRAK UML Profile

TRAK is an enterprise architecture framework based on the UK MoD's MODAF 1.2.

TRAK provides a way of describing systems and their place in the world through architectural models. The node and connector elements used to make the TRAK models is defined by the TRAK Metamodel. The TRAK views that contain these elements are defined by TRAK Viewpoints.

TRAK adopts the ISO 42010 / IEEE 1471 approach where each viewpoint specifies the content and interpretation of an individual TRAK architecture view.

Governance

Release of the TRAK UML profile is under the control of the TRAK Steering Group, chaired by the UK Department of Transport.

What is the TRAK UML Profile?

The TRAK UML profile is a UML implementation of the TRAK metamodel. It provides a UML representation of the set of node and connector elements from the TRAK Metamodel that may appear in one or more TRAK architecture views. These (UML) elements can be used with any general UML modelling tool.

Note - having a set of UML node and connector elements is a partial representation of the TRAK metamodel since there is nothing that defines the allowed combinations of nodes and a connector to form a triple i.e.

• Mitigation (a node element) uses (a connector element) Zone (a node element)

There are over 750 triples in the TRAK metamodel that may be used in TRAK views.

The TRAK Metamodel document specifies the simplified metamodel on a single sheet for easy reference.

The TRAK metamodel does not, however, tell you what you what triples the TRAK architecture views present - what elements and relationships you must and may show for each view type and the stakeholder questions they address. This is defined in the TRAK Viewpoints document.

Most good UML modelling tools allow you to load a UML profile. Once loaded you should then be able to pick objects and relationships from a palette to create architecture views that conform to the definitions in the TRAK Viewpoints.

If you are using Sparx Systems Enterprise Architect please visit the MDG Technology for TRAK site where you will find a tool-specific plugin that builds on this UML profile for TRAK.

Non-UML tools such as Salamander MooD can be used to create TRAK-compliant views and architecture description. In the case of MooD a template has been created for the 2010 version and is available on Sourceforge.

Where Does this Fit In?

The UML profile for TRAK is an implementation of TRAK.

TRAK is defined logically (free of implementation or solution) by 3 documents:

• an overall set of requirements (e.g. colour, conformance with TRAK, Bye Laws etc)
• the architecture viewpoints that specify each architecture view - TRAK Viewpoints
• the allowed elements and relationships - TRAK Metamodel

The definition of TRAK is released through Sourceforge as open source.

Implementations of TRAK

There are also implemementations of TRAK for various tools including:

• UML profile for TRAK. This site. Provides a set of objects and relationships for any UML modelling tool.

Where Do I Get It?

The TRAK Viewpoints document is available here ...

Modification Date: January 31, 2022