MétaCan
Menu
Back to cohort
Record W4385692580 · doi:10.46254/sa04.20230110

Agile Course Planning in Educational Programs

2023· article· en· W4385692580 on OpenAlexaff
Manohar S. Madan, Kingsley Gnanendran

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsCourse (navigation)Agile software developmentComputer scienceSoftware engineeringEngineering managementEngineering

Abstract

fetched live from OpenAlex

An approach to course planning in educational programs was presented in Madan and Gnanendran (2020). There, each student's journey through a degree program was viewed as a "project" requiring completion of a set of tasks (courses) with each task having a specific duration (semester) and, possibly, precedence requirements (prerequisites). The institution is expected to offer courses in an appropriate sequence and timing so that students may progress toward graduation efficiently. Given the large number of students that could matriculate every semester, the institution needs to manage myriad individual degree pathways. To make this problem tractable, Madan and Gnanendran (2020) considered cohorts of students, rather than individuals, according to when each entered the program. The institution then only needs to manage a limited number of simultaneous projects with outcomes that are measured on the typical criteria of time and cost. Recently, researchers (e.g., Rigby et. al., 2016) have espoused the "agile" approach over the traditional "waterfall" approach to managing projects in environments where changes to requirements are to be expected, the work can be modularized, and there are avenues to collaborate with end-users. Since degree programs possess all of these characteristics, we propose heuristics based on agile methodology to address course planning and demonstrate their application via numerical examples.

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 distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.653
Threshold uncertainty score0.139

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.

Opus teacher head0.040
GPT teacher head0.335
Teacher spread0.294 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreMethods

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".

Quick stats

Citations0
Published2023
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207