MétaCan
Menu
Back to cohort
Record W2462137674

Architecting tools to support transitions in workstyle

2004· article· en· W2462137674 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 institutionsQueen's University
Fundersnot available
KeywordsCollaborative softwareVariety (cybernetics)Computer-supported cooperative workComputer scienceDomain (mathematical analysis)Human–computer interactionKnowledge managementSoftware engineeringWork (physics)Engineering
DOInot available

Abstract

fetched live from OpenAlex

Challenges in designing effective groupware include technical issues associated with concurrent and distributed work, as well as social issues associated with supporting group activities. These challenges are further complicated by limited experience with successful designs and insufficient understanding of group interaction dynamics. Although groupware applications must be well designed for individual users, they must also appropriately support the activities of interactive groups. Specifically, members of collaborative groups interact with each other in a variety of ways, so groupware tools must be designed to support a variety of collaborative working styles. Furthermore, members of collaborative groups move frequently between different styles of interaction throughout the course of their work, so groupware tools must be designed to support fluid transitions between different interaction styles. In order to focus our research, we have concentrated on the limited domain of collaborative software design tools. We have applied ethnographic study and activity analysis to demonstrate the importance of supporting different styles of interaction and transitions between them in collaborative software design, and to identify common interaction styles and transitions in this domain. We have developed design and analysis techniques that link requirements to architectural decisions in order enable systematic design of architecture to support different interaction styles and transitions between them. We have applied these techniques to the design of a prototype tools supporting collaborative software design. Although our investigation has been limited to the domain of collaborative software design, we believe these techniques to be widely applicable.

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.000
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: Empirical · Consensus signal: none
Teacher disagreement score0.654
Threshold uncertainty score0.303

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.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.051
GPT teacher head0.282
Teacher spread0.231 · 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
Published2004
Admission routes1
Has abstractyes

Explore more

Same topicUsability and User Interface DesignFrench-language works237,207