Your are required to develop the software architecture for a healthcare system, which provides check-in, payment, and automatic no-show charge use cases depicted in Figs. 1-6 using the communication diagram. Develop the software architecture for a healthcare system in the following order: 1. Develop the consolidated communication diagram that merges all communication diagrams to show all objects and their interaction. (3 pts) 2. Determine the subsystems (or components) of healthcare system and depict them on the consolidated communication diagram. (3 pts) 3. Depict function call or message communication for interactions between objects or between subsystems on the consolidated communication diagram. (3 pts) 4. Develop the software architecture diagram t that shows subsystems and their interaction. (6 pts) Fig. 1 Communication diagram for Check-in Patient use case CI: Check Appointment C2 Patient Input CI.3: Appointmmt made C2.12 Checked in aStaff CI.4 Appointment made C2.11: Checked in CL.I: Check Appointment CI2: Check Appointment C2.4 Authorize ebusiness logico Chack-in system C2.7 Confirmation Number C 1.3 [Appointment made C2.5 Authorize 6: [Approval Confirmation C2.10: Add Patient Number cC2.2: Patient Input Medical Record C28: Confirmation Nuanber | 02.3: HI Inform. Patient Medical Record wentatys aHealth Insurance Company Your are required to develop the software architecture for a healthcare system, which provides check-in, payment, and automatic no-show charge use cases depicted in Figs. 1-6 using the communication diagram. Develop the software architecture for a healthcare system in the following order: 1. Develop the consolidated communication diagram that merges all communication diagrams to show all objects and their interaction. (3 pts) 2. Determine the subsystems (or components) of healthcare system and depict them on the consolidated communication diagram. (3 pts) 3. Depict function call or message communication for interactions between objects or between subsystems on the consolidated communication diagram. (3 pts) 4. Develop the software architecture diagram t that shows subsystems and their interaction. (6 pts) Fig. 1 Communication diagram for Check-in Patient use case CI: Check Appointment C2 Patient Input CI.3: Appointmmt made C2.12 Checked in aStaff CI.4 Appointment made C2.11: Checked in CL.I: Check Appointment CI2: Check Appointment C2.4 Authorize ebusiness logico Chack-in system C2.7 Confirmation Number C 1.3 [Appointment made C2.5 Authorize 6: [Approval Confirmation C2.10: Add Patient Number cC2.2: Patient Input Medical Record C28: Confirmation Nuanber | 02.3: HI Inform. Patient Medical Record wentatys aHealth Insurance Company