## 5 Research Results
### Delivery of Learning Material and Pre-Course Surveys to Measure Changes in Knowledge and Skills
\begin{table}
\begin{tabular}{p{113.8 pt} p{113.8 pt} p{113.8 pt} p{113.8 pt}} \hline \hline
**Topic** & **Question** & **Key Themes** & **Example Answers** \\ \hline Lessons Learned & What lessons have you learned from previous projects regarding architectural design that you ap current project? & Gradual adoption and planning & “Starting small with MACH components and gradually migrating other services helped manage the transition smoothly”. \\ \cline{3-4}  & What lessons have you learned from previous projects regarding architectural design that you ap current project? & Training and communication & “Ensuring the team is well-trained on cloud-native tools before starting the project minimized delays”. \\ \cline{3-4}  & What lessons have you learned from previous projects regarding architectural design that you ap current project? & Security and monitoring & “We found that setting up a robust monitoring system early in the project was essential”. \\ \cline{3-4}  & What lessons have you learned from previous projects regarding architectural design that you ap current project? & Modularity and flexibility & “We could easily add new microresources without affecting existing ones, thanks to the architecture’s modularity”. \\ \cline{3-4}  & How adaptable is your architecture to changes in project scope, technology, or requirements? Can you provide examples where you had to adapt your architecture? & “We could quickly scale our architecture to support a global user base, thanks to its modular design”. \\ \cline{3-4}  & How do you manufacturer architectural? & Security and compliance & “When security requirements tightened, we could quickly adapt by implementing new protocols without major overhauls”. \\ \cline{3-4}  & How do you manage architectural documentation, and what role does it play in your project? How do you ensure that it stays relevant and useful? & Automation and integration & “We use automated testing to ensure our documentation is accurate and up-to-date”. \\ \cline{3-4}  & How do you manage architectural documentation, and what role does it play in your project? How do you ensure that it stays relevant and useful? & “We ensure that all stakeholders, including non-technical ones, can access and understand the documentation”. \\ \cline{3-4}  & How do you ensure that it stays relevant and useful? & Version control and consistency & “We use version-controlled documentation to track changes and maintain consistency across teams”. \\ \hline \hline Future Trends & What trends do you foresee in software architecture that might influence your future projects? & Serverless and edge computing & “I foresee increased adoption of serverless architecture combined with MACH for greater scalability”. \\ \cline{3-4}  & What trends do you foresee in software architecture that might influence your future projects? & AI and automation & “The increasing complexity of IT environments will drive the need for more automated, AI-driven management tools”. \\ \cline{3-4}  & Security and privacy & “Decentralized architectures, like blockchain, might start integrating with MACH to enhance security and data integrity”. \\ \hline \end{tabular}
\end{table} 
Table 3: _Cont._each student team [43; 44]. Before starting the implementation of the sprint, another set of qualitative and quantitative questionnaires was delivered. The aim of these questionnaires was to measure changes in skills related to the understanding and implementation of MACH principles. The questions were designed to provide insight into theoretical practices and the application of each of the four MACH principles. Each question had two parts: the first was a knowledge assessment where students choose one of four offered answers (one correct answer), and the second was a self-assessment of their skills, where they rated their skills on a scale from 1 to 5, with 1 representing a low skill level and 5 representing a high skill level. The questionnaire is provided in Table 4.  
**Pre-Course Survey on MACH Architecture**  
**Microservices Implementation**  
**1.