SysML v2 RFP Working Group Meeting Summary

New Orleans, Louisiana

September 26, 28, 2017

The following is a summary and the follow-up actionsfrom our1.5day face-to-face Working Group meeting at the OMG meeting in New Orleans, Louisianaon September 26, 28, 2017. Thismeeting summaryis postedon the New Orleans meeting pageand the OMG site (syseng/2017-09-06).

Hedley provided the web and dial up information for our next SysML v2 RFP WG telecon on Wednesday, October 11, at 11:00 AM ET, where we will review the meeting results, and discuss the plans to prepare for the next OMG meeting in Burlingame the week of December 4. At this meeting, we plan to present the SysML v2 RFP and SysML v2 API and Services RFP for vote and issuance.

At the New Orleansmeeting, we held an SE DSIG meeting on Tuesday morning, and then held the SysML v2 RFP Working Group meeting on Tuesday afternoon and all-day Thursday. We also presented the Draft RFP’s to the ADTF on Wednesday afternoon.

ACTIONS

  • Sandy and Ed to respond to OMG Architecture Board actions
  • Integrated Structure and Behavior Working Group to refine the SECM and ensure integration across the concept model
  • Sandy and John to update the SysML v2 RFP and SysML v2 API & Services RFP and post by Nov 6

The following sections are included below:

  • SysML v2 Requirements Review and RFP Status
  • SysML v2 Language Concepts
  • SysML v2 Presentation to ADTF
  • Open SysML v2 Submission Team Planning
  • SysML v2 Metamodel Approach (KerML)

Sanford Friedenthal

SysML v2 Working Group Chair

MEETING SUMMARY

TheNew Orleans meeting is the fifth dedicated SysML v2 RFP Working Group meeting at the OMG following the RFP kickoff in Orlando in June, 2016. The objectives and agenda for the Working Group meeting on September 26, 28, 2017 are included below.

Meeting Objectives

  • Review Draft SysML v2 RFP
  • Present Draft RFP’s to the ADTF
  • Discuss initial submission team planning
  • Review Proposed Approach for SysML v2 Metamodel

Meeting Agenda(CDT timezone)

Tuesday, September 26, 2017

09:00 – 12:00 SE DSIG (refer to

13:00 – 17:00 Draft SysML v2 RFP Review - Sandy Friedenthal

Wednesday, September 27, 2017

13:30 – 16:00 Draft SysML v2 RFP and SysML v2 API & Services RFP Presentation to the ADTF

Thursday, September 28, 2017

09:00 – 12:00 Initial discussion regarding Submission Team Planning - Ed Seidewitz/Sandy Friedenthal

13:00 – 17:00 Proposed SysML v2 Metamodel Approach (KerML) - Chas Galey, Conrad Bock

SysML v2 Requirements Review and RFP Status.Since the Brussels meeting the week of June 5, the SysML v2 Requirements were reviewed extensively and updated based on the feedback. The first review was an internal review by the Working Group, and the second review was distributed to approximately 25 representative organizations for their review and feedback. The updated SysML v2 Requirements Support Document is posted on the SysML v2 Requirements Review page. This document contains the requirements and additional background and context information for the requirements.

Since the last meeting in Brussels, it was decided to split the requirements into 2 separate RFP’s called the SysML v2 RFP and the SysML v2 API & Services RFP. The drafts for these 2 RFP’s were posted to the OMG site. The OMG document numbers for these documents and 2 accompanying spreadsheets are:

syseng/2017-09-01SysML v2 Requirements Support Document 2017-09-23

syseng/2017-09-02SysML v2 Requirements Spreadsheet 2017-09-23

syseng/2017-09-03SysML v2 API and Service Requirements Spreadsheet 2017-09-23

syseng/2017-09-04SysML v2 RFP Draft 2017-09-23

syseng/2017-09-05SysML v2 API and Services RFP Draft 2017-09-23

Draft SysML v2 RFP Presentation to ADTF. Sandy and Ed Seidewitz presented an overview of the draft SysML v2 RFP and the draft SysML v2 API and Services RFP to the ADTF on Wednesday, September 27. (omg document number ad/2017-09-06). This was a 2-hour presentation that provided a general overview of the RFP’s, and additional detail on the language architecture requirements which were thought to be of specific interest to the ADTF. Pete Rivett raised some questions that were brought later in the week to the Architecture Board for further discussion.

The particular concern that Pete raised was whether SysML v2 is intended to leverage existing OMG technologies such as MOF. Ed and Sandy were invited to the Architecture Board on Thursday afternoon to discuss this further. Ed provided the justification for some of the language architecture requirements, which were originally formulated by the SysML v2 Formalism Working Group. The follow-up actions were to provide the Draft RFP numbers to the AB for their further review, and to provide the driving needs that drove these requirements.

Presentation of SysML v2 Language Concepts.On Tuesday afternoon,Sandy provided an overview of the language concepts that are reflected in the requirements in the SysML v2 RFP. The concepts are part of the Systems Engineering Concept Model (SECM), and are summarized in section 6.2.2 of the SysML v2 RFP, and in section 3.1.2 of the SysML v2 Requirements Support Document.

SysML v2 Submission Team General Planning. Ed Seidewitzled the Thursday morning session to present an open proposal for a submission approach that emphasizes incremental releases to mitigate risk. This presentation is available on the New Orleans meeting page.

Proposed SysML v2 Metamodel Approach.Chas Gayley presented a proposed SysML v2 metamodel approach called KerML. Chas, Conrad Bock, Bjorn Cole, and others have been working on this approach for the last couple of years. They are in the process of evaluating how the approach can satisfy the SysML v2 RFP requirements. Chas’s presentation is available on the New Orleans meeting page.

A few key aspects of the approach include:

  • A small core metamodel is defined at the M2 level. The model libraries at the M1 level extend these concepts and specify the semantics for the domain concepts. This enables the domain concepts to be more easily extended.
  • Common patterns are used to specify behavior and structure. This helps to ensure more integration.