MétaCan
Menu
Back to cohort

Deriving Safety Assurance Case Argumentation from WF+ Models

2023· article· en· W4390098501 on OpenAlexaff
Nicholas Annable

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicSafety Systems Engineering in Autonomy
Canadian institutionsMcMaster UniversityMcMaster University Medical Centre
Fundersnot available
KeywordsArgumentation theorySafety caseWorkflowCertificationSoftware deploymentComputer scienceSafety assuranceQuality assuranceRisk analysis (engineering)Work (physics)Argument (complex analysis)Systems engineeringProcess managementManagement scienceSoftware engineeringEngineeringOperations managementMedicine

Abstract

fetched live from OpenAlex

Safety-critical systems often require safety certification before their deployment. It has become common for the safety argument to be documented in an assurance case, and in many domains assurance cases are recommended or required for certification. However, the rapidly increasing complexity and scale of safety-critical systems is making it increasingly difficult to produce rigorous and convincing assurance cases. Recent work on the Workflow+ framework has presented an opportunity to make more rigorous assurance cases while also coping with the complexity of modern systems. To do this, principles for the derivation of safety case argumentation based on safety analysis and development processes modelled in Workflow+ must be developed. These principles will allow for arguments to be constructed systematically and potentially semi-automatically. This work outlines the approach for my research aiming to develop these principles, a method to systematically construct argumentation based on these principles and to automate the construction of argumentation where possible.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.009
metaresearch head score (Gemma)0.035
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.009
Threshold uncertainty score0.046

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0090.035
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.003
Bibliometrics0.0050.002
Science and technology studies0.0020.003
Scholarly communication0.0050.005
Open science0.0020.007
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0070.002

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.015
GPT teacher head0.207
Teacher spread0.192 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations1
Published2023
Admission routes1
Has abstractyes

Explore more

Same topicSafety Systems Engineering in AutonomyFrench-language works237,207