-
Key: SYSML16-225
-
Status: closed
-
Source: Airbus Group ( Mr. Yves Bernard)
-
Summary:
Two notable problems with the definition of the stakeholder model element:
1. it is defined as being an extension of the UML Classifier: It is not clear whether the intention was to define the meta-model object as a class to which the Stakeholder stereotype is attached, or for the "stakeholder" stereotype to be applied to anything in the model that is a classifier - which is a very long list of things in UML. If it was the latter then a constraint should be added to subset the set of classifiers to just those considered applicable. Class and Actor have been suggested, but this creates choice and that is a source of inconsistent modelling. The example provided for its application in viewpoint modelling (e.g. Figure D.27 SysML 1.5) shows the stakeholder with a class-like node representation. So maybe it should be implemented as a stereotyped UML class.
2. The standard does not indicate whether or not Stakeholder model elements can be used for any other purpose beyond that of defining a stakeholder-viewpoint relationship. If a BDD allows stakeholder model elements to be shown (ordinarily it only allows Block, Activity, and comment model elements), then a basic form of stakeholder relationship modelling could be supported, which is a missing capability from SysML and one that is not possible when a modelling tool enforces all of the UML defined constraints on the actor model element kind. Other UML derived profiles appear to have a richer set of Stakeholder modelling capabilities and include a richer set of people centric modelling elements. Furthermore, a point of integration with SysML could be found if these profiles all use stereotyped UML class objects, since the SysML Stakeholder stereotype could be applied to their model element kinds and thus used for defining SysML viewpoints.
The SysML RTF need to agree how the Stakeholder concept should be developed for SysML modelling. -
Reported: SysML 1.6 — Fri, 24 Feb 2017 15:37 GMT
-
Disposition: Resolved — SysML 1.6
-
Disposition Summary:
constrain applicability of stakeholder stereotype
stakeholder stereotype extends Classifier which includes also classifiers which make not much sense, e.g. use case, association.
There is no consensus to further restriction for the stakeholder stereotype usage.
-
Updated: Mon, 1 Apr 2019 18:17 GMT
SYSML16 — Stakeholder model element not precisely defined
- Key: SYSML16-225
- OMG Task Force: SysML 1.6 RTF