Supporting Embedded Medical Software Development with MDevSPICE® and Agile Practices

Authors: Surafel Demissie, Frank Keenan, Fergal McCaffery

Abstract:

Emerging medical devices are highly relying on embedded software that runs on the specific platform in real time. The development of embedded software is different from ordinary software development due to the hardware-software dependency. MDevSPICE^® has been developed to provide guidance to support such development. To increase the flexibility of this framework agile practices have been introduced. This paper outlines the challenges for embedded medical device software development and the structure of MDevSPICE^® and suggests a suitable combination of agile practices that will help to add flexibility and address corresponding challenges of embedded medical device software development.

Keywords: Agile practices, challenges, embedded software, MDevSPICE®, medical device.

Digital Object Identifier (DOI): doi.org/10.5281/zenodo.1129135

References:

[1] Espicom, “United States Medical Devices Report,” 2015. (Online). Available: http://www.espicom.com/usa-medical-device-market.html. (Accessed: 25-Feb-2016).
[2] Z. Jiang and R. Mangharam, “High-Confidence Medical Device Software Development,” Found. Trends® Electron. Des. Autom., vol. 9, no. 4, pp. 309–391, 2015.
[3] R. F. Munzner and D. Ph, “Entering the U. S. Medical Device Market,” pp. 3548–3550, 2003.
[4] AAMI, “AAMI TIR45: Guidance on the use of AGILE practices in the development of medical device software,” 2012.
[5] M. McHugh, F. McCaffery, and V. Casey, “Changes to the International Regulatory Environment,” J. Med. Device., vol. 6, no. 2, p. 21004, 2012.
[6] D. Greer and Y. Hamon, “Agile Software Development,” Aug. 2011.
[7] K. Beck, “Extreme Programming Explained: Embrace Change,” XP Ser., no. c, p. 224, 1999.
[8] K. Schwaber and M. Beedle, Agile Software Development with Scrum, vol. 18. 2001.
[9] S. R. Palmer and M. Felsing, “A Practical Guide to Feature-Driven Development,” Nov. 2001.
[10] N. Hrgarek, “Certification and regulatory challenges in medical device software development,” 2012 4th Int. Work. Softw. Eng. Heal. Care, SEHC 2012 - Proc., pp. 40–43, 2012.
[11] W. H. W. H. Wolf, “Hardware-software co-design of embedded systems,” Proc. IEEE, vol. 82, no. 7, pp. 967–989, 1994.
[12] J. Teich, “Hardware/software codesign: The past, the present, and predicting the future,” Proc. IEEE, vol. 100, no. SPL CONTENT, pp. 1411–1430, 2012.
[13] T. Dingsøyr, S. Nerur, V. Balijepally, and N. B. Moe, “A decade of agile methodologies: Towards explaining agile software development,” J. Syst. Softw., vol. 85, no. 6, pp. 1213–1221, 2012.
[14] VersionOne Inc, “VersionOne 10th Annual State of Agile Report,” 2016.
[15] K. Mar and K. Schwaber, “Scrum with XP,” Informit. com, 2002.
[16] H. Kniberg, Scrum and XP from the Trenches. Lulu. com, 2015.
[17] Z. Mushtaq and M. R. J. Qureshi, “Novel Hybrid Model: Integrating Scrum and XP,” Int. J. Inf. Technol. Comput. Sci., vol. 4, no. 6, pp. 39–44, 2012.
[18] H. Jonsson, S. Larsson, and S. Punnekkat, “Agile Practices in Regulated Railway Software Development,” in 2012 IEEE 23rd International Symposium on Software Reliability Engineering Workshops, 2012, pp. 355–360.
[19] B. Fitzgerald, K. J. Stol, R. O’Sullivan, and D. O’Brien, “Scaling agile methods to regulated environments: An industry case study,” Proc. - Int. Conf. Softw. Eng., pp. 863–872, 2013.
[20] F. McCaffery, M. Pikkarainen, and I. Richardson, “Ahaa --agile, hybrid assessment method for automotive, safety critical smes,” Int. Conf. Softw. Eng., p. 9, 2008.
[21] T. Myklebust, T. Stalhane, and N. Lyngby, “An agile development process for petrochemical safety conformant software,” in 2016 Annual Reliability and Maintainability Symposium (RAMS), 2016, no. Fitzgerald, pp. 1–6.
[22] S. H. VanderLeest and A. Buter, “Escape the waterfall: Agile for aerospace,” in 2009 IEEE/AIAA 28th Digital Avionics Systems Conference, 2009, p. 6.D.3-1-6.D.3-16.
[23] R. Y. Takahira, L. R. Laraia, F. A. Dias, A. S. Yu, P. T. S. Nascimento, and A. S. Camargo, “Scrum and Embedded Software development for the automotive industry,” Proc. PICMET ’14 Conf. Portl. Int. Cent. Manag. Eng. Technol. Infrastruct. Serv. Integr., pp. 2664–2672, 2014.
[24] R. Rasmussen, T. Hughes, J. R. Jenks, and J. Skach, “Adopting agile in an FDA regulated environment,” Proc. - 2009 Agil. Conf. Agil. 2009, pp. 151–155, 2009.
[25] P. A. Rottier and V. Rodrigues, “Agile Development in a Medical Device Company,” Agil. 2008 Conf., pp. 218–223, 2008.
[26] B. Haugset and G. K. Hanssen, “The Home Ground of Automated Acceptance Testing: Mature Use of FitNesse,” in 2011 AGILE Conference, 2011, pp. 97–106.
[27] L. W. Alistair Cockburn, “The Costs and Benefits of Pair Programming,” Extrem. Program. examined, pp. 223–247, 2000.
[28] Hoby Van Hoose, “Experience Design and Cross-Functional Pairing - SolutionsIQ,” 2013. (Online). (Accessed: 11-Oct-2016). Available: http://www.solutionsiq.com/experience-design-and-cross-functional-pairing/.
[29] James E. Hewson, “Cross-functional pair programming | Embedded,” 2003. (Online). (Accessed: 11-Oct-2016). Available: http://www.embedded.com/design/prototyping-and development/4024901/Cross-functional-pair-programming.
[30] B. F. Hanks, “Distributed Pair Programming: An Empirical Study,” Springer Berlin Heidelberg, 2004, pp. 81–91.
[31] J. Ronkainen and P. Abrahamsson, “Software development under stringent hardware constraints: do agile methods have a chance?,” Extrem. Program. Agil. Process. Softw. Eng., pp. 1012–1012, 2003.
[32] K. Beck, “Test-Driven Development By Example,” Rivers, vol. 2, no. c, p. 176, 2003.
[33] R. Jeffries and G. Melnik, “TDD--The Art of Fearless Programming,” Software, IEEE, vol. 24, no. 3, pp. 24–30, 2007.
[34] M. Karlesky, W. Bereza, and C. Erickson, “Effective Test Driven Development for Embedded Software,” in 2006 IEEE International Conference on Electro/Information Technology, 2006, no. 616, pp.382–387.
[35] ISO/IEC 15504-5. Information technology – process assessment - Part 5: an exemplar process assessment model. 2012. p. 211
[36] IEC TR 80002-3: Medical device software -- Part 3: Process reference model of medical device software life cycle processes (IEC 62304). 2014. IEC: Geneva, Switzerland. p.23.