Vibe Engineering – Freeing System Engineers from Their Chains
In many automotive development projects, particularly those involving systems such as an ADAS Level 2+ Highway Assistant, a significant portion of the underlying architecture, sensor setups, and functional approaches — whether algorithmic, hybrid, or end-to-end AI-based — draws on knowledge that is largely publicly available.
Nevertheless, established processes often require substantial effort to create detailed specification documents and perform comprehensive top-down decomposition. This creates a recurring tension between the need for strict ASPICE and functional safety compliance on one hand, and the desire for innovation and competitive time-to-market on the other.
Vibe Engineering offers a structured way to ease this tension. As an integrated approach encompassing Vibe System Engineering, Vibe Coding, and Vibe Testing, it supports the entire V-Model through AI-assisted, traceability-driven methods. The result is a noticeable reduction in the effort required for specifications and documentation, while maintaining — or even strengthening — compliance and traceability.
The Tension in Traditional System Engineering
Many organizations with budget and P&L responsibility are familiar with the challenges of the current situation. At a time when much foundational system knowledge is accessible externally, teams still invest considerable time in creating and maintaining extensive internal documentation. This is done with good reason: ASPICE-conform processes, clear traceability, and robust safety cases are essential for series development and regulatory acceptance.
At the same time, this thoroughness comes at a cost. Turnaround times for change requests frequently extend over days or weeks. Budgets are tied up in repetitive tasks, and the ability to explore and compare architectural variants remains limited.
Vibe Engineering: A Pragmatic Further Development
Vibe Engineering builds on established standards rather than replacing them. It combines the strengths of model-based and AI-supported methods with rigorous traceability, enabling more efficient work across the full V-Model.
Key principles include:
- Vertical Traceability: A clear, unbroken chain from top-level solution definition through features and capabilities down to requirements, code, and test cases.
- Solution Architectural Traceability: The linking of elements within the product itself (capabilities, interfaces, data flows, and system topology, including online services). It aligns with the System Architectural Design phase in ASPICE.
- Horizontal Traceability: Clear, bidirectional links connecting the left side of the V (requirements and design) with the right side (implementation, integration, testing, and verification).
Faster Turnaround Times as a Practical Advantage
One of the most tangible improvements is the dramatic reduction in turnaround time for changes. In traditional setups, even moderately complex modifications — such as updates to communication signals — often require several days to weeks. With Vibe Engineering, it becomes realistic to complete the left side of the V within a single day and the right side overnight.
Architectural Variants as a Strategic Opportunity
The reduced effort in system engineering opens new possibilities for portfolio management. Different system architectures can be modeled and compared as variants of an overarching system. Thanks to strong Solution Architectural Traceability, these variants remain consistent and comparable.
Estimated Savings Potential of Vibe Engineering
The following overview compares Vibe Engineering with the classical, specification-intensive ASPICE process:
| Scenario | Focus | Effort Savings | Innovation Capability |
|---|---|---|---|
| Budget Development | Strong cost focus, maximum reuse of public knowledge | 45–65 % | Medium |
| Innovations Engineering | High innovation focus while considering legacy elements | 25–45 % | Very high |
| Balanced | Balanced approach between innovation and costs | 35–55 % | High |
Practical Implementation and Anchoring
Vibe Engineering integrates well with existing ASPICE processes. It does not require a complete methodological shift but rather a targeted enhancement through better traceability and tool-supported efficiency.
The Automotive Guardrail Development Manifest provides a valuable overarching framework. It emphasizes claim-based elements, solution-oriented traceability, reuse, and incremental integration — principles that align closely with Vibe Engineering.
Consider, for example, how an agent can reason when it has access to both the SDV Protocols & E/E Architecture Overview and the Automotive OS Comparison. The process unfolds as a series of targeted questions and answers:
- The agent first identifies the communication protocols natively supported by a specific operating system.
- It then cross-checks which hardware platforms are compatible with that operating system and its protocol stack.
- Next, it determines which additional protocols would require external middleware or hardware acceleration.
- Finally, it evaluates the implications for system architecture.
Through this iterative back-and-forth, the agent builds a coherent picture of feasible configurations. The outcome can then be translated into precise, traceable entries in the requirements database.
Do we still need formal requirements — or at least a human-readable system twin?
Answer: Yes. Even when an AI can read millions of lines of ADAS code quickly, you still need formal requirements or a clear human-readable system twin.
Code alone shows what currently exists. It does not reliably show what the system is supposed to do, what is safe, or what the original intent was. In a system of this size and complexity, no one — human or AI — can fully understand all interactions, assumptions, and edge cases just by reading the implementation.
When requirements or a system twin are missing, you lose the ability to assess the impact of changes, maintain traceability for safety and compliance, verify that the code fulfills its intended purpose, and enable AI agents to reason about correctness rather than just describe current behavior.
Bottom line: For safety-critical systems like ADAS, “just read the code” is not sufficient. You need an explicit, human-readable layer above the code that captures intent, goals, and constraints.
Still debating formal requirements with AI in the loop?
Even when AI accelerates coding and code reviews, the need for clear intent, traceability, and safety argumentation doesn’t disappear. We’ve published a practical, ready-to-use discussion prompt that helps Automotive teams explore whether formal requirements — or at least a human-readable system twin — are still essential in the age of AI. Use it in your next architecture review or cross-functional workshop.
Challenges and Proven Guardrails
Introducing more efficient methods naturally raises valid questions regarding quality, safety, and organizational integration. Experience shows that strong traceability combined with the guardrails described in the Automotive Guardrail Development Manifest helps maintain — and in many cases even improve — the required level of confidence and auditability.
Outlook
In an industry where development cycles are shortening and architectural complexity is increasing, approaches that combine efficiency with compliance offer clear advantages. Vibe Engineering supports system engineers in focusing more on value-creating architectural work while providing P&L-responsible leaders with improved cost structures, faster response capabilities, and greater portfolio flexibility.
Explore How Vibe Engineering Fits Your Organization
It could be valuable to discuss in an open conversation how Vibe Engineering might align with your specific processes, projects, and strategic goals.
Get in Touch