# Real-Time Evaluation of the Improved Eagle Strategy Model in the Internet of Things
## 5 Testing and Validation
### Evaluate the Correctness of the Service Selected
This application supports multiple protocols such as WDSL, SOAP, etc. To evaluate the correctness of the services, ReadyAPI was used [42]. In our research, we employed the SOAP protocol, primarily due to its robust security features and well-defined standards, which were crucial for our application's specific requirements. SOAP's capability for built-in error handling and support for ACID-compliant transactions was particularly aligned with the needs of our Improved Eagle Strategy (IES) model. For the Smart Toilet System, the intricate nature of transactions and the necessity for detailed error reporting made SOAP an ideal choice. Its ability to efficiently manage complex transactions ensured the reliable execution of critical functions, including the'send SMS' service. Although the superior performance and flexibility of RESTful services and GraphQL are recognized, these protocols did not meet the stringent criteria for security and transactional integrity. The rigorous security standards and reliable transaction support provided by SOAP were indispensable for maintaining the integrity and reliability of the IES model, especially in scenarios demanding high-stakes data handling and communication. Figure 23 illustrates the flowchart for using the send SMS function of the WS. Sending an SMS when the alarm is triggered is part of the flowchart of the Smart Toilet System. A test case was run to verify the selected service by the IES. This was done to ensure that the IES selected the correct service. The method name needed to be provided based on the requirement. As per the case study, sending an SMS service was required. Therefore, the keyword that was provided in the IES system was \"SMS\". Figure 24 below shows the user interface for keying in the keyword. \begin{table}
\begin{tabular}{c c c} \hline
**Response Code** & **Meaning** & **Description** \\ \hline
200 & OK & The request was successful, and the server returned the requested data. \\ \hline
404 & Not Found & The requested resource could not be found on the server. \\ \hline
401 & Unauthorized & The client attempted to access a protected resource without proper authentication credentials. \\ \hline
403 & Forbidden & The server refused to fulfill the request, likely because the client did not have proper permission to access the resource. \\ \hline
500 & Internal Server Error & The server encountered an error while attempting to fulfill the request. \\ \hline \end{tabular}
\end{table} 
Table 7: HTTP response state. Send SMS services successfully passed the test cases as the objective of the selected service was achieved, as shown in TC1, Table 9. The selected service can send messages to the stated phone number. To validate the process further, test cases were conducted on an additional two (2) services. The keyword was provided randomly. The keywords used to perform test cases were \"weather\" and \"currency\". The table below shows the weather service test objective and test cases. Table 10 shows the test objective for the weather conversion. The test aimed to ensure the value keyed in the Celsius column can be converted to Fahrenheit. Test case details are presented in the following table. According to the test cases for the weather Table 11, the conversion was successful if the input value is an integer. If not, the error message was displayed. The weather conversion was successfully providing the output. Table 12 shows the test objective for the currency keyword. The test aimed to list the details of a country based on the currency chosen. Test case details are presented in Table 13. The test case's result was successful, as the expected and actual outcomes matched.