Measuring Curriculum-Labor Market Alignment at the Scale of a Program Portfolio

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.12356v1 Announce Type: cross Abstract: A college offering several overlapping computing degrees implicitly assumes that its programs are differentiated in line with how the labor market segments computing work and that, together, they prepare graduates for that market. Testing this is difficult, because the instruments available to curriculum committees, namely advisory boards, tracer studies, and employer surveys, are slow, narrow, and hard to reproduce. We apply one uniform, taxonomy-anchored alignment analysis across all five undergraduate programs of a College of Information Technology, comparing 1,922 course learning outcomes against 103,349 competencies extracted from a unified corpus of 5,186 deduplicated job openings from four boards. Every competency is obtained by a grounded single-language-model procedure that copies it verbatim from the source and verifies it against the source, then assigns it to one of eleven ESCO-aligned domains and a Bloom cognitive level; the curricular supply is read not as a catalog but on a realized-attainment basis that respects the credit-hour and elective constraints under which a student completes a degree. The extraction is validated blind by two independent faculty raters (domain kappa 0.91, Bloom level kappa 0.86) and the ESCO matching against a human-adjudicated gold set (kappa 0.72). Four findings emerge. The content gaps are systemic rather than program-specific, concentrated in systems, software engineering, security, and web development; the shared college core satisfies only about a third of the demanded …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.12356
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.