The significance of requirements in medical device software development

Software to be used in or as a medical device is subject to user requirements. However, unlike unregulated software, medical device software must meet both the user’s requirements and the requirements of the regulatory body of the region into which the software will be marketed. Regulatory requirements are fixed and can be planned for; unfortunately, the same is not true with user requirements. As many medical device software development organisations are following traditional sequential Software Development Life Cycles (SDLC), they are experiencing difficulties accommodating changes in requirements once development has begun. Agile methods and practices offer the ability to overcome the challenges associated with following a sequential SDLC. Whilst the regulatory requirements are fixed, this paper presents these requirements and shows how they appear to mandate the use of a sequential SDLC. This paper also explains how agile methods and practices can be successfully adopted in the development of medical device software without hindering the process of achieving regulatory approval.

[1]  Osman Balci,et al.  Verification, Validation, and Testing , 2007 .

[2]  Ali Mohsenzadeh,et al.  The impact of agile methods on software project management , 2005, 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'05).

[3]  Abdelwahab Hamou-Lhadj,et al.  Investigating the Capability of Agile Processes to Support Life-Science Regulations: The Case of XP and FDA Regulations with a Focus on Human Factor Requirements , 2010, SERA.

[4]  Martin Höst,et al.  A Snapshot of the State of Practice in Software Development for Medical Devices , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[5]  Fergal McCaffery,et al.  Medical Device Software Traceability , 2012, Software and Systems Traceability.

[6]  Fergal McCaffery,et al.  Standalone Software as an Active Medical Device , 2011, SPICE.

[7]  Frank Maurer,et al.  Requirements engineering and agile software development , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[8]  Mike Cohn,et al.  Succeeding with Agile: Software Development Using Scrum , 2009 .

[9]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[10]  Whole Grain Label Statements.  Guidance for Industry and FDA Staff , 2006 .

[11]  Jane Cleland-Huang,et al.  A machine learning approach for tracing regulatory codes to product specific requirements , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[12]  Slim Kallel,et al.  Enabling Technologies: Infrastructure for Collaborative Enterprises , 2015, Comput. J..

[13]  Martin Mc Hugh,et al.  Barriers to Using Agile Software Development Practices within the Medical Device Industry , 2012 .

[14]  Fergal Mc Caffery,et al.  Med-Trace: Traceability Assessment Method for Medical Device Software Development , 2011 .

[15]  Fergal Mc Caffery,et al.  The Need for a Software Process Improvement Model for the Medical Device Industry , 2007 .

[16]  Franco Pavese,et al.  Data modeling for metrology and testing in measurement science , 2009 .

[17]  Fergal McCaffery,et al.  Verification & Validation in Medi SPICE , 2011, SPICE.

[18]  Aristides Dasso.  Verification, Validation And Testing In Software Engineering , 2006 .

[19]  Thomas H. Faris,et al.  Safe and Sound Software: Creating an Efficient and Effective Quality System for Software Medical Device Organizations , 2006 .

[20]  Paul L Jones,et al.  Risk management in the design of medical device software systems. , 2002, Biomedical instrumentation & technology.

[21]  Carl T. DeMarco.  Medical Device Design and Regulation , 2011 .