SysML 1.6 RTF Avatar
  1. OMG Issue

SYSML16 — SysML does not clearly defines how an association defines properties

  • Key: SYSML16-192
  • Status: closed  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    In section 8.3.1.3 the SysML specification excludes the dot notation of the association that shows the ownership of the defined properties.

    But the SysML specification does not specify how the ownership of properties is defined. There are different usages of the association relationship like composition in bdd, actor/use case relationship or in conceptual bdds. Different usages require different ownerships of the defined properties.

    Proposal:
    Define a default and allow the dot notation if the modeler wants to define it differently.

  • Reported: SysML 1.4 — Fri, 5 Feb 2016 12:17 GMT
  • Disposition: Closed; No Change — SysML 1.6
  • Disposition Summary:

    Association end ownership is defined according to the navigability

    In SysML the ownership of association ends is fully defined according to the navigability of those ends. If the classifier (e.g. a Block) has a navigable association to another classifier it owns the end corresponding to the role played by that other classifier. If the association end is not navigable it is owned by the association itself.

    This is enforced by SysML::Block constraint#3:

    In the UML metamodel on which SysML is built, any instance of the Property metaclass that is typed by a block (a Class with the «block» stereotype applied) and which is owned by an Association must [sic] not have a name and may not be defined as a navigable owned end of the association

  • Updated: Mon, 1 Apr 2019 18:17 GMT