Contents

Introduction

An Architecture Description Language is defined as:

Architecture Description Language (ADL) An ADL is any form of expression for use in Architecture Descriptions. An ADL might include a single Model Kind, a single viewpoint or multiple viewpoints. Examples of ADLs: Rapide, SysML, ArchiMate, ACME, xADL.

Source: Architecture Description Language - ISO/IEC/IEEE 42010:2011

TRAK is defined in an agnostic way i.e. independently of any means or notation that might be used.

As part of any potential implementation using an ADl such as the UML, the SysML, RDF (or anything else) an assessment has to be made on the suitability:-

• does it have elements with similar or acceptable semantics to represent the AD elements?
• does the ADL permit these elements to be connected together to represent the TRAK metamodel triples that form the basis of each TRAK architecture view?
  • if not, how much is missing?
  • can all of each TRAK architecture viewpoint concerns be addressed?
  • is it still possible to meet the minimum acceptable architecture view content criteria specified for each?
• how many of the TRAK architecture views can be implemented using the ADL?

This approach has to be used for any potential ADL.

Approach Used

Original

Note that the use of a spreadsheet was the original way in which an assessment was made - by comparing each of the architecture viewpoints versus every metamodel triple. This was not only large and tedious in terms of constructing and maintaining the spreadsheet it meant systematically unpacking/ 'multiplying-out' every generalisation relationship wherever there was a class hierarchy.

Current

The TRAK metamodel and the TRAK architecture viewspoints are now described (modelled) in a Neo4J graph database. This is based on a set of 6 (non-TRAK) architecture viewpoints defined in [1] and described in [2].

This provides the means to create a map (relationships) between each ADL element and a TRAK element, ADL triple to TRAK metamodel triple and from a triple to the TRAK architecture view(s) that allow or require that triple and hence the concerns framed by each governing architecture viewpoint.

References

1. N. Plum, ‘Architecture Description Viewpoints. Metamodel Description, Implementation and Model Changes’, Eclectica Systems Ltd, 3736126–001, Jul. 2024. https://www.researchgate.net/publication/335176248_Architecture_Description_Viewpoints_Metamodel_Description_Implementation_and_Model_Changes.
2. N. Plum, ‘Using directed graphs to define viewpoints to keep a metamodel, an architecture framework and views using different modeling languages consistent’, Engineering Reports, vol. 2, no. 6, p. e12168, Jun. 2020, doi: 10.1002/eng2.12168.

Files / Folders

• UML - an assessment of the use of the UML
• ADL_vs_TRAK_template.ots - generic template