Lmst

New "Turtle all the way down" version of the TRAK architecture framework. Provides semantically accurate description of conformance claim. Also means to describe a fault tree. More than a little added Turtle/RDF examples of TRAK architecture views.

#trak #opensource #mbse #KnowledgeGraphs #architectureFramework

https://trakviewpoints.sourceforge.io/architecture_viewpoints/SVp-11.html
https://trakmetamodel.sourceforge.io/metamodel/node/Event.html

An example of a TRAK SV-11 Solution Event causes architecture view. This architecture view describes a simple fault tree where if any of 3 child events occurs the top event occurs.

The example uses an n-ary tuple to link the top event to the collection of child events which are all joined using a logical 'OR' relationship.

A fragment of a TRAK MV-04 Assurance architecture view. This architecture view presents a single claim of conformance which is formed from 2 parts:

1) a Conformance Assertion Triple - Software.'XML Studio' satisfies Standard. 'ISO?IEC 14882:2024 Programming Language C++'

2) a Conformance Claim triple - Claim 'XML Studio fully complies with ISO/IEC 14882:2024' about Conformance Assertion Triple

i.e. the object of the triple starting with the Claim is itself a triple.

@trak_af @neo4j The graphic is a Model Change & Configuration architecture view produced against its defining architecture viewpoint[1].

The architecture view describes the changes, additions made in the 9th January 2025 release of the TRAK. Viewpoints specification in the context of the previous 40 releases since the original release in 2010. https://tinyurl.com/35v3hete https://tinyurl.com/trakviewpoints-html https://tinyurl.com/trakmetamodel-html #neo4j #opensource #architectureframework #trak #mbse

Example of a Model Change & Configuration Architecture View using the architecture viewpoint definition in ‘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.

Describes the changes made to the TRAK Architecture Viewpoints specification - TRAK00001. TRAK. Enterprise Architecture Framework. Viewpoints at https://sourceforge.net/p/trakviewpoints. Describes the modifications and additions made to the individual TRAK architecture viewpoints (specifications for architecture views in accordance with ISO/IEC/IEEE 42010) in the context of all of the releases of the specification to date.

Generated from a directed property graph model of TRAK held in Neo4j - ‘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.

New version of the TRAK architecture viewpoints specification https://sourceforge.net/projects/trakviewpoints/files/TRAK_ArchitectureViewpoints.pdf/download

This version incorporates recent changes to the TRAK metamodel.

https://sourceforge.net/p/trakviewpoints/code/78/

New version will be represented in the web pages at https://trakviewpoints.sourceforge.io/viewpoint_concerns.html when modifications to the Neo4J graph model of TRAK are complete.

#opensource #trak #architecturedescription #architectureframework #mbse #entarch #architectureviewpoints #neo4j

@trak_af New release of MDG for TRAK plugin for Sparx EA. https://sf.net/p/mdgfortrak #trak #opensource #architectureframework #mbse #sparxsystems #enterprisearchitect #uml #sysml

Shows a SysML implementation of a TRAK MV-02 Architecture Description Design Record architecture view. The architecture view describes a task sponsored by the engineering directorate to assess the risk control mitigation assessment. This is in response to a concern about a claim made against BS EN 60601 that the manufacturer has specified methods to verify the effectiveness of risk control methods. This architecture view shows the concern about the claim and the reference to the architecture view that addresses this concern.

TRAK MVp-02 Architecture Description Design Record - https://trakviewpoints.sourceforge.io/architecture_viewpoints/MVp-02.html

Note that there appears to be a bug in using an Association with compositionKind='Aggregation at Source' where it is not possible to hide the diamond symbol (unlike a connector based on either Aggregation or Composition UML Metaclasses).

@trak_af New release for the MDG for TRAK plugin for Sparx SYstems Enterprise Architect UML (and SysML) modelling tool. https://sf.net/p/mdgfortrak #trak #opensource #mbse #enterprisearchitecture #architectureframework

Shows the customised Sparx Enterprise QuickLink feature in works for a TRAK SV-01 Solution Structure Architecture View implemented as a SysML Block Definition Diagram. The customised Quicklink allows the user to drag away from the selected node element on the diagram and the MDG for TRAK plugin then offers a set of allowed node and connector elements. Selecting one causes the triple to be created on the architecture view. The diagram shows the newly-added 'Software plays Role' triple offered as a valid triple.

This version of the metamodel adds definitions of enumerated values for metamodel element properties and links them to trusted vocabularies or sources (so that the graph of TRAK can then produce a richer ontology description using RDF(S) + OWL in linked to these vocabularies).

#trak #opensource #architectureframework #mbse #architecturedescription

https://sf.net/p/trakmetamodel

Metamodel Provides Triples to Define Architecture Viewpoints. ISO/IEC/IEEE 42010 defines a set of concepts. A Stakeholder has one or more concerns. Each Architecture Viewpoint frames one or more of these concerns. An Architecture Viewpoint - a specification for an Architecture View has to define the content. It is the metamodel that defines a set of triples. An Architecture View presents one or more triples. Each triple presented therefore has to address one or the architecture viewpoint concerns. A triple may be allowed, for example to provide context. Triples that directly address the concerns are required by the architecture viewpoint.

On the left hand side there are 3 nodes and 2 connectors forming 2 triples (and hence a path). On the right hand side is shown the 3 nodes and 2 connectors as disconnected atomic elements. Defining indinidvidual elements does not define any triples.

The diagram shows the graph output from a model of TRAK held in the Neo4J graph database. The diagram shows the modifications, additions and deletions made for this metamodel release. It shows a long tail of all of the previous releases of the TRAK metamodel. There are more than 50 of these releases. The right hand side shows particular changes made. Most changes concern enumerated property values. An addition is represented by Change - ADDS - Value - TO - Property or Change deletes Value from Property. The graph database holds each version of the TRAK metamodel together with the architecture viewpoint definitions. It is also used to produce the ontology description of the metamodel elements in RDF and OWL.

Update to the open sourceTRAK architecture framework metamodel. Added section on ontology description of TRAK metamodel. Added links to other vocabs for the metamodel properties.

#trak #mbse #architectureframework #opensource #ontology

https://sf.net/p/trakmetamodel

The TRAK metamodel exhibits an ontology (a particular architecture) that is described by an ontology description. The ontology description uses OWL and RDF - both ontology description languages.

The TRAK metamodel is formed from triples. An ontology differs because it is defined by individual connector, node and property elements not the triples i.e. not the combinations of the node and connector elements that form the metamodel.

A metamodel therefore contains an ontology but an ontology is not a metamodel.

Release of the TRAK metamodel. Links element definitions to the OED and other vocabularies.

Adds triples to allow TRAK to define its own architecture viewpoints - allowed content, minimum acceptable content and combination rules. All in a fully model-based way without text etc.

Adds hyperlinks from properties to the node and connector elements having those properties.

Restores phantom / missing Risk element in table.

#trak #architectureframework #opensource #mbse #enterprisearchitecture