Investigation of Traceability within a Medical Device Organization - Abstract and Study Overview

Sep 12, 2026

Upload by Aurora

Requirements traceability is critical for achieving software quality by enabling impact analysis, regression test selection, and compliance verification and validation throughout the requirements lifecycle. Although promoted by research and expert practice communities, evidence shows many software organizations avoid implementation due to cost and complexity. In safety-critical medical device domains, organizations are mandated to implement traceability yet struggle with efficiency and ongoing compliance, prompting targeted investigation.

LanguageEnglish

CategoryGeneral

FormatPDF

Pages12

Reading Time4 min

AccessFree to download

1 Introduction

Importance of traceability

Regulatory and standards context

2 Related Work

Trace and traceability concepts

Requirements traceability definition

Investigation of Traceability within a Medical Device Organization Gilbert Regan , Fergal Mc Caffery , Kevin Mc Daid , Derek Flood Dundalk Institute of Technology , Dundalk , Ireland {gilbert.regan, fergal.mccaffery, kevin.mcdaid, [derek.flood}@dkit.ie](derek.flood}@dkit.ie) Abstract. Requirements traceability helps to ensure software quality. It supports quality assurance activities such as impact analysis, regression test selection, compliance verification and validation of requirements. Its implementation has long been promoted by the research and expert practitioner communities. However, evidence indicates that few software organizations choose to implement traceability processes, in the most part due to cost and complexity issues. Organizations operating within the safety critical domains are mandated to implement traceability, and find the implementation and maintenance of an efficient and compliant traceability process a difficult and complex issue. Through interviews with a medical device SME, this paper seeks to determine how traceability is implemented within the organization, the difficulties it faces in implementing traceability, how compliant it is with the medical device standards and guidelines, and what changes could be made to improve the efficiency of their traceability implementation and maintenance. Keywords: traceability, requirements traceability, software traceability, medical device, software process improvement 1 Introduction The importance and role of traceability in supporting software development have been long recognised [1] . Requirements tracing helps ensure that the customers’requirements are being met and that the quality of the final product is maximised while minimising costly rework due to errors in the requirements. Traceability through the software development and risk management process is particularly important in safety critical industries such as the medical device domain, where it is incumbent on manufacturers to produce safe software [2] . The effect of poor quality medical device software can be seen from the recent announcement by Johnson & Johnson that some of its Animas insulin pumps will become defunct at the stroke of midnight on December 31, 2015 . The company has warned European regulators that the pumps will stop delivering insulin at the start of 2016 and will generate a "call service alarm" due to a software fault. During November 2012 the company began to warn patients of the impending malfunction, offering to replace devices that have warranties that will still be in effect when the software glitch is expected to hit [3] . Organizations building safety critical systems are often legally required to demonstrate that all parts of the code trace back to valid requirements. Laws such asthe US Sarbanes-Oxley Act 2002 [4] require organizations to implement change management processes with explicit traceability coverage for any parts of a software product that potentially impact the balance sheet [5] . Regulations and guidelines exist to assist medical device organisations to produce quality software. The documents which medical device manufacturers must adhere to are IEC 62304 [6] (which is endorsed by the European Union and the U.S.), FDA Guidance for the Content of Pre-market Submission for Software in Medical Devices [7], FDA General Principles of Software Validation(GPSV) [8], FDA Off-the Shelf Software Use in Medical Devices [9] and ISO 14971 [10] . These documents emphasise to different degrees the requirement for traceability through the software development lifecycle (SDLC), risk management and change management processes. Understanding the different degrees of requirements for traceability and implementing those requirements is a difficult and complex task for a medical device small to medium enterprise (SME) . A lack of detailed guidance and direction on how to implement and maintain traceability could lead to many medical device SMEs implemen

FAQs

Why is requirements traceability important in medical device software development?

Requirements traceability supports software quality by ensuring requirements are met and by enabling impact analysis and regression test selection. It is especially important in medical device domains where manufacturers must produce safe software and demonstrate coverage of code to valid requirements.

What standards and guidelines emphasize traceability in the medical device lifecycle?

Key documents include IEC 62304, FDA guidance for pre-market software submission content, FDA General Principles of Software Validation (GPSV), FDA guidance on off-the-shelf software use, and ISO 14971. These documents describe expectations for traceability across SDLC, risk management, and change management.

How does the paper investigate traceability implementation in practice?

The paper conducts interviews with a medical device SME to determine how traceability is implemented, what difficulties arise, and how compliant the organization is with relevant standards and guidelines. It also identifies potential changes to improve the efficiency of traceability implementation and maintenance.

Sep 12, 2026

Upload by Aurora