Sciweavers

Free Online Productivity Tools i2Speak i2Symbol i2OCR iTex2Img iWeb2Print iWeb2Shot i2Type iPdf2Split iPdf2Merge i2Bopomofo i2Arabic i2Style i2Image i2PDF iLatex2Rtf Sci2ools

7

ARCS
2004
Springer

favoriteEmaildiscussreport

133views Software Engineering» more ARCS 2004»

Root Cause Analysis as a Guide to SRE Methods

13 years 9 months ago

Root Cause Analysis as a Guide to SRE Methods

Download subs.emis.de

Abstract: Which Software Reliability Engineering (SRE) methods should be applied during the various phases of the lifecycle of a product? The answer given here centres on learning from errors. The classification and evaluation of methods is strictly based on causal analyses of disasters, accidents and incidents with undesired outcome. The lifecycle model of IEC Standard 61508 has been adopted as a classification scheme. A couple of examples are given. The SRE methods considered here are those of IEC 61508. These methods are dealing with software reliability as well as with the production of highly reliable software. As an example of some more recent proposals Extreme Programming (XP) has been included.

Timm Grams

Real-time Traffic

ARCS 2004 | Software Reliability | Software Reliability Engineering | SRE Methods |

claim paper

Related Content

» URCA Pulling out Anomalies by their Root Causes

» Automated known problem diagnosis with event traces

» An analysis of the Ariane 5 flight 501 failurea system engineering perspective

» A first step toward understanding interdomain routing dynamics

» Collecting Sensor Data for HighPerformance Computing A Casestudy

» Golden implementation driven software debugging

» Agile Methods for Embedded Systems

» Counterexample Explanation by Anomaly Detection

» High volume microprocessor test escapes an analysis of defects our tests are missing

Post Info
More Details (n/a)

Added	30 Jun 2010
Updated	30 Jun 2010
Type	Conference
Year	2004
Where	ARCS
Authors	Timm Grams

Comments (0)