TY - GEN
T1 - An Iterative Approach for Development of Safety-Critical Software and Safety Arguments
AU - Ge, X
AU - Paige, R F
AU - McDermid, J A
N1 - Paper from AGILE Conference 2010, London
PY - 2010
Y1 - 2010
N2 - The benefits ascribed to Agile methods are attractive to software engineers working in the safety-critical software domain. There is limited industrial experience and evidence of successful applications of Agile methods in this domain, however, academic research has identified some of the key challenges of their adoption and application, and has started to present feasibility studies. In this paper, we propose an iterative approach for developing safety-critical software, making two novel contributions. Firstly, we address the notion of up-front design in safety-critical software development, and describe the characteristics fan up-front design that is minimal from the perspective of achieving safety objectives. Secondly, we identify a key difficulty of using iterative development for building safety-critical software, and present a way to develop both a software system and a safety argument iteratively. We also give details of a proof-of-concept example illustrating the use of the approach.
AB - The benefits ascribed to Agile methods are attractive to software engineers working in the safety-critical software domain. There is limited industrial experience and evidence of successful applications of Agile methods in this domain, however, academic research has identified some of the key challenges of their adoption and application, and has started to present feasibility studies. In this paper, we propose an iterative approach for developing safety-critical software, making two novel contributions. Firstly, we address the notion of up-front design in safety-critical software development, and describe the characteristics fan up-front design that is minimal from the perspective of achieving safety objectives. Secondly, we identify a key difficulty of using iterative development for building safety-critical software, and present a way to develop both a software system and a safety argument iteratively. We also give details of a proof-of-concept example illustrating the use of the approach.
UR - http://www.scopus.com/inward/record.url?scp=77958010843&partnerID=8YFLogxK
U2 - 10.1109/AGILE.2010.10
DO - 10.1109/AGILE.2010.10
M3 - Conference contribution
SP - 35
EP - 43
BT - AGILE Conference, 2010
PB - IEEE
ER -