MétaCan
Menu
Back to cohort
Record W4303022300 · doi:10.1002/sys.21643

Integration of systems design and risk management through model‐based systems development

2022· article· en· W4303022300 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

VenueSystems Engineering · 2022
Typearticle
Languageen
FieldEngineering
TopicSystems Engineering Methodologies and Applications
Canadian institutions123 Certification (Canada)
Fundersnot available
KeywordsFault tree analysisFailure mode and effects analysisReliability engineeringDependabilityComputer scienceRisk managementRisk analysis (engineering)Hazard analysisHazard and operability studyRisk assessmentEngineeringSystems Modeling LanguageSystems engineeringUnified Modeling LanguageSoftwareComputer security

Abstract

fetched live from OpenAlex

Abstract Model‐based systems engineering is a powerful methodology to develop safety‐critical systems. The use of the system model as a single source of truth for risk and dependability analysis results in a consistent and complete assessment. Besides, representation and logging of the assessment within the model result in a complete and up‐to‐date single source of information that can be used during the device certification as well. This paper aims to provide a comprehensive risk management SysML profile that includes interconnected safety analysis [functional hazard assessment (FHA), fault tree, and failure mode and effect analysis (FTA, FMEA)], control measure, and evaluation model elements in compliance with the medical standards. Model‐based risk assessment of a point‐of‐care diagnostic device for sepsis has been shown as a case study to show the implementation of the profile. This device is a standalone unit and the test results obtained directly affect the patient. Therefore, both the top‐down (FHA and FTA) and bottom‐up (FMEA) safety assessment methods have been used. Another objective of the study is to define a systematic and holistic method to perform fault tree analysis, not only from the system architecture models but also from the functional, activity, and sequence diagrams of the system model.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.881
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.052
GPT teacher head0.239
Teacher spread0.187 · 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