Dealing better with changes in systems engineering

It is becoming increasingly difficult to deal with change as we are confronted with more and more change. We therefore need a new paradigm for dealing with change. I recently presented the idea of a Toolbox for dealing with changes before.
Of course, dealing with change is nothing new, and many organizations have established processes to deal with change. Therefore, the aim here is to enable systematic improvement with simple and proven patterns.
These concepts will be presented at ReConf 2019 in the lecture Development patterns for dealing with change.
A more detailed description of these concepts in English: Dealing with Change in Systems Engineering >>
Systems engineering can deal with changes
Dealing with changes has always been an integral part of systems engineering, as can be read in ISO 15288, for example. But standards only describe what needs to be done, not necessarily how. This is where the library of patterns helps: existing processes can be systematically and purposefully improved.
Organize samples
This article is not about the patterns. Instead, it is about organizing the patterns in a meaningful way. There are two dimensions to this: Results and activities:
- Improve quality - In the context of changes, we want to reduce the bugs, inconsistencies, etc. caused by changes.
- Increase efficiency - Changes require rework, which should be minimized. Automation can also increase efficiency.
- Increase transparency - The effects of changes must be analyzed beforehand and be comprehensible afterwards. Transparency enables us to make the right compromises and trade-offs.
- Reduce the impact of changes - Changes can trigger a ripple effect, whereby changes to one element cause further changes, and these in turn spread further.
- Improve collaboration - At the end of the day, systems are developed by people. Improved collaboration ensures that stakeholders understand the impact of planned changes and that the team has the option to optimize the change.
Activities
ISO 15288 describes a large number of activities, which can also be roughly categorized:
- Structuring
- Develop
- Analyze
- Document
- Change
The results and activities can be used to create a matrix, which is filled with five exemplary patterns below:

A brief description of these five patterns can be found in the article Dealing with Change in Systems Engineering to find.
In planning: A catalog of samples
What has been presented here is a framework for patterns that help with the handling of changes. How far this idea will be developed depends, among other things, on the feedback I receive on the ReConf 2019 will get.



