When Complexity Tips: Tim Weilkiens on the Digital Storm in Engineering
Tim Weilkiens describes the situation in engineering, with the explosion of complexity and other areas, as a perfect storm.
Review 2025 and trends for 2026: Who dares to look into the crystal ball?
This 2025 review looks at SysMl v2 and automotive, as well as trends for 2026 such as AI, investments and product velocity.
SysML v2: A four-page overview for practitioners
This 4-page overview of SysML v2 shows the metamodel, methodology, structure and behavior. Also available as a free PDF download.
Keeping an overview: The inheritance hierarchy of SysML v2
Inheritance hierarchy SysML v2 has many surprises in store, understanding it and its relationship to KerML helps with modeling.
When is SysML correct and when is it not?
An exchange of blows between Juozas Vaicenavičius and Andrius Armonas falls short; the question of correct SysML v2 is far more complex.
Starforge: How AI and SysML v2 accelerate engineering
Starforge is a new software that enables the integration of development models for Industrial DevOps.
- Interview | Menschen | Open Source | SE-Trends | Werkzeuge
The Model as Code Paradigm: An Interview with Juozas Vaicenavicius of Sensmetry
In this interview, Juozas Vaicenavičius (Sensmetry) explains how SysIDE implements the "Model as Code" paradigm, and why MBSE needs openness.
The best SysML v2 Cheat Sheets!
Cheat sheets help you to be more productive at work. When learning a new notation such as SysML v2, here are a few good ones.
Interface modeling with SysML v2 (in SysIDE)
SysML v2 is ideal for interface modeling. However, choosing the right model elements is not easy.
Interview with Prof. Bernhard Rumpe: Industrialization with modelling
In this interview, Prof. Bernhard Rumpe talks about the acute industrial crisis and how MBSE can help us overcome it.
SeaLion case study: Satellite development with Docs-as-Code
The SeaLion project developed a CubeSat with docs-as-code: Artifacts are stored in gitHub in YAML notation.
SysML v2: Text notation as a bridge to requirements?
There is a lot of friction in the traceability between requirements and MBSE models. The text notation of SysML v2 could help.
