Part One: First Steps

Posted: April 28, 2025

In this article

Mats Larsson

After almost 20 years at SystemWeaver, I believe it can be interesting to look back and to reflect upon how we, as well as our environment, have changed over time.

Looking back, it is easy to see that the insight from the founding fathers that the introduction of software to an automotive industry where processes and development tools were based on mechanics would be a game changer was correct but that the insight was long before its time.

First steps

After initially working from within Mecel (now a part of Aptiv), SystemWeaver was created in 2000 to address the growing software problem in automotive. However, management was not yet aware of the gravity of the problem and being first in a new market isn’t necessarily an advantage for a small company.

We were fortunate to attract interest from early adaptors at both AB Volvo and Volvo Cars and thanks to this we were able to launch the world’s first System Engineering tools for Software.

Lesson: Everyone needs sponsors to get going

White Paper: Model-Based Systems Engineering
Download this White Paper as a PDF Unmanaged Complexity is the Real Bottleneck for Innovation System complexity has exploded. The industries that build the world's most complex, safety-critical products have undergone a fundamental shift over the past decade: products have become software-defined. The challenge now is maintaining consistency and quality while hundreds [...]
White Paper: Subsystems, Meta-Models and Architecture
Download this White Paper as a PDF Executive summary The meta-model supports the architecture without defining it. Clear, cohesive subsystems with explicit interfaces are what make model-based systems engineering usable at scale. This white paper distills ten practical insights drawn directly from SystemWeaver experts and practitioners, both at SystemWeaver and customers to SystemWeaver. [...]
5 Realities of AI in Modern Cybersecurity
Every vendor in security claims AI changes everything. Ask the engineers actually building these systems and a different story comes up: a context gap. The AI returns a threat analysis that reads well and sounds confident but has little connection to the product. That is where a recent conversation with Anders Hallgren and Marcus [...]