Presented at the MBSE Meeting, MODELS 2018 conference, Copenhagen

1. SysML v2 and MBSE: The Next Ten Years
16 October 2018
Ed Seidewitz
Chief Technology Officer
Model Driven Solutions
ed-s@modeldriven.com ● @seidewitz
MBSE Meeting at MODELS 2018, Copenhagen
Copyright © 2018 Model Driven Solutions, Inc.

2. Page 2
Systems Engineering
focuses on ensuring
the pieces work together
to achieve the
objectives of the whole
16 October 2018INCOSE SE Vision 2025

3. Page 3
Model-Based System Engineering (MBSE)
16 October 2018
A Practical Guide to SysML 3rd Edition (Figure 18.1)
puts the System Model
at the center

4. Page 4
MBSE: The Vision
from
modeling as a way to deal with the limitations of
document-based approaches
to
systems modeling as standard practice…
fully integrated with other engineering modeling
using internet-based knowledge representation
to share human understanding of systems
in a virtual environment
INCOSE SE Vision 2025
16 October 2018

5. Page 5
MBSE: Extending Maturity and Capability
16 October 2018
2010 2020 2025
Maturity
AdHocWellDefinedInstitutionalized
Distributed & secure model repositories
crossing multiple domains
Defined MBSE theory, ontology,
and formalisms
Emerging MBSE standards
Matured MBSE methods and metrics,
Integrated System/HW/SW models
Architecture model integrated
with Simulation, Analysis, and Visualization
INCOSE MBSE Roadmap (original version 2007)
2015

6. Page 6
MBSE: Adoption Challenges
2.60
2.71
2.90
2.93
2.98
3.10
3.32
3.47
3.54
3.64
3.91
1 2 3 4 5
Availability of tools
MBSE training
Tool maturity
Other
Method maturity
Risk associated with the…
Lack of management…
Lack of perceived value…
Availability of skills
MBSE learning curve
Cultural and general…
MBSE 2015
2.84
2.93
2.95
3.01
3.13
3.29
3.37
3.45
3.48
3.71
3.82
1 2 3 4 5
Availability of tools
Risk associated with the…
MBSE training
Tool maturity
Method maturity
Lack of management…
Lack of perceived value…
Availability of skills
MBSE learning curve
Other
Cultural and general…
MBSE 2012
Rank each item below in terms of the extent that it currently inhibits
successful adoption of the MBSE within your organization/company.
MBSE Survey, January 24, 2015
Dr. Robert Cloutier, Ms. Mary Bone
16 October 2018

7. Page 7
Systems Modeling Language™ (SysML®)
SysML has facilitated awareness and adoption of MBSE
Much has been learned from using SysML for MBSE
SysML has evolved to address user and vendor needs
v1.0, adopted in 2006; v1.5, current version; v1.6, in process
But…
16 October 2018
Supports the specification, analysis, design, and verification and
validation of complex systems that may include hardware, software,
information, processes, personnel, and facilities

8. Page 8
Language Design
16 October 2018
Can nested parts have
different properties?
Can system behavior be related
to subsystem structure?
Internal structure is
the same for all
instances of a type.
There is no semantic connection
between flows and connectors.
SysML language design has been limited by being a UML profile

9. Page 9
Enhancements
16 October 2018Friedenthal and Oster, Architecting Spacecraft with SysML
SysML needs some functional enhancements

10. Page 10
Visualization
16 October 2018
Source: C. Schreiber, J. Feingold, M. Sarrel
Interactive Display
Dynamic Visualization
Model Differencing
Table
Diagram
Text
part vehicle_C1: VehicleDefinitions.Vehicle {
part frontAssembly: AxleAssembly {
part frontWheel: Wheel[2];
part frontAxle: Axle;
}
part rearAssembly: AxleAssembly {
part rearWheel: Wheel[2];
part rearAxle: Axle;
}
}
Physical Envelope
SysML models need to be flexibly visualizable

11. Page 11
Interoperability
16 October 2018
Axel Reichwein , Koneksys
SysML v2 Model Interoperability & Standard API Requirements
SysML tooling must interoperate with other tools
Basic syntactic model interchange is not sufficient!

12. Page 12
APIs and Services
16 October 2018
From: SysML v2 API & Services RFP
Standard APIs and services provide a mechanism for tool interoperability.

13. Page 13
SysML v2 Requests for Proposals
SysML v2 RFP issued December, 2017
Initial Submission: November, 2019
Revised (Final) Submission: November, 2020
SysML v2 API & Services RFP issued June, 2018
Initial Submission: February, 2020
Revised (Final) Submission: February, 2021
SysML Submission Team (SST) formed December 2017
Leads: Sandy Friedenthal, Ed Seidewitz
16 October 2018

14. Page 14
SysML v2 Submission Team (SST)
A broad team of end users, vendors, academics, and
government liaisons
Currently 89 members from 56 organizations
Developing submissions to both RFPs
Driven by RFP requirements and user needs
16 October 2018

15. Page 15
Requirements /
User Needs Feedback
SysML Abstract Syntax
SST Agile Collaborative Approach
NamespaceDefinition:
PackageDefinition | ClassifierDefinition
PackageDefinition:
PackageDeclation “{“ PackagedElement* “}”
PackagedElement: NamespaceDefinition | …
ClassifierDefinition: ClassDefinition | …
ClassDefinition:
ClassDeclaration “{“ ClassMember* “}”
ClassMember: FeatureDefinition | …
FeatureDefinition: AttributeDefinition | …
AttributeDefinition:
Visibility Name “:” QualifiedName
Concrete Syntax (Textual Grammar)
Parse
Guide
UML Abstract Syntax / Profile
Services
Repository
Visualization / Analysis
Generate
Semantic Tooling / OWL
Store
16 October 2018

16. Page 16
Usage Focused Modeling
A paradigm shift to make SysML v2
more precise and intuitive to use
Emphasizes modeling of usages
Allows modeling on the internal block diagram (IBD)
Supports other language requirements
variant design and configurations, individuals,
analysis, verification,…
16 October 2018

17. Page 17
Usage Focused Modeling
Multiple Views of the System
16 October 2018
Graphical notation for illustrative purposes only

18. Page 18
Vehicle: Internal Block Diagram (SysML v1)
16 October 2018
Internal structure is
the same for all
instances of a type.

19. Page 19
Vehicle: Internal Block Diagram (SysML v2)
16 October 2018
Connector to
nested port
Usage-specific
property values

20. Page 20
Vehicle: Textual Notation Parsing
vehicle_c1:Vehicle{
partengine:Engine{
portoutdrivePwrPort;
}
parttransmission:Transmission{
portinclutchPort;
portoutdriveShaftPort;
}
partrearAxleAssembly:AxleAssembly{
partredefinesaxle{
portindriveAxlePort;
}
partredefineswheel{
partredefineslugbolt[6]{
torque=20;
}
}
}
partfrontAxleAssembly:AxleAssembly{
partredefineswheel{
partredefineslugbolt[4]{
torque=10;
}
}
}
connectorenginePoweris
engine::drivePwrPortto
transmission::clutchPort;
connectordriveshaftis
transmission::driveShaftPortto
rearAxleAssembly::axle::driveAxlePort;
} 16 October 2018

21. Page 21
Conclusion
Over the last decade…
SysML v1 has facilitated awareness and adoption of MBSE
Over the next decade…
SysML v2 will increased adoption and effectiveness of MBSE
by enhancing…
Precision and expressiveness of the language
Consistency and integration among language concepts
Interoperability with other engineering models and tools
Usability by model developers and consumers
16 October 2018