<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<front>
<journal-meta>
<journal-id/>
<issn/>
<banner>
<href>banner.jpg</href>
<size width="100%"/>
</banner>
</journal-meta>
<doi>0928-cd</doi>
<article-meta>
<title-group>
<article-title>Iterative and Incremental Development of Reliable Systems</article-title>
</title-group>

<author>Marc Zeller<sup>1</sup> and Sebastian Klabes<sup>2</sup></author>

<aff><sup>1</sup>Siemens AG, Corporate Technology, Germany</aff>

<email><a href="mailto:marc.zeller@siemens.com">marc.zeller@siemens.com</a></email>

<aff><sup>2</sup>RAMS Department, Siemens Mobility AG, Switzerland</aff>

<email><a href="mailto:sebastian.klabes@siemens.com">sebastian.klabes@siemens.com</a></email>

</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>Agile development is getting increasing attention for the development of systems - also in context of safetycritical applications. However, the assurance of emerging properties of a system like reliability or functional safety becomes an even more challenging task, since the system needs to be re-assessed in terms of reliability or safety in each development cycle (or sprint). Because the architecture as the basis for the reliability or safety analysis is continuously changing, a lot of extra work for maintaining the reliability/safety assessments is necessary by the experts. With Component Fault Trees (CFTs) there is an approach to cope with this challenge by a modular and hierarchical methodology to assess the safety or reliability of the system. In this paper, we show the application of the CFT methodology in an iterative and incremental development life-cycle. Using a case study in the railway domain we demonstrate that the CFT methodology eases the reliability/safety assessment in agile development significantly.</p>
<p><italic>Keywords: </italic>Component Fault Tree, Reliability, Safety, Incremental, Iterative.</p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>0928</hpdf>
</fpdf>
</body>
</article>