Logo PTI
Polish Information Processing Society
Logo FedCSIS

Annals of Computer Science and Information Systems, Volume 8

Proceedings of the 2016 Federated Conference on Computer Science and Information Systems

AgileSafe – a method of introducing agile practices into safety-critical software development processes


DOI: http://dx.doi.org/10.15439/2016F360

Citation: Proceedings of the 2016 Federated Conference on Computer Science and Information Systems, M. Ganzha, L. Maciaszek, M. Paprzycki (eds). ACSIS, Vol. 8, pages 15491552 ()

Full text

Abstract. This article introduces AgileSafe, a new method of incorporating agile practices into critical software development while still maintaining compliance with the software assurance requirements imposed by the application domain. We present the description of the method covering the process of its application and the input and output artefacts.


  1. A. Kaczorowska, “Traditional And Agile Project Management In Public Sector And ICT,” in Proceedings of the Federated Conference on Computer Science and Information Systems (FedCSIS), Łódź, Poland, September 2015. http://dx.doi.org/10.15439/2015F279
  2. G. B Alleman., M Henderson., C. H. M. Hill, R.Seggelke, “Making Agile Development Work in a Government Contracting Environment Measuring velocity with Earned Value,” in Proceedings of the Agile Development Conference 2003, Salt Lake City, Utah, June 2003. http://dx.doi.org/10.1109/ADC.2003.1231460
  3. R. Paige, R. Charalambous, X. Ge, P. Brooke, “Towards Agile Engineering of High- Integrity Systems,” in Proceedings of 27th International Conference on Computer Safety, Reliability and Security (SAFECOMP), September 2008. http://dx.doi.org/10.1007/978-3-540-87698-4_6
  4. K. Petersen, C. Wohlin, “The effect of moving from a plan-driven to an incre- mental software development approach with agile practices,” in Empirical Software Engineering, 15(6):654–693, 2010. http://dx.doi.org/10.1007/s10664-010-9136-6
  5. R. Rasmussen, T. Hughes, J. R. Jenks, J. Skach, “Adopting Agile in an FDA Regulated Environment,” in Proceedings of Agile Conference, Chicago, USA, August 2009. http://dx.doi.org/10.1109/AGILE.2009.50
  6. J. Górski, K. Łukasiewicz. „Assessment of Risks Introduce to Safety Critical Software by Agile Practices – a Software Engineer’s Perspective“ in. Computer Science, 13(4), AGH University of Science and Technology Press 2012. http://dx.doi.org/http://dx.doi.org/10.7494/csci.2012.13.4.165
  7. AAMI TIR45: 2012 Technical Information Report Guidance on the use of AGILE practices in the development of medical device software
  8. ISO/IEC 62304 Medical device software — Software life cycle processes, standard
  9. SafeScrum, http://www.sintef.no/safescrum
  10. T. Stålhane, T. Myklebust, G. K. Hanssen, “Safety standards and Scrum – A synopsis of three standards”, http://www.sintef.no/globalassets/safety-standards-and- scrum_may2013.pdf
  11. M. Mc Hugh, F. Mc Caffery, G. Coady “An Agile Implementation within a Medical Device Software Organisation”, in Proceedings of The 14th International SPICE Conference Process Improvement and Capability dEtermination 2014. http://dx.doi.org/10.1007/978-3-319-13036-1_17
  12. ISO/IEC 15026 Systems and software engineering -- Systems and software assurance
  13. C. B. Weinstock, J. B. Goodenough. “Towards an Assurance Case Practice for Medical Devices”. TECHNICAL NOTE Software Engineering Institute October 2009. http://www.sei.cmu.edu/reports/09tn018.pdf
  14. FDA: Guidance – Total Product Life Cycle: Infusion Pump-Premarket Notification Submissions [510(k)], 2010
  15. J. Górski, “Trust Case – a case for trustworthiness of IT infrastructures” in Cyberspace Security and Defense: Research Issues, NATO Science Series II: Mathematics, Physics and Chemistry, 196 (). Springer-Verlag, pp. 125-142 (2005). http://dx.doi.org/10.1007/1-4020-3381-8_7
  16. Argevide NOR-STA, https://www.argevide.com/en