DownloadThe architecture viewpoints (specifications for architecture views iaw ISO 42010) for TRAK. 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.
Defines a total of 24 viewpoints. The ones needed are selected by taking the task sponsor's concerns and matching them to the typical concerns that each TRAK viewpoint addresses. The triples that address each concern are defined in the TRAK metamodel (https://sf.net/p/trakmetamodel).
The mapping between metamodel triple and architecture viewpoint is held with a Neo4J graph model (https://doi.org/10.1002/eng2.12168) and defined using (more) architecture viewpoints (https://www.researchgate.net/publication/335176248_Architecture_Description_Viewpoints_Metamodel_Description_Implementation_and_Model_Changes).
The minimal process is defined in the overall TRAK specification (https://sf.net/p/trak)
Features
- 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)
- defines each TRAK architecture viewpoint (specifications for architecture views)
- architecture viewpoints conform to ISO/IEC/IEEE 42010:2011 for architecture description of systems
- architecture viewpoints cover enterprise, concept, procurement, solution and management & everything from structure, behaviour, interchange to assurance, requirements and the architecture description task itself
- specification for each TRAK architecture view - content/ tuples from the TRAK metamodel (https://sf.net/p/trakmetamodel)
- defines naming convention
- defines stakeholder concerns addressed
- provides method for selecting architecture viewpoints needed to address stakeholder concerns
- defines subject & optional architecture tuples for each view
- specifies minimum acceptable content for each view (well-formedness) based on tuples
- defines consistency rules between views
- defines minimum allowed view sets so that elements can be found where you'd expect them to be
- designed to be used with the TRAK Overall (https://trak.sf.net) & TRAK metamodel (https://trakmetamodel.sf.net) (available on sourceforge)
- MVp-04 assurance viewpoint based on Claim, Argument, Evidence - can be used for any assurance e.g. claim of design compliance with requirements
- SVp-13 Solution Risk viewpoint integrates description of safety and security (Threat/Hazard, Vulnerability, Mitigation) with that of the design itself
- implementations for Sparx EA, MooD, Visio and OmniGraffle for Mac / iPad on Sourceforge
- implementation for Sparx EA at https://sf.net/p/mdgfortrak
- defines difference wrt original MODAF 1.2 used as partial source
Project Samples
License
GNU Free Documentation LicenseUser Reviews
-
Anonymous single word thumbs downs like "Pointless" don't contribute anything. By way of balance, TRAK works for me - its easy to get to grips with and being open source my company doesn't tie itself to big maintenance bills.
-
Simple, accessible, logical - as my first foray into enterprise architecture, TRAK has made the experience a lot easier than wading through defence-specific standards and dogma. Its genericity could see it used throughout business and civil services.