-
Key: UAF12-1
-
Status: closed
-
Source: International Business Machines ( Graham Bleakley)
-
Summary:
Submitted on behalf of Torsten Graeber in response to comments made by UAF group to queries previously submitted queries made by Torsten Graeber, June 2017
System (specialisation of resource architecture) and Software, Hardware (specialisation of physical resource) are disjoint. No whole/part relationship for common superclass ResourcePerformer (or its superclasses) found. Or is ResourceRole to be used for this? UAFP describes ResourceRoleKinds, but they are not included in the DM2.
Yes, Whole-Part is derived from the UML MM. Resource Roles are contextualised usage of ResourcePeformer and there is an Enumerated Type, ResourceRole Kind(Part, Component, Used Configuration,Used Physical Architecture,Human Resource, Platform, System, Sub Organization,Post Role, Responsibility Role,Equipment, Sub System Part,Hosted Software,Artifact Component,Natural Resource Component, Other) in the MM but this is not shown on the diagram. An issue will be raised to reference and show this on the diagram.
-
Reported: UAF 1.0 — Mon, 26 Jun 2017 11:03 GMT
-
Disposition: Closed; No Change — UAF 1.2
-
Disposition Summary:
Derivation of RoleKind names is up to the tool vendors
RoleKinds and how they are notated on the diagrams is solely tool vendor issue. UAF specification defines only the list of possible kinds where tool vendor can define how they appear on the diagrams.
-
Updated: Thu, 31 Mar 2022 19:31 GMT
UAF12 — Add the element ResourceRoleKinds to the relevant diagrams in the UAF DMM
- Key: UAF12-1
- OMG Task Force: Unified Architecture Framework (UAF) 1.2 RTF