2026· International Conference on Data Technologies and Applications· pp. 887-898· 0 citations· 25 references
Computer Science
TL;DR
The results show that lifecycle integrity can be evaluated as a structural property of the artifact graph, enabling early, machine-checkable detection of missing relations.
Abstract
: Industrial cyber-physical systems rely on structured safety lifecycle in which hazards, risks, requirements, architecture, and verification activities are related across defined phases. In practice, these elements are distributed across heterogeneous documents, making structural consistency and traceability difficult to maintain. This paper presents an approach in which lifecycle elements are encoded as structured documentation artifacts with explicit types and relations. From a data-centric perspective, these artifacts are treated as structured data objects whose relations form a constrained graph representation of lifecycle information. A controlled vocabulary and constrained relations define a consistent representation of lifecycle data. The artifacts are processed through a documentation build workflow that acts as a deterministic data processing and validation pipeline, automatically generating traceability views and completeness checks. Structural constraints over artifact relations cover verification, evidence linkage, SIL allocation, and hazard coverage. The approach is demonstrated on a reproducible IEC 61508 SIL 2 Emergency Stop example, with an open demo site and repository that provide all sources and build scripts. Violations introduced by removing required relations are detected as non-empty coverage tables. The results show that lifecycle integrity can be evaluated as a structural property of the artifact graph, enabling early, machine-checkable detection of missing relations.
A lifecycle model for LLM systems is proposed that supports security analysis by structuring it around security-relevant boundaries rather than workflow optimisation, and is supported by a 12-stage LLMOps pillar and a 9-category governance pillar.
Eleftherios Batzolis, George Drosatos, V. Katsouros et al.· ARES· 0 citations
An airborne software development approach for manned and unmanned aerial vehicles aimed at reducing inconsistencies across system, model-based functional, and embedded software domains is presented and a repository-centered implementation to address recurring failure modes is proposed.
Nils Schlautmann, V. Sinitsyn, Benjamin Engelhard et al.· 0 citations
Compliance reporting for well integrity remains narration-heavy, labour-intensive, and inconsistent across assets. This study develops a compliance-as-code approach that encodes integrity obligations (hazard identification, risk assessment, barrier verification, documentation) into 187 machine-checkable rules mapped...
O. Ogali, I. Okafor, E. Okoro et al.· SPE Nigeria Annual Internati...· 0 citations
The evaluation shows that ASSERT makes document-infrastructure inconsistencies measurable, but reveals a trade-off between discovering undocumented entities and enforcing a schema.
Lea R. Muth, Marian Margraf· International Conference on...· 0 citations
The results indicate that language-model assistance can add value in regulated automotive requirements workflows when it is embedded in deterministic, provenance-rich, and expert-governed processes.
The central finding is that the same four points generalize without modification to AI coding agents and to general agentic workflows, where a defined purpose, an auditable trail, verification, and safe delivery produce tamper-evident evidence at every stage.
P. Gresham· Universal Library of Innovat...· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.