Software Engineering Standards in the Nuclear Power Industry—Safety‐Related Applications
Bibliographic record
Abstract
Abstract Nuclear power is very much an international industry. U.S., Canadian, and European vendors are actively involved in the deployment of modern nuclear reactors (including I&C systems) in Asia. I&C systems are routinely delivered across national boundaries; for instance U.S. designed systems have been implemented in Czech Republic, Ukraine, and South Korea; German designed systems have been implemented throughout Europe and proposed for the United States; Canadian designed systems have been installed in Canada and South Korea. The Canadian software engineering technology for safety critical software has been considered for adoption in the development of new I&C safety‐related systems outside of Canada. Japanese I&C systems have proven reliable and should attract wider interest. The global nature of nuclear power points to the strong need for consistency in international sets of nuclear and other standards in addition to consistent approaches to licensing such systems. The application of standards in the nuclear industry is a nontrivial exercise. Many standards organizations worldwide develop standards that affect nuclear I&C systems. Developing a system in one country to one set of standards is no longer sufficient. As such systems cross national boundaries, they need to demonstrate conformance to more than one set of standards and must be licensable in the country of implementation. There is a broad consensus on general principles and approaches in the standards, and national licensing approaches are converging. However, there remain a number of specific issues on which consensus is still outstanding. Examples are the benefits to be gained from the use of formal methods, how to quantify the benefits from applying diversity principles to software, methods for measuring and achieving software reliability and requirements, and methods for the validation of transformation tools and of their output. As technology advances, issues of concern today may be solved, or new issues may arise. Nuclear industry standards and regulatory criteria will have to be periodically updated to keep pace with new international standards, increasing regulatory rigor with respect to software, fast‐paced computer technology advances, and experience gained, both within and outside the nuclear industry, for safety‐related computer‐based I&C systems.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.038 | 0.052 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.007 | 0.009 |
| Science and technology studies | 0.002 | 0.010 |
| Scholarly communication | 0.009 | 0.012 |
| Open science | 0.003 | 0.005 |
| Research integrity | 0.007 | 0.007 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".