SYSML12 — SysML Issue based on UML Issue 10044: Profile Structure Diagrams are missing from Annex A

UML 2.1 added a new structural diagram type, Profile Diagram for the purposes of containing the profile-defining elements. SysML either should be made consistent or should explicitly indicate that the diagram is not part of SysML

The Profile Diagram was proposed as a new SysML diagram since it was added
to UML to support profile definitions. However, the Superstructure Specification,
Table 18.1 and Table 18.2, does not require that profiles be defined on a profile
diagram. The diagram elements needed to specify a profile can be represented
on any structure diagram. As a result, it is recommended not to add a profile
diagram in SysML to limit the number of diagram kinds, and that profile
definitions be represented on package diagrams.
The following text was originally proposed as part of the resolution for this issue,
but did not fit as part of the scope of Annex A. It could be considered as part of a
future revision of SysML, for example as part of Chapter 17, Profiles and Model
Diagrams:
... extra caution is warranted regarding the intent of a profile diagram as
explained below. ...
As far as UML is concerned, a profile can extend the UML metamodel
instead of the UML4SysML subset of UML metamodel. However, a profile
extending the UML may not be compatible with the SysML profile that
extends the UML4SysML subset of the UML. For example, a stereotype
called <<AssociationWithNavigableEnds>> extending UML::Association
with a constraint to the effect that the association ends are navigable and
also owned directly by the association would clearly be incompatible with
the <<Block>> stereotype of SysML per 8.3.2.2. For such cases where the
user intent is clearly in extending the UML4SysML subset of the UML in a
manner that is compatible with the SysML stereotypes and their
constraints, it is important that a SysML tool provides support for
distinguishing user-defined profiles extending the UML metamodels and user-defined profiles extending the UML4SysML subset of the UML in a
manner that is compatible with respect to the SysML stereotypes and their
constraints.
Revised Text:
On p. 171, Annex A.1, change the third paragraph, currently:
SysML does not use all of the UML diagram types such as the object
diagram, communication diagram, interaction overview diagram, timing
diagram, and deployment diagram. This is consistent with the approach
that SysML represents a subset of UML. In the case of deployment
diagrams, the deployment of software to hardware can be represented in
the SysML internal block diagram. In the case of interaction overview and
communication diagrams, it was felt that the SysML behavior diagrams
provided adequate coverage for representing behavior without the need to
include these diagram types. Two new diagram types have been added to
SysML including the requirement diagram and the parametric diagram.
with the following:
SysML does not use all of the UML diagram types such as the object
diagram, communication diagram, interaction overview diagram, timing
diagram, deployment diagram, and profile diagram. This is consistent with
the approach that SysML represents a subset of UML. In the case of
deployment diagrams, the deployment of software to hardware can be
represented in the SysML internal block diagram. In the case of interaction
overview and communication diagrams, it was felt that the SysML
behavior diagrams provided adequate coverage for representing behavior
without the need to include these diagram types. In the case of the profile
diagram, profile definitions can be captured on a package diagram, which
is also allowed in SysML. Two new diagram types have been added to
SysML including the requirement diagram and the parametric diagram.