A post by guest author Axel Scheithauer: SysML is based on the UML, and I think that was a good choice. However, some concepts of the UML don’t make sense in the world of systems and then sometimes lead to not so useful ideas, like typed binding connectors (how many user defined types of equality are there?). One of these concepts is the possibility to conjugate ports. You probably know that ports are interaction points of blocks, used to connect them in...

The third and last part of the blog post series about the changes of SysML 1.5 covers several minor updates. Reception compartment Now SysML explicitly defines a block compartment for signal receptions. It is the same notation as in UML. The following figure depicts an example of the reception compartment. [caption id="attachment_1298" align="aligncenter" width="125"] Signal reception compartment of a block in SysML 1.5[/caption]   Requirement compartments The SysML specification mentions that requirement relationships could also be depicted in compartments. But the notation was not explicitly defined,...

This post is the second part of the blog post series about the changes of SysML 1.5. The biggest novelty in SysML 1.5 is only visible on the second view. If you do not use the new feature, you will not recognize it. Since version 1.0 SysML provides the model element Requirement to model text-based requirements, it has only two properties: one to specify the ID of the requirement and another one for the requirement text. SysML intends that modelers can define additional...

This blog post series presents the changes of the SysML version 1.5 that are relevant for modelers. I skip those changes that only affect the specification document like typos or rewordings. You may also be interested in the blog post series about the changes of the SysML version 1.4. The first part of this blog post series gives a brief overview of SysML 1.5. The second part covers the main change that affects the modeling of requirements, and the last part...

Five years ago, Erik Herzog and I had the idea for a special conference tour in northern Europe. The Nordic Systems Engineering Tour was and is still a great success. Organized by the local chapters of INCOSE in Finland, Sweden, Denmark, Germany, and Poland it is an event from and for the systems engineering community to share knowledge and to make long lasting contacts with other system engineers. The important dates - Mark your calendars: The Call for Presenters ends at Feb...

The second edition of my book SYSMOD – Systems Modeling Toolbox – Pragmatic MBSE with SysML was published by MBSE4U. It is based on the SYSMOD version 4.1 and SysML 1.4. What's new? Updated the variant stereotypes based on my new book Variant Modeling with SysML (published by MBSE4U, 2016). The variant stereotypes are part of the SYSMOD profile. Added the integration of functional architectures. The modeling of functional architectures is described by the FAS method that is not part of...

Last week I was a panelist together with Bruce P. Douglass and Stefan Hänggi at the SWISSED conference in Zurich. The topic of the panel was “How does implementing Systems Engineering enhance an organization’s competitiveness?”. We had a very good discussion and since I was one of the panelists and not the minute taker I cannot repeat the discussion here. But my preparation notes of the panel are a good source for a blog post and I have turned my bullet...

NoSE 2016 successfully finished in Warsaw today. The 4th Nordic Systems Engineering Tour was again a great event. The tour speakers started in Helsinki at Monday, headed then to Stockholm at Tuesday, Copenhagen Wednesday (in collaboration with the Systems Engineering Spring School), Hamburg at Thursday and finally Warsaw. Each location was enriched by talks of local speakers. I had the pleasure to be a local speaker at two locations: Hamburg and Warsaw. If you were not at any of the events, you...

The figure shows the Gap of Slackness. The vertical axis represents the typical challenges for product vendors. They are for example more innovation, less time-to-market, less cost, and perfect quality. You can certainly mention more of them for your domain. The system curve along the time always increases and reflects the steadily increasing demand for improvements. The globalization and accompanying worldwide dynamics change the linear slope of the curve to an exponential slope. More competitors with different backgrounds make the markets...