Systems Engineering Interoperability Workgroup

The Systems Engineering Interoperability project originated as part of the SysML Roadmap effort within the OMG Systems Engineering Domain Special Interest Group (SE DSIG). The near term goal is to identify requirements related to interoperability such that SysML can support standards for data interoperability, traceability, analytics in a multi-disciplinary engineering context.

• The next-generation modeling language and tools must support MBSE in the broader context of Model-Based Engineering (MBE), where the models and tools are fully integrated across discipline-specific engineering tools, including hardware and software design, analysis and simulation, and verification. All these model-based tools working together establish an environment for engineering the total system.
• The next-generation modeling language must provide a standard application programming interface (API) to provide dynamic access to the model, while providing appropriate access controls.
• It should also integrate with emerging platforms for managing and integrating model-based content, such as Open Services for Lifecycle Collaboration (OSLC), which is based on linked data and semantic web technology, and the Functional Mockup Interface (FMI), which provides model exchange and co-simulation capability for executable behavior models.
• Model transformation is another core capability of the SME, by providing the ability to translate from one modeling language to another.

1. Elaborating a SysML Block with a behavioural model described in a different language (e.g. Modelica) and keeping the interfaces in synch
2. Rendering a SysML diagram on a lightweight / web based tool
3. Reading SysML models by analysis tools, for example, making sure the model conforms to some pre-defined rules
4. Linking SysML elements with external elements such as requirements or test cases
5. Model transformation rules (UPDM→SysML, SysML→UML)

and more…

• No cross-disciplinary traceability
• Different (proprietary) data formats
• Need to capture multi-disciplinary engineering data and relationships in a common data format
• No standard API to access SysML data
• No standard Web API to access SysML data
• No standard Query API to perform complex queries on SysML data

SysML data is currently not available:

• in a standardized graph-based data format
• through a standard API
• through a standard Web API
• through a standard Query API to perform complex queries

System Modeling Environment (SME) should support:

• a data format suitable for describing graphs
• a non-proprietary data format
• a widely adopted data format
• Standard Web API to access SysML data
• Standard Web API supporting complex queries

• Adoption of data format and data access standards aligned with W3C standards
• Adoption of data format and data access standards aligned with the larger web community
• Merging/Linking different systems engineering standards (STEP/OMG/ISO/OSLC) through Linked Data

• Data of the System Modeling Environment (SME) should be available in the W3C standard Resource Description Framework (RDF)
• Metadata (semantics) in the System Modeling Environment (SME) should be defined in RDF vocabularies (W3C standard RDF Schema) and shape constraints (W3C standard SHACL)
• Web API of the System Modeling Environment (SME) should be RESTful and conform to the W3C standard Linked Data Platform
• Query API of the System Modeling Environment (SME) should conform to the W3C standards SPARQL and SPARQL Protocol

• SysML v2 Model Interoperability Requirements - Axel Reichwein - Dec 10 2015
• SysML v2 Model Interoperability Requirements - Charles Galey- June 24 2016
• SysML v2 API Requirements-draft-2016-12-22

• SysML 2 API Basics and Protoype Demo at SysML 2 RFP WG mtg at OMG Technical Meeting, Reston (Mar 20-24, 2017)
• Open-source OSLC and Linked Data solutions available at GitHub ld4mbse

Most services listed in the spreadsheet are useful for supporting data traceability/interoperability.

More information on the services listed below can be found here.

• Services to create, read, update, and delete links between tools
• Services to create, read, update, delete, and execute transformations to/from SysML models
• Services to export and import unstructured and structured data
• Services to create, update, delete, and execute model elements and patterns
• Services to create, read, update, and delete viewpoints
• Services to create, read, update, delete, and execute model queries to support visualization and analysis
• Services to generate and manage views
• Services to create, read, update, delete, and execute model validation rules to validate input data and model
• Services to create, read, update, delete, and execute analytical models
• Services to manage model metadata
• Services to manage changes to model
• Services to create, read, update, delete, and execute workflows and notifications

Link to Test Service Description 1

• Address requirements related to FMI and model transformation
• Present traceability/interoperability requirements in the context of change management scenarios
• Illustration of how their concepts supports the Hybrid SuV scenario
• Address Security aspects (e.g. HTTPS)
• Create example Web API documentation (list of services) whereby each service has an individual URL for referencing

Last updated August 27, 2016