By Topic

Executable use cases: requirements for a pervasive health care system

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
$31 $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

2 Author(s)
Baek Jorgensen, J. ; Aarhus Univ., Denmark ; Bossen, C.

Many software experts argue that when we design a new system, we should create an explicit description of the environment in which the proposed system is to be used. The argument becomes crucial for pervasive computing, which aims to tightly integrate systems into their environments and into the work processes they're to support. However, prototypes typically provide an explicit representation only of the system itself. Executable use cases, on the other hand, can also describe the environment. EUCs are designed to: narrow the gap between informal ideas about requirements and the formalization that eventually and inevitably emerges during system implementation; and spur communication between users and system developers. Iterative prototyping is a feasible starting point to pursue these goals. But EUCs encompass both iterative prototyping and explicit environment descriptions in terms of workflow modeling. This article describes a case study in which developers used EUCs to prototype an electronic patient record system for hospitals in Aarhus, Denmark.

Published in:

Software, IEEE  (Volume:21 ,  Issue: 2 )