MétaCan
Menu
Back to cohort
Record W2157129284 · doi:10.1145/1082983.1083000

Human and social factors of software engineering

2005· article· en· W2157129284 on OpenAlexaff
Michael John, Frank Maurer, Bjørnar Tessem

Bibliographic record

VenueACM SIGSOFT Software Engineering Notes · 2005
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsSocial software engineeringSoftware developmentPersonal software processSoftware Engineering Process GroupAgile software developmentSoftware engineeringSoftware requirementsSoftware peer reviewSoftware constructionComputer scienceSoftware development processSoftwareEngineeringEngineering management

Abstract

fetched live from OpenAlex

Software is developed for people and by people. Human and social factors have a very strong impact on the success of software development endeavours and the resulting system. Surprisingly, much of software engineering research in the last decade is technical, quantitative and deemphasizes the people aspect. The workshop on Human and Social Factors in Software Engineering has been picking up on the some of the soft aspects in software development that was highlighted in the early days of software engineering. It also follows a recent trend in the software industry, namely the introduction of agile methods, and provides a scientific perspective on these. Including and combining approaches of software engineering with social science, the workshop looked at software engineering from a number of perspectives, including those of agile methods and communication theory, in order to point out solutions and conditions for human-centred software engineering.

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.007
metaresearch head score (Gemma)0.024
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.998
Threshold uncertainty score0.035

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0070.024
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.002
Science and technology studies0.0020.009
Scholarly communication0.0050.003
Open science0.0000.003
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0050.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.020
GPT teacher head0.254
Teacher spread0.233 · 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 designTheoretical or conceptual
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

Citations67
Published2005
Admission routes1
Has abstractyes

Explore more

Same venueACM SIGSOFT Software Engineering NotesSame topicSoftware Engineering Techniques and PracticesFrench-language works237,207