The definition of the metamodel for TRAK (defines allowed AD elements and relationships i.e. tuples/ triples for the TRAK viewpoints and views). TRAK is a general systems-thinkers'/system engineering enterprise architecture framework. It is simple, user-friendly, pragmatic and not limited to IT. 100% triple-centric and semantically-sound. Forms basis for RDF + OWL ontology description - see https://trakmetamodel.sourceforge.io/vocab/TRAK_metamodel.html
Features
- defines tuples / triples (declarative statements) that appear in TRAK viewpoints and views
- metamodel triples designed to address architecture viewpoint concerns (and architecture view subject)
- designed by systems engineers for others & based on need / typical application
- supports simple, pragmatic, no nonsense, just "good enough" way of addressing typical concerns (not populating a data model)
- metamodel (A3) for easy reference when modelling - see snapshot below for example
- defines each TRAK triple (node-connector-node) / statement / assertion in architecture description)
- defines attributes/properties of each element type e.g. Dublin Core, security descriptors, safety-related
- provides tests for/against to determine what type to use when modelling using TRAK
- defines colours/ presentation for each element
- defines tuple set rules (combinations of paths)
- provides rationale/justification for relationships
- released under GNU Free Documentation License
- written for users/architects/human beings - not specifiers or tool vendors
- Overall rules/process at https://sf.net/p/trak
- designed to be used with TRAK Viewpoints document (https://trakviewpoints.sf.net) - also on Sourceforge
- defines central (RDF + OWL) ontology description to enable TRAK architecture description as a knowledge graph (https://trakmetamodel.sourceforge.io/vocab/TRAK_metamodel.html)
- defines semantic sources / vocabulary basis for each element, property & value (semantics)
- defines initial baseline against MODAF 1.2
License
Other License
You Might Also Like
Rate This Project
Login To Rate This Project
User Reviews
-
Anonymous thumbs down reviews that simply ask a question "What's the point?" are not terribly reliable or encouraging. TRAK works for me because it offers a system-centric approach which in other frameworks is either missing or obscured by an overburdened metamodel.
-
I'm not hugely expert on metamodels but I understand from others that this one is, by comparison, very simple and generic. This must make it really useful for making the case for architectural modelling to organisations that need it but don't realise it yet...