Figure is a fully developed use case description for the use case Print patient invoices in the dental clinic system. Do the following:

a. Develop a first-cut sequence diagram, which only includes the actor and problem domain classes.
b. Add the view layer classes and the data access classes to your diagram from part a.
c. Develop a design class diagram based on the domain class diagram and the results of parts a and b.
d. Develop a package diagram showing a three layer solution with view layer, domain layer, and data access layerpackages.

Transcribed Image Text:

Use Case Scenario: Triggering Event: At the end of the month, invoices are printed ame: Print patient invoices Print patient invoices Brief Description: The billing clerk manually checks to see that all procedures have been collected. The clerk spot- checks, using the written records to make sure procedures have been entered by viewing them with the system. The clerk also makes sure all payments have been entered. Finally, he/she prints the invoice reports. An invoice is sent to each patient. Actors: Preconditions Postconditions:Patient Records are updated with last billing date Billing Clerk, Dentist Patient Records must exist, Procedures must exist Flow of Activities: Actor System 1. Collect al written notes about procedures completed this month. 2. View several patients to verify that procedure 2.1 Display patient information, including information has all been entered. 3. Review log of payments received and verify that 3.1 Display patient information, including procedure records. payments have been entered. 4. Enter month-end date and request invoices. 5. Verify invoices are correct. 6. Close invoice print process. account balance and last payment transactions. 4.1 Review every patient record. Find unpaid procedures. List on report as aged or current. Calculate and break down by copay and insurance pay Exception None