Skip to content

GCRI · Foundry

Safety-critical software engineering

Software and safety-critical systems engineering applies rigorous practice where a software fault could reach a decision with real consequences. In this field it means fail-closed defaults, verified builds, known components, tested recovery, and an assurance case that states what has and has not been shown.

01Qeyd

Safety-critical software engineering on the record.

Method recordSTEM method
  1. MethodSoftware and safety-critical systems engineering
  2. Applied inFoundry
  3. Canonical pageSTEM Commons
02Serlêdan

What software and safety-critical systems engineering does here.

Software and safety-critical systems engineering develops software whose failure could cause harm, loss of life or major disruption. It applies rigorous processes to control-system, medical, aviation and infrastructure software. In data and compute and methods and modelling, safety-critical software practice limits the chance that a software fault cascades through physical infrastructure. It informs assurance requirements for automated control in interconnected systems. The canonical description is on the STEM Commons.

Fail-closed policy gates

Every consequential request is evaluated against identity, mandate, purpose and data class; when no explicit decision exists the gate denies, and the denial is recorded.

Build provenance and bills of materials

Releases are built by a controlled pipeline that signs provenance attestations and produces a software bill of materials, so a deployed artefact can be traced to its source and components.

Assurance cases

Claims about a system, such as tenant isolation or kill-switch effectiveness, are argued from evidence in a structured case, with gaps and residual risks stated rather than assumed away.

03Rêbaz û delîl

How safety-critical software engineering is modelled, measured and tested.

Model, texmînên wî, daneyên wî û nediyariya wî, bi şeweyê ku zanyar an endezyar kontrol bike. Avahî rêbazên weşandî dişopînin. Nirxên hatine xêzkirin nimûneyî ne, ne encam in.

Model, hevkêşe û texmîn

The model structure used for safety-critical software engineering, the assumptions it makes and how each is tested.

Xetera hêmana iRi = f(Hi, Ei, Vi, Ci)metirsî, rûbirûbûn, lawazî û kapasîteya serederiyê
Windahiya salane ya hêvîkirîEAL = ∑k pk · Lkover events k with annual probability pk
Pergalên girêdayîxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error
TexmînÇima tê çêkirinÇawa tê ceribandin
Metirsî û rûbirûbûn di nav bûyerekê de serbixwe neEntegrala windahiyê ji hesabkirinê re maqûl dihêleBi lihevhatineke copula li ser tomarên hevbeş re bidin ber hev
Girêdan li nêzî xala xebatê xêzik inDihêle şok di A de belav bibinJi derveyî rêza xêzik tevlihev bike û bide ber hev
Xêzên lawaziyê di navbera cihan de têne veguhastinXêzikên herêmî kêm tên dîtinLi hember windahiyên çavdêrîkirî erê bike li cihê ku hene
Têketin
danehevên bi guhertoyan û çavkaniyê
Derketin
belavkirin, tu carî jimarên tenê
Kod
bi qerta modelê û ceribandinan re hat weşandin
Zêdebûn
heman dane, kod, jîngeh û tov
Formulasyonên standard ên xetereyê û qada rewşê; texmînên navborî ji bo rêbazê tîpîk in, ji bo nirxandinê hatine diyarkirin, ne encam in.
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
04Dane

What the method consumes.

Datasets and records used by software and safety-critical systems engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.

DaneRolNîşan
Source repositories and review recordsChange history and approvalÇAVDÊRÎKIRÎ
Test coverage and mutation resultsVerification depthÇAVDÊRÎKIRÎ
Software bills of materialsComponent inventoryÇAVDÊRÎKIRÎ
Vulnerability advisoriesExposure of componentsHATIYE RAPORKIRIN
Incident and fault logsFailure analysisÇAVDÊRÎKIRÎ
05Pêvajo

Pêvajo çawa dimeşe.

Process explorer · Process

Safety-critical software engineering: Risk management process

8 gav5 qonax

Pêvajo

Safety-critical software engineering: Risk management process

ISO 31000:2018 sets out an iterative risk management process, from scope, context and criteria through assessment and treatment to monitoring, review and reporting.

  1. 01 Frame

    1. 01Scope, context and criteriaDataset · Project ownerThe frame for the process: the scope, the external and internal context, and the risk criteria. Later steps are read against this frame.
  2. 02 Risk assessment

    1. 04Risk identificationStep · Project ownerThe first part of risk assessment. Risk is usually expressed by risk sources, potential events, their consequences and likelihood.
    2. 05Risk analysisModel · Project ownerThe second part of risk assessment. It considers consequences and likelihood of the identified risks, with guidelines, not a formula.
    3. 06Risk evaluationStep · Project ownerThe last part of risk assessment. Results of the analysis are compared with the risk criteria to see where more action is needed.
  3. 03 Treatment

    1. 07Risk treatmentStep · Project ownerTreatment options are selected, then plans are prepared and implemented. Residual risk is documented and goes to monitoring and review.
  4. 04 Across the process

    1. 02Communication and consultationStep · Project ownerCommunication and consultation with stakeholders is its own process element. The standard draws it alongside the others, not in sequence.
    2. 03Monitoring and reviewStep · Project ownerMonitoring and review take place at every stage. New experience, knowledge and analysis can revise elements, actions and controls.
  5. 05 Record and report

    1. 08Recording and reportingRecord · Project ownerThe process and its outcomes are documented and reported. The standard does not name who receives the report in the clauses read.

Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval.

06Erêkirin

How results are checked.

Software is verified through reviews, testing to defined coverage criteria and formal proofs where justified. Independent assessment examines the safety case.

Kontrol bikinHow it is done
Deny-by-default testsRequests without an explicit policy decision are tested to confirm they fail closed
Provenance verificationDeployed artefacts are checked against signed attestations before they run
Fault injectionDependencies are failed deliberately to test recovery and isolation
Independent assessmentThe assurance case is reviewed by an assessor outside the development team

Complex software interacting with uncertain environments cannot be exhaustively tested. Updates and third-party components introduce new failure paths.

08Parastin û serperiştî

Who maintains the method.

Cybersecurity and Digital Resilience stewards software and safety-critical systems engineering for the Consortium and reviews how it is applied across platforms.

10Pirs

Pirs û bersiv.

What are the limits of software and safety-critical systems engineering in this field?
Complex software interacting with uncertain environments cannot be exhaustively tested. Updates and third-party components introduce new failure paths.
How are results checked?
Software is verified through reviews, testing to defined coverage criteria and formal proofs where justified. Independent assessment examines the safety case.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method’s use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
rêzeya Pergalên StratejîkTevkarî bike

Ji vê rûpelê delîl bidin.

Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.

GCRIFoundryFoundry Build and Readiness
Foundry

Rêbazek, danehevek an pirsek bîne.

Agahî û pirs îro vekirî ne. Pirsek referansekê distîne û gava piştî wê dide nasîn; serlêdan, drav, veqetandina hesabkirinê û tomarkirin tenê dema ku tîm, mercên wê û kapasîteya vekolînê hebin vedibin.

The Global Centre for Risk and Innovation (GCRI Canada) is a Canadian not-for-profit organisation, not a registered charity, with its registered office in Ontario.