A Large Scale Agile Teaching Framework for Software Engineering
Bibliographic record
Abstract
There has been a great deal of interest in software engineering as a rewarding career in recent years as industry demands for software professionals continues to rise. As such enrollments in tech-related majors such as software engineering and computer science continues to increase. There are several sources available for learning software engineering including Massive Online Open Courses (MOOCs). Meanwhile, universities are the primary providers of high-quality instruction in this field. Universities have to accept many students, which has created many challenges, such as reducing the quality of education and difficulty managing classes by instructors and assistants. Universities also need to increase their faculty members and improve the educational infrastructure. The industry is changing rapidly and demands graduates to adapt to the needs of the industry as quickly as possible. In addition, they are expected to have some soft skills, such as critical thinking and teamwork, that make university training harder. Various methods have been developed for software engineering education to manage the challenges of large enrollments and providing hands-on learning. These methods are based on active learning, which focuses on the learner rather than the educator, and require more work from instructors. This thesis provides a framework for teaching software engineering (SE) that utilizes DevOps concepts in teaching to respond to the needs of universities, based on agile methodologies and project-based learning that have matured in the industry and educational field after many years. We used machine learning and ML4Code methods to address the challenges of providing scalable feedback in universities, which is an essential need for a practical discipline such as software engineering. During the winter of 2021, this framework was implemented in ENSF 607 - Advanced Software Development and Architecture at the University of Calgary. It was evaluated based on the students’ perceptions of its impact on their learning journey.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.020 | 0.010 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".