Issue 17016: Property Based Requirements (sysml-rtf) Source: Lockheed Martin (Mr. John Watson, jcwatson(at)ieee.org) Nature: Revision Severity: Significant Summary: In SysML today requirements can be represented in a model only in a textual form. Being textually based these requirements often introduce ambiguity, are often redundant with other model element properties, and lack a formally making it difficult to leverage directly in parametric and other analysis efforts. This issue suggests an alternative means of representing requirement in the model environment without using a pure text string. The alternative means is referred to as Property Based Requirement (PBR). PBR defines a requirement mathematically and defines a set of requirement properties. The goal is declare other types of model elements as requirements and apply these properties to those model elements. A PBR theory is described in a paper called “Toward a Property Based Requirements Theory: System Requirements Structured as a Semilattice” by Patrice Micouin. This technique is further elaborated in a paper called “Requirements Management within a Full Model-Based Engineering Approach” by Yves Bernard Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: January 19, 2012: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org To: Subject: Issue/Bug Report ******************************************************************************* Name: John Watson Employer: Lockheed Martin mailFrom: john.watson@lmco.com Terms_Agreement: I agree Specification: OMG Systems Modeling Language Section: Requirements FormalNumber: ptc/2011-08-09 Version: 1.3 Doc_Year: 2001 Doc_Month: September Doc_Day: 01 Page: Title: Property Based Requirements Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: In SysML today requirements can be represented in a model only in a textual form. Being textually based these requirements often introduce ambiguity, are often redundant with other model element properties, and lack a formally making it difficult to leverage directly in parametric and other analysis efforts. This issue suggests an alternative means of representing requirement in the model environment without using a pure text string. The alternative means is referred to as Property Based Requirement (PBR). PBR defines a requirement mathematically and defines a set of requirement properties. The goal is declare other types of model elements as requirements and apply these properties to those model elements. A PBR theory is described in a paper called .Toward a Property Based Requirements Theory: System Requirements Structured as a Semilattice. by Patrice Micouin. This technique is further elaborated in a paper called .Requirements Management within a Full Model-Based Engineering Approach. by Yves Bernard. Subject: RE: issue 17016 -- SysML RTF issue Date: Thu, 19 Jan 2012 13:05:46 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 17016 -- SysML RTF issue Thread-Index: AczW4kulIwN8SiPAQZCmJeCcptznFwAC0njQ From: "Pete Rivett" To: Cc: How much of this is covered by OMG.s existing Requirements Interchange Format (ReqIF) standard http://www.omg.org/spec/ReqIF/1.0.1/ ? Pete From: Juergen Boldt [mailto:juergen@omg.org] Sent: Thursday, January 19, 2012 11:40 AM To: issues@omg.org; sysml-rtf@omg.org Subject: issue 17016 -- SysML RTF issue From: webmaster@omg.org Date: 19 Jan 2012 14:35:26 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: John Watson Employer: Lockheed Martin mailFrom: john.watson@lmco.com Terms_Agreement: I agree Specification: OMG Systems Modeling Language Section: Requirements FormalNumber: ptc/2011-08-09 Version: 1.3 Doc_Year: 2001 Doc_Month: September Doc_Day: 01 Page: Title: Property Based Requirements Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: In SysML today requirements can be represented in a model only in a textual form. Being textually based these requirements often introduce ambiguity, are often redundant with other model element properties, and lack a formally making it difficult to leverage directly in parametric and other analysis efforts. This issue suggests an alternative means of representing requirement in the model environment without using a pure text string. The alternative means is referred to as Property Based Requirement (PBR). PBR defines a requirement mathematically and defines a set of requirement properties. The goal is declare other types of model elements as requirements and apply these properties to those model elements. A PBR theory is described in a paper called .Toward a Property Based Requirements Theory: System Requirements Structured as a Semilattice. by Patrice Micouin. This technique is further elaborated in a paper called .Requirements Management within a Full Model-Based Engineering Approach. by Yves Bernard. Best regards, -Juergen Juergen Boldt Director, Member Services 140 Kendrick Street, Building A Suite 300 Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org Date: Thu, 19 Jan 2012 16:22:16 -0500 From: "Chonoles, Michael J" Subject: RE: RE: issue 17016 -- SysML RTF issue To: Pete Rivett , "Watson, John" Cc: "sysml-rtf@omg.org" Thread-Topic: RE: issue 17016 -- SysML RTF issue Thread-Index: AczW4kulIwN8SiPAQZCmJeCcptznFwAC0njQAACrtEA= Accept-Language: en-US acceptlanguage: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7361,1.0.211,0.0.0000 definitions=2012-01-19_09:2012-01-19,2012-01-19,1970-01-01 signatures=0 For the most part, ReqIF is irrelevant to the issue identified by John Watson. Michael From: Pete Rivett [mailto:pete.rivett@adaptive.com] Sent: Thursday, January 19, 2012 4:06 PM To: Watson, John Cc: sysml-rtf@omg.org Subject: Ex: RE: issue 17016 -- SysML RT F issue How much of this is covered by OMG.s existing Requirements Interchange Format (ReqIF) standard http://www.omg.org/spec/ReqIF/1.0.1/ ? Pete From: Juergen Boldt [mailto:juergen@omg.org] Sent: Thursday, January 19, 2012 11:40 AM To: issues@omg.org; sysml-rtf@omg.org Subject: issue 17016 -- SysML RTF issue From: webmaster@omg.org Date: 19 Jan 2012 14:35:26 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: John Watson Employer: Lockheed Martin mailFrom: john.watson@lmco.com Terms_Agreement: I agree Specification: OMG Systems Modeling Language Section: ; Requirements FormalNumber: ptc/2011-08-09 Version: 1.3 Doc_Year: 2001 Doc_Month: September Doc_Day: 01 Page: Title: Property Based Requirements Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: In SysML today requirements can be represented in a model only in a textual form. Being textually based these requirements often introduce ambiguity, are often redundant with other model element properties, and lack a formally making it difficult to leverage directly in parametric and other analysis efforts. This issue suggests an alternative means of representing requirement in the model environment without using a pure text string. The alternative means is referred to as Property Based Requirement (PBR). PBR defines a requirement mathematically and defines a set of requirement properties. The goal is declare other types of model elements as requirements and apply these properties to those model elements. A PBR theory is described in a paper called .Toward a Property Based Requirements Theory: System Requirements Structured as a Semilattice. by Patrice Micouin. This technique is further elaborated in a paper called .Requirements Management within a Full Model-Based Engineering Approach. by Yves Bern ard. Best regards, -Juergen Juergen Boldt Director, Member Services 140 Kendrick Street, Building A Suite 300 Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org