Well, actually it is summertime. However the weather reminds me more of autumn. At least here in Sweden. In any case it is a good time to plan and book your next training. One of my favourite projects the Nordic MBSE School provides a comprehensive MBSE program. Four course modules for you to combine to a 2, 4, 6 or 8 days training. Each course module is two days long and is conducted in central Stockholm. I will do the modules...

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 Nordic MBSE School is one of my favourite projects. The Nordic MBSE School is organized by the Nordic Systems Engineering Alliance - a network of small and medium-sized organisations with unique competencies in product creation and technical leadership. One of these organisations is my company oose. Model-based Systems Engineering (MBSE), has for the last decade gradually changed the practice of development and procurement of complex technical systems. Wisely used, MBSE contains a significant potential for improving the quality and efficiency...

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...

End of this week is the deadline for the Call for Presenters for the 3rd Nordic Systems Engineering Tour. Share your knowledge and join the tour. The NoSE Tour is a non-commercial community event organized by four local chapters of INCOSE. It is a 1-day conference traveling from Hamburg to Copenhagen via Stockholm to Helsinki. Find more information about the tour on the official website: www.nordic-systems-engineering-tour.com. Reports from the last tours NoSE 2013 and NoSE 2014. See you, Tim ...

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...