Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Mi 03.07.2024 00:00:12 61.917 +2 3.513.906 56,8 Fosstodon 4.2.9 500 Di 02.07.2024 00:01:44 61.915 -2 3.510.479 56,7 Fosstodon 4.2.9 500 Mo 01.07.2024 00:00:33 61.917 0 3.507.420 56,6 Fosstodon 4.2.9 500 So 30.06.2024 00:00:34 61.917 +2 3.504.671 56,6 Fosstodon 4.2.9 500 Sa 29.06.2024 00:01:13 61.915 +2 3.501.982 56,6 Fosstodon 4.2.9 500 Fr 28.06.2024 00:01:07 61.913 +3 3.498.459 56,5 Fosstodon 4.2.9 500 Do 27.06.2024 00:00:32 61.910 0 3.495.444 56,5 Fosstodon 4.2.9 500 Mi 26.06.2024 00:00:07 61.910 +1 3.494.703 56,4 Fosstodon 4.2.9 500 Di 25.06.2024 00:00:06 61.909 +1 3.491.246 56,4 Fosstodon 4.2.9 500 Mo 24.06.2024 00:00:01 61.908 0 3.488.299 56,3 Fosstodon 4.2.9 500
TRAK Architecture Framework (@trak_af) · 07/2023 · Tröts: 14 · Folger: 2
Mi 03.07.2024 14:41
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.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0