High-integrity agile processes for the development of safety critical software

Richard F. Paige, Andy Galloway, Ramon Charalambous, Xiaocheng Ge, Phillip J. Brooke

    Research output: Contribution to journalArticleResearchpeer-review

    Abstract

    Typically, safety critical software systems are developed using plan-driven development processes. Agile processes have evolved to help reduce costs of software development and seek to minimise documentation overheads. For safety critical systems that must undergo certification, documentation is essential. The question this paper addresses is: can a process based on agile principles be used to deliver a safety critical software product, but also the evidence needed to satisfy assurance objectives? The paper makes three contributions. Firstly, it presents an analysis of agile processes and their applicability in this domain. It reviews positive indicators for their use, outlines challenges associated with their deployment and proposes strategies for addressing these challenges. Secondly, it makes a number of recommendations for adapting an agile process to the domain. Finally, the paper reports on an experiment to demonstrate the plausibility of using of an adapted agile process for building a safety critical software system.
    Original languageEnglish
    Pages (from-to)181-216
    JournalInternational Journal of Critical Computer-Based Systems
    Volume2
    Issue number2
    DOIs
    Publication statusPublished - 1 Jan 2011

    Fingerprint

    Software engineering
    Costs
    Experiments

    Cite this

    Paige, Richard F. ; Galloway, Andy ; Charalambous, Ramon ; Ge, Xiaocheng ; Brooke, Phillip J. / High-integrity agile processes for the development of safety critical software. In: International Journal of Critical Computer-Based Systems. 2011 ; Vol. 2, No. 2. pp. 181-216.
    @article{73b4504e94fb4b4e86e89ecf29d850c6,
    title = "High-integrity agile processes for the development of safety critical software",
    abstract = "Typically, safety critical software systems are developed using plan-driven development processes. Agile processes have evolved to help reduce costs of software development and seek to minimise documentation overheads. For safety critical systems that must undergo certification, documentation is essential. The question this paper addresses is: can a process based on agile principles be used to deliver a safety critical software product, but also the evidence needed to satisfy assurance objectives? The paper makes three contributions. Firstly, it presents an analysis of agile processes and their applicability in this domain. It reviews positive indicators for their use, outlines challenges associated with their deployment and proposes strategies for addressing these challenges. Secondly, it makes a number of recommendations for adapting an agile process to the domain. Finally, the paper reports on an experiment to demonstrate the plausibility of using of an adapted agile process for building a safety critical software system.",
    author = "Paige, {Richard F.} and Andy Galloway and Ramon Charalambous and Xiaocheng Ge and Brooke, {Phillip J.}",
    year = "2011",
    month = "1",
    day = "1",
    doi = "10.1504/IJCCBS.2011.041259",
    language = "English",
    volume = "2",
    pages = "181--216",
    journal = "International Journal of Critical Computer-Based Systems",
    issn = "1757-8779",
    publisher = "Inderscience Publishers",
    number = "2",

    }

    High-integrity agile processes for the development of safety critical software. / Paige, Richard F.; Galloway, Andy; Charalambous, Ramon; Ge, Xiaocheng; Brooke, Phillip J.

    In: International Journal of Critical Computer-Based Systems, Vol. 2, No. 2, 01.01.2011, p. 181-216.

    Research output: Contribution to journalArticleResearchpeer-review

    TY - JOUR

    T1 - High-integrity agile processes for the development of safety critical software

    AU - Paige, Richard F.

    AU - Galloway, Andy

    AU - Charalambous, Ramon

    AU - Ge, Xiaocheng

    AU - Brooke, Phillip J.

    PY - 2011/1/1

    Y1 - 2011/1/1

    N2 - Typically, safety critical software systems are developed using plan-driven development processes. Agile processes have evolved to help reduce costs of software development and seek to minimise documentation overheads. For safety critical systems that must undergo certification, documentation is essential. The question this paper addresses is: can a process based on agile principles be used to deliver a safety critical software product, but also the evidence needed to satisfy assurance objectives? The paper makes three contributions. Firstly, it presents an analysis of agile processes and their applicability in this domain. It reviews positive indicators for their use, outlines challenges associated with their deployment and proposes strategies for addressing these challenges. Secondly, it makes a number of recommendations for adapting an agile process to the domain. Finally, the paper reports on an experiment to demonstrate the plausibility of using of an adapted agile process for building a safety critical software system.

    AB - Typically, safety critical software systems are developed using plan-driven development processes. Agile processes have evolved to help reduce costs of software development and seek to minimise documentation overheads. For safety critical systems that must undergo certification, documentation is essential. The question this paper addresses is: can a process based on agile principles be used to deliver a safety critical software product, but also the evidence needed to satisfy assurance objectives? The paper makes three contributions. Firstly, it presents an analysis of agile processes and their applicability in this domain. It reviews positive indicators for their use, outlines challenges associated with their deployment and proposes strategies for addressing these challenges. Secondly, it makes a number of recommendations for adapting an agile process to the domain. Finally, the paper reports on an experiment to demonstrate the plausibility of using of an adapted agile process for building a safety critical software system.

    U2 - 10.1504/IJCCBS.2011.041259

    DO - 10.1504/IJCCBS.2011.041259

    M3 - Article

    VL - 2

    SP - 181

    EP - 216

    JO - International Journal of Critical Computer-Based Systems

    JF - International Journal of Critical Computer-Based Systems

    SN - 1757-8779

    IS - 2

    ER -