Skip to content
Open access

A Framework for Cross-Domain Integration and Validation in Software-Defined Vehicle Systems

Aug 2026 · International Journal of Engineering Science and Information Technology · Vol 6 · 0 citations

TL;DR

A structured framework for cross-domain integration and system-level validation in SDV environments that unifies four foundational engineering capabilities: explicit modeling of inter-domain dependencies, standardized signal interface definitions aligned with AUTOSAR Adaptive specifications, cross-domain temporal synchronization mechanisms, and coordinated scenario-based validation orchestration.

Abstract

The transition from isolated domain-specific electronic control unit (ECU) architectures to fully integrated software-defined vehicle (SDV) platforms has introduced a new class of engineering challenge: cross-domain integration complexity. As vehicle software increasingly emerges from the dynamic interaction of subsystems spanning body control, powertrain coordination, thermal management, active safety, and connectivity, validation strategies designed for component-level verification are fundamentally insufficient. Integration defects   arising from timing misalignment, inconsistent signal interpretation, and conflicting control arbitration across domains surface late in development when remediation costs are highest. This paper presents a structured framework for cross-domain integration and system-level validation in SDV environments. The framework unifies four foundational engineering capabilities: explicit modeling of inter-domain dependencies, standardized signal interface definitions aligned with AUTOSAR Adaptive specifications, cross-domain temporal synchronization mechanisms, and coordinated scenario-based validation orchestration. Empirical evaluation against component-only validation baselines, using a reference defect set of confirmed cross-domain integration defects drawn from multi-domain automotive program integration records, demonstrates that the framework increases cross-domain defect detection rate by 64%, reduces integration cycle time by 58%, and expands cross-domain validation coverage from 43% to 91%. By elevating cross-domain interactions from emergent side effects to first-class engineering artifacts, the framework materially advances the state of practice in SDV system integration and validation

Read PDF

Similar papers

Book Open access Jul 2026

Dependency-Aware Over-the-Air Framework for Reliable Software-Defined Vehicle Updates

A dependency-aware OTA orchestration framework that addresses challenges in improving update success rates, efficiency in execution time and update requests through optimized scheduling, and feasibility in maintaining system-wide integrity by successfully reconciling stringent safety requirements and diverse update sensitivity constraints is proposed.

Juyeon Park, In-Young Ko · 0 citations
Open access Jul 2026

Towards a Unified Engineering Approach for Variability and Modular Architecture Management in Automotive Systems

An integrated methodology that combines variability modeling principles from SPLE with architectural modularization concepts is proposed, which bridges variability management and modular architecture design to address increasing system complexity in the automotive industry.

Fabian Goihl, Yannick Lindebauer, Richard von Esebeck et al. · 0 citations
Preprint Aug 2026

From Architecture to Binary: Ensuring Cross-Domain Consistency in Model-Based Airborne Software Development

This paper presents an airborne software development approach for manned and unmanned aerial vehicles aimed at reducing inconsistencies across system, model-based functional, and embedded software domains. In environments influenced by standards such as ARP-4754B and DO-178C, these inconsistencies typically stem from insufficient enforcement across domain boundaries rather than missing process definitions. Building on a previously proposed toolchain centered on a relational interface database, we identify recurring failure modes and propose a repository-centered implementation to address them, tailored to small, resource-constrained teams operating without heavyweight process overhead. Each domain is assigned a primary repository with cross-repository references and dedicated CI pipelines that generate, update, and validate the exchanged artifacts. Automated interface updates, differential change notifications, and consistency checks propagate changes with minimal manual effort and surface inconsistencies before the time-consuming code-generation and compilation steps. An initial implementation in an ongoing experimental project is described, with qualitative feedback from its early use.

Nils Schlautmann, V. Sinitsyn, Benjamin Engelhard et al. · 0 citations
Review Open access Jul 2026

Bridging the Embedded Execution Gap: A Review of the Functional Mock-up Interface for Actuator-Centric Execution Workflows in Industrial Embedded Systems

Industrial actuators integrate multi-domain physical dynamics with embedded control algorithms under strict timing constraints. Despite mature model-based design workflows, a persistent embedded execution gap separates validated high-fidelity simulation models from deterministic, resource-bounded execution on embedded industrial platforms. This review examines the Functional Mock-up Interface (FMI) as an interoperability enabler for actuator development workflows and argues that interoperability at the model-exchange level does not automatically translate into interoperability at the execution level. The review analyzes the evolution of FMI from version 2.0 to 3.0, systematizes actuator-relevant fidelity requirements (nonlinearities, compliance/resonance, timing effects), and evaluates representative approaches for integrating FMI into industrial and robotic toolchains. Two deployment trajectories are synthesized: (i) runtime-constrained FMU execution on edge/MCU-class platforms for prototyping, monitoring, and non-safety-critical functions; and (ii) analyzable code-generation paths such as Embedded FMI (eFMI) and GALEC, which target bounded memory and timing transparency for certification-oriented workflows. Although FMI 3.0 introduces improved timing semantics through clocks and Scheduled Execution, end-to-end feasibility remains limited by toolchain maturity, scheduler integration patterns, and the scarcity of complete quantitative evidence on jitter, WCET, and memory footprint under realistic load. The review identifies key challenges in determinism, fidelity management, certification alignment, and ecosystem-level conformance/validation, clarifying the technical barriers that must be addressed to fully bridge the gap between high-fidelity simulation and embedded actuator deployment.

Sebastian Rojas-Ordoñez, Mikel Segura, Irune Yarza et al. · 0 citations
Preprint Aug 2026

JTA: Joint Testability Architecture for Scenario-Based Validation of Safety-Critical Software

Validation adequacy in safety-critical software depends on more than the system under test. Critical scenarios must be constructed under controlled conditions, execution evidence must be aligned into verdict-ready form, and abnormal outcomes must be attributable to actionable causes. Existing testability research remains largely artifact-centric and offers little architectural support for reasoning about the combined capability of the scenario, the test system, and the system under test. Joint Testability Architecture (JTA) addresses this gap by treating those three elements as a single object of analysis and design. It characterizes validation capability along three dimensions--controllability, observability, and isolability--and organizes them through three domains, three bridges, and an analysis-design-evaluation-refinement loop. JTA also introduces scenario contracts, joint capability assessment, validation blind-spot identification, and bridge-oriented design actions that map capability gaps to concrete improvements in control points, evidence organization, and attribution boundaries. An illustrative analysis of ArduPilot failsafe validation shows that link-loss scenarios are comparatively mature, whereas state-estimation anomaly scenarios remain harder to validate because evidence alignment and attribution semantics are weaker. JTA is not a replacement for existing testing or safety-analysis techniques; it provides an architectural basis for modeling, designing, and assessing scenario-based validation in safety-critical software.

Wenyao Xue, Jiandi Wang, Yichen Wang · 0 citations
Open access Aug 2026

Architecture-Driven Hardware-in-the-Loop Verification: A Bidirectional MBSE Framework Demonstrated on a Low-Cost UAV

Integrating Model-Based Systems Engineering (MBSE) with Digital Twins (DTs) offers a promising way to transform static system models into dynamic, runtime-connected representations that enable execution, monitoring, and validation. Much current research in this area remains focused on descriptive modeling, simulation-based workflows, or unidirectional data flow, leaving a gap in methods that link architectural models directly to physical system behavior in a closed-loop system. This study fills that gap by proposing and demonstrating a four-layer framework that supports traceable, bidirectional interaction between a system’s architecture and its physical implementation. The framework consists of four interconnected layers: System Definition, Model Translation and Integration, Execution and Monitoring, and Feedback and Synchronization. The System Definition Layer captures mission goals, functional responsibilities, subsystem decomposition, and mission parameters in Capella using the Arcadia methodology. The Model Translation and Integration Layer translates these properties into executable commands via Python4Capella, converting architecture-level parameters into actionable instructions. The Execution and Monitoring Layer executes these commands in MATLAB, while the Feedback and Synchronization Layer returns runtime data to the model, supporting validation, model awareness, and refinement. A UAV case study is used to validate the framework: the UAV architecture is decomposed into key logical subsystems, and mission behaviors such as takeoff, movement, turning, and landing were modeled parametrically using the Property Values Management Tool (PVMT). These properties were translated into MATLAB commands, executed on a physical UAV, and evaluated based on telemetry-based mission distance accuracy. This work demonstrates that an MBSE model can serve not only as a design artifact but also as an authoritative, execution-connected component of a digital twin workflow. The framework contributes to MBSE-driven digital twin research by providing a structured process for integrating architecture, translation, execution, monitoring, and synchronization in a traceable manner. Overall, the study provides a scalable foundation for future developments in hardware-in-the-loop testing and digital twin applications for cyber–physical systems, and further empirical evaluation is needed to assess the framework’s transferability across domains.

Md Robiul Islam, Aditya Akundi, Sergio A. Luna Fong · 0 citations