Extreme programming explained: embrace change
Extreme programming explained: embrace change
Agile software development
Software Engineering Economics
Software Engineering Economics
Efficient authoring of software documentation using RaPiD7
Proceedings of the 25th International Conference on Software Engineering
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
Breaking the Ice for Agile Development of Embedded Software: An Industry Experience Report
Proceedings of the 26th International Conference on Software Engineering
Ahaa --agile, hybrid assessment method for automotive, safety critical smes
Proceedings of the 30th international conference on Software engineering
Empirical Software Engineering
Adopting agile practices in teams with no direct programming responsibility - a case study
PROFES'11 Proceedings of the 12th international conference on Product-focused software process improvement
Hi-index | 0.00 |
This paper takes a look at how XP and other agile practices can improve a software process for the development of avionics software. Developers of mission critical airborne software are heavily constrained by the RTCA DO-178B regulations [8]. These regulations impose strict rules regarding traceability and documentation that make it extremely hard to employ an iterative software development process. In particular, the extra validation overhead increases the time spent on small iteration cycles (for example, a bug-fix) to several weeks. Currently, this sector is also pressed to switch to a more agile, customer driven approach. In this paper we investigate how to speed up development and cope with changing requirements using agile techniques. The research was carried out in cooperation with Barco, a major Belgian avionics equipment supplier. We explain why certain agile techniques have less effect as the project progresses. We point out the stadia in which each XP practice is beneficial and where XP practices might cause a slowdown.