Proceedings ArticleDOI
Minimizing the ambiguities in medical devices regulations based on software requirement engineering techniques
Reads0
Chats0
TLDR
This paper will present a method to minimize the ambiguities in MDR requirements based on requirement engineering techniques (user story and use case diagram) and this work will be evaluated by the critical-to-quality tree measurement technique.Abstract:
Trusted medical software devices, must comply with one of the healthcare regulations such as Food and Drug Administration (FDA), EU Medical Device Regulation (MDR), and Health Insurance Portability and Accountability Act (HIPAA). Since these regulations are enacted by law legislators and written in a legal text, these regulations are typically written with ambiguities. However, people have a different interpretation for the legal text for example, software developers faced challenges in identifying and understanding the regulatory requirements that are related to the software development process. Moreover, ambiguous in regulatory requirements play a big role in software compliance with regulatory particularly, when the requirements are legal text. In this paper, we intend to minimize the ambiguities in EU MDR requirements based on requirement engineering techniques in order to make MDR requirements clear and precise for software developers. In our previous work, we extracted the requirements of MDR that would affect the software development life cycle (SDLC) directly or indirectly. Herein, we will identify the ambiguity types in the extracted requirements of MDR. Moreover, this paper will present a method to minimize the ambiguities in MDR requirements based on requirement engineering techniques (user story and use case diagram). Finally, this work will be evaluated by the critical-to-quality tree measurement technique.read more
Citations
More filters
Journal ArticleDOI
From Legal Contracts to Formal Specifications: A Systematic Literature Review
TL;DR: In this article , the authors present a systematic literature review of papers for the main steps related to the transformation of a legal contract expressed in natural language into a formal specification, and identify promising approaches, best practices, and existing gaps in the literature.
Journal ArticleDOI
Checklist Approach for the Development of Educational Applications by Novice Software Developers
TL;DR: In this paper , the authors investigated the checklist approach for novice software developers in developing educational applications and found that 89.19% of the respondents had understood and benefited from the provided checklist.
Journal ArticleDOI
Checklist Approach for the Development of Educational Applications by Novice Software Developers
Nor Hasrul Akhmal Ngadiman,Shahida Sulaiman,Nor Aini Haji Idris,Mohd Razak Samingan,Hasnah Binti Mohamed +4 more
TL;DR: In this paper , the authors investigated the checklist approach for novice software developers in developing educational applications and found that 89.19% of the respondents had understood and benefited from the provided checklist.
Proceedings ArticleDOI
Assessment of Machine Learning Security: The Case of Healthcare Data
TL;DR: In this paper, a health system was studied in a hospital in Jordan after collecting information on 769 records for pregnant diabetics, using Python to test the accuracy of this information and improve the performance of the model being created using machine learning algorithms, including decision trees and random forests.
Journal ArticleDOI
From Legal Contracts to Formal Specifications: A Systematic Literature Review
TL;DR: In this paper , the authors present a systematic literature review of papers for the main steps related to the transformation of a legal contract expressed in natural language into a formal specification, and identify promising approaches, best practices, and existing gaps in the literature.
References
More filters
Book
User Stories Applied: For Agile Software Development
TL;DR: The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users.
Book
Software Requirements: Objects, Functions and States
TL;DR: 1. The Software Requirements Specification: Specifying Behavioral Requirements and Nonbehavioral Requirements and Requirements Prototyping.
From Contract Drafting to Software Specification: Linguistic Sources of Ambiguity
TL;DR: This handbook describes the ambiguity phenomenon from several points of view, including linguistics, software engineering, and the law, and several strategies for avoiding and detecting ambiguities are presented.
Journal ArticleDOI
An experimental study of fault detection in user requirements documents
TL;DR: This paper describes a software engineering experiment designed to confirm results from an earlier project which measured fault detection rates in user requirements documents (URD) and provide new results concerning variability in inspection team performance and the relative difficulty of locating different classes of URD faults.
Book ChapterDOI
Ambiguity in Requirements Specification
Daniel M. Berry,Erik Kamsties +1 more
TL;DR: This chapter describes a full range of techniques and tools for avoiding and detecting ambiguity in natural language requirements specifications and a dictionary, linguistic, and software engineering definitions of ambiguity are given.