Author: Tim Weilkiens

SysML 1.4 - View and Viewpoint - Example

What’s new in SysML 1.4 – View and Viewpoint

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…
Read more

SysML 1.4 ElementGroup

What’s new in SysML 1.4 – Grouping of Elements

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: 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…
Read more

The digital product model

The Digital Product Model – The Hechenberg theses

“It grows together what belongs together.” – Mechatronics, Systems Engineering, OSLC, ReqIF, AutomationML, feature teams, cross-functional teams, … After a strict separation of the engineering disciplines in the past, now the movement is unmistakably towards a closer integration. The market demands ever more complex systems in ever shorter time-to-market times. This is clearly demonstrated by…
Read more

Logo OMG Systems Modeling Language (OMG SysML)

What’s new in SysML 1.4 – Overview

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…
Read more

Systems Engineering with SysML/UML

New edition Systems Engineering with SysML/UML covers SysML 1.4 and more

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.…
Read more

NoSE Traveling 2014: David Long, Tim Weilkiens, Paul Schreinemakers, Jonas Andersson

NoSE 2014 – A Report from the Tour

What a great week! Summer, Fun, Great Cities and Systems Engineering. The 2nd Nordic Systems Engineering Tour from Hamburg via Copenhagen and Stockholm to Helsinki has just finished. Four tour speakers who did the whole tour and several local speaker gave great performances and shared their knowledge and experience with nearly 200 participants. And vice…
Read more

NoSE on Tour 2014 – Here we go!

The Program is online, the registration is open – we are looking forward to see you in Hamburg, Copenhagen, Stockholm or Helsinki. Register here! The 2nd Nordic Systems Engineering Tour 2014 starts May 20th in Hamburg and ends May 23rd in Helsinki. At each venue we provide a one-day conference with great speakers and time…
Read more

Collaboration Requirements Engineering / Systems Architect

A System Architecture is what System Architects create

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…
Read more

European Systems Engineering Tours

Last year we did the first Nordic Systems Engineering Tour. It was a fantastic success. We had great presentations, discussions and of course fun! Behind the scenes it was a collaboration between the German and the Swedish chapters of INCOSE and the Danish systems engineering community. See also my blog post about the tour: NoSE…
Read more

Use case with property ownedBehavior shown in a diagram

HowTo Model Use Case Activities in SysML

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),…
Read more