Skip to content
Preprint

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

Aug 2026 · 0 citations
Computer Science

TL;DR

JTA provides an architectural basis for modeling, designing, and assessing scenario-based validation in safety-critical software and 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.

Abstract

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.

View source

Similar papers

Review Open access 2026

Virtual Continuous Testbeds with LLM-Based Test Case Generation: Toward Closed-Loop Validation of Safety-Critical Systems

: This paper presents an automated approach to deriving informal test cases from Requirements Interchange Format (ReqIF)-structured system requirements based on general-purpose Large Language Models (LLMs) with integrated linkage to test evidences based on Digital Dependability Identities (DDIs). Our method enables scenario-based testing while drastically reducing effort and cost: test cases become available within hours instead of months. The automation supports formal traceability, safety argumentation, and change impact analysis. An automated conversion of derived test cases into ASAM OpenScenario (XOSC) and Open Test Sequence Exchange (OTX) formats accelerates design and implementation of platform-independent, executable test specifications while improving their reuse across development stages. A systematic review process allows domain experts to refine and extend generated specifications. We discuss testbed configuration including resource allocation, toolchain integration, and parameter initialization to satisfy test constraints and strengthen confidence in results against the original acceptance criteria. Finally, we execute the reviewed test cases in a simulated environment within a Virtual Continuous Testing (VCT) pipeline for efficient verification and validation in an X-in-the-Loop (XiL) testbed based on VCIP/FERAL. The closed-loop approach advances automated testing by combining efficiency, consistency, and scalability in test generation, which is showcased within an automotive use case.

Adam Bachorek, Stefan Schwenk, Naveed Akram et al. · 0 citations
2026

Dynamic Requirement Verification and Safety Assessment of Complex Systems using MBSE and Co-Simulation

Critical infrastructures, particularly nuclear energy systems, face growing complexity due to regulatory constraints, performance demands, and the transition toward low-carbon power. Model-Based Systems Engineering (MBSE) supports complexity management by linking system architecture with multiphysics simulation, ensuring traceability from requirements to behavior. However, most MBSE verification approaches remain limited to nominal operating conditions and do not explicitly integrate reliability-driven degradation into requirement evaluation. In practice, aging, wear-out mechanisms, and random faults progressively erode safety margins, limiting early detection of degraded performance. This paper proposes an integrated methodology combining MBSE with stochastic degradation modeling for dynamic requirement verification under both functional and degraded scenarios. A stochastic Petri net (SPN) with Weibull-distributed transitions is embedded into a Dymola physical model to represent time-dependent failure behavior. Safety and performance requirements are formalized using the Common Requirement Modeling Language (CRML) within a SysML architecture model developed in Catia Magic and continuously evaluated during co-simulation. Interoperability between architectural and behavioral domains is ensured via Functional Mock-up Units (FMUs) and UDP-based communication, preserving synchronization and bidirectional traceability. The framework is applied to the primary loop of a Molten Salt Reactor (MSR), focusing on stochastic degradation of the primary fuel pump over 5000 s simulation. Results show a 39% mass-flow reduction, core temperature rise beyond the 708 °C safety limit, and an 18% increase in thermal power, demonstrating significant safety margin erosion. The proposed approach transforms verification from static compliance checking into a dynamic, reliability-aware assessment of system behavior over time.

S. Gyasi, M. El Alaoui, Nicolas Bureau et al. · 0 citations
Open access Aug 2026

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

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.

Sumaiyya Fatima · 0 citations

CTForge: Automatically Generating Test Suites for Software Configuration

CTForge is presented, an LLM-powered framework that automatically generates configuration-specific test suites and demonstrates that structured configuration-aware refinement is essential for LLM to produce effective test suites.

Yuanliang Zhang, Zhizheng Zheng, Shanshan Li et al. · 0 citations
Jul 2026

Characterizing Structural Testability in JavaScript: An Empirical Study

This paper operationalizes structural testability as a seven-dimensional construct capturing controllability, observability, branching complexity, asynchronous coordination, event-driven behaviour, encapsulation, and side-effect intensity and applies this framework to 30 open-source JavaScript projects spanning diverse domains and sizes.

Shahrzad Mirzaei, Saba Alimadadi · 0 citations
Open access Aug 2026

DEVELOPING AN AUTOMATED FUNCTIONAL TESTING FRAMEWORK - A PRACTICAL CASE STUDY

Test automation addresses limitations such as time consuming, error prone, and difficult to reproduce at a scale by enabling systematic, efficient, and repeatable validation of software functionality across multiple deployments. This project presents an analysis of the client’s CRM system, with the primary objective of designing and implementing an automation test plan, a supporting test architecture, and executable test scripts capable of generating reports and a deployable .jar file. The proposed automation framework adopts the Page Object Model (POM), which enhances maintainability and promotes code reuse by separating page objects from test logic. Functional test cases are derived from user stories to ensure that automated scenarios accurately reflect real user interactions. The project scope includes configuring the test environment, developing automation scripts, producing TestNG reports, packaging the executable .jar file, and setting up the EspoCRM instance locally using MAMP server.

Rajat Sharma, Shahid Ali · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.