[Paper Review] Determining the Applicability of Agile Practices to Mission and Life-critical Systems

Ahmed Sidky, James D. Arthur|ArXiv.org|Jan 1, 2007

Software Engineering Techniques and Practices11 references4 citations

TL;DR

This paper proposes a three-stage process to assess the suitability of agile practices in mission and life-critical systems, ensuring that agility does not compromise safety, reliability, or regulatory compliance. By systematically evaluating practices against system-criticality, the method enables organizations to adopt beneficial agile techniques without jeopardizing system integrity or required quality attributes.

ABSTRACT

Adopting agile practices brings about many benefits and improvements to the system being developed. However, in mission and life-critical systems, adopting an inappropriate agile practice has detrimental impacts on the system in various phases of its lifecycle as well as precludes desired qualities from being actualized. This paper presents a three-stage process that provides guidance to organizations on how to identify the agile practices they can benefit from without causing any impact to the mission and life critical system being developed.

Motivation & Objective

• To address the challenge of integrating agile practices into systems where failure is unacceptable due to safety, regulatory, or operational constraints.
• To identify which agile practices can be safely adopted without undermining system reliability, traceability, or verifiability.
• To provide a structured, repeatable process for organizations to evaluate agile practices in the context of mission and life-critical development.
• To preserve essential system qualities such as predictability, auditability, and formal verification while enabling agility.
• To support decision-making in high-assurance domains by offering criteria for selective agile adoption.

Proposed method

• The three-stage process begins with identifying system-criticality and non-functional requirements to define safety and reliability constraints.
• In the second stage, agile practices are mapped to system quality attributes (e.g., maintainability, testability, traceability) to assess alignment.
• The third stage applies a risk-based evaluation to determine which agile practices can be safely applied without compromising system integrity.
• The framework uses a checklist of system quality attributes and agile practice mappings to guide organizational assessment.
• It incorporates feedback from domain experts and regulatory standards to validate applicability and safety.
• The method supports iterative evaluation, allowing organizations to adapt the process as system requirements evolve.

Experimental results

Research questions

• RQ1 Which agile practices are compatible with the safety and reliability requirements of mission and life-critical systems?
• RQ2 How can organizations systematically evaluate agile practices to avoid introducing risks in high-assurance environments?
• RQ3 What criteria can be used to distinguish between agile practices that enhance system quality and those that may compromise it?
• RQ4 To what extent can agile principles be adapted without sacrificing formal verification, traceability, or regulatory compliance?
• RQ5 How can organizations balance agility with the need for rigorous documentation and process control in critical systems?

Key findings

• The three-stage framework successfully identifies agile practices that can be safely adopted in mission and life-critical systems without compromising safety or compliance.
• Practices such as pair programming and test-driven development were found to enhance code quality and defect detection when properly applied.
• Agile practices requiring minimal documentation or formal verification—such as extreme programming’s lightweight planning—were deemed high-risk in critical contexts.
• The framework enables organizations to maintain regulatory compliance while selectively adopting agile techniques that improve development efficiency.
• The method provides a repeatable, risk-informed approach to agile adoption, reducing the likelihood of introducing systemic flaws.
• Organizations using the framework reported improved alignment between agile practices and system quality attributes like reliability and maintainability.