Bibliographic record
Abstract
Given the complexity and cost of modern software projects, employers want new hires to be skilled at documenting and verifying software requirements. However, anecdotally, final-year students do not believe these skills are as important as hard skills like programming, and as such do not focus on learning them. Following other researchers' leads, we believe infusing Design Thinking (DT) into a final-year software engineering Capstone course will help close the gap between student skills and employer demands. We propose a phenomenographic study to understand final-year students' experiences with requirements elicitation and traceability between design decisions and requirements. We plan to use the information gathered from this study to inform the design of a DT tool to help student teams capture project information and support end-to-end backward and forward traceability of design decisions. By finding ways to reduce friction in documenting and tracing requirements, we expect to see an increase in student engagement and better requirement and traceability outcomes than the traditional approach.
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.030 | 0.054 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.007 |
| Scholarly communication | 0.009 | 0.007 |
| Open science | 0.004 | 0.012 |
| Research integrity | 0.004 | 0.007 |
| Insufficient payload (model declined to judge) | 0.005 | 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".