Develop a multilayer sequence diagram for the fully developed use case (shown below) that includes the domain classes and data access layers.
Fully developed use case description: Use Case Name: Scenario: Triggering Event: The patient wants to view glucose history Brief Description: The patient will interact with the system to view past glucose reports in View Patient Historv. Patient wants to view reported glucose history chronological order. Patient Patient, Doctor, Sandia. Glucose Subsystem must be running. Patient history must be recorded and available in the database. Patient account must be in the system Patient history is up to date. Patient will have to option to specify update interval Patient will be able to view history in tabular or graph form Actors Stakeholders Preconditions: Postconditions Flow of Activities: Actor System 1. Patient logs into system with an 1. System is initialized and account. user is authenticated 2. Patient can choose to wait til glucose level updates at default 5-minute interval or at user specified time. Patient navigates to glucose report history 2. System records glucose level 3. 3. Displays pages for navigation 4. Patient views recorded history in tabular or graph form 4. System displays history in specified time Exceptiorn Conditions 1.1 User cannot be authenticated, request for email or password recovery. 2.1 System cannot record history or set user specified time, display error message 3.1 GUI is not responding, display error message. 4.1 Database could not be reached, display network failure message. Fully developed use case description: Use Case Name: Scenario: Triggering Event: The patient wants to view glucose history Brief Description: The patient will interact with the system to view past glucose reports in View Patient Historv. Patient wants to view reported glucose history chronological order. Patient Patient, Doctor, Sandia. Glucose Subsystem must be running. Patient history must be recorded and available in the database. Patient account must be in the system Patient history is up to date. Patient will have to option to specify update interval Patient will be able to view history in tabular or graph form Actors Stakeholders Preconditions: Postconditions Flow of Activities: Actor System 1. Patient logs into system with an 1. System is initialized and account. user is authenticated 2. Patient can choose to wait til glucose level updates at default 5-minute interval or at user specified time. Patient navigates to glucose report history 2. System records glucose level 3. 3. Displays pages for navigation 4. Patient views recorded history in tabular or graph form 4. System displays history in specified time Exceptiorn Conditions 1.1 User cannot be authenticated, request for email or password recovery. 2.1 System cannot record history or set user specified time, display error message 3.1 GUI is not responding, display error message. 4.1 Database could not be reached, display network failure message
