What you need to know about SYSMOD

The reason for this article is the publication of the new book on SYSMOD by Tim Weilkiens, who also made a significant contribution to the SysML standard. The book can be buy now (I don't earn anything from it).

What is SYSMOD anyway? SYSMOD sees itself as a "toolbox for pragmatic, model-based system development. It can be implemented with SysML, but does not have to be." Specifically, it consists of methods, roles, results, etc.

SYSMOD is a toolbox for pragmatic, model-based system development (MBSE).

SYSMOD is not new. It has already been described in the book "Systems Engineering with SysML/UML" (also by Tim Weilkiens), where it is presented using a specific example. There have also been corresponding extensions for tools (Enterprise Architect and No Magic) for years. The new book is intended more as a reference. However, it also contains a complete example.

The following topics are covered: requirements management, system context, use cases and architectures. It contains guidelines for the different aspects of modeling, a complete example and a complete SysML profile.

Who is SYSMOD for? I see two target groups:

Teams starting a new MBSE project. If there are no methodological guidelines, it is certainly wise to use existing approaches as a guide. However, this should not be limited to this approach. Another lightweight approach is, for example, ICONIX.

Teams that are reorienting themselves towards MBSE. If you are already working traditionally, you can take many good ideas from SYSMOD on how a more model-based development can look.

For teams that are already successfully practicing MBSE, you could certainly take a look at the bigger picture.