Sandia Medical Devices

Recall the Sandia Medical Devices Real-Time Glucose Monitoring (RTGM) system introduced in Chapter 2. As the project began, interviews with patients and physicians about potential RTGM capabilities and interaction modes identified several areas of concern that will need to be incorporated into the system requirements and design. The relevant patient concerns include:

Viewing and interpreting data and trends. Patients want to be able to view more than their current glucose level. They would like to see glucose levels over various time periods, with a specific focus on time periods during which their glucose was within and outside of acceptable ranges. A graphical view of the data is preferred, although some patients also want to be able to see actual numbers.

Entering additional data. Some patients want to be able to enter text notes or voice messages to supplement glucose level data. For example, patients who see a high glucose alert might record voice messages describing how they feel or what they had recently eaten. Some patients thought that sharing such information with their health-care providers might be valuable, but others only wanted such information for themselves. Physicians expressed these concerns:

They do not want to be the first line of response to all alerts. They prefer that nurses or physician assistants be charged with that role and that physicians be notified only when frontline personnel determine that an emergency situation exists.

They want to be able to monitor and view past patient data and trends in much the same way as described for patients.

They want all their actions to be logged and for patient-specific responses to be stored as part of the patients electronic medical record. Perform the following tasks by using

1. identify all actors who will use RTGM.

2. do BOTH of the followings:

1. Using the actors that you identified in question, (1) identify their goals, (2) develop a list of use cases based on the user goal's technique, and (3) draw a use case diagram for these use cases.
2. Using the event decomposition technique, (1) identify the events, (2) name the events and state the type of the events, (3) develop a list of use cases based on the events, and (4) draw a use case diagram for these use cases.