Index Introduction
1. Entity-relationship diagram that shows the data strorage requirements for Relable Pharamceutical Supply -------------------3
2. Domain meta class for RPS. -------------------4
3. Activity diagram for each use case related to entering new orders -------------------5
4. System sequence diagram -------------------8
5. State machine diagram for an order ------------------11
6. Three-layer architecture for this new system ------------------12
7. Design two separate menu hierarchies ------------------13
8. Steps of the dialog between the user and the system for the use case Place new order for nursing home employees -----14
9. Input controls ------------------15
10. Create a work breakdown structure of your proposed plan. -------------------16
Introduction
To process a prescription order, RPS needs to know about the patients, the nursing home, and the nursing home unit where each patient resides. Each nursing home has at least one, but possibly many, units. A patient is assigned to a specific unit. An order consists of one or more prescriptions, each for one specific drug and one specific patient. An order, therefore, consists of prescriptions for more than one patient. Careful tracking and record keeping is crucial. In addition, each patient has multiple prescriptions, and one pharmacist fills each order.
There are several points in the order-fulfillment process at which information must be recorded in the system. Case manifests must be printed at the start of each shift. Because a prescription may take a long time to be used completely, information must be entered into the system each time a medication is sent, noting the quantity sent and which pharmacist filled the prescription for that shift.