MétaCan
Menu
Back to cohort
Record W4400335802 · doi:10.1145/3649405.3659512

Fostering Teamwork in Software Engineering Projects

2024· article· en· W4400335802 on OpenAlexaff
Mirela Gutica

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsBritish Columbia Institute of Technology
Fundersnot available
KeywordsTeamworkSoftware engineeringComputer scienceEngineering managementSoftware developmentSystems engineeringSoftwareEngineeringOperating systemManagement

Abstract

fetched live from OpenAlex

Part of computer science disciplines, software engineering (SE) is concerned with the software lifecycle and the rigorous methods and processes required for designing, implementing, modifying and maintaining high-quality software systems. Project-based and experiential learning are core to developing SE competencies and skills. Besides technical competencies, soft skills including adaptability, communication, critical thinking and teamwork are required and highly valued by employers. Several aspects affect the success of a project: the student engagement and participation, the team's dynamics and diversity, the mentoring strategy and the peer feedback process. Important aspects of teamwork are achievement of a high-level of cohesiveness between team members, and effective communication. However, we found that these aspects are impacted by deterrents to diversity and inclusion, and are not always achieved. The purpose of this study is to explore instructional models for teaching SE project courses that foster diversity and inclusion in teamwork, and promote engagement.

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.006
metaresearch head score (Gemma)0.021
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.006
Threshold uncertainty score0.032

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.021
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0020.001
Scholarly communication0.0020.001
Open science0.0010.006
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0020.001

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.029
GPT teacher head0.274
Teacher spread0.245 · 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.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreEmpirical

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

Citations1
Published2024
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207