Challenges Experienced by Medical Device Software Organisations while following a Plan-driven SDLC

Medical device software organisations face challenges not faced by generic software development organisations. These challenges include the adherence to regulatory controls. Regulatory bodies require medical device software organisations to provide objective evidence that the software they are developing is safe and reliable. To produce this, regulatory bodies require a number of deliverables which must be achieved. However, they do not dictate which Software Development Life Cycle (SDLC) must be followed in order to achieve these deliverables. Despite not dictating which SDLC must be followed when developing medical device software, organisations typically develop their software in accordance with a Plan-Driven software development lifecycle. By conducting semi structured interviews with seven medical device software organisations, we gained a deeper insight into how the challenges experienced impact on the development of medical device software. The interviews also attempted to learn from the participants how they believe the challenges experienced can be overcome. The aim of this paper is to explain the methodology used to perform interviews with medical device software organisations and to present these interviews

Adopting Agile Practices when Developing Medical Device Software

Agile methods are gaining momentum amongst the developers of non-safety critical software. They offer the ability to improve development time, increase quality and reduce development costs. Despite this, the rate of adoption of agile methods within safety critical domains remains low. On face value agile methods appear to be contradictory to regulatory requirements. However while they may appear contradictory, they align on key values such as the development of the highest quality software. To demonstrate that agile methods could in fact be adopted when developing regulatory compliant software they were implemented on a medical device software development project. This implementation showed that not only can agile methods be successfully followed, but it also revealed that benefits were acquired. For example, the medical device software development project was completed 7% faster when following agile methods, when compared to if it had been completed in accordance with a plan-driven approach. While this implementation is confined to a single project, within a single organization it does strengthen the belief that adopting agile methods within regulated domains can reap the same benefits as those acquired in non-safety critical domains

How Can Software SMEs Become Medical Device

The amount of software content within medical devices has grown considerably over recent years and will continue to do so as the level of complexity of medical devices increase. This is driven by the fact that software is introduced to produce sophisticated medical devices that would not be possible using only hardware. This therefore presents opportunities for software development SMEs to become medical device software development organisations. However, some obstacles need to be addressed and overcome in order to make the transition from being a generic software development organisation to becoming a medical device software development organisation. This paper describes these obstacles and how research that is currently being performed within the Regulated Software Research Group in Dundalk Institute of Technology may be used to assist with this transitio

Adopting Agile Practices When Developing Software for Use in the Medical Domain

Non-safety critical software developers have been reaping the benefits of adopting agile practices for a number of years. However, developers of safety critical software often have concerns about adopting agile practices. Through performing a literature review, this research has identified the perceived barriers to following agile practices when developing medical device software. A questionnaire based survey was also conducted with medical device software developers in Ireland to determine the barriers to adopting agile practices. The survey revealed that half of the respondents develop software in accordance with a plan driven software development lifecycle and that they believe that there are a number of perceived barriers to adopting agile practices when developing regulatory compliant software such as: being contradictory to regulatory requirements; insufficient coverage of risk management activities and the lack of up-front planning. In addition, a comparison is performed between the perceived and actual barriers. Based upon the findings of the literature review and survey, it emerged that no external barriers exist to adopting agile practices when developing medical device software and the barriers that do exists are internal barriers such as getting stakeholder buy in

The mat sat on the cat : investigating structure in the evaluation of order in machine translation

We present a multifaceted investigation into the relevance of word order in machine translation. We introduce two tools, DTED and DERP, each using dependency structure to detect differences between the structures of machine-produced translations and human-produced references. DTED applies the principle of Tree Edit Distance to calculate edit operations required to convert one structure into another. Four variants of DTED have been produced, differing in the importance they place on words which match between the two sentences. DERP represents a more detailed procedure, making use of the dependency relations between words when evaluating the disparities between paths connecting matching nodes. In order to empirically evaluate DTED and DERP, and as a standalone contribution, we have produced WOJ-DB, a database of human judgments. Containing scores relating to translation adequacy and more specifically to word order quality, this is intended to support investigations into a wide range of translation phenomena. We report an internal evaluation of the information in WOJ-DB, then use it to evaluate variants of DTED and DERP, both to determine their relative merit and their strength relative to third-party baselines. We present our conclusions about the importance of structure to the tools and their relevance to word order specifically, then propose further related avenues of research suggested or enabled by our work

Integrating Agile Practices with a Medical Device SDLC.

The rate at which agile software development practices are being adopted is growing rapidly. Agile software development practices and methodologies appear to offer the silver bullet which can solve the problems associated with following plan driven software development lifecycles. Agile software development practices offer the possibility of achieving lower development costs, increased efficiency and improved software quality. However, there is currently a low rate of publicly available information that suggests there is widespread adoption of agile practices within the medical device software domain. This is largely due to the fact that software developed for medical devices includes challenges not faced when developing non safety critical software. As a result of these challenges, medical device software is typically developed using plan driven software development lifecycles. However, such lifecycles are quite rigid and cannot accommodate changes easily. Previous research has revealed that medical device software development projects can benefit from adopting agile practices whilst still maintaining the discipline associated with following plan driven development lifecycles. This paper outlines the challenges faced by developers when developing medical device software and how shortcomings in both agile and plan driven approaches can be resolved by following a mixed method approach to medical device software developmen

Improving Safety in Medical Devices from Concept to Retirements

As with many domains the use of software within the healthcare industry is on the rise [1, 2] within the last 20 years

An Agile V-Model for Medical Device Software Development to Overcome the Challenges with Plan Driven SDLCs

Through the use of semi structured interviews with medical device software organizations it emerged that medical device software organizations are experiencing difficulties when following plan driven Software Development Life Cycles (SDLC), particularly in the area of requirements management. To attempt to resolve these issues an examination of the non-regulated industry was performed to determine if lessons learned there could be applied to the development of medical device software. This examination revealed that agile methods are being widely adopted in the non-regulated software industry. To learn if agile methods could be adopted when developing medical device software a mapping study was performed which looked for instances of where agile methods have been used in regulated industries and where they have been adopted, to what success. This mapping study revealed that incorporating agile practices with the existing plan driven SDLC is the most favourable choice for medical device software organizations. This research aims to develop a SDLC which has a foundation of a plan driven SDLC which incorporates agile practices which can be followed when developing regulatory compliant software

Defining functional classes of Barth syndrome mutation in humans

The X-linked disease Barth syndrome (BTHS) is caused by mutations in TAZ; TAZ is the main determinant of the final acyl chain composition of the mitochondrial-specific phospholipid, cardiolipin. To date, a detailed characterization of endogenous TAZ has only been performed in yeast. Further, why a given BTHS-associated missense mutation impairs TAZ function has only been determined in a yeast model of this human disease. Presently, the detailed characterization of yeast tafazzin harboring individual BTHS mutations at evolutionarily conserved residues has identified seven distinct loss-of-function mechanisms caused by patient-associated missense alleles. However, whether the biochemical consequences associated with individual mutations also occur in the context of human TAZ in a validated mammalian model has not been demonstrated. Here, utilizing newly established monoclonal antibodies capable of detecting endogenous TAZ, we demonstrate that mammalian TAZ, like its yeast counterpart, is localized to the mitochondrion where it adopts an extremely protease-resistant fold, associates non-integrally with intermembrane space-facing membranes and assembles in a range of complexes. Even though multiple isoforms are expressed at the mRNA level, only a single polypeptide that co-migrates with the human isoform lacking exon 5 is expressed in human skin fibroblasts, HEK293 cells, and murine heart and liver mitochondria. Finally, using a new genome-edited mammalian BTHS cell culture model, we demonstrate that the loss-of-function mechanisms for two BTHS alleles that represent two of the seven functional classes of BTHS mutation as originally defined in yeast, are the same when modeled in human TAZ