Co-aligning User-Centered Design and Software Engineering Courses
Bibliographic record
Abstract
Introducing students to different perspectives and roles in the development process allows them to engage in the work of cross-disciplinary diverse teams and even can enable them to change roles in designer-developer interactions. Industry work often places recent graduates in preexisting polarized relationship dynamics between different participants in the design and development process. This paper describes a two-stage attempt at co-alignment of software engineering and user-centered design courses: from full alignment with topic intersections and joint project to partial alignment through separate activities. We discuss challenges of both ways including time or technical constraints, increased effort from the program developers and instructors, students' and instructors' frustrations. We finalize by describing benefits of providing students with early experience identifying trade-offs between design requirements and architecture and opportunities for diverse group with different background in computer science.
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.031 | 0.067 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.003 | 0.002 |
| Scholarly communication | 0.010 | 0.007 |
| Open science | 0.003 | 0.015 |
| Research integrity | 0.002 | 0.006 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
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".