Human and social factors of software engineering
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
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.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,001 |
| Science ouverte | 0,001 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle