-
Key: UAF13-25
-
Status: closed
-
Source: Department of Navy ( Mr. James Ciarcia)
-
Summary:
UAF::ProtocolImplementation is really a subset of all UAFElement.conformsTo Standards. Aka if a UAF::ProtocolImplementation implements a UAF::Protocol it should also count as conformingTo it. Recommend making the implements tag a subsetted property of the conformsTo tag. Also, to allow Standards to actually enforce parametric constraints or execute behavioral simulations as part of UAF models, recommend creating a <<ConformsTo>> property stereotype that has <<Standard>> as a target and <<UAFElement>> as a Source (or maybe just limit to PropertySet), and/or add a derived Tag to UAFElement that derives a subset of conformsTo relationships from classifier.properties that have <<Standard>> or stereotypes derived from <<Standard>> as their type.
-
Reported: UAF 1.2 — Thu, 17 Mar 2022 20:30 GMT
-
Disposition: Deferred — UAF 1.3b1
-
Disposition Summary:
UAF RTF 1.3 scope is limited to Mission Engineering only
Out of scope for 1.3
-
Updated: Mon, 24 Mar 2025 13:35 GMT
UAF13 — UAFElement.conformsTo and ProtocolImplementation.implements alignment and reification with fUML
- Key: UAF13-25
- OMG Task Force: Unified Architecture Framework (UAF) 1.3 RTF