Engineering Safety - and Security-Related Requirements for Software-Intensive Systems

D. Firesmith
{"title":"Engineering Safety - and Security-Related Requirements for Software-Intensive Systems","authors":"D. Firesmith","doi":"10.1109/ICSECOMPANION.2007.35","DOIUrl":null,"url":null,"abstract":"Summary form only given. Many software-intensive systems have significant safety ramifications and need to have their associated safety-related requirements properly engineered. It has been observed by several consultants, researchers, and authors that inadequate requirements are a major cause of accidents involving software-intensive systems. Yet in practice, there is very little interaction between the requirements and safety disciplines and little collaboration between their respective communities. Most requirements engineers know little about safety engineering, and most safety engineers know little about requirements engineering. Also, safety engineering typically concentrates on architectures and designs rather than requirements because hazard analysis typically depends on the identification of hardware and software components, the failure of which can cause accidents. This leads to safety-related requirements that are often ambiguous, incomplete, and even missing. The tutorial begins with a single common realistic example of a safety critical system that will be used throughout to provide good examples of safety-related requirements. The tutorial then provides an introduction to requirements engineering for safety engineers and an introduction to safety engineering for requirements engineers. The tutorial then provides clear definitions and descriptions of the different kinds of safety-related requirements and finishes with a practical process for producing them","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2007-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"53","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSECOMPANION.2007.35","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 53

Abstract

Summary form only given. Many software-intensive systems have significant safety ramifications and need to have their associated safety-related requirements properly engineered. It has been observed by several consultants, researchers, and authors that inadequate requirements are a major cause of accidents involving software-intensive systems. Yet in practice, there is very little interaction between the requirements and safety disciplines and little collaboration between their respective communities. Most requirements engineers know little about safety engineering, and most safety engineers know little about requirements engineering. Also, safety engineering typically concentrates on architectures and designs rather than requirements because hazard analysis typically depends on the identification of hardware and software components, the failure of which can cause accidents. This leads to safety-related requirements that are often ambiguous, incomplete, and even missing. The tutorial begins with a single common realistic example of a safety critical system that will be used throughout to provide good examples of safety-related requirements. The tutorial then provides an introduction to requirements engineering for safety engineers and an introduction to safety engineering for requirements engineers. The tutorial then provides clear definitions and descriptions of the different kinds of safety-related requirements and finishes with a practical process for producing them
软件密集型系统的工程安全和安全相关需求
只提供摘要形式。许多软件密集型系统都有重要的安全分支,需要对其相关的安全相关需求进行适当的设计。一些顾问、研究人员和作者已经注意到,需求不足是涉及软件密集型系统的事故的主要原因。然而在实践中,需求和安全规程之间的相互作用很少,他们各自社区之间的协作也很少。大多数需求工程师对安全工程知之甚少,而大多数安全工程师对需求工程知之甚少。此外,安全工程通常侧重于架构和设计,而不是需求,因为危害分析通常依赖于硬件和软件组件的识别,这些组件的故障可能导致事故。这导致了与安全相关的需求常常是模糊的、不完整的,甚至是缺失的。本教程从安全关键系统的一个常见实际示例开始,该示例将贯穿始终,提供与安全相关的需求的良好示例。然后,本教程为安全工程师介绍了需求工程,并为需求工程师介绍了安全工程。然后,本教程提供了不同类型的安全相关需求的明确定义和描述,并以生成这些需求的实际过程结束
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信