ACM Home Page
Please provide us with feedback. Feedback
Rational quality requirements for medical software
Full text PdfPdf (218 KB)
Source
International Conference on Software Engineering archive
Proceedings of the 30th international conference on Software engineering table of contents
Leipzig, Germany
SESSION: Requirements engineering table of contents
Pages 633-638  
Year of Publication: 2008
ISBN:978-1-60558-079-1
Authors
Barbara Paech  Institute for Computer Science, Heidelberg, Germany
Thomas Wetter  Institute of Medical Biometry and Medical Informati s, Heidelberg, Germany
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 39,   Downloads (12 Months): 185,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1368088.1368176
What is a DOI?

ABSTRACT

In this paper we discuss the challenges of software quality for medical software and present some ideas for improving medical software quality requirements through software engineering methods. We apply the quality requirements engineering method MOQARE to elicit specific quality requirements for an imaginary drug advisory system and report our lessons learned.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Paech, B., Kerkow, D. 2004. Non-Functional Requirements Engineering - Quality is Essential. In: Regnell, B., Kamsties, E., Gervasi, V. (eds) Proceedings of the 10th Intl. Workshop on Requirements Engineering REFSQ04, Essener Informatik Beiträge Bd 9, 237--250.
 
2
Chen, B., Avrunin, G.B., Clarke, L.A., Osterweil, L.J. 2006. Automatic Fault Tree Derivation from Little-JIL Process Definitions, Software Process Workshop (SPW 2006) and 2006 Process Simulation Workshop (PROSIM 2006), Springer-Verlag LNCS, Vol. 3966, 150--158.
 
3
Wetter, Th. 2008. Why is medical software so hard? accepted for Computer Science Research and Development, Springer.
 
4
Jones, M.T.2003. Computers can land people on Mars, why can't they get them to work in hospitals? Methods Inf Med 42 410--5.
 
5
Wetter, Th. 2007. To decay is system: The challenges of keeping a health information system alive; Int. J. Med. Inform. 76 (S1), 252--260.
 
6
 
7
Cimino, J.J., Li, J., Bakken, S., Patel, V.S. 2002. Theoretical, empirical and practical approaches to resolving the unmet information needs of clinical information system users; Proc. AMIA Symp., 170--174.
 
8
 
9
Wetter, Th. 2006. Safeguarding clinical software - A managerial case study about project management and oversight; Proc. APAMI conference, Taipei, 27--31. Oct 2006

Collaborative Colleagues:
Barbara Paech: colleagues
Thomas Wetter: colleagues