MétaCan
Menu
Back to cohort
Record W1988244506 · doi:10.1109/agile.2014.17

Integrating Agile and User-Centered Design: A Systematic Mapping and Review of Evaluation and Validation Studies of Agile-UX

2014· article· en· W1988244506 on OpenAlexaff
Gabriela Jurca, Theodore D. Hellmann, Frank Maurer

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsAgile software developmentComputer scienceUser storyAgile usability engineeringField (mathematics)Agile Unified ProcessSystematic reviewSoftware engineeringUser experience designData scienceSoftwareSoftware developmentHuman–computer interactionSoftware development process

Abstract

fetched live from OpenAlex

Agile software engineering and user-centered design are two important development processes for ensuring that an application has good user experience. However, integrating these two different processes into a single Agile-UX approach remains difficult. We performed a systematic mapping study to identify relevant research and understand what the field of Agile-UX looks like at present. This mapping discovered that there were only a few evaluation and validation papers published to date, so we performed a review of these papers to better understand the recommendations of these types of papers. Based on this, we are able both to provide a discussion of common trends in these papers that should be of interest to practitioners and to identify gaps in existing literature that indicate strong opportunities for future work.

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 imitation

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

metaresearch head score (Codex)0.097
metaresearch head score (Gemma)0.264
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: Evaluation · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.903
Threshold uncertainty score0.514

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0970.264
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0040.003
Bibliometrics0.0390.035
Science and technology studies0.0020.003
Scholarly communication0.0060.007
Open science0.0020.004
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0010.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.105
GPT teacher head0.354
Teacher spread0.249 · 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 source (direct Gemma or distilled Codex), not a consensus.

Study designSystematic review
DomainEvaluation
GenreReview

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

Citations87
Published2014
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207