## 3 Validation and Experimentation
### Empirical Validation
#### 3.2.2 Quantitative
For instance, participants P6, P8, P9, P11, P13, and P26 scored above 90%, all with standard deviations below 11. Conversely, participants P2, P17, and P33 achieved the lowest average success percentages, scoring 31 (SD = 27.1), 33.3 (SD = 32.7), and 34.9 (SD = 19.9), respectively. These lower results are primarily attributed to low scores in tasks involving the use of Handlebars templates (TT4). These outcomes not only offer insights into participants' strengths and weaknesses in executing specific tasks but also suggest opportunities for continuous improvement. Providing additional resources, specific training on Handlebars template usage, and alternative approaches to address identified challenges could benefit the future execution of similar tasks. Table 6 presents the success rate and completion of tasks carried out by the participants in the experiment. The rows represent the 18 tasks that the participants performed during the study (see Table 4 for additional details). In the \"Task Success Rate\" columns, the results of successful task execution, their types, and associated main activities are displayed. It is noteworthy that the development of the SQLRho program (MA1) achieved a higher average success rate than the corporate website development (MA2), recording 65 (SD = 28.6) and 50.4 (SD = 34.9), respectively. It is relevant to mention the high variability with standard deviations above 25 in both cases. Among the task types, those related to configuring the SQLRho program with the 'employees' database (TT1) and operations in the 'employees' table (TT3) obtained the highest ratings, with 99 (SD = 6.4) and 63 (SD = 26.6), respectively. All these results surpassed the 50% threshold, considered positive, especially given the diversity and difficulty of the tasks. Generally, tasks involving the use of Handlebars templates obtained lower success rates due to their higher level of difficulty. These tasks required the utilization of previous task outcomes as well as integrating templates, CRUD operations, and diagrams for website development. It is observed that activities related to the initial setup of the SQLRho program (MA1) stand out with more consistent and higher performance compared with corporate website development (MA2). This discrepancy might suggest a greater familiarity or mastery by the participants in program configuration rather than web design and development. Regarding the task completion rate, Table 6 identifies the number of incomplete tasks (considered as null scope in task execution), completed tasks (with some level of success ful execution), and the rate (calculated as the ratio between the number of incomplete and completed tasks). It is notable that tasks T1, T8, and T9 achieved a 100% completion ratio. Moreover, 94% of the tasks achieved a completion ratio higher than 80%, which is considered positive given the variety and difficulty of the evaluated tasks. Toward the conclusion of our experimental session, participants were asked to complete a comprehensive 30-question questionnaire to evaluate the usability of our proposal. This questionnaire was designed to assess various aspects such as utility, ease of use, ease of learning, and satisfaction. Figure 12 depicts the outcomes derived from analyzing the questionnaire responses, showcasing the average scores (ranging from 1 to 5) obtained for each dimension. Additionally, these results are presented alongside error bars, representing the standard deviation (\(\pm\sigma\)). Given the proximity of the mean results across the four dimensions, we delved into a potential correlation among these values. Consequently, a calculation was conducted to gauge the correlation coefficient between the assessed dimensions. This analysis sought to quantify the extent of linear association among these dimensions.