You are hired to develop an automatic patient monitoring sys

You are hired to develop an automatic patient monitoring system for a home-bound patient. The system is required to read out the patient’s heart rate and blood pressure and compare them against specified safe ranges. The system also has activity sensors to detect when the patient is exercising and adjust the safe ranges. In case an abnormality is detected, the system must alert a remote hospital. (Note that the measurements cannot be taken continuously, since heart rate is measured over a period of time, say 1 minute, and it takes time to inflate the blood-pressure cuff.)

The system must also

(i) check that the analog devices for measuring the patient’s vital signs are working correctly and report failures to the hospital; and,

(ii) alert the owner when the battery power is running low. Enumerate and describe the requirements for the system-to-be.

(iii) Consider the automatic patient monitoring system. Identify the
actors and their goals. Briefly, in one sentence, describe each use case but do not elaborate
them. Draw UML the use case diagram.

(iV)  include a UML diagram that shows actors for the patient, device, and hospital personnel.

Solution

A use case diagram is \"a diagram that shows the relationships among actors and use instances inside a machine. \"Use case diagrams are often used to:

offer an outline of all or part of the usage requirements for a gadget or agency in the form of an crucial version or a commercial enterprise model
talk the scope of a improvement mission
version your analysis of your utilization requirements within the form of a device use case model>
A use case model is comprised of one or greater use case diagrams and any supporting documentation together with use case specs and actor definitions. within most use case fashions the use case specifications have a tendency to be the primary artifact with use case diagrams filling a supporting position because the \"glue\" that maintains your requirements model together. Use case fashions should be evolved from the factor of view of your challenge stakeholders and no longer from the (frequently technical) point of view of developers. There are pointers for:

Use cases
Actors
Relationships
machine Boundary containers
- See greater at: http://agilemodeling.com/fashion/useCaseDiagram.htm#sthash.yqyds6Od.dpuf