NextGenSysML Part 12 – Example Model, Model Libraries, and Conformance Requirements
This blog post presents the requirements for the example model of the SysML v2 specification, for model libraries, and for test suites to check that a SysML v2 tool conforms to the specification. It is part of a blog post series about the upcoming new SysML v2 and SysML API & Services standard. The blog posts present the requirements for the standard stated in the request for proposals (RFP) published by the OMG. See the end of this post for a list of all posts of this series, including a link to the first post of the series that provides an overall introduction.
The SysML v1(!) specification provides an example model of a Hybrid Sport Utility Vehicle (HSUV) to demonstrate the application of the SysML language. It is only an example and a non-normative part of the language. SysML v2 also provides an example to facilitate the understanding of how to use the language features.
You need model libraries for an effective application of a system modeling environment to enable the reuse of generic elements. Imagine a software engineering world without libraries, and you know how important they are. Unfortunately, by now model libraries are not very common in the SysML modeling world yet.
The SysML v2 RFP specifies a non-mandatory requirement asking for model libraries with generic elements in the following domain areas:
- Primitive Value Types
- Units and Quantity Kinds
- Natural environments
- Verification methods
- Basic geometric shapes
- Basic material kinds
- Viewpoint methods
- View definitions
- Domain-specific symbols
Although this RFP requirement is optional, it will be very likely implemented by the SysML v2 submission team, and, if adopted by the OMG, it is a mandatory part of SysML v2.
SysML v2 provides test cases to verify that a SysML v2 modeling tool conforms to the standard. It is possible that a modeling tool implements only parts of SysML v2. The standard defines conformance levels covering specific parts of the language. The test cases are grouped accordingly to verify that a tool conforms to a conformance level of the standard. The test cases assess the conformance of tools with the metamodel specification as well as the profile specification, and the model interchange capabilities. A traceability matrix depicts how each language feature is verified by the conformance test suites.
The next blog post covers the requirements of the SysML v2 API & Services. Stay tuned!
Previous blog posts of this series:
- NextGenSysML Part 0 – Next Generation Modeling: SysML v2 and SysML API & Services – Introduction
- NextGenSysML Part 1 – Overview SysML v2 and SysML API & Services RFP’s
- NextGenSysML Part 2 – The General OMG Requirements
- NextGenSysML Part 3 – Language Architecture and Formalism Requirements
- NextGenSysML Part 4 – Cross-cutting Requirements
- NextGenSysML Part 5 – Properties, Values & Expressions Requirements
- NextGenSysML Part 6 – Structure Requirements
- NextGenSysML Part 7 – Interface Requirements
- NextGenSysML Part 8 – Behavior Requirements
- NextGenSysML Part 9 – Requirements Requirements
- NextGenSysML Part 10 – Verification Requirements
- NextGenSysML Part 11 – Analysis Requirements
Planned future blogs posts:
- NextGenSysML Part 13 – SysML API & Services Overview
- NextGenSysML Part 14 – SysML API & Services: Architecture and Conformance Requirements
- NextGenSysML Part 15 – SysML API & Services: Service Requirements