SysML 1.6 RTF Avatar
  1. OMG Issue

SYSML16 — Constraints on Satisfy and Verify should refer to AbstractRequirement

Open Closed All
  • Key: SYSML16-367
  • Status: closed  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    Constraints owned by either Satisfy or Verify stereotype still refer to the SysML::Requirement stereotype while they should have been modified so that they refer to the AbstractRequirement stereotype added in 1.5
  • Reported: SysML 1.5 — Thu, 21 Sep 2017 09:34 GMT
  • Disposition: Duplicate or Merged — SysML 1.6
  • Disposition Summary:

    Merged with SYSML16-274

    To be fixed as suggested by SYSML16-311
    Constraints owned by either Satisfy or Verify stereotype shall refer to SysML::AbstractRequirement instead of the SysML::Requirement stereotype.

    Revised Text:
    SysML::Satisfy::Constraint#1 shall be replaced by:
    The supplier shall be an element stereotyped by any subtype of «AbstractRequirement»

    AbstractRequirement.allInstances().base_NamedElement->includes(self.base_Abstraction.supplier)

    SysML::Verify::Constraint#1 shall be replaced by:
    The supplier shall be an element stereotyped by any subtype of «AbstractRequirement»

    AbstractRequirement.allInstances().base_NamedElement->includes(self.base_Abstraction.supplier)
  • Updated: Mon, 1 Apr 2019 18:17 GMT