A conceptual model of agile software development in a safety-critical context: A systematic literature review

Heeager, Lise Tordrup; Nielsen, Peter Axel

doi:10.1016/j.infsof.2018.06.004

Cited by 52 publications

(25 citation statements)

References 41 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It is often required in standards and approval procedures that development follows a documented and rigid process (Heeager and Nielsen 2018), and that this occurs at the outset is mostly in line with plan-driven software development; thus, for a long time, agility was considered at odds with safety-critical software that can cause serious injury to people, the environment or the economy. Several studies have engaged in the question of whether agile processes can be used when developing safety-critical software; the majority are studies comparing an agile process, such as Scrum or XP, with a certain regulatory standard (e.g.…”

Section: Agility In Safety-critical Software Developmentmentioning

confidence: 99%

“…The use of documentation of safety-critical software gets much attention in the research literature as it is considered a primary challenge for applying agile development (Heeager and Nielsen, 2018). Documentation is essential for providing what is called the safety argument in the development of safety-critical software, and agile processes do not provide enough documentation or provide the wrong kind of documentation for this purpose (Hajou et al 2015a;Sidky and Arthur 2007;Wäyrynen et al 2004).…”

Section: The Use Of Documentationmentioning

confidence: 99%

“…Abdelaziz et al 2015;Van Schooenderwoert and Shoemaker 2018). The research literature shows that organizations use a variety of elements of agile processes while developing safety-critical software (Heeager and Nielsen, 2018), and surveys show how several organizations have experimented with agile development of safety-critical software (McCaffery et al 2016;Notander et al 2013a). However, to fulfil the regulatory requirements while using agile processes, the development processes need to be tailored for this specific purpose (e.g.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Meshing agile and plan-driven development in safety-critical software: a case study

Heeager

Nielsen

2020

Empir Software Eng

Self Cite

View full text Add to dashboard Cite

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 safetycritical 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.

show abstract

Section: Agility In Safety-critical Software Developmentmentioning

confidence: 99%

Section: The Use Of Documentationmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Meshing agile and plan-driven development in safety-critical software: a case study

Heeager

Nielsen

2020

Empir Software Eng

Self Cite

View full text Add to dashboard Cite

show abstract

“…El objetivo del estudio fue comprender como se puede utilizar los procesos agiles en el desarrollo de software crítico para la seguridad. El análisis indica que el desarrollo incremental es más adecuado que el desarrollo iterativo para software crítico para la seguridad [27].…”

Section: Estado Del Arteunclassified

Estimation of effort in agile software development: Study of the current state in Bogotá

Bustamante

2020

ITECKNE

View full text Add to dashboard Cite

Context: Over the years, numerous studies have been developed related to estimating effort in agile software development, which allow us to understand the advances that have been made and the need for their use in companies. Objective: To know the perspective of entrepreneurs from different organizations in Bogotá that work in the sector or are related to the development of agile software and those who have had projects related to the subject. Method: For the elaboration of the article, a bibliographic research is carried out. Results: The data obtained are from 314 respondents in the city of Bogotá, the main findings are: 1) For companies it is extremely important with (34%) the adoption of an effort estimation methodology. 2) The most used estimation technique is the use case point with (43.31%). 3) The most used effort predictor is the Code Line (38.85%) and followed by this STORY POINT with (33.76%). 4) The agile methodology adopted in companies is SCRUM with (43.95%). 5) As the most determining factor to estimate the effort, the team experience with (53.50%) is considered. 6) In the percentage of error between estimate of projected effort and real effort (26.75%) of the respondents determine that this 5% -25% is underestimated. 7) Finally, as a difficulty in your company to estimate the effort of projects through agile software development, the respondents recognize (26.11%) that the resources are the greatest. Conclusions: The estimation of effort is relatively variable, for many companies this depends on the needs of each one, on the other hand, the use of agile methodology and estimation techniques varies in its use depending on the cross between them and how they are used. complement each other.

show abstract

“…Many standards acknowledge software components as essential parts of modern safety-critical systems and demand the fulfillment of a series of high-level safety requirements and process compliance obligations [Ebert 2015]. In the context of Agile Software Development (ASD) approaches, it is paramount that the production of certification documentation follows the system development [Heeager and Nielsen 2018].…”

Section: Problem Characterizationmentioning

confidence: 99%

Using Assurance Cases in Requirements Engineering for Safety-Critical Systems

Almendra¹,

Barros²,

Silva³

2019

Anais Estendidos Do X Congresso Brasileiro De Software: Teoria E Prática (CBSoft Estendido 2019)

View full text Add to dashboard Cite

Context: Certification of safety-critical systems (SCS) demands thorough documentation that demonstrates why a system shall be considered safe. Assurance Case Development (ACD) is an approach for discussing, analyzing and assessing the safety properties of systems. Software requirements of a SCS are an essential information included in assurance cases, alongside system design and safety analysis information. Lack of integrated analysis of requirements and safety concerns may lead to safety issues in the development of critical systems. One of the challenges for the agile development of SCS is to address both Requirements Engineering (RE) and ACD in an integrated way throughout the development life cycle. Objective: This research proposes a framework to integrate the Assurance Case Development and Agile RE in the development of SCS. Method: This research is organized in three main phases. First, a systematic mapping study is performed to understand how incremental ACD is addressed by current approaches, and a survey with experts is carried out to understand the development of ACs during Agile RE activities in practice. Second, the framework and its supporting tools and documentation will be designed and developed. Finally, a series of empirical studies will evaluate aspects of the framework in a multi-perspective manner and as long as it is developed. Conclusions: We expect that this approach contributes to leverage the development of ACs earlier and integrated with RE activities in agile development of SCS.

show abstract

A conceptual model of agile software development in a safety-critical context: A systematic literature review

Abstract: This is the accepted manuscript (post-print version) of the article. Contentwise, the accepted manuscript version is identical to the final published version, but there may be differences in typography and layout.

Cited by 52 publications

References 41 publications

Meshing agile and plan-driven development in safety-critical software: a case study

Meshing agile and plan-driven development in safety-critical software: a case study

Estimation of effort in agile software development: Study of the current state in Bogotá

Using Assurance Cases in Requirements Engineering for Safety-Critical Systems

Contact Info

Product

Resources

About