The Diagram Definition (DD - previously known as Diagram Interchange (DI)) is a format to exchange diagram data between tools. The data about diagrams is separated from the data about the model information. The interchange format for the model data is XMI (XML Metamodel Interchange; see XMI specification page). The following figure depicts the whole picture of the SysML Diagram Interchange architecture. As well as SysML is an extension of UML, the SysML Diagram Interchange is an extension of the UML...

The sixth part of the blogpost series about the changes in SysML 1.4 presents the updated concepts for blocks and ports. The new concept of bound references is already covered in the special blogpost What’s new in SysML 1.4 – Constraining decompositions. Behavior Compartment A SysML block can own behaviors. For instance a state machine or an interaction. A special behavior owned by the block is the so-called classifier behavior. It represents the autonomous behavior of a block and is executed when...

The fifth part of the blogpost series about the changes in SysML 1.4 presents the updated concept of units. But first a big sorry for being quiet for such a long time. But better be quiet than posting spam. I hadn’t enough time to continue my series about the news and updates of SysML 1.4 as well as other interesting things for the MBSE community. The reason for my absence was one of those interesting things: I was on the final spurt...

The fourth part of the blogpost series about the changes in SysML 1.4 presents the new concept to constrain a decomposition hierarchy. The following figure shows a simple product tree of a drone subsystem (DS) for a forest fire detection system (FFDS). It is the sample system I've also used in some previous posts. [caption id="attachment_866" align="aligncenter" width="300"] Product tree of a drone subsystem for a forest fire detection system (click to enlarge)[/caption] The structure allows different configurations of drone subsystem instances due...

The third part of the blogpost series about the changes in SysML 1.4 presents the updated concept of view and viewpoints. View and Viewpoint are model elements of SysML since the very first public version 1.0. As you may know SysML was developed based on a request for proposal with a set of requirements. One requirement was about views: [caption id="attachment_836" align="aligncenter" width="762"] SysML 1.4 - View and Viewpoint - Requirement (click to enlarge)[/caption] In SysML 1.0 the view and viewpoint concept...

The second part of the blogpost series about the changes in SysML 1.4 presents the new concept to group elements. The use case is simple: Create a group of model elements: [caption id="attachment_820" align="aligncenter" width="300"] SysML 1.4 ElementGroup Use cases (click to enlarge)[/caption] Okay, on the second thought there are some more: Update a group and Delete a group. And I’m sure that you’ll find some more use cases on the third thought. It also depends on your personal definition of a use...

We are still waiting for the official release of the SysML version 1.4. The work on the update already finished several months ago. Due to some organization obstacles the official release is delayed. In April 2014 the OMG published a beta version of the SysML 1.4 and some tool vendors already published updates of their modeling tools with SysML 1.4. You can find the SysML 1.4 beta specification on the SysML specification website. So it is time to report about the...

My publisher just released the third edition of my book "Systems Engineering with SysML/UML". To be exact it is the German version of my book "Systems Engineering mit SysML/UML". Since the second edition 6 years have passed. In this time the language SysML, my MBSE methodology SYSMOD and MBSE in general have been further developed. The media book could hardly follow the high dynamics that currently happens in our engineering environment. Extremely spoken the book is outdated when it leaves the...

Activities are commonly used to describe the behavior of use cases. In SysML these are separate model elements: the use case and the activity. The use case is a specification of behavior. Whereas the activity is the definition of the implementation of the behavior. Instead of an activity you can also use interactions (sequence diagrams), state machines or opaque behavior. However I favor the activity. Typically in a SysML model the activitiy is in the namespace of the use case. You...