-
Key: UAF13-169
-
Status: open
-
Source: Eclectica Systems Ltd ( Nic Plum)
-
Summary:
2.2 Core Principles - Compliance Levels p 5 states:
'Compliance levels: UAFML has a single compliance level based upon a combination of the reuse of UML and SysML elements. It is expected that the views that are created as result of this profile have frames that reflect the underlying SysML diagram type that is used as the basis for the view. It is also expected that the graphical notation used to display elements within those views correspond to the standard SysML graphical notation of the SysML/UML metaclass that the stereotype extends.'
1) What does 'the UAFML has a single compliance level' actually mean?
2) This makes no sense. The UAFML must conform to the DMM - the DMM defines the concepts, their meaning etc with which the UML + SysML implementation in this profile is required to conform. The DMM essentially defines the set of input requirements which any implementation, including the OMG's own UML + SysML profile, must meet
3) Where is the traceability mapping to the DMM? This is missing and is required as part of the evidence of conformance to the DMM.
4) This conformance is local to this UML profile. Given that there is a normative profile file what does conformance mean? The OMG define both so either the UML profile that the OMG also produces either conforms or it doesn't . If the OMG are stating that in order to conform some extra requirements have to be met which are not defined by the UML profile these requirements must be identified to enable a fully-traceable conformance assessment i.e. to UML profile + to other atomic requirements. At the moment this is incomplete - where is the evidence that the OMG with their UML profile for the UAF + 'something else' conform to the DMM?
5) There is no reference to and this might be inconsistent with the conformance types stated in the UAF DMM section 2 (Type 1 to Type 3). The UAF DMM defines conformance levels for an implementation which have nothing to do with this local conformance and vice versa.
-
Reported: UAF 1.2 — Tue, 23 Apr 2024 12:25 GMT
-
Updated: Wed, 24 Apr 2024 14:05 GMT
UAF13 — 2.2 Core Principles - Compliance Levels - Doesn't Define Compliance Levels. Not Consistent With UAF DMM Conformance Types. OMG Define UML Profile ...
- Key: UAF13-169
- OMG Task Force: Unified Architecture Framework (UAF) 1.3 RTF