Meshing Agile and Plan-Driven Development in Safety-Critical Software: A Case Study

Lise Tordrup Heeager, Peter Axel Nielsen

Publikation: Bidrag til tidsskriftTidsskriftartikelForskningpeer review

1 Downloads (Pure)

Resumé

Organizations developing safety-critical software are increasingly seeking to create better practices by meshing agile and plan-driven development processes. Significant differences between the agile and the plan-driven processes make meshing difficult, and very little empirical evidence on using agile processes for safety-critical software development exists. There are four areas of concern, in particular, for meshing the development of safety-critical software concerning: documentation, requirements, life cycle and testing. We report on a case study of a pharmaceutical organization in which a Scrum process was implemented to support agile software development in a plan-driven safety-critical project. The purpose was to answer the following research question: For safety-critical software, what can a software team do to mesh agile and plan-driven processes effectively? The main contribution of the paper is an elaborated understanding of meshing in the four areas of concern and how the conditions for safety-critical software influence them. We discuss how meshing within the four areas of concern is a contribution to existing research.
OriginalsprogEngelsk
TidsskriftEmpirical Software Engineering
ISSN1382-3256
StatusUdgivet - 2020

Fingerprint

Software engineering
Drug products
Life cycle
Testing

Citer dette

@article{498395dafb9e4dd1b153351b96d2d1da,
title = "Meshing Agile and Plan-Driven Development in Safety-Critical Software: A Case Study",
abstract = "Organizations developing safety-critical software are increasingly seeking to create better practices by meshing agile and plan-driven development processes. Significant differences between the agile and the plan-driven processes make meshing difficult, and very little empirical evidence on using agile processes for safety-critical software development exists. There are four areas of concern, in particular, for meshing the development of safety-critical software concerning: documentation, requirements, life cycle and testing. We report on a case study of a pharmaceutical organization in which a Scrum process was implemented to support agile software development in a plan-driven safety-critical project. The purpose was to answer the following research question: For safety-critical software, what can a software team do to mesh agile and plan-driven processes effectively? The main contribution of the paper is an elaborated understanding of meshing in the four areas of concern and how the conditions for safety-critical software influence them. We discuss how meshing within the four areas of concern is a contribution to existing research.",
keywords = "Agile software development · Plan-driven software development · Process · Safety-critical software · Meshing · Compliance · Scrum · FDA",
author = "Heeager, {Lise Tordrup} and Nielsen, {Peter Axel}",
year = "2020",
language = "English",
journal = "Empirical Software Engineering",
issn = "1382-3256",
publisher = "Springer",

}

Meshing Agile and Plan-Driven Development in Safety-Critical Software: A Case Study. / Heeager, Lise Tordrup; Nielsen, Peter Axel.

I: Empirical Software Engineering, 2020.

Publikation: Bidrag til tidsskriftTidsskriftartikelForskningpeer review

TY - JOUR

T1 - Meshing Agile and Plan-Driven Development in Safety-Critical Software: A Case Study

AU - Heeager, Lise Tordrup

AU - Nielsen, Peter Axel

PY - 2020

Y1 - 2020

N2 - Organizations developing safety-critical software are increasingly seeking to create better practices by meshing agile and plan-driven development processes. Significant differences between the agile and the plan-driven processes make meshing difficult, and very little empirical evidence on using agile processes for safety-critical software development exists. There are four areas of concern, in particular, for meshing the development of safety-critical software concerning: documentation, requirements, life cycle and testing. We report on a case study of a pharmaceutical organization in which a Scrum process was implemented to support agile software development in a plan-driven safety-critical project. The purpose was to answer the following research question: For safety-critical software, what can a software team do to mesh agile and plan-driven processes effectively? The main contribution of the paper is an elaborated understanding of meshing in the four areas of concern and how the conditions for safety-critical software influence them. We discuss how meshing within the four areas of concern is a contribution to existing research.

AB - Organizations developing safety-critical software are increasingly seeking to create better practices by meshing agile and plan-driven development processes. Significant differences between the agile and the plan-driven processes make meshing difficult, and very little empirical evidence on using agile processes for safety-critical software development exists. There are four areas of concern, in particular, for meshing the development of safety-critical software concerning: documentation, requirements, life cycle and testing. We report on a case study of a pharmaceutical organization in which a Scrum process was implemented to support agile software development in a plan-driven safety-critical project. The purpose was to answer the following research question: For safety-critical software, what can a software team do to mesh agile and plan-driven processes effectively? The main contribution of the paper is an elaborated understanding of meshing in the four areas of concern and how the conditions for safety-critical software influence them. We discuss how meshing within the four areas of concern is a contribution to existing research.

KW - Agile software development · Plan-driven software development · Process · Safety-critical software · Meshing · Compliance · Scrum · FDA

M3 - Journal article

JO - Empirical Software Engineering

JF - Empirical Software Engineering

SN - 1382-3256

ER -