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

Project Samples

Each TRAK metamodel element is defined in simple language - you don't need to be a technical priest! TRAK Allows Architecture Task/Scope to be Described Pragmatic Attributes Recognise Everyday Use / Needs Is Described by OWL and RDF Defines Triples Used to Define TRAK Architecture View Content SImple Understandable Metamodel is THE Defining Metamodel. The TRAK Metamodel Specification defines the user (solution-independent) requirements in accordance with typical systems engineering practice.

Project Activity

See All Activity >

Categories

Semantic Web, Knowledge Management, Graph Databases

License

Other License

Follow TRAK Metamodel

TRAK Metamodel Web Site

You Might Also Like
HRSoft Compensation - Human Resources Software Icon
HRSoft Compensation - Human Resources Software

HRSoft is the only unified, purpose-built SaaS platform designed to transform your complex HR processes into seamless digital ones

Manage your enterprise’s compensation lifecycle and accurately recognize top performers with a digitized, integrated system. Keep employees invested and your HR team in control while preventing compensation chaos.
Learn More
Rate This Project
Login To Rate This Project

User Ratings

5.0 out of 5 stars
★★★★★
★★★★
★★★
★★
★
2
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

User Reviews

Be the first to post a review of TRAK Metamodel!

Additional Project Details

Intended Audience

Aerospace, Government, Science/Research, End Users/Desktop, Engineering

Registered

2010-02-11
Report inappropriate content