面向软件安全性需求分析过程的追踪模型  

Traceability Model Oriented to Software Safety Requirement Analysis Process

作　　者：郑培真 苑春春[1] 刘超[1] 吴际[1] 杨海燕[1] 胡宁[2] 

机构地区：[1]北京航空航天大学计算机学院,北京100191 [2]中航工业西安航空计算技术研究所,西安710065

出　　处：《计算机科学》2017年第4期30-34,共5页Computer Science

基　　金：某国家重点科研项目(MJ-S-2012-05)资助

摘　　要：追踪性即关联一些制品及其中各种相关要素的机制或能力。安全关键系统开发不仅包括一般系统的开发过程,更重要的是必需要有独立的安全性分析,建立并验证系统的安全性需求。目前针对安全性分析过程的追踪性研究较少。安全相关标准如ARP-4761和DO 178C等提供了安全性分析过程的指导意见,然而其由于涉及的概念和方法很多,因此在实际应用和研究中常会忽略对一些关键信息的追踪。此外,软件安全性需求分析不仅应考虑系统到软件的安全性分析,还应考虑软件到系统的安全性分析。面向软件安全性需求分析过程建立安全性相关信息的双向追踪,有助于了解安全性需求的前因后果,为验证工作和影响分析提供便利。参照标准,构建面向软件安全性需求分析过程的追踪模型。Traceability is the mechanism or the ability to relate artefacts and the attached factors.Safety-critical system development,besides the general system development,contains more independent safety analysis which generates and verifies system safety requirements.At present,there are few traceability researches oriented to safety analysis process,which are of extremely challenging.Safety related standards,such as ARP-4761,DO 178 C,provide guidelines for conducting safety analysis.However,some information may be neglected since there are a lot of concepts and methods.Besides,software safety requirement analysis should include both system to software and software to system safety analysis.Establishing bi-directional traceability of safety related information oriented to software safety requirement analysis process helps to simplify the verification and impact analysis.In this paper,we established a traceability model oriented to software safety requirement analysis process.

关 键 词：追踪性 软件安全性需求 安全性分析 

分 类 号：TP311[自动化与计算机技术—计算机软件与理论]