<mets:mets OBJID="eprint_407" LABEL="Eprints Item" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mets="http://www.loc.gov/METS/" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mets:metsHdr CREATEDATE="2017-11-03T18:10:43Z"><mets:agent ROLE="CUSTODIAN" TYPE="ORGANIZATION"><mets:name>STÓR</mets:name></mets:agent></mets:metsHdr><mets:dmdSec ID="DMD_eprint_407_mods"><mets:mdWrap MDTYPE="MODS"><mets:xmlData><mods:titleInfo><mods:title>A Traceability Process Assessment Model for the Medical Device Domain</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Gilbert</mods:namePart><mods:namePart type="family">Regan</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Miklos</mods:namePart><mods:namePart type="family">Biro</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Fergal</mods:namePart><mods:namePart type="family">McCaffery</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Kevin</mods:namePart><mods:namePart type="family">McDaid</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Derek</mods:namePart><mods:namePart type="family">Flood</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Traceability of requirements through the software development lifecycle (including supporting processes such as risk management and change management) is a difficult and expensive task. The implementation of effective traceability allows organizations to leverage its many advantages, such as impact analysis, product verification and validation, and facilitation of code maintenance. Traceability is conducive to producing quality software.&#13;
Within the medical device domain, as in other safety critical domains, software must provide reliability, safety and security because failure to do so can lead to injury or death. However, despite its criticality most software systems don’t employ explicit traceability between artefacts. Numerous barriers hamper the effective implementation of traceability such as cost, complexity of relationship between artefacts, calculating a return on investment, different stakeholder viewpoints, lack of awareness of traceability and a lack of guidance as to how to implement traceability. &#13;
To assist medical device organisations in addressing the lack of guidance on how to implement effective traceability, this paper aims to present the devel-opment of a traceability process assessment model and how traceability process assessment and maintenance could be fully automated using the Open Services for Lifecycle Collaboration (OSLC) initiative. The process assessment model will allow organisations to identify strengths and weaknesses in their existing traceability process and pinpoint areas for improvement.&#13;
</mods:abstract><mods:classification authority="lcc">Computer Science</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8061">2014-06</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mets:xmlData></mets:mdWrap></mets:dmdSec><mets:amdSec ID="TMD_eprint_407"><mets:rightsMD ID="rights_eprint_407_mods"><mets:mdWrap MDTYPE="MODS"><mets:xmlData><mods:useAndReproduction>
<p xmlns="http://www.w3.org/1999/xhtml"><strong>For work being deposited by its own author:</strong> 
In self-archiving this collection of files and associated bibliographic 
metadata, I grant STÓR the right to store 
them and to make them permanently available publicly for free on-line. 
I declare that this material is my own intellectual property and I 
understand that STÓR does not assume any 
responsibility if there is any breach of copyright in distributing these 
files or metadata. (All authors are urged to prominently assert their 
copyright on the title page of their work.)</p>

<p xmlns="http://www.w3.org/1999/xhtml"><strong>For work being deposited by someone other than its 
author:</strong> I hereby declare that the collection of files and 
associated bibliographic metadata that I am archiving at 
STÓR) is in the public domain. If this is 
not the case, I accept full responsibility for any breach of copyright 
that distributing these files or metadata may entail.</p>

<p xmlns="http://www.w3.org/1999/xhtml">Clicking on the deposit button indicates your agreement to these 
terms.</p>
    </mods:useAndReproduction></mets:xmlData></mets:mdWrap></mets:rightsMD></mets:amdSec><mets:fileSec><mets:fileGrp USE="reference"><mets:file ID="eprint_407_1131_1" SIZE="132841" OWNERID="http://eprints.dkit.ie/407/1/EUROSPI%202014%20A%20Traceability%20Process%20Assessment%20Model%20for%20the%20Medical%20Device%20Domain.docx" MIMETYPE="application/vnd.openxmlformats-officedocument.wordprocessingml.document"><mets:FLocat LOCTYPE="URL" xlink:type="simple" xlink:href="http://eprints.dkit.ie/407/1/EUROSPI%202014%20A%20Traceability%20Process%20Assessment%20Model%20for%20the%20Medical%20Device%20Domain.docx"></mets:FLocat></mets:file></mets:fileGrp></mets:fileSec><mets:structMap><mets:div DMDID="DMD_eprint_407_mods" ADMID="TMD_eprint_407"><mets:fptr FILEID="eprint_407_document_1131_1"></mets:fptr></mets:div></mets:structMap></mets:mets>