Conception centrée sur l'utilisateur lors de la définition des exigences en RUP<sup>©</sup>. Une étude de cas
Bibliographic record
Abstract
We report a case study on how an HCI team introduced a User Centered Design (UCD) process into the Rational Unified Process (RUP) adapted by a software development project during the requirements discipline. The method suggested by the RUP for de user-interface design and the method used by the HCI team are presented. They are compared with the prescriptions of the ISO 13407 standard and the activities proposed by the RUP. The comparison corroborates some criticisms formulated in the literature about the weaknesses of the RUP for interactive application design. Nevertheless, we conclude that UCD can be integrated into the RUP. UCD allows requirements validation through use case iteration.
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.017 | 0.022 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.004 | 0.004 |
| Science and technology studies | 0.002 | 0.011 |
| Scholarly communication | 0.013 | 0.011 |
| Open science | 0.003 | 0.003 |
| Research integrity | 0.005 | 0.008 |
| Insufficient payload (model declined to judge) | 0.005 | 0.003 |
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".