Human and social factors of software engineering
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.
Bibliographic record
Abstract
Workshop Summary: From its initial days in the sixties and seventies, the field of software engineering has to a large extent been concerned with the technological aspects of software as well as the formal procedures to be followed and artifacts to be produced in order to create high quality software. However, for some years we have seen a growing awareness that software engineering is a process involving humans, with all their particularities, working together in a social context: software projects rarely fail because of technical issues - their often fail because of human and communication problems. Psychological and sociological perspectives and theories have been used in order to understand concerns that may cause problems in the process of constructing and maintaining software, and further to develop means to cope with these issues. In particular among agile software development approaches, we have seen new and inventive approaches to solve some of the issues relating to behavior, group interaction and society. To make the social and human factors of software engineering more explicit, we aim among others to focus on psychological aspects of software developers and on the communication among software developers, between developers and users and other actors and stakeholders related to the software process. The formation of the social environment of the software developers, as well as its impact on productivity of the developments process and the quality of software is another pertinent issue. Another perspective is the role technological tools play in the construction of the social environment in which software engineers work. Thus, including and combining approaches of software engineering with theories of cognitive science, psychology and social science, the workshop will try to systematize the relevant factors, establishing a common ground for further studies on the topic. In particular, the workshop looks at software engineering from the perspectives of agile methods and communication theory in order to point out solutions and conditions for human-centered software engineering processes. Typical topics to be investigated are practices for knowledge dissemination in software engineering teams, knowledge reuse in software engineering projects, interactions in software development processes, social software approaches, decision making processes in software development and communication architectures for human-centric collaboration support of developer teams. In more general terms, we aim to provide a forum for researchers and practitioners to discuss the latest developments in the areas of cognitive & social science approaches to software development problems, knowledge engineering and software engineering approaches, and how these interact to create a human centered software development process.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it