## 2 Proposed Software Architecture
### Software Architecture Evaluation
#### 2.4.2 Functional Suitability  
In this approach, functional suitability tests were performed using simulated scenarios. To evaluate the developed system for functional suitability, unit and integration tests were carried out to develop system services considering simulated earthquake scenarios. The simulated earthquake scenarios used in the unit and integration tests were based on the earthquake drills description outlined in the Mexican Civil Protection Program and school civil protection programs [5; 6; 7; 8], which detail the actions to be carried out before, during, and after an earthquake. In general, the scenarios included three two-floor buildings, two safety zones, two alarms, and the four brigades proposed in the civil protection program (evacuation, search and rescue, first aid and prevention, and fire extinguishing). Each brigade included two members: the brigade leader and an alternate. Each building was simulated to have 10 to 15 occupants. During scenario development, it was assumed that two to three individuals would remain inside the buildings, and the other participants would move to the safety zones. In the security zones, the brigade leaders conducted a roll call of people, marking individuals as located or absent from their applications. Subsequently, the head of the search and rescue brigade, using the developed system's services, identified the location of the people who remained inside the buildings to assist with the corresponding evacuation. Additionally, in one building, a participant simulated reporting a fire emergency. As a result, the brigade leader received an emergency report containing the name of the individual reporting, the type of emergency, and the location where the emergency was occurring. Finally, brigade leaders were instructed to compile a comprehensive report on the simulated earthquake drill for submission to the civil protection authorities. In the case of the mobile tier, it was deployed on three mobile devices. Concerning the manager tier, it was executed on a laptop. Table 1 describes the characteristics of these devices. The execution of the tests followed the standard format composed of the following elements:  
* Module: Name of the module to test. * Test: Test identifier. * Goal: Indicates the purpose of performing the test. * Requirements: Conditions that must be listed to execute the module. * Sequence: Indicates the steps that must be performed to achieve operation. * Achieved: Indicates if the correct operation is achieved or not. * Result: Indicates the results obtained. The purpose of applying unit tests is to ensure that the services or modules produce the expected results. Table 2 shows the general report of the unit tests conducted on the services of the manager tier modules, considering the administrator and assistant administrator users. Errors detected in the executed unit tests were fixed. On the other hand, Table 3 shows the final report of the unit tests conducted on the services of mobile tier modules for the GHEI personnel, evacuation brigade leader, and search and rescue brigade leader users. Errors detected in the executed unit tests were fixed. \begin{table}
\begin{tabular}{c c c c c c c} \hline \hline
**Devices** & **Operative** & **Processor** & **Processor** & **Processor** & **Graphic** & **RAM** \\  & **System** & & **Speed** & **Cores** & **Processor Unit** & **6 GB** \\ \hline Motorola Moto G4 (Sourced by & & & & & & \\ Motorola Mobility in & & & & & & \\ Gurgaon, India.) & & & & & & \\ Samsung Galaxy A51 (Sourced by & & & & & \\ Samsung Electronics SA de CV in & & & & & \\ Bae Ninh, Vietnam.) & & & & & \\ Xiaomi POCO X3 Pro (Sourced by & & & & & \\ Xiaomi Communications Co., Ltd. & & & & & \\ in Beijing, China.) & & & & & & \\ MacBook Air (Sourced by Apple & & & & & \\ in Beijing, China.) & & & & & & \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Device description.