Please use this identifier to cite or link to this item: http://buratest.brunel.ac.uk/handle/2438/7780
Full metadata record
DC FieldValueLanguage
dc.contributor.authorTulasidas, S-
dc.contributor.authorMackay, R-
dc.contributor.authorCraw, P-
dc.contributor.authorHudson, C-
dc.contributor.authorGkatzidou, V-
dc.contributor.authorBalachandran, W-
dc.date.accessioned2013-12-10T09:55:11Z-
dc.date.available2013-12-10T09:55:11Z-
dc.date.issued2013-
dc.identifier.citationJournal of Software Engineering and Applications, 6(9a), 1-13, 2013en_US
dc.identifier.issn1945-3116-
dc.identifier.urihttp://bura.brunel.ac.uk/handle/2438/7780-
dc.descriptionCopyright © 2013 Sivanesan Tulasidas et al. This is an open access article distributed under the Creative Commons Attribution Li-cense, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.en_US
dc.descriptionThis article has been made available through the Brunel Open Access Publishing Fund.-
dc.description.abstractThis paper presents a holistic methodology for the design of medical device software, which encompasses of a new way of eliciting requirements, system design process, security design guideline, cloud architecture design, combinatorial testing process and agile project management. The paper uses point of care diagnostics as a case study where the software and hardware must be robust, reliable to provide accurate diagnosis of diseases. As software and software intensive systems are becoming increasingly complex, the impact of failures can lead to significant property damage, or damage to the environment. Within the medical diagnostic device software domain such failures can result in misdiagnosis leading to clinical complications and in some cases death. Software faults can arise due to the interaction among the software, the hardware, third party software and the operating environment. Unanticipated environmental changes and latent coding errors lead to operation faults despite of the fact that usually a significant effort has been expended in the design, verification and validation of the software system. It is becoming increasingly more apparent that one needs to adopt different approaches, which will guarantee that a complex software system meets all safety, security, and reliability requirements, in addition to complying with standards such as IEC 62304. There are many initiatives taken to develop safety and security critical systems, at different development phases and in different contexts, ranging from infrastructure design to device design. Different approaches are implemented to design error free software for safety critical systems. By adopting the strategies and processes presented in this paper one can overcome the challenges in developing error free software for medical devices (or safety critical systems).en_US
dc.language.isoenen_US
dc.publisherScientific Research Publishingen_US
dc.subjectPoint of care testingen_US
dc.subjectSystem architectureen_US
dc.subjectSafety critical systemsen_US
dc.subjectSoftware developmenten_US
dc.titleProcess of designing robust, dependable, safe and secure software for medical devices: Point of care testing device as a case studyen_US
dc.typeArticleen_US
dc.identifier.doihttp://dx.doi.org/10.4236/jsea.2013.69A001-
pubs.organisational-data/Brunel-
pubs.organisational-data/Brunel/Brunel Active Staff-
pubs.organisational-data/Brunel/Brunel Active Staff/School of Info. Systems, Comp & Maths-
pubs.organisational-data/Brunel/Brunel Active Staff/School of Info. Systems, Comp & Maths/IS and Computing-
Appears in Collections:Computer Science
Brunel OA Publishing Fund
Dept of Computer Science Research Papers

Files in This Item:
File Description SizeFormat 
Fulltext.pdf1.04 MBAdobe PDFView/Open


Items in BURA are protected by copyright, with all rights reserved, unless otherwise indicated.