Skip to main content
Log in

The nonfunctional requirement focus in medical device software: a systematic mapping study and taxonomy

  • Original Paper
  • Published:
Innovations in Systems and Software Engineering Aims and scope Submit manuscript

Abstract

This paper describes the results and analysis of a systematic mapping study of research focusing on the nonfunctional requirements in software intensive medical devices. The review covered 238 journal papers from five digital libraries. The 55 papers that met the review inclusion criteria focused on 22 NFRs, each describing a unique system behavior quality. The most dominant of these NFRs were interoperability,usability, performance,security, privacy, safety, and accuracy. A noticeable NFR gap is the notion of caring. It is not readily apparent how a medical device that monitors a patient or delivers medications or anesthetics can “care about” the sufferings, feelings and emotional needs of a patient; however, in the healthcare arena these are valid concerns. A second theme found in the papers reviewed focused on software standards/process improvement when developing software intensive medical devices. This research also provides an analysis of the software architecture tactics those researchers utilized to implement the NFRs in the medical devices.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4

Similar content being viewed by others

References

  1. Makary M, Daniel M (2016) Medical error-the third leading cause of death in the US. BMJ 353:2139. doi:10.1136/bmj.i2139

    Article  Google Scholar 

  2. Leveson NG, Turner CS (1993) An investigation of the Therac-25 accidents. Computer 26:18–41. doi:10.1109/MC.1993.274940

    Article  Google Scholar 

  3. Sandler K, Ohrstrom L, Moy L, McVay R (2010) Killed by code: software transparency in implantable medical devices, Software Freedom Law Center. https://www.softwarefreedom.org/resources/2010/transparent-medical-devices.pdf

  4. Jones P, Taylor AL (2015) Medical device risk management and safety cases. Biomed Instrum Technol 49(s1):45–53. doi:10.2345/0899-8205-49.s1.45

    Article  Google Scholar 

  5. Finkelstein A, Dowell J (1996) A comedy of errors: the London ambulance service case study. In: Proceedings of the 8th international workshop software specifications and design, pp 2–5

  6. Weber M, Wesbrot J (2003) Requirements engineering in automotive development: experiences and challenges. IEEE Softw 20(1):16–24. doi:10.1109/MS.2003.1159025

    Article  Google Scholar 

  7. Kassab M (2015) The changing landscape of requirements engineering practices over the past decade. In: EmpiRE15 in conjunction with the 23rd IEEE international requirements engineering conference. Ottawa, Canada. doi:10.1109/EmpiRE.2015.7431299

  8. Chung L, Nixon BA, Yu E, Mylopoulos J (2000) Nonfunctional requirements in software engineering. Kluwer Academic Publishing, Dordrecht. doi:10.1007/978-1-4615-5269-7

  9. Svensson RB, Gorschek T, Regnell B (2009) Quality requirements in practice: an interview study in requirements engineering for embedded systems. In: Requirements engineering: foundation for software quality. Lecture notes in computer science, vol 5512. Springer

  10. Eckhardt J, Fernández DM, Vogelsang A (2017) How to specify non-functional requirements to support seamless modeling? A study design and preliminary results. arXiv:1702.07643

  11. Laplante PA (2014) Licensing professional software engineers: seize the opportunity. Commun ACM 57(7):38–40. doi:10.1145/2618111

    Article  Google Scholar 

  12. International Organization for Standardization, IEC (2006) Medical device software: software life cycle processes. https://www.iso.org/obp/ui/#iso:std:iec:62304:ed-1:v1:en

  13. International Organization for Standardization, IEC (2016) Medical devices: quality management systems: requirements for regulatory purposes. http://www.iso.org/iso/catalogue_detail?csnumber=59752

  14. Kitchenham B, Budgen D, Brereton P (2016) Evidence-based software engineering and systematic reviews. CRC Press, Boca Raton, FL

    Google Scholar 

  15. Wallace DR, Richard KD (2001) Failure modes in medical device software: an analysis of 15 years of recall data. Int J Reliab Qual Saf Eng 8:351–372. http://stareast.techwelldev.com/sites/default/files/articles/XDD6449filelistfilename1_0.pdf

  16. Kramer DB, Baker M, Ransford B, Molina-Markham A, Stewart Q, Fu K et al (2012) Security and privacy qualities of medical devices: an analysis of FDA postmarket surveillance. PLoS ONE 7(7):e40200. doi:10.1371/journal.pone.0040200

    Article  Google Scholar 

  17. Fu K (2011) Trustworthy medical device software. Public Health Eff FDA 510. http://css.csail.mit.edu/6.858/2014/readings/medical-sw.pdf

  18. Kassab M, Ormandjieva O (2014) Non-functional requirements in process oriented approaches. In: Encyclopedia of software engineering. Taylor & Francis Group

  19. Matoussi A, Laleau R (2008) A survey of non-functional requirements in software development process, TR-LACL-2008-7. http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.174.1704&rep=rep1&type=pdf

  20. Melo JD, Neto S, Leite JCS, Cysneiros LM (2000) Non functional requirements for object-oriented modeling. In: WER, pp 109–125

  21. Ameller D, Franch X, Gómez C, Araujo J, Svensson R, Biffl S, Cabot V, Cortellessa J, Daneva M, Méndez Fernández D, Moreira A, Muccini H, Vallecillo A, Wimmer M, Amaral V, Brunelière H, Burgueño L, Goulão M, Schätz B, Teufl S (2015) Handling non-functional requirements in model-driven development: an ongoing industrial survey. In: Requirements engineering conference (RE)

  22. Svensson RB, Olsson T, Regnell B (2013) An investigation of how quality requirements are specified in industrial practice. Inf Softw Technol 55:1224–1236

    Article  Google Scholar 

  23. Kitchenham B (2004) Procedures for performing systematic reviews. In: Keele University Technical Report, TR/SE-0401. http://www.inf.ufsc.br/~awangenh/kitchenham.pdf

  24. LaPES. Start-state of the art through systematic review. http://lapes.dc.ufscar.br/tools/start_tool

  25. Brereton P, Kitchenham B, Budgen D, Turner M, Khalil M (2007) Lessons from applying a systematic literature review process within the software engineering domain. J Syst Softw 80:571–583. doi:10.1016/j.jss.2006.07.009

    Article  Google Scholar 

  26. Tumyrkin R, Mazzara M, Kassab M, Succi G, Lee J (2016) Quality attributes in practice: contemporary data. In: Agent and multi-agent systems technology and applications. Springer

  27. Bass L, Clements P, Kazman R (2012) Software architecture in practice, 3rd Edn. Addison-Wesley. https://www.pearsonhighered.com/program/Bass-Software-Architecture-in-Practice-3rd-Edition/PGM317124.html

  28. Harrison N, Avgeriou P, Zdun U (2010) On the impact of fault tolerance tactics on architecture patterns. In: Proceedings of 2nd international workshop SERENE, pp 12–21

  29. The Software Engineering Institute, Carnegie Mellon University. http://www.sei.cmu.edu/architecture/index.cfm

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to J. DeFranco.

Appendix

Appendix

See Tables 3 and 4.

Table 3 A full citation list of specific NFR research papers
Table 4 A full citation list of process improvement NFR research papers

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

DeFranco, J., Kassab, M., Laplante, P. et al. The nonfunctional requirement focus in medical device software: a systematic mapping study and taxonomy. Innovations Syst Softw Eng 13, 81–100 (2017). https://doi.org/10.1007/s11334-017-0301-6

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11334-017-0301-6

Keywords

Navigation