From April 15th to April 17th I did the first Nordic Systems Engineering Tour. I’ve initiated the tour together with Erik Herzog from Saab in Sweden. NoSE is a 1-day conference event in Hamburg, Copenhagen, and Stockholm in 3 days. The purpose of the events is to promote Systems Engineering and also to strengthen the links between the German and the Swedish chapters of INCOSE and to support the Danish systems engineering community. It was great fun and very experiencing....

Could you easily answer this question? Is a document a model? Why not? Most references define a model or properties of a model like this A model is a representation of something. It captures not all attributes of the represented thing, but rather only those seeming relevant. The model is created for a certain purpose and stakeholders. That definition includes text documents. They are also a representation of something and do not capture all attributes of the real thing. However I don’t feel...

Did you know that you use patterns every day? It’s a very powerful mechanism and much more powerful when they are explicit and known. A pattern describes a proven solution for a problem. Every experienced engineer has a huge set of patterns. Think about your daily work. If you must solve a problem that you’ve solved successfully before, you will remind your solution and apply it again. If you describe your solution in a general and reusable way, you’ve made your...

I proudly present the Nordic Systems Engineering Tour - a one-day conference event at three different locations in three days. From Hamburg via Copenhagen to Stockholm. Together with Erik Herzog I had the idea to boost systems engineering in northern Germany, Denmark, and Sweden. Why these countries? The answer is easy: Erik lives in Sweden and I in the north of Germany. Denmark is located in between. Of course that's not the only reason. The purpose of the events is also to...

The previous posts Death of the Actor and Death of the Use Case reported about two serious killings in the modeling scene. Many eyewitnesses commented the report. Now it is time for a short review. First the good news: The concepts Actor and Use Case survived the massacre. I’ve seen them still alive and very active in many projects. Sadly the SysML/UML model element Actor is dead – rest in peace – and the modeling element UseCase is in intensive care. The concept Actor...

Although UML is a modeling language for software, it is sometimes also used in systems engineering projects. Since SysML is a kind of a profile you can define your own SysML stereotypes to use a UML modeling tool for SysML modeling. Please click here: http://list.ly/list/2io-popular-uml-modeling-tools  ...

After killing the Actor in The Death of the Actor my next victim is the use case. Don't use Use cases in SysML (or UML) models anymore! My statement seems to be revolutionary or stupid (or both). Just to be not misunderstood, I'm not against the concept of use cases and actors. I believe that the SysML model elements Actor and UseCase are not necessary and useful. I've already explained it for the Actor in my previous post The Death of the...

Please click here: http://list.ly/list/23A-popular-sysml-modeling-tools Unfortunately I have technical problems with the list.ly Wordpress plugin and can't show the list embedded in this blog post....

Many companies deal with the challenge to introduce MBSE. As a consultant for MBSE I often ask my customer about their objectives to apply MBSE techniques. The answers are more or less the same: the systems are getting more complex and at the same time we must decrease costs and time-to-market and increase the quality. These are good arguments to change development processes and to apply MBSE. However these arguments are not new. I would had heard the same arguments 20...

It is very well unknown and I know only a single modeling tool that explicitly supports it: the SysML activity tree. Although it is very useful and supports common systems engineering practice. What am I talking about? You may know use cases and activities to describe the use case flows. Simply spoken they describe the functions of the system from the user perspective. The following figure shows a use case and the activity of a forest fire detection system (FFDS), The...