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

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

doi:10.1504/ijccbs.2011.041259

Cited by 8 publications

(15 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Requirements tend to be more volatile (even late in the development process), calling for better approaches to manage requirements and their changes in more flexible ways [5,15,16]. We also see an increased customer orientation where industry wants to listen more closely to customers [1,3,16,21,22], opening up for a more flexible development process with less emphasis on complete and detailed up-front design. Experience also indicates that cost and schedule overruns are happening too frequently [1,4].…”

Section: Why This Interest In Agile Methods?mentioning

confidence: 99%

See 1 more Smart Citation

An Assessment of Avionics Software Development Practice: Justifications for an Agile Development Process

Hanssen

Wedzinga

Stuip

2017

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Avionic systems for communication, navigation, and flight control, and many other functions are complex and crucial components of any modern aircraft. Present day avionic systems are increasingly based on computers and a growing percentage of system complexity can be attributed to software. An error in the software of a safety-critical avionic system could lead to a catastrophic event, such as multiple deaths and loss of the aircraft. To demonstrate compliance with airworthiness requirements, certification agencies accept the use of RTCA document DO-178 for the software development. Avionics software development is typically complex and is traditionally reliant on a strict plan-driven development process, characterized by early fixture of detailed requirements and late production of working software. In this process, requirement changes and solving software errors can lead to much rework, and create a risk of budget and schedule overruns. This raises the question whether avionics software development could benefit from the application of agile approaches. Based on the results of three activities: (1) a literature study on industrial experience with the use of agile methods in a DO-178 context, (2) an expert assessment of the DO-178 objectives, and (3) a survey conducted among European avionics industry, an outline is presented of an agile development process, where Scrum is extended to achieve the DO-178 objectives. The application of agile methods is expected to support frequent delivery of working software and ability to respond to changes, resulting in reduced risk of budget and schedule overruns.

show abstract

Section: Why This Interest In Agile Methods?mentioning

confidence: 99%

“…Some empirical data is presented in only three of the papers. Wils et al [22] provide some minor insights from the Barco company, Paige et al [16] present a very small-scale experiment, and Carlson and Turner [1] make a review of five case studies.…”

Section: Overview Of Existing Research and Industry Experiencementioning

confidence: 99%

An Assessment of Avionics Software Development Practice: Justifications for an Agile Development Process

Hanssen

Wedzinga

Stuip

2017

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…DO-178B) and helpful in addressing engineering challenges, such as dealing with changes in requirements and their consequent effects [19], and supporting evidence-based safety assurance approach [9].…”

Section: Examplementioning

confidence: 99%

“…In the context of safety-critical software, change management is more challenging in comparison to general software development. This is because safety is not compositional and any change generally requires having to perform the safety process again [19]. Additionally, the system should be certified before entering the operational environment to show that it is acceptably safe, which normally requires creating a safety case.…”

Section: Examplementioning

confidence: 99%

“…These challenges include ensuring that evidence is available to demonstrate that safety requirements have been met [16], dealing with changing requirements and the corresponding effects on certification arguments [19], and supporting evidence-based safety assurance [9]. However, evolution of artefacts (including DSMLs and trace models) in domains like safety is problematic, because safety is not compositional -that is, if a system has been shown to be acceptably safe to operate (i.e., safety requirements are met), and an engineering artefact evolves, then the safety process has to be fully re-executed.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Agile requirements traceability using domain-specific modelling languages

Taromirad

Paige

2012

Proceedings of the 2012 Extreme Modeling Workshop

Self Cite

View full text Add to dashboard Cite

Requirements traceability is an important mechanism for managing verification, validation and change impact analysis challenges in system engineering. Numerous modelbased approaches have been proposed to support requirements traceability, but significant challenges remain, including finding the appropriate level of granularity for modelling traceability and coping with the lack of uniformity in requirements management tools. This paper argues for an agile modelling approach to managing requirements traceability and, in this context, proposes a domain/project-specific requirements traceability modelling approach. The preliminary approach is illustrated briefly in the context of the safety-critical systems engineering domain, where agile traceability from functional and safety requirements is necessary to underpin certification.

show abstract

Safety and Risk Documents

Myklebust

Stålhane

2021

Functional Safety and Proof of Compliance

View full text Add to dashboard Cite

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

Cited by 8 publications

References 0 publications

An Assessment of Avionics Software Development Practice: Justifications for an Agile Development Process

An Assessment of Avionics Software Development Practice: Justifications for an Agile Development Process

Agile requirements traceability using domain-specific modelling languages

Safety and Risk Documents

Contact Info

Product

Resources

About