Metraipolis › archive › dc_276b68c57424
JTA: Joint Testability Architecture for Scenario-Based Validation of Safety-Critical Software — arXiv:2608.05594
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2608.05594
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-27T08:04:33.845Z
- SHA-256 of the archived text
4e510c33ecbfe4c2fbeef03e0562717f4876c901d73adc2a5550f1cdd9c3a735- Stable URL of this page
https://metraipolis.com/documento/dc_276b68c57424
How to cite
JTA: Joint Testability Architecture for Scenario-Based Validation of Safety-Critical Software — arXiv:2608.05594 — arXiv (en), https://arxiv.org/abs/2608.05594 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_276b68c57424 (Metraipolis archive dc_276b68c57424, sha256 4e510c33ecbfe4c2fbeef03e0562717f4876c901d73adc2a5550f1cdd9c3a735)
BibTeX
@misc{dc276b68c57424,
title = {JTA: Joint Testability Architecture for Scenario-Based Validation of Safety-Critical Software — arXiv:2608.05594},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2608.05594},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_276b68c57424; sha256 4e510c33ecbfe4c2fbeef03e0562717f4876c901d73adc2a5550f1cdd9c3a735},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.05594. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
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. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-08-07 in cs.SE). Categorie arXiv: Software Engineering (cs.SE) ; Robotics (cs.RO). Pagina del lavoro: https://arxiv.org/abs/2608.05594 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-27T07:55:47.035Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-08-07?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).