Using the UML models from last week's discussion, begin what is known as a high-level design, which is a 30,000 foot level view of the project that you wrote software requirements for in Project 1. High-level designs are used to inform the customer, managements, and other developers know and understand the design path you want to take.

2. Once the major classes are known, draw a sequence diagram, which shows the interaction between your objects. The methods on your objects are the arrows between classes. This will help you better understand how your objects interact. See page 133-134, Figure 5-6 and 5-7.

Classes, Attributes, Methods:

Figure 5.6:

Figure 5.7:

\begin{tabular}{|l|} \hline Report \\ \hline report_id \\ report_type \\ report_data \\ \hline generate_report() \\ \hline \end{tabular} gure 5.6 Sequence agram for View patient formation conditions indicated in square brackets, with alternative interaction option rated by a dotted line. You can read Figure 5.6 as follows: 1. The medical receptionist triggers the ViewInfo method in an instance PatientInfo object class, supplying the patient's identifier, PID to id required information. P is a user interface object, which is displayed showing patient information. 2. The instance P calls the database to return the information required the receptionist's identifier to allow security checking. (At this sta Figure 5.7 Sequence diagram for Transfer Data to be uploaded to a national PRS (patient records system). You can read this dis? as follows: 1. The receptionist logs on to the PRS. 2. Two options are available (as shown in the "alt" box). These allow the "? transfer of updated patient information from the Mentcare dafalase PRS and the transfer of summary health data from the Mentcare diatibe the PRS. 3