In the software-defined vehicle (SDV) era, where software constitutes the primary driver of functionality and value, inefficient practices like redundant code development and cumbersome requirements handoffs overhead, slow progress and inflate costs. Emphasizing code reuse and adopting innersource principles, treating internal code as open-source for shared access and collaboration can streamline workflows and foster efficiency. This article explores the current barriers to reuse and the resulting overhead, their impact on SDV development, and practical strategies to promote reuse through innersource, reducing administrative burdens while enhancing innovation and scalability. 

The Bureaucratic Overhead from Limited Code Reuse 

Traditional automotive software development often involves siloed teams recreating similar functionality due to a lack of centralized, reusable components, exacerbated by model-based approaches that favor monolithic structures over modular designs. This leads to duplicated efforts, such as implementing common utilities for data processing or interfaces multiple times, rather than drawing from shared libraries. Bureaucratic overhead arises from formal requirements communications and handoffs between teams, where specifications must be documented, reviewed, and approved before implementation, creating delays and administrative layers that stifle quick iterations. 

Without mechanisms for easy sharing, teams resort to proprietary silos, limited visibility and collaboration across projects. This is particularly acute in SDVs, where software spans diverse domains, and the absence of reuse perpetuates inefficiency, turning what could be a streamlined process into a web of redundant work and oversight. 

Consequences for SDV Efficiency and Collaboration 

The lack of code reuse and ensuing bureaucratic processes significantly hinder SDV development velocity, leading to higher costs from repeated implementations and extended timelines for feature delivery. Teams spend disproportionate time on administrative tasks like requirement negotiations and approvals, diverting resources from core innovation and reducing overall productivity. In the non-safety-critical 95% of software, covering areas like infotainment and connectivity – this inefficiency delays user-centric enhancements, while the safety-critical 5% benefits from structured reuse but often drags the broader stack into slower cycles. 

This setup fosters silos, limiting knowledge transfer and collaborative potential, which in turn slows adaptation to emerging technologies and market demands. The result is a competitive disadvantage, as organizations miss opportunities for scalable architectures and new revenue models, underscoring the need for practices that prioritize sharing to cut through administrative barriers. 

Strategies to Enhance Code Reuse Through Innersource Principles 

To address these challenges and reduce bureaucratic overhead, organizations can embrace code reuse via innersource principles, creating an internal open-source culture that promotes shared ownership and accessibility. Start by establishing centralized repositories for common components, allowing teams to contribute, review, and pull reusable code without formal handoffs – replacing lengthy requirement discussions with direct merge requests that implement features collaboratively. This approach democratizes access, enabling reuse across projects and reducing duplication while fostering collective responsibility. 

For the non-safety-critical 95% of software, innersource accelerates velocity by encouraging modular designs and open collaboration, where code becomes a shared asset rather than a team-specific artifact. Integrate governance through code reviews and standards to maintain quality without adding bureaucracy, leveraging tools for automated checks and dependency management to ensure seamless integration. In safety-critical domains, apply innersource selectively with compliance wrappers to balance reuse with regulatory needs. 

Cultural and organizational shifts are key: provide training on innersource workflows and incentivize contributions to build a collaborative mindset, breaking down silos and minimizing administrative layers. Pilot programs in non-critical areas can showcase reduced overhead, such as faster feature implementation through direct pulls and provide metrics to justify broader adoption. 

For customized guidance on implementing code reuse and innersource principles to streamline your SDV initiatives, contact us. 

Author: Hendrik Jilderda (hjilderda@knowmadmood.de)