Software safety analysis of digital protection system requirements using a qualitative formal method

被引:1
|
作者
Lee, JS
Kwon, KC
Cha, SD
机构
[1] Korea Atom Energy Res Inst, MMIS Team, Taejon 305353, South Korea
[2] Korea Adv Inst Sci & Technol, Div Comp Sci, Dept EECE, Taejon 305701, South Korea
[3] AITrc, Taejon 305701, South Korea
关键词
software requirements; safety analysis; formal method;
D O I
10.13182/NT04-A3528
中图分类号
TL [原子能技术]; O571 [原子核物理学];
学科分类号
0827 ; 082701 ;
摘要
The safety analysis of requirements is a key problem area in the development of software for the digital protection systems of a nuclear power plant. When specifying requirements for software of the digital protection systems and conducting safety analysis, engineers find that requirements are often known only in qualitative terms and that existing fault-tree analysis techniques provide little guidance on formulating and evaluating potential failure modes. A framework for the requirements engineering process is proposed that consists of a qualitative method for requirements specification, called the qualitative formal method (QFM), and a safety analysis method for the requirements based on causality information, called the causal requirements safety analysis (CRSA). CRSA is a technique that qualitatively evaluates causal relationships between software faults and physical hazards. This technique, extending the qualitative formal method process and utilizing information captured in the state trajectory, provides specific guidelines on how to identify failure modes and the relationship among them. The QFM and CRSA processes are described using shutdown system 2 of the Wolsong nuclear power plants as the digital protection system example.
引用
收藏
页码:227 / 239
页数:13
相关论文
共 50 条
  • [1] A formal software requirements specification method for digital nuclear plant protection systems
    Yoo, J
    Kim, T
    Cha, S
    Lee, JS
    Son, HS
    JOURNAL OF SYSTEMS AND SOFTWARE, 2005, 74 (01) : 73 - 83
  • [2] Safety analysis of safety-critical software for nuclear digital protection system
    Park, Gee-Yong
    Lee, Jang-Soo
    Cheon, Se-Woo
    Kwon, Kee-Choon
    Jee, Eunkyoung
    Koh, Kwang Yong
    COMPUTER SAFETY, RELIABILITY, AND SECURITY, PROCEEDINGS, 2007, 4680 : 148 - +
  • [3] Fault tree construction of hybrid system requirements using qualitative formal method
    Lee, JS
    Cha, SD
    RELIABILITY ENGINEERING & SYSTEM SAFETY, 2005, 87 (01) : 121 - 131
  • [4] Handling safety critical requirements in system engineering using the B formal method
    Essamé, D
    COMPUTER SAFETY, RELIABILITY, AND SECURITY, PROCEEDINGS, 2004, 3219 : 115 - 115
  • [5] An Analysis Method of Safety Requirements for Automotive Software Systems
    Matsubara, Moe
    Aoyama, Mikio
    2017 24TH ASIA-PACIFIC SOFTWARE ENGINEERING CONFERENCE (APSEC 2017), 2017, : 408 - 416
  • [6] Development of a normative package for safety-critical software using formal regulatory requirements
    Vilkomir, SA
    Ghose, AK
    PRODUCT FOCUSED SOFTWARE PROCESS IMPROVEMENT, 2004, 3009 : 523 - 537
  • [7] Software requirements specification and system safety
    Heimdahl, MPE
    Reese, JD
    RE '97 - PROCEEDINGS OF THE THIRD IEEE INTERNATIONAL SYMPOSIUM ON REQUIREMENTS ENGINEERING, 1997, : 264 - 264
  • [8] An effective technique for the software requirements analysis of NPP safety-critical systems, based on software inspection, requirements traceability, and formal specification
    Koo, SR
    Seong, PH
    Yoo, J
    Cha, SD
    Yoo, YJ
    RELIABILITY ENGINEERING & SYSTEM SAFETY, 2005, 89 (03) : 248 - 260
  • [9] From safety analysis to software requirements
    Hansen, KM
    Ravn, AP
    Stavridou, V
    IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 1998, 24 (07) : 573 - 584
  • [10] Evaluating a Formal Scenario-Based Method for the Requirements Analysis in Automotive Software Engineering
    Greenyer, Joel
    Haase, Maximilian
    Marhenke, Joerg
    Bellmer, Rene
    2015 10TH JOINT MEETING OF THE EUROPEAN SOFTWARE ENGINEERING CONFERENCE AND THE ACM SIGSOFT SYMPOSIUM ON THE FOUNDATIONS OF SOFTWARE ENGINEERING (ESEC/FSE 2015) PROCEEDINGS, 2015, : 1002 - 1005