By Topic

Ensuring Sufficient Breadth in Use Case Development: How Should Non-functional Requirements Be Elicited and Represented?

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Rick Schrenker ; Massachusetts Gen. Hosp., Boston

Requirements informed by clinical context are needed to drive the development of emerging medical device communications interoperability standards and practices. Efforts thus far have focused on working with clinical engineers and clinicians to elicit functional requirements. We provide rationale to extend the effort to include eliciting nonfunctional requirements from the provider community, suggest methods to be explored, and identify issues germane to the realization of standards-based interoperability that this work may inform.

Published in:

High Confidence Medical Devices, Software, and Systems and Medical Device Plug-and-Play Interoperability, 2007. HCMDSS-MDPnP. Joint Workshop on

Date of Conference:

25-27 June 2007