Issue 19857: Satisfy, Verify and DeriveReqt could be used with non-requirement elements (sysml-rtf) Source: ALSTOM (Mr. Wagner Mendes, wagner.schalch(at)alstom.com) Nature: Enhancement Severity: Significant Summary: SysML specification constraints the usage of Satisfy, Verify and DeriveReqt relationships to requirement model elements. When in MBSE approach, textual requirements are most likely to be left aside and non-textual requirements start commonly being used. For example, an Activity can represent a functional requirement, as it has inputs, outputs and a processing that shows how inputs are transformed into outputs. When using non-textual requirements, other model elements will start representing requirements. Therefore, those relationships should accept elements that are not SysML::Requirement model elements. Resolution: Requirement Relationship Constraints are Appropriate Requirement relationships need to be contained to have at least one end be identified as a "requirement" in the model. The resolution to [1]SYSMLR-155 has clarified the scope of requirement properties, which may help address the originator's concern. ---------------------------------------------------------------------------------------- [1] http://issues.omg.org/browse/SYSMLR-155 Revised Text: Actions taken: November 24, 2015: received issue January 3, 2017: Closed; No Change April 6, 2017: closed issue Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 01 Dec 2015 14:13:34 -0500 To: juergen@omg.org From: Juergen Boldt Subject: Fwd: Issue/Bug Report 19857 X-Virus-Scanned: amavisd-new at omg.org From: webmaster@omg.org Date: 24 Nov 2015 06:13:45 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Wagner Schalch Mendes Employer: Alstom Brasil mailFrom: wagner.schalch@alstom.com Terms_Agreement: I agree Specification: OMG Systems Modeling Language (OMG SysML™) Section: 16.3.2 FormalNumber: formal/2015-06-03 Version: Version 1.4 Doc_Year: 2015 Doc_Month: June Doc_Day: 03 Page: 164-168 Title: Satisfy, Verify and DeriveReqt could be used with non-requirement elements Nature: Enhancement Severity: Significant CODE: 3TMw8 B1: Report Issue Remote Name: 159.245.32.90 Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36 Time: 06:13 AM Description: SysML specification constraints the usage of Satisfy, Verify and DeriveReqt relationships to requirement model elements. When in MBSE approach, textual requirements are most likely to be left aside and non-textual requirements start commonly being used. For example, an Activity can represent a functional requirement, as it has inputs, outputs and a processing that shows how inputs are transformed into outputs. When using non-textual requirements, other model elements will start representing requirements. Therefore, those relationships should accept elements that are not SysML::Requirement model elements. Juergen Boldt Vice President, Member Services Object Management Group 109 Highland Ave Needham, MA 02494 USA Tel: +1 (781) 444 0404 x 132 fax: +1 (781) 444 0320 www.omg.org []