Conclusions
The MSES602 DevOps course, and the labs it requires, are a fundamental component of the Enterprise Systems Engineering Program. However, an analysis of the perspectives of the pertinent stakeholders for the course and the key disciplines of Information Technology Management, Information Assurance, Data Management, Systems Engineering and Software Engineering shows several opportunities for improvement and functionality gaps in the current class structure. Consequently, in order to remain relevant and useful to future students MSES602 needs to evolve and adapt to the changing education climate.
Problem Statement
The core issues with the MSES602 DevOps labs revolve around the inconsistencies the students experience when attempting to complete the labs. The variances in student operating systems and hardware coupled with frequent updates to the software required for the labs and instructions that may not reflect these changes create a stressful and unstable environment. Additionally, the inability of the facilitators to know if students are struggling with a particular lab acts as an impediment to assisting the students.
…show more content…
Some aspects, such as the GitHub repositories, can still be effectively utilized. Unfortunately, any changes to the labs will come at a price which must be in alignment with Regis administration’s cost competitiveness goals. Therefore, the MSES602 labs must migrate from implementation on individual student machines with software packages installed on an ad hoc basis to a more unified implementation system capable of improving student satisfaction via delivery of a more consistent lab experience, increasing facilitator responsiveness through active monitoring of the labs, and yet support the cost competitiveness goals of the Regis