MétaCan
Menu
Back to cohort
Record W2066363949 · doi:10.4271/2015-01-0265

From Natural Language to Semi-Formal Notation Requirements for Automotive Safety

2015· article· en· W2066363949 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSAE technical papers on CD-ROM/SAE technical paper series · 2015
Typearticle
Languageen
FieldEngineering
TopicSafety Systems Engineering in Autonomy
Canadian institutionsInfineon Technologies (Canada)
Fundersnot available
KeywordsComputer scienceNotationAutomotive industryNatural languageFormal methodsProgramming languageNatural language processingEngineeringLinguistics

Abstract

fetched live from OpenAlex

<div class="section abstract"><div class="htmlview paragraph">The standard ISO 26262 stipulates a “top-down” approach based on the process “V” model, by conducting a hazard analysis and risk assessment to determine the safety goals, and subsequently derives the safety requirements down to the appropriate element level. The specification of safety goals is targeted towards identified hazardous events, whereas the classification of safety requirements does not always turn out non-ambiguous. While requirement formalization turns out to be advantageous, the translation from natural language to semi-formal requirements, especially in context of ISO 26262, poses a problem. In this publication, a new approach for the formalization of safety requirements is introduced, targeting the demands of safety standard ISO 26262. Its part 8, clause 6 (“Specification and management of safety requirements”) has no dedicated work product to accomplish this challenging task. The five levels of requirements for writing safety requirements are distributed throughout the standard, increasing the probability of misapplication. For these reasons, a dedicated requirement template is proposed. It is applicable for writing new or checking existing requirements, independent of any tool. By reviewing a number of industrial relevant use cases the applicability of the new template is verified and its effectiveness is demonstrated. Furthermore, a semi-formal notation technique is shown to express these formalized requirements, including their associated attributes and resulting relationships. By following the proposed approach, we meet the obligations of ISO 26262 to write e.g. unambiguous, consistent, verifiable, and complete requirements. In the end, this has the potential to dramatically reduce the probability of systematic failures during development of automotive embedded systems.</div></div>

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.974
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.014
GPT teacher head0.254
Teacher spread0.240 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it