EvacSafe You have been assigned to develop a new system 'EvacSafe' which includes a desktop web application and a mobile app to support the Falls Prevention initiative. Melissa, Mustafa and Rohan return... Lakeview Residences Regional Manager - Melissa Johnson Thanks for the awesome design models you gave us last week! Weve considered a lot more about how the EvacSafe will be used, in particular the different statuses that the resident record can have during our operational workflow... over to Mustafa, please. Lakeview Residences Group Technology Manager - Mustafa Bayoumi Usually a resident record can't be created without the resident personal information, which is exported from OurHomeSMS, so new resident records must always have the imported Resident information. The imported resident record always begins its life cycle in the IMPORTED status. In some cases, a resident record is entered manually from a blank slate such as when the resident is transferred as part of an evacuation very soon after moving in, before any care staff or nurse has imported the personal data from OurHomeSMS. Or if there are any issues with the import process, and the record has to be created. It is important that every resident has details in the evacuation form to plan the evacuation. The resident record then will have the status of MANUAL. After the import or manual entry, the staff member will make a check of the details and then confirm that this is a correct record. The record will then move to ACTIVE status. From here the record will mostly remain, until the resident is part of an evacuation transfer. The status will change to EVAC-PLANNED once the Admin manager or Head Nurse plans the transfer. Post-transfer their status will be EVAC-TRANSFERRED. When the resident returns to their original Lakeview residence, or if the planned transfer didn't eventuate, their status will return to ACTIVE. Before importing or manually entering a resident record, it is important to check if there are any resident records already raised - so the Lakeview staff member can search resident records by resident name and DOB. Sometimes it is discovered later that a resident record is already created - in this case the superfluous record ( it is usually the one created first that is kept, but it's not a fixed rule) can be assigned the status of DUPLICATE.

Sometimes, too, a resident record is imported in error, due to bad data in OurHomeSMS. In this case, the resident record can be finalised with an ERROR status. From MANUAL status, a record can just be deleted if it is not moved to ACTIVE. DHHS Program Coordinator - Rohan Huang Our department is very concerned with the safe evacuation of residents during an emergency. The Lakeview Admin manager should be able to use EvacSafe to generate a report of all residents transferred as part of an emergency during a particular month. Just like the reports we receive from Lakeview's OurHomeSMS, we have the API details you can set up for EvacSafe to submit any transferred residents, in XML format - these reports will be uploaded to our departmental systems electronically. All reports are also archived in EvacSafe so Lakeview has a record of all previous submissions to DHHS. Lakeview Residences Group Technology Manager - Mustafa Bayoumi Not all resident records post-transfer are reportable to DHHS. For example, any DUPLICATE records are not reportable for a resident after a transfer because there should be an original or active record that would be reportable instead. Once a record reaches EVAC-TRANSFERRED status, it is reportable, and should have the DHHS-REPORTABLE status as well. Once EvacSafe has sent the record details to DHHS, EvacSafe will set the record to DHHS-REPORTED to notate that the monthly reporting requirement is met. Any EVAC-TRANSFERRED or ACTIVE resident records that remain in DHHS-UNREPORTED will result in daily reminder email notifications to the Lakeview manager and proprietor roles until they are reported or the status changed. A resident record, that is previously assessed as reportable, can also move to DHHS-RESCINDED status if it is re-evaluated by the Admin Manager to be not reportable. Lakeview Residences Regional Manager - Melissa Johnson Is this meeting on record? Great! Once the resident has left the residence permanently, the record is set to CLOSED, and it should remain in our records for seven years, according to our legal requirements... Anyway thats enough for now. Were so glad you are building EvacSafe for us! Here are some user scenarios for you that we prepared earlier...

Your Tasks Develop Sequence Diagrams (2 x 5 marks) a) Create two sequence diagrams, one for each of the user scenarios provided by the customer. Show how objects will interact to achieve the aims of the user. b) Your diagram will be assessed on: i. Consistency and completeness with the scenario and the refined class diagram provided in this assignment ii. Appropriate identification and use of objects, messages, lifelines, activations, frames (for iteration or selection), etc. c) The user scenario(s) provided by Melissa are: i. The Plan Evacuation use case initiated by the Actor (Lead Nurse or Admin Manager) first involves generating a resident list in EvacSafe (for a Wing). EvacSafe will only return a list of ACTIVE residents (in particular, who are not otherwise transferred!). The Actor will review the list and for each Resident, if they are not part of the evacuation for any reason, the Actor will select them for deletion. If the resident is to be evacuated, the Actor retrieves the destination details. If the resident's destination details are correct, the Actor will leave them, otherwise they will enter alternative destination details (location, custodian and contact details). ii. The Review Resident use case initiated by the Actor (Nurse or Care Staff) involves searching the Resident by name (or ID) and a Wing number for the residence. EvacSafe returns a list of existing residents. Selecting a resident would display a list of patient data (as found in the evacuation template). If there are any updates for a patient data type, the Actor will enter the updated data for that type and save the entry. Furthermore, if the data type is diagnosis, if any of these updates arise from a specialist or general medical practitioner diagnosis, then the Actor will also append to the diagnosis, the contact name and details of the medical practioner.

2) Develop a State Diagram (8 marks) a) Develop a State Diagram to model the Resident Record statuses/states based on the stakeholder statements.. b) Your diagram will be assessed on: i. Consistency and completeness with both the stakeholders statements and your updated class diagram in this assignment. ii. Appropriate use of UML notation 3) Refine the Class Diagram from Assignment One (2 marks) a) Based on the stakeholder statements, and the modelling in earlier questions, revise the class diagram and highlight two new classes from recent stakeholder information. b) Your diagram will be assessed on: i. consistency with your sequence and state diagram ii. appropriate use of UML notation 4) Develop an Activity Diagram (2 x 5marks) a) Create activity diagrams based on the two use cases mentioned in Question 1. Your diagram will be assessed on: i. Consistency and completeness with both the scenario and class diagram. ii. Include all of the following where relevant : Actions, decisions, joins, forks, merges, and swimlanes. iii. Include different swimlanes for the relevant objects within the system. (For example the driver class, and any object that has its attribute values accessed or modified)