This is not yet a real learning unit, but only a short guide to the club. If you have already discovered and seen it on the club page, you can simply skip it.

In the SysML v2 Learning Community, we regularly post short exercises and discuss them. In this section, you'll find a list of the exercises. If your membership level grants you access to the community, you can view the discussions there or ask additional questions. If you've just started this course, you should skip the exercises for now and start with the basics.

Learn the origins of SysML as part of its context. It is helpful to classify SysML in general and to understand the different viewpoints that people have on SysML. It also partly explains why SysML is the way it is.

We don't want to bore you with theory for too long. Therefore, we jump into the cold water and start with a simple example.

Element and Relationship are the basis for all SysML model elements. Dependency is a general concrete relationship.

The separation of definition and usages is a common principle in modeling languages. Before we dive into the details of SysML v2, it is important to know the fundamentals on which many elements are based.

In addition to definitions and usages, the concept of specializations is another fundamental concept of SysML v2.

The more we model, the more model elements we get. A little order is good.

You can use filter conditions to selectively import elements into a package.

Enumerations and attributes are fundamental structural elements used to represent values in a system model. Some of these values are associated with units. Quantities and units provide essential context—without a unit, “42” is just a number. The Behind the Scenes: Quantities and Units learning nugget explains how they work and why this knowledge is crucial if you plan to define your own quantities and units.

Looks similar - but it's not. Here you can learn the difference between binding and assignment.

Annotations are little helpers that make a model easier to understand.

The essential foundations have been laid, let's get started with the modeling of structures.

The learning unit "Structures - Basics" presents the basics of modeling structures. The focus there is on the parts. This learning unit is about the connections between parts.

In addition to the modeling of structures, modeling is another important pillar of SysML v2. This learning unit initially only provides an overview.

Actions are a broad field in SysML v2. This learning unit starts quite simply with the basics and following learning units cover step by step more action modeling elements.

Use cases are an integral part of requirements analysis and are of course also included in SysML v2.

Requirements are elementary. You can learn how to model textual requirements here.

SysML v2 can do more than just textual requirements. Learn how to formalize your requirements here.

Here you will learn the basics of state modeling.

Flows and messages are model elements for transferring payloads between elements. This happens both between structural elements and between behavioral elements.

Views are the key elements to show the model content to stakeholders.

SysML is a general-purpose language. This makes it very general. Language extensions can be used to adapt it to specific domains.

Short stopover before we continue modeling SysML v2. What will actually become of the SysML v1 models?

This chapter contains special learning units with Cameo Systems Modeler.

This chapter contains special learning units with SysIDE.

This chapter contains special learning units with SysON.

This chapter walks you step by step through the ZigZag pattern of the SYSMOD approach.

This session contains learning units about developing a lightweight Python Flask server for engineering apps accessing the SysML v2 API.