## 4 Verification and Comparison of Desirable Requirements Considered in Related Work and Our Work  
This section verifies and compares the desirable requirements considered in software architectures aimed at developing SMDS focused on managing ECs reported in related work [11-25] and our work. The requirement verification is based on identifying desirable requirements that the systems oriented to managing the activities of the victims and evacuation, search, and rescue brigades must carry out before, during, and after an earthquake (see Section 2.1). Based on the requirement verification results obtained, one related work can be classified within the prevention subprogram of civil protection since it included a functional requirement to show the protocols when personal emergencies occur, i.e., it shows a first aid manual according to the situation [18]. Regarding the aid subprogram, five works consider functional requirements that are oriented toward the activities of this subprogram, such as showing the route to the nearest exit depending on the user's location, real-time consultation of risk areas, and modifying the indications of the nearest exits [13,15,16,18,25]. Concerning the recovery subprogram, after the emergency, it is notable that all the systems consider the functional requirements that are focused on the activities of this subprogram [11-25]. We note that none of the related works [11-25] propose a reference software architecture that includes all the desirable requirements that a system must consider for emergencies such as earthquakes. In particular, the requirements that are not considered in the software architectures proposed are the following: RF17--See list of academic staff, students, and outsiders, RF18--See details of the selected person, RF20--Classify building departments, RF22--Closing off evacuated areas and RF23--View report on closed areas.  
The lack of attention to the desirable requirements in the proposed works has led to suboptimal design decisions. Suboptimal design decisions in software architectures generate SMDSs focused on managing emergency cases that are not standardized in terms of the services provided to users, types and formats of data, and the use of incompatible protocols for exchanging, processing, and storing the information obtained. This implies a fragmentation of the developed systems and affects the functional suitability, usability, and interoperability of the proposed systems, as well as other types of systems needed in case of earthquakes in health and security. Specifically, imprecise architectural design has led to a lack of standardization and low quality of SMDSs focused on managing ECs regarding requirement coverage and correctness. Therefore, these works [11-25] do not adequately implement the activities that victims and evacuation, search, and rescue brigades must carry out in case of earthquakes in the proposed systems. Our work is characterized by modeling all the desirable requirements that a software architecture focused on developing systems oriented to managing the activities of the victims and evacuation, search, and rescue brigades must carry out before, during, and after an earthquake at GHEI. Based on the results obtained, our software architecture provides adequate architectural supportfor developing smart mobile distributed systems oriented to manage emergency cases at GHEIs with the required requirements and quality attributes.