Export Citations
Save this search
Please login to be able to save your searches and receive alerts for new content matching your search criteria.
- ArticleSeptember 2015
Software Reliability Forecasting: Singular Spectrum Analysis and ARIMA Hybrid Model
TASE '15: Proceedings of the 2015 International Symposium on Theoretical Aspects of Software EngineeringPages 111–118https://doi.org/10.1109/TASE.2015.19In the software reliability growth phase, the nature of the failure data is, in a sense, determined by the software testing process. A hybrid model is proposed for medium and long-term software failure time forecasting in this paper. The hybrid model ...
- ArticleMay 2015
Software Engineering View of a Large-Scale System Failure and the Following Lawsuit
SER-IP '15: Proceedings of the 2015 IEEE/ACM 2nd International Workshop on Software Engineering Research and Industrial PracticePages 18–24https://doi.org/10.1109/SERIP.2015.12In 2005, a system trouble occurred in the Tokyo Stock Exchange Order System, which caused a loss of more than 40 billion yen to Mizuho Securities and Mizuho filed a lawsuit demanding compensation for the loss to the Tokyo Stock Exchange (TSE).The ...
- ArticleOctober 2014
Providing high availability in cloud storage by decreasing virtual machine reboot time
A Virtual Storage Architecture (VSA) is a storage controller deployed as a virtual machine on a server with a hypervisor. The advantage of VSA is to leverage shared data storage services without procuring additional storage hardware, which is a cost ...
- research-articleJanuary 2011
The Evolution of Flight Management Systems
In 1978, Honeywell began developing its flight management system (FMS), putting the first FMS into service as standard equipment in 1982 on the Boeing B757 and B767. Now, every major aircraft manufacturer includes a Honeywell FMS in the cockpit. In ...
- research-articleApril 2009
First-aid: surviving and preventing memory management bugs during production runs
EuroSys '09: Proceedings of the 4th ACM European conference on Computer systemsPages 159–172https://doi.org/10.1145/1519065.1519083Memory bugs in C/C++ programs severely affect system availability and security. This paper presents First-Aid, a lightweight runtime system that survives software failures caused by common memory management bugs and prevents future failures by the same ...
-
- articleApril 2009
Developing high quality software
International Journal of Parallel, Emergent and Distributed Systems (IJPEDS), Volume 24, Issue 2Pages 171–187https://doi.org/10.1080/17445760802544110Performance related problems are a key aspect in the software development process (SDP). In particular an early integration of performance considerations inside the SDP has been recognised during last years as an effective approach to speed up the ...
- research-articleJuly 2008
Testing the Value of Checklists in Code Inspections
Checklists are an important part of code and design inspections. Ideally, they aim to increase the number of faults found per inspection hour by highlighting known areas of previous failure. In practice, although some researchers have quantified ...
- keynoteMay 2008
Quality software development: what do we need to improve in the software development process?
WoSQ '08: Proceedings of the 6th international workshop on Software qualityPages 1–2https://doi.org/10.1145/1370099.1370100There are a number of authors who have documented problems with our software development processes. Unrealistic schedules and budgets, with continuing steams of requirements changes lead to projects with a high risk of failure. There is too often only a ...
- ArticleOctober 2005
Rx: treating bugs as allergies---a safe method to survive software failures
SOSP '05: Proceedings of the twentieth ACM symposium on Operating systems principlesPages 235–248https://doi.org/10.1145/1095810.1095833Many applications demand availability. Unfortunately, software failures greatly reduce system availability. Prior work on surviving software failures suffers from one or more of the following limitations: Required application restructuring, inability to ...
Also Published in:
ACM SIGOPS Operating Systems Review: Volume 39 Issue 5 - discussionNovember 2004
Seeing More of the World
Requirements engineering experience shows that failing to look at all aspects of the problem space results in missing or incorrect requirements. The author provides a systematic approach for identifying which parts of the world require attention, along ...
- ArticleMarch 2002
Software security vulnerability testing in hostile environments
SAC '02: Proceedings of the 2002 ACM symposium on Applied computingPages 260–264https://doi.org/10.1145/508791.508844Traditional Black box software testing can be effective at exposing some classes of software failures. Security class failures, however, do not tend to manifest readily using these techniques. The problem is that many security failures occur in stressed ...
- articleJuly 1999
Why softwarre fails
ACM SIGSOFT Software Engineering Notes (SIGSOFT), Volume 24, Issue 4Pages 81–83https://doi.org/10.1145/329155.329168This note summarizes conclusions from a three year study about why released software fails. Our method was to obtain mature-beta or retail versions of real software applications and stress test them until they fail. From an analysis of the causal faults,...
- ArticleJune 1997
Dynamic Reconfiguration: Checkpointing Code Generation
SAST '97: Proceedings of the 5th International Symposium on Assessment of Software Tools (SAST '97)Page 52Abstract: The author describes a component bused checkpointing code generation tool. Scientific applications that require long computation runtimes experience the risk of hardware or software failures. Failure during a long computation requires that the ...
- ArticleOctober 1996
Software reliability engineering for client-server systems
Too often, when doing software reliability modeling and prediction, the assumption is made that the software involves either a single module or a single node. The reality in today's increasing use of multi-node client-server systems is that there are ...
- ArticleOctober 1996
High assurance engineering: the good, the bad, and the ugly
Over the past two decades, substantial research efforts have been devoted to the design and development of high assurance systems, including general approaches and specific systems. Researchers in fault tolerant systems have developed effective ...
- research-articleNovember 1993
In-Process Evaluation for Software Inspection and Test
IEEE Transactions on Software Engineering (ISOF), Volume 19, Issue 11Pages 1055–1070https://doi.org/10.1109/32.256853The goal of software inspection and test is to reduce the expected cost of software failure over the life of a product. The authors extend the use of defect triggers, the events that cause defects to be discovered, to help evaluate the effectiveness of ...
- doctoral_thesisJanuary 1993
Unification of software reliability models by self-exciting point processes
Assessing the reliability of software has been an active area of research over the past twenty years. To date, over a hundred software reliability models have been proposed. In this dissertation, we unify practically all of the existing software ...
- doctoral_thesisJanuary 1992
An empirical examination of the influence of formal specifications on program diversity
The design, modeling, verification, and validation of highly reliable systems has become increasingly important in recent years. These systems, particularly those which are distributed or involve real-time constraints, are extremely complex and the ...
- research-articleApril 1991
Determining an Optimal Time Interval for Testing and Debugging Software
IEEE Transactions on Software Engineering (ISOF), Volume 17, Issue 4Pages 313–319https://doi.org/10.1109/32.90431A decision-theoretic procedure for determining an optimal time interval for testing software prior to its release is proposed. The approach is based on the principles of decision-making under uncertainty and involves a maximization of expected utility. ...
- research-articleSeptember 1980
Theories of Software Reliability: How Good Are They and How Can They Be Improved?
IEEE Transactions on Software Engineering (ISOF), Volume 6, Issue 5Pages 489–500https://doi.org/10.1109/TSE.1980.230790An examination of the assumptions used in early bug-counting models of software reliability shows them to be deficient. Suggestions are made to improve modeling assumptions and examples are given of mathematical implementations. Model verification via ...