The Systems Analysis Workgroup is formed under the SysML Assessment and Roadmap Working Group to research and gather requirements for seamless and integrated analyses of complex systems across their lifecycle. This workgroup focuses on the system analysis challenge stated in INCOSE Insight article (Vol 18, Issue 2, Aug 2015) Evolving SysML and the System Modeling Environment to Support MBSE that states:

The next-generation modeling language must include precise semantics that avoid ambiguity and enable a concise representation of the concepts. SysML currently leverages the UML metamodel for much of its semantic foundations. The language must derive from a well-specifed logical formalism that can leverage the model for a broad range of analysis and model checking. This includes the ability to validate that the model is logically consistent, and the ability to answer questions such as the impact of a requirement or design change, or assess how a failure could propagate through a system. The language and tools must also integrate with a diverse range of equation solvers and execution environments that enable the capture of quantitative data.

The System Analysis Workgroup is pursuing the following goals for SysML 2.0:

• Analysis must be seamless integrated with system development and operation
• Support various types of system analyses and execution tools
• Manage analysis models and relate results to decisions
• Improved user interaction to define/generate, execute, archive analysis models (analysis lifecycle)

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

• Open-source OSLC and Linked Data solutions available at GitHub ld4mbse

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

• 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, resd, 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

1. System Analysis presentation at Reston (Mar 2016)
2. System Analysis presentation at La Jolla (Dec 2015)

Last updated Apr 19, 2016