## 4 Discussion of the Findings
### Empirical Validation  
Both quantitative and qualitative studies were carried out to explore the proposed RestRho, determining if it enabled software engineers and domain experts to build web pages faster with the least code possible. The quantitative study included both an experiment and a questionnaire, followed up by a qualitative usability questionnaire. The experiment illustrated that as the complexity became more difficult, it directly impacted the quality of the outcome and the ability to complete each task, which was expected. This is evident by analyzing the sub-categories (see Table 4) demonstrating a high completion rate at the beginning of the set of tasks, which steadily decreased as tasks became more complex. This was compounded by both the prior understanding of the DBRestRho and SQL-Rho languages versus the need for additional learning in specific functionality in RestRho. Students were able to easily apply their knowledge to producing higher-quality outcomes when prior knowledge existed. However, as the tasks became more complex and more native to the platform, the students were required to learn new functionalities via tutorials and written documentation. Nevertheless, in the qualitative study, many students raised their concerns about the steep learning curve. A total of 12.8% of respondents implied a low validity of RestRho because of a lack of documentation and the need for additional tutorials. This indicates that with additional time (training and practice) and further detailed documentation, the validity score will increase. As a result, the limited learning resources impacted the learning curve and, in turn, both the success rate and completion rates of latter tasks within each sub-category. Additionally, the qualitative study revealed that the absence of error handling proved to be challenging when it came to troubleshooting issues and finding resolutions. Additionally, the usability questionnaire, conducted during the quantitative study, demonstrated a dispersed response range, indicating that the ease of use of RestRho must be improved. Yet, in the same usability questionnaire, which explored utility, ease of use, ease of learning, and satisfaction, there is a direct correlation between ease of learning and ease of use. This is an expected result; when a platform is easier to learn, it becomes easier to use. Likewise, when a platform is easier to use, it becomes easier to learn. A direct correlation between the two is expected. The qualitative study supports this where the majority of respondents indicated the quick development in comparison with alternative tools as a direct result of ease of use. It is, then, evident that RestRho permits software engineers and domain experts to quickly create web pages while writing the least code possible, the purpose of this proposal. While the ease of use and usability indicate that there is a steep learning curve, students expressed in the qualitative feedback that once the workflow was known, it was easy to implement, especially because they could use existing languages. As previously identified, this steep learning curve could be solved with more documentation, examples, and tutorials. The same correlation exists between ease of use and utility. The more useful the application was to the student, the easier it became to use (implying that when the motivation to learn is high, ease of use subsequently increases). The purpose of this proposal was to enable software engineers and domain experts to quickly create web pages while writing as little code as possible. As main drivers in selecting a platform, it is imperative that these attributes were achieved. The qualitative study demonstrated that the main benefits were speed, efficiency, flexibility, and modularity. As a result, by focusing on the motivations that increase ease of use (the usefulness of the application) alongside the main drivers in selecting a platform (speed and efficiency), it is evident that RestRho successfully achieves what has been proposed, faster delivery with less coding.