Abstract
The quality requirements for medical software have become increasingly demanding. Several quality standards and models are already in place, but there is a debate on whether these are specific enough for medical software. Moreover, mapping requirements to quality criteria can be challenging but is required throughout the software development process. We propose a workflow in which we apply proven methods and tools for systematic collection, analysis, and evaluation of software quality criteria based on the ISO/IEC 25010:2011. We employ affinity diagrams, Kano analysis and quality function deployment for the systematic requirement development, analysis, and management. We outline a systematic approach on how to use the recommended process when developing medical software. The paper proposes a systematic approach for requirements management that could be used for mapping medical software quality criteria and stakeholder requirements, independent from the quality criteria (and the underlying model) itself.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
