DevOps in Regulated Software Development: Case Medical Devices
Authors:
- Teemu LaukkarinenTLTeemu Laukkarinen
- Kati KuusinenKKKati Kuusinen
- Tommi MikkonenTMTommi Mikkonen
- 1 May 2017
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 15-18
Abstract
DevOps and continuous development are getting popular in the software industry. Adopting these modern approaches in regulatory environments, such as medical device software, is not straightforward because of the demand for regulatory compliance. While DevOps relies on continuous deployment and integration, regulated environments require strict audits and approvals before releases. Therefore, the use of modern development approaches in regulatory environments is rare, as is the research on the topic. However, as software is more and more predominant in medical devices, modern software development approaches become attractive. This paper discusses the fit of DevOps for regulated medical device software development. We examine two related standards, IEC 62304 and IEC 82304-1, for obstacles and benefits of using DevOps for medical device software development. We found these standards to set obstacles for continuous delivery and integration. Respectively, development tools can help fulfilling the requirements of traceability and documentation of these standards.Keywords
This publication has 5 references indexed in Scilit:
- DevOpsIEEE Software, 2016
- Towards DevOps in the Embedded Systems Domain: Why is It So Hard?2016
- An agile V-model for medical device software development to overcome the challenges with plan-driven software development lifecycles2013
- Lean/Agile Software Development Methodologies in Regulated Environments – State of the Art2010
- SCRUM Development Process1997