Proceedings of the 5th Workshop on Evaluation and Usability of Programming Languages and Tools
Notice bibliographique
Résumé
It is our great pleasure to welcome you to the 5th Workshop on Evaluation and Usability of Programming Languages and Tools -- PLATEAU'14. This year's workshop continues its tradition of being the forum for presentation of research results and experience reports on methods, metrics, and techniques for evaluating the usability of languages and language tools. PLATEAU gives researchers and practitioners a unique opportunity to share their perspectives with others interested in the various aspects of evaluation of mprogramming languages and tools. Putting together PLATEAU 2014 was a team effort. We first thank the authors for providing the content of the program. We are grateful to the program committee who worked very hard in reviewing papers and providing feedback for authors. Finally, we thank the hosting organization SPLASH, sponsors: ACM and SIGPLAN, conference supporters, and the SPLASH Workshop Co-Chairs Stephanie Balzer and Du Li. Workshop Overview Programming languages exist to enable programmers to develop software effectively. But how efficiently programmers can write software depends on the usability of the languages and tools that they develop with. The aim of this workshop is to discuss methods, metrics and techniques for evaluating the usability of languages and language tools. The supposed benefits of such languages and tools cover a large space, including making programs easier to read, write, and maintain; allowing programmers to write more flexible and powerful programs; and restricting programs to make them more safe and secure. We plan to gather the intersection of researchers in the programming language, programming tool, and human-computer interaction communities to share their research and discuss the future of evaluation and usability of programming languages and tools. We are also interested in the input of other members of the programming research community working on related areas, such as refactoring, design patterns, program analysis, program comprehension, software visualization, end-user programming, and other programming language paradigms. Main Themes and Goals Following on from the four previous workshops at SPLASH, this workshop aims to bring together practitioners and researchers interested in discussing usability and evaluation of programming languages and tools with respect to language design and related areas. We will consider: empirical studies of programming languages; methodologies and philosophies behind language and tool evaluation; software design metrics and their relations to the underlying language; user studies of language features and software engineering tools; visual techniques for understanding programming languages; critical comparisons of programming paradigms, such as object-oriented vs. functional; and tools to support evaluating programming languages. We have two goals: Develop and sustain a research community that shares ideas and collaborates on research related to the evaluation and usability of languages and tools. Encourage the languages and tools communities to think more critically about how usability affects the design and adoption of languages and tools. Workshop Progam For the workshop program we solicited three kinds of papers: research papers, position papers, and hypothesis papers. Research papers can describe work-in-progress or recently completed work on the themes and goals of the workshop or related topics. Position papers can report on experience, question accepted wisdom, raise challenging open problems, or propose speculative new approaches. Hypothesis papers will identify and collect the unsubstantiated beliefs of the research community or software industry. The hypotheses can be collected from mailing lists, blog posts, paper introductions, developer forums, or interviews. Authors were encouraged to document the source or sources of each hypothesis and to discuss the impact of the hypotheses on research or practice. Research papers were limited to 10 pages in length and both position and hypothesis papers limited to 2 pages in length. The call for papers attracted submissions from the following countries: Australia, Austria, Canada, Chile, China, Germany, New Zealand, and the United States. The program committee reviewed and accepted the following papers: Track Reviewed Accepted Rate Research Full Papers 8 5 63% Position / Hypothesis Papers 6 5 83%
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.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,061 | 0,081 |
| Méta-épidémiologie (sens strict) | 0,002 | 0,002 |
| Méta-épidémiologie (sens large) | 0,002 | 0,002 |
| Bibliométrie | 0,004 | 0,002 |
| Études des sciences et des technologies | 0,003 | 0,004 |
| Communication savante | 0,017 | 0,013 |
| Science ouverte | 0,004 | 0,010 |
| Intégrité de la recherche | 0,004 | 0,006 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,048 | 0,016 |
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écouleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».