Abstract
Regulation normally requires critical systems to be certified before entering service. This involves submission of a safety case - a reasoned argument and supporting evidence that stringent requirements have been met and that the system is acceptably safe. A good safety case encompasses an effective risk mitigation process which is highly dependent on requirements traceability. However despite its many benefits and regulatory requirements, most existing software systems lack explicit traceability links between artefacts. Reasons for the lack of traceability include cost, complexity and lack of guidance on how to implement traceability.To assist medical device organisations in addressing the lack of guidance on how to implement effective traceability, this paper aims to present the development and validation of a traceability process assessment model and the actions to be taken as a result of the validation. The process assessment model will allow organisations to identify strengths and weaknesses in their existing traceability process and pinpoint areas for improvement.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
RTCA, DO-178B Software Considerations in Airborne Systems and Equipment Certification, ed. Washington, DC (1992)
CENELEC, Railway applications – Communications, signalling and processing systems – Software for railway control and protection systems ed. (2001)
ANSI/AAMI/IEC, 62304:2006 Medical device software—Software life cycle processes, ed. Arlington, VA: AAMI (2006)
Lucia, A.D., et al.: Information Retrieval Methods for Automated Traceability Recovery. In: Cleland-Huang, J., et al. (eds.) Software and Systems Traceability, pp. 88–111. Springer, Heidelberg (2012)
Cleland-Huang, J.: Just Enough Requirements Traceability. Presented at the Proceedings of the 30th Annual International Computer Software and Applications Conference, vol. 01 (2006)
Kannenberg, A., Saiedian, D.H.: Why Software Requirements Traceability Remains a Challenge. CrossTalk The Journal of Defense Software Engineering, p. 5 (2009)
Jarke, M.: Requirements tracing. Commun. ACM 41, 32–36 (1998)
Regan, G., et al.: The Barriers to Traceability and their Potential Solutions: Towards a Reference Framework. Presented at the 38th Euromicro Conference on Software Engineering and Advanced Applications, Cesme, Turkey (2012)
McCaffery, F., Casey, V.: Med-Trace: Traceability Assessment Method for Medical Device Software Development. Presented at the EuroSPI Denmark (2011)
Mader, P., et al.: Motivation Matters in the Traceability Trenches. Presented at the Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE (2009)
ISO/IEC, 15504-5: An exemplar Process Assessment Model, ed. Switzerland: ISO (2006)
Sig, A.: Automotive SPICE® Process Assessment Model, ed (2010)
ECCS, Space Product Assurance- Software process assessment and improvement – Part 2: Assessor instrument, ed. Netherlands: ESA Requirements and Standards Division (2010)
S. E. Institute, CMMI® for Development, Version 1.3, in Improving processes for developing better products and services, ed. (2010)
ISO/IEC, 12207: Systems and software engineering — Software life cycle processes, ed. Geneva, Switzerland: ISO (2008)
Regan, G., et al.: Implementation of traceability best practices within the medical device domain. Presented at the EuroSPI 2013, Dundalk, Ireland (2013)
Barafort, B., et al.: A transformation process for building PRMs and PAMs based on a collection of requirements – Example with ISO/IEC 20000. Presented at the SPICE, Nuremberg, Germany (2008)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this paper
Cite this paper
Regan, G., McCaffery, F., McDaid, K., Flood, D. (2014). The Development and Validation of a Traceability Assessment Model. In: Mitasiunas, A., Rout, T., O’Connor, R.V., Dorling, A. (eds) Software Process Improvement and Capability Determination. SPICE 2014. Communications in Computer and Information Science, vol 477. Springer, Cham. https://doi.org/10.1007/978-3-319-13036-1_7
Download citation
DOI: https://doi.org/10.1007/978-3-319-13036-1_7
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-13035-4
Online ISBN: 978-3-319-13036-1
eBook Packages: Computer ScienceComputer Science (R0)