We build bridges through a common language

We need to break down our silos to survive in the world of software-defined vehicles

We need bridges with a common language

We need bridges with a common language.

Siggi and Harry are both passionate engineers, but they speak a different language

Harry and Siggi are both passionate engineers - but they have a different mindset, even when it comes to operations. They simply speak a different language.

Für Siggi ist ein Package ein bestimmter Bauraum, der für die Kompnente zur Verfügung steht

Example: a package

For Harry, a package is a collection of parts that have to fit into a specific installation space of the vehicle.

For Siggi, a package is a bundling of SW artefacts

For Siggi, the term package has a completely different meaning: for him, a package is a container that contains a specific software release and can contain several variants for the same software component.

The solution: create a new, generic language world: Systems Engineering

The solution is quite simple: both terms are correct in their context. They are both a derivation of the generic term ‘system artefact’. Both the hardware package and the software package are needed to build a vehicle completely and correctly.

We need a common language!

In order to bring the two poles together, it is necessary to use a common language. And we call this Systems Engineering (SE). SE has the right mindset, but we need a scalable approach.

We need a common language. You can find out how we can achieve this in the following blog posts.

What experiences and examples do you have of SW and HW people not getting along?

Do you agree that you first have to agree on a common language in order to be able to work together effectively and efficiently?

Please leave a comment or send me a message. Stay tuned for more to come soon!

And don't forget: keep on rocking in a free world!