SysML/UML Interoperability Ed Seidewitz Discussion with the SysML v2 RFP Working Group Reston, Virginia 23 March 2017

SysML1.x/UML Interoperability SysML defined as a profile of UML Technically, SysML models are UML models Non-SysML UML models can reference SysML models Non-SysML and SysML models can be managed together in UML tools Promotes, e.g., consistency between system and software models Allows clear traceability from system design to software requirements Allows software architecture to be modeled in the context of system architecture

SysML v2/UML Interoperability SysML defined with its own metamodel SysML models are not UML models. MOF-level interoperability has not proven successful (e.g., BPMN vs. UML experience). SysML profile defined to provide a UML representation Will likely not cover all the capabilities of the metamodel. Does not encourage true integration with metamodel-based tools/community (e.g., BPMN Profile experience). In a System Modeling Environment, how are the models of different disciplines related? What are the requirements for cross-referencing, traceability, semantic interoperability, etc.? How much can be subsumed into the SysML language itself?

Strawman Requirements for a “UML Interoperability Subset” of SysML Submissions shall identify a modeling subset of SysML that has equivalent semantics to a correspondingly identified subset of UML. This subset shall include at least the ability to model software architectures. The UML profile for SysML shall cover the entire identified subset. A SysML model in the identified subset, when expressed in the UML profile for SysML, shall have the same semantics as given by the UML specification to the model, considered as a UML model without the profile applied.