How faults cause software failures: implications for software reliability engineering

W. K. Ehrlich, A. Iannino, Bala Prasanna, J. Stampfel, Jar R. Wu
{"title":"How faults cause software failures: implications for software reliability engineering","authors":"W. K. Ehrlich, A. Iannino, Bala Prasanna, J. Stampfel, Jar R. Wu","doi":"10.1109/ISSRE.1991.145386","DOIUrl":null,"url":null,"abstract":"Software systems typically contain design and code defects that manifest themselves as software failures at various points during program execution. These software faults can be viewed as causing failures to occur according to some chance mechanism that is often taken to be a Poisson process. Individual per-fault failure sequences (resulting from delayed fault detection and software correction) during test execution were analyzed to determine whether they satisfied Poisson process assumptions. The system analyzed, a large, complex, industrial software system, was executed under a defined operational profile corresponding to a controlled command and autonomous event mix characteristic of the system's actual usage. The failure events, defined as severe, system-wide affecting events attributed to software faults, typically occurred following many cycles of interacting system features in the expected user mode. Execution times between failure events were calculated and then statistically analyzed for conformance to Poisson process assumptions. The results indicated that first-time failure events conformed to the assumptions of a Poisson process and were consistent with a reliability growth Poisson model but that per-fault failure sequences attributed to specific faults tended to violate Poisson assumptions due to failure clustering.<<ETX>>","PeriodicalId":338844,"journal":{"name":"Proceedings. 1991 International Symposium on Software Reliability Engineering","volume":"22 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1991-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"12","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings. 1991 International Symposium on Software Reliability Engineering","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISSRE.1991.145386","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 12

Abstract

Software systems typically contain design and code defects that manifest themselves as software failures at various points during program execution. These software faults can be viewed as causing failures to occur according to some chance mechanism that is often taken to be a Poisson process. Individual per-fault failure sequences (resulting from delayed fault detection and software correction) during test execution were analyzed to determine whether they satisfied Poisson process assumptions. The system analyzed, a large, complex, industrial software system, was executed under a defined operational profile corresponding to a controlled command and autonomous event mix characteristic of the system's actual usage. The failure events, defined as severe, system-wide affecting events attributed to software faults, typically occurred following many cycles of interacting system features in the expected user mode. Execution times between failure events were calculated and then statistically analyzed for conformance to Poisson process assumptions. The results indicated that first-time failure events conformed to the assumptions of a Poisson process and were consistent with a reliability growth Poisson model but that per-fault failure sequences attributed to specific faults tended to violate Poisson assumptions due to failure clustering.<>
故障是如何导致软件故障的:对软件可靠性工程的启示
软件系统通常包含设计和代码缺陷,这些缺陷在程序执行期间的各个点表现为软件故障。这些软件故障可以被看作是根据一些通常被认为是泊松过程的偶然机制导致故障发生的。在测试执行过程中,分析单个故障故障序列(由延迟的故障检测和软件纠正引起),以确定它们是否满足泊松过程假设。所分析的系统是一个大型、复杂的工业软件系统,在与系统实际使用的受控命令和自主事件混合特征相对应的定义操作剖面下执行。故障事件被定义为由于软件故障导致的严重的系统范围影响事件,通常发生在预期用户模式下交互系统特性的许多周期之后。计算失效事件之间的执行时间,然后对是否符合泊松过程假设进行统计分析。结果表明,首次故障事件符合泊松过程的假设,与可靠性增长泊松模型一致,但由于故障聚类,归因于特定故障的每次故障序列往往违反泊松假设。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约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学术官方微信