## 3 Validation and Experimentation
### Empirical Validation
#### 3.2.3 Qualitative
Much of the homework was done with the knowledge that I simply had up to now.\"_ (Student 1)  
_\"I find it quite useful once the workflow is known.\"_ (Student 30)  
However, in order to achieve this, some students noted that there was an initial steep learning curve that could be resolved with additional documentation, examples, and tutorials. _\"Little documentation.\"_ (Student 6)  
_\"I wish there was more documentation to look at in case there is a concept that I do not understand.\"_ (Student 8)  
_\"The documentation should be a bit more explanatory.\"_ (Student 18)\"Lack of clear documentation and usage examples.\"_ (Student 21)  
Additionally, inconsistencies in syntax and behavior were highlighted, impacting the usability of RestRho. \"Having to learn new syntax and use more than one program to see results.\" (Student 12)  
Ease  
The ease of use of the proposed RestRho is ascertained by this theme as it explores the ease of navigation and functionality. Moreover, negative aspects of RestRho are explored and analyzed. The majority of respondents indicated the quick development of web pages in comparison with using other tools, as RestRho required less coding. \"The server is much faster and its syntax is easier to handle. There is obviously an advantage against Java Spring, for example.\" (Student 1)  
\"In general it is quite complete and fast.\" (Student 7)  
\"Speed and above all his intuitiveness to do things.\" (Student 13)  
\"The server is much faster and its syntax is easier to handle. There is obviously an advantage against Java Spring, for example.\" (Student 18)  
\"It can be done faster unlike other programs\" (Student 27)  
\"Speed to create them [Web Microservices].\" (Student 30)  
\"It is faster\" (Student 39)  
Additionally, the ease of creating CRUD operations and making database queries was highlighted as a key advantage. \"Simplicity and Fast code creation (crud, services, login)\" (Student 6)  
\"It delivers a framework, where you only have to worry about defining what is necessary.\" (Student 30)  
However, some respondents noted error handling challenges, which made troubleshooting difficult. \"Error handling is complicated due to JavaScript; this could be improved in the future.\" (Student 21)  
\"Mainly error handling, it would be useful to know what I'm missing or what I've done wrong, for example, if I misspelled the name of a table, it could indicate that \"table \"table1\" does not exist in the database\" or something for the style\" (Student 32)  
Security  
Security addresses issues associated with security, performance, and authentication. While there was no specific question addressing security, it was a common theme that arose in questions two, five, and six (see Table 7), suggesting that security is both an advantage of RestRho yet also a negative requiring improvement. When identifying the advantages of using RestRho to create web pages, flexibility and security were identified as the main advantages. \"Flexibility--Control over the page--Security and personalization\" (Student 16)  
Yet, security was also raised as a negative aspect of RestRho, as it may create dependencies on other libraries and tools, creating security issues. \"Ifthe RestRho uses third-party libraries or tools, there is a risk of being dependent on their maintenance and updating. If these dependencies are not regularly updated or become outdated, there could be security issues or lack of long-term support.\"_ (Student 5)  
In light of these negative aspects, the qualitative study also provided opportunities for improvement in the areas of authentication and security. \"Consider including authentication and authorization functionalities in the RestRho.\" (Student 5)  
\"Focus on security: Make sure that the RestRho implements strong security measures to protect web pages and associated data.