MétaCan
Menu
Back to cohort
Record W2346164804 · doi:10.1145/2851581.2851584

From Two CSCW Frameworks to User Requirements Definition for a Retail Planning Collaborative Software

2016· article· en· W2346164804 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicUsability and User Interface Design
Canadian institutionsJDA Software (Canada)
Fundersnot available
KeywordsComputer-supported cooperative workComputer scienceCollaborative softwareSoftwareSoftware engineeringHuman–computer interactionWorld Wide WebEngineeringProgramming languageWork (physics)

Abstract

fetched live from OpenAlex

This case study explains how we used two computer-supported cooperative work (CSCW) frameworks to define collaboration-related user requirements and experience attributes for Retail.Me, a new retail planning solution currently being designed at JDA Software. Our focus is on how this kind of framework can be used in industry and if one particular framework better answered our need to define user requirements and experience attributes for collaborative software. We explain how we configured each of the frameworks, how we reconciled them, and how this helped us reach our goal of defining user requirements and experience attributes for Retail.Me. At the end of this case study, we highlight differences in using the two frameworks, discuss their respective advantages and disadvantages and identify what we could have done to improve our process of defining user requirements and experience attributes.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.427
Threshold uncertainty score0.426

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.085
GPT teacher head0.328
Teacher spread0.243 · 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

Quick stats

Citations0
Published2016
Admission routes1
Has abstractyes

Explore more

Same topicUsability and User Interface DesignFrench-language works237,207