MétaCan
Menu
Back to cohort
Record W4399339128 · doi:10.1109/tem.2024.3409178

The Personas of Cloud CAD Collaboration: A Case Study of a Team of CAD Professionals

2024· article· en· W4399339128 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

VenueIEEE Transactions on Engineering Management · 2024
Typearticle
Languageen
FieldComputer Science
TopicPersona Design and Applications
Canadian institutionsUniversity of Toronto
FundersAlfred P. Sloan Foundation
KeywordsCADPersonaCloud computingEngineeringComputer scienceKnowledge managementEngineering managementHuman–computer interactionEngineering drawing

Abstract

fetched live from OpenAlex

Computer-aided design (CAD) has become a fundamental tool in engineering projects, particularly in product design and development. Recent advancements have shifted CAD systems to the cloud, referred to by us and others as <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">Cloud CAD</i> , offering a new realm for collaboration in product development projects. The transition to Cloud CAD introduces substantial changes to how one might manage product design teams, impacting how design tasks are divided among team members, the choices designers make in undertaking different tasks, and the additional responsibilities team members must fulfil. In this paper, we investigate the “personas,” described as patterns of activity representing an engineer's roles and responsibilities, that are essential to successful collaboration in Cloud CAD. To achieve this, we conducted a mixed-methods case study of a self-organized, time-bounded, and geographically distributed team of CAD professionals. This unique setting allowed us to identify and understand the personas that engineers adopt during Cloud CAD projects, where the engineers are not constrained to predefined roles and responsibilities. By analyzing CAD user action logs, the final CAD model, and semi-structured interview transcripts, we identified three integral personas in Cloud CAD projects: the guide, the integrator, and the communicator. We further observed that the emergence of each persona is temporally dependent, varying at different stages of the design process. Our work contributes an in-depth analysis of three personas in Cloud CAD, their relevance and benefits to CAD projects, and practical implications for engineering managers to support effective Cloud CAD collaboration.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.909
Threshold uncertainty score0.305

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.001
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.014
GPT teacher head0.265
Teacher spread0.252 · 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