SysML 1.7 RTF Avatar
  1. OMG Issue

SYSML17 — Risk, Source and Verification Method Are Attributes of Any / All Requirements Not Just an Extended Requirement

  • Key: SYSML17-635
  • Status: open  
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    The verifyMethod, source and risk attributes are only available for extended requirements i.e. a straight vanilla Requirement has no associated verification method or risk. This doesn't reflect reality / the actual taxonomy and has nothing to do with the sub-classification of a requirement as physical, functional etc. i.e. these are attributes of the parent Requirement not the child extended requirement. It also then requires that a SE has to subclassify before they can ascribe a risk level or verification method.

    Even looking at the definiton of extendedRequirements this definition has nothing to do differentiation in terms of an ontology - only the means to do things. 'A mix-in stereotype that contains generally useful attributes for requirements'

    It also means that if the SE has a requirement that doesn't fit into the OMG classification schema i.e. none of the existing categories then they cannot easily assign these attributes (e.g. a requirement to conform to a standard isn't a design constraint, isn't functional etc). These common attributes should be present without forcing the SE to subclassify before they are available.

  • Reported: SysML 1.5 — Fri, 26 May 2023 11:10 GMT
  • Updated: Thu, 15 Jun 2023 12:48 GMT