MBSE4U published a new book. It is only available in German. The introduction of new technologies as part of the digitalization of the maritime domain leads to the establishment of a large number of heterogeneous non-cooperating systems in a complex system environment. With the introduction of e-navigation, the International Maritime Organization (IMO) wants to enable interoperability between established and future systems, including the more operational processes. The Maritime Architecture Framework (MAF) for describing socio-technical maritime systems introduced in this book provides the...

There are hundreds of definitions about architecture available. Fortunately they have a lot of things in common. Personally I like the following definition: “An architecture is the set of fundamental decisions that cannot be reversed without greater effort and impact.” That definition focusses on the role of the system architect. It does not define the set of artifacts that are part of an architecture. It could be anything. This definition - as any other - is vague at the borderline. It does...

How to relate requirements and architecture on different abstraction levels The SYSMOD zigzag pattern describes the different levels of abstractions and the relationship between requirements and architecture. [caption id="attachment_135" align="aligncenter" width="584" caption="The SYSMOD-Zigzag-Pattern"][/caption] Your system requirements do not start at the very top of the levels, i.e. they already include some technical decisions. The base architecture is the architecture one level above your top level requirements. The following figure shows a simple base architecture of a forest fire detection system (FFDS). [caption id="attachment_406" align="aligncenter" width="469"...