## 3 Methodology
### Selection and Evaluation Criteria for MLP Based on Adopted Framework  
FMEA implementation goes through a series of processes that involve the development of an FMEA data-gathering template. Software analysis using FMEA is achieved by evaluating each criterion derived from the developed framework and estimating their potential failure modes. These failure modes are called risk factors. In this study, the criteria  
Figure 8: Quality evaluation model based on ISO/IEC 9126.  
for evaluation are adopted from the developed framework ISO/ IEC 9126 standard. These attributes represent a detailed model for evaluating any software system [48]. Additionally, these criteria are used to evaluate the quality of the mobile learning platforms.  
The adopted model from the ISO/IEC 9126 standards has seven sub-criteria: time\(-\) behavior, fault tolerance, understandability, learnability, operability, attractiveness, and suitability. These sub-criteria cut across four main characteristics: efficiency, reliability, usability, and functionality. The choice of the criteria listed in the adapted framework was based on the criteria modified specifically for mobile learning platforms. The characteristics and sub-characteristics of the adopted framework are given earlier in Table 1.  
In this study, the sub-characteristics selected for evaluation are suitability, fault tolerance, understandability, learnability, operability, attractiveness, and time behavior.  
1. [label=(0)]
2. Suitability: The suitability of software refers to the essential functionality characteristic. It helps to answer the question, \"Can the software perform the tasks required? It enumerates a set of attributes used for the explicit assessment of functions to prescribed tasks, and to determine their adequacy for performing the tasks. It answers the question; \"How appropriate are the functions of software applied to the specification?\"  
A quality model is used to determine the quality of the software. Usability, which is one of the sub-characteristics of the quality model, is defined as the capability of the software product to be understood, learned, and used and the ability to provide visual appeal under certain specific conditions of usage (the effort needed for use).
3. Fault tolerance: Fault tolerance helps to determine if the software is capable of handling errors. It refers to the ability of a system to withstand component failure. It is defined as a set of attributes used to assess a software's ability to maintain the desired performance level in the unlikely event of operational defects or infringement of specified interfaces.
4. Understandability: This refers to how well or easily a user comprehends the functionality of a system. System functions and things like layout consistency, functions of buttons, clear prompts for input, consistent use of terms throughout the system, and proper documentation will all contribute to the ease of the system being understood.
5. Learnability: The learnability of software depicts how easily a user can learn to use the system. Although learnability is very similar to understandability, a major sub-characteristic is that it has to do with how long it takes users to learn how to use specific functions and the effectiveness of help systems. It is the learning effort required by users of various levels of difficulty during the learning process.
6. Operability: This is also one of the sub-characteristics of usability. It characterizes the ability to use the system with minimal effort. The operability of software depends on whether a user can operate and control the software in a given environment.
7. Attractiveness: Factors such as screen design, color, and general software interface are considered in determining the attractiveness of software.
8. Time Behavior: This characterizes how quickly the system responds and processing time when carrying out functions like file upload and download. The rate at which transactions are being processed and its ability to give an appropriate response time for a given throughput.