CHASE 2019

12th International Workshop on Cooperative and Human Aspects of Software Engineering

(CHASE 2019)

An ICSE 2019 Workshop

Montréal, QC, Canada

May 27, 2019

Workshop Overview

The software industry is experiencing dramatic changes: distributed software development done in an agile way; agile methodologies scaled to meet the requirements to support projects with several hundred developers; and frequently deploying software which leads to continuous development practices. As software engineering practices evolve, the Cooperative and Human Aspects of Software Engineering (CHASE) change as well. It is crucial to understand current and emerging software practices, processes, and tools and their impact on important local and global issues. In turn, this enables us to design tools and support mechanisms that improve software creation and maintenance, customer communication, and the use and evolution of deployed software systems. 

CHASE will provide a forum for both exploring new directions, presenting mature research, and discussing early results. This will be the 12th in a series of workshops held at ICSE focusing on this theme. Based on our experience, it will be a meeting place for the academic, industrial, and practitioner communities interested in this area, and will give opportunities to present and discuss works-in-progress.. 

This will be the 12th in a series of workshops held at ICSE focusing on this theme. The visualization of CHASE history and CHASE authors' network can be viewed in the following link: http://chasevis.azurewebsites.net/.

Workshop Program

May 27, 2019

List of Accepted Papers

• Orit Hazzan and Yael Dubinsky. A Biomimicry Perspective at Agile Software Exponential Organizations

• Julio Cesar Cortes Rios, Kamilla Kopec-Harding, Sukru Eraslan, Christopher Page, Robert Haines, Caroline Jay, and Suzanne M. Embury. A Methodology for Using GitLab for Software Engineering Learning Analytics

• Karina Kohl and Rafael Prikladnicki. A Systematic Mapping Study of Diversity in Software Engineering: A Perspective from the Agile Methodologies

• Jinghui Cheng and Jin L.C. Guo. Activity-Based Analysis of Open Source Software Contributors: Roles and Dynamics

• Emily Winter, Stephen Forshaw, Lucy Hunt, and Maria Angela Ferrario. Advancing the Study of Human Values in Software Engineering

• Vibhu Saujanya Sharma, Rohit Mehra, Vikrant Kaulgud, and Sanjay Podder. An Extended Reality approach for creating Immersive Software Project Workspaces

• Daniel Helgesson, Emelie Engström, Per Runeson, and Elizabeth Bjarnason. Cognitive Load Drivers in Large Scale Software Development

• Rafael Chanin, Leandro Pompermaier, Afonso Sales, and Rafael Prikladnicki. Collaborative Practices for Software Requirements Gathering in Software Startups

• Adriana Meza Soria and André van der Hoek. Collecting Design Knowledge through Voice Notes

• Mohammed Alhamed and Tim Storer. Crowd Planning Poker: Where Crowds Plan as well as Experts

• Peggy Gregory and Katie Taylor. Defining Agile Culture: A Collaborative and Practitioner-led Approach

• Felipe Fonseca, Eduardo Bezerra, and Diogo S. Mendonça. Designing Dojo: A collaborative method for teaching design patterns

• Tudor B. Ionescu. Developing Software for the Shopfloor on the Shopfloor: An Ethnographic Study of Software Engineering Practices in and for the Smart Factory

• Adriana Lopes, Edson Oliveira, Tayana Conte, and Clarisse de Souza. Directives of Communicability: Towards a Better Communication Through Software Models

• Shahab Bayati. Effect of Newcomers Supportive Strategies on Open Source Projects Socio-Technical Activities

• André Pinheiro, Caio Rabello, Leonardo Furtado, Gustavo Pinto, and Cleidson R.B. de Souza. Expecting the Unexpected: Distilling Bot Development, Challenges, and Motivations

• Rafael de Mello, Anderson Uchôa, Roberto Oliveira, Daniel Oliveira, Baldoino Fonseca, Alessandro Garcia, and Fernanda de Mello. Exploring the Theory of Social Representations: A Preliminary Study of Code Smell Identification

• Tamara Lopez, Helen Sharp, Thein Than Tun Tun, Arosha Bandara, Mark Levine, and Bashar Nuseibeh. 'Hopefully We Are Mostly Secure': Views on Secure Code in Professional Practice

• Johannes Berglind Söderqvist, Ludvig Lindlöf, and Lars Trygg. Inter-team coordination in agile development - Learning from non-software contexts

• Shreya Kumar and Charles Wallace. Patterns of Identity and Interaction in an Evolving Agile Workplace

• Benjamin Meyers, Nuthan Munaiah, Andrew Meneely, and Emily Prud'Hommeaux. Pragmatic Characteristics of Security Conversations: An Exploratory Linguistic Analysis

• Giovanni Viviani and Gail Murphy. Reflections on onboarding practices in mid-sized companies

• Tiago Massoni, Nilton Ginani, Wallison Silva, Zeus Barros, and Georgia Moura. Relating Voluntary Turnover with Job Characteristics, Satisfaction and Work Exhaustion - An Initial Study with Brazilian Developers

• Rohan Krishnamurthy, Thomas Heinze, Carina Haupt, Andreas Schreiber, and Michael Meinel. Scientific Developers v/s Static Analysis Tools

• Myrian Raquel Noguera Salinas, Adolfo Gustavo Serra Seco Neto, and Maria Claudia Figueiredo Pereira Emer. Short Datathon for the Interdisciplinary Development of Data Analysis and Visualization Skills

• Caio Borges, Sabrina Marczak, Cleidson R.B. De Souza, Luiz Guerra, Luiz Mosmann, Fernando Figueira Filho, and Marcelo Perin. Social Aspects and How They Influence MSECO Developers

• Andreas Bäckevik, Erik Tholén, and Lucas Gren. Social Identity in Software Development

• Carol Cardenas, Jenny Gil, and Paula Rodríguez. Soft Skills Training: Performance Psychology Applied to Software Development

• Abdulaziz Alaboudi and Thomas D. LaToza. Supporting Software Engineering Research and Education by Annotating Public Videos of Developers Programming

• Leticia Machado, Ricardo R.M. Melo Melo, and Cleidson R.B. De Souza. The Role of Platform Moderators in Software Crowdsourcing Projects

• Farshid Anvari, Hien Minh Thi Tran, Deborah Richards, and Michael Hitchens. Towards a Method for Creating Personas with Knowledge and Cognitive Process for User Centered Design of a Learning Application

• Sami Jantunen, Rex Dumdum, and Donald Gause. Towards New Requirements Engineering Competencies

• Mario Rosado de Souza, Robert Haines, Markel Vigo, and Caroline Jay. What makes research software sustainable? An interview study with research software engineers.

• Ronnie E.S. Santos, Maria Teresa Baldassarre, Fabio Q. B. da Silva, Cleyton Vanut Cordeiro de Magalhães, Luiz Fernando Capretz, and Jorge Correia-Neto. Work Design and Job Rotation in Software Engineering: Results from an Industrial Study

Important Dates

• • Workshop paper submissions due: February 1, 2019  February 7, 2019 AOE.

  • Notification to workshop paper authors: March 1, 2019 AOE.

  • Camera Ready deadline: March 15, 2019 AOE.

  • Workshop: May 27, 2019.

Workshop Themes                                                

Topics of interest are about the human, cooperative, and collaborative aspects of software engineering such as:

• • Software design or engineering philosophies, practices, and tools;

  • Adapting tools or processes to accommodate a range of organizational and cultural situations;

  • Sociological, cultural, psychological, or cognitive aspects of software design or engineering;

  • Managerial or organizational aspects focused on people and their interactions;

  • Teamwork, collaboration, or cooperation in or across various development teams and methodologies;

  • Community-based software development (e.g., Open Source, crowdsourcing, etc);

  • Coordination and knowledge sharing at different scales (e.g., distributed teams, semi-anonymous collaboration, “borderless” teams);

  • Stakeholder participation within and across phases;

  • Processes and tools to support communication, collaboration, and cooperation among stakeholders.

Possible contributions include:

• • Empirical studies of software engineering teams or individuals in situ;

  • Laboratory studies of individual or team software engineering behavior;

  • Novel tools or processes motivated by observed needs or empirical investigations; 

  • Use of analysis techniques or frameworks from disciplines outside software engineering, applied to empirical software engineering topics;

  • Meta-research topics.

Submissions

We have three paper categories: 

• 8-page full papers.

• 4-page short papers.

• 2-page notes.

These different categories offer researchers who are at different stages in their research maturity the opportunity to benefit from workshop participation. Page limits include references. 

All paper and notes submissions will be reviewed by 3 program committee members. The authors of accepted submissions will be asked to join the workshop. We will encourage all participants to submit at least a 2-page note, but the workshop will be open. All interested parties are welcome to register, even without an accepted paper.

Submissions should be made at the following website: 

https://easychair.org/conferences/?conf=chase2019

Workshop proceedings will be prepared by IEEE CPS and published by ACM. Workshop papers must follow the ICSE 2019 Format and Submission Guidelines. Accepted papers will be hosted on a password-protected, CHASE-hosted, collaboration site to foster discussion prior to the workshop. The official publication date of the workshop proceedings is the date the proceedings are made available in the ACM Library. This date may be up to two weeks prior to the first day of ICSE 2019. The official publication date affects the deadline for any patent filings related to published work.

Given time limitations and the interactive nature of CHASE's workshop format (for instance, see the CHASE 2018 Program), only a subset of papers will be selected for presentations based on their representativeness and potential for generating discussion. All accepted papers may contribute a poster to a poster session. All interested parties are welcome to register, even without an accepted paper.

Workshop Organizers 

• • Yvonne Dittrich, IT University of Copenhagen, Denmark

  • Fabian Fagerholm, University of Helsinki, Finland and Blekinge Institute of Technology, Sweden

  • Rashina Hoda, The University of Auckland, New Zealand

• David Socha, University of Washington Bothell, USA 

• Igor Steinmacher, Northern Arizona University, USA

Program Committee

• • Andrew Begel, Microsoft Research, USA

  • Matthias Book, University of Iceland, Iceland

  • Fabio Calefato, University of Bari, Italy

  • Tayana Conte, UFAM, Brazil

  • Cleidson R. B. de Souza , Universidade Federal do Pará and Instituto Tecnológico Vale, Brazil

  • Giuseppe Destefanis, Brunel University, United Kingdom

  • Torgeir Dingsøyr, SINTEF Information and Communication Technology, Norway

  • Neil Ernst, Software Engineering Institute, USA

  • Robert Feldt, Blekinge Institute of Technology, Sweden

  • Fernando Figueira Filho, Federal University of Rio Grande do Norte, Brazil

  • Davide Fucci, University of Hamburg, Germany

  • Daniel Graziotin, University of Stuttgart, Germany

  • Lucas Gren, Gothenborg, Sweden

  • Hideaki Hata, Nara Institute of Science and Technology, Japan

  • Sandeep Kaur Kuttal, University of Tulsa, USA

  • Filippo Lanubile, University of Bari, Italy

  • Thomas Latoza, George Mason University, USA

  • Meira Levy, Shenkar Engineering, Design, Art, Israel

  • Sherlock Licorish, University of Otago, New Zealand

  • Tamara Lopez, The Open University, United Kingdom

  • Stephen MacDonell, Auckland University of Technology, New Zealand

  • Sabrina Marczak, PUCRS, Brazil

  • Rahul Mohanani, University of Oulu, Finland

  • Leonardo Murta, UFF, Brazil

  • James Noble, Victoria University of Wellington, New Zealand

  • Jacob Nørbjerg, Copenhagen Business School, Denmark

  • Nicole Novielli, University of Bari, Italy

  • Maria Paasivaara, IT University of Copenhagen, Denmark

  • Gustavo Pinto, Federal University of Pará, Brazil

  • Lutz Prechelt, Freie Universität Berlin, Germany

  • Rafael Prikladnicki, PUCRS, Brazil

  • Razieh Saremi, Systems Engineering Research Center (SERC), Hoboken, NJ, USA

  • Anita Sarma, Oregon State University, USA

  • Carolyn Seaman, University of Maryland - Baltimore County, USA

  • Alexander Serebrenik, Eindhoven University of Technology, Netherlands

  • Helen Sharp, The Open University Walton Hall, United Kingdom

  • Leif Singer, Automattic Inc., USA

  • Margaret-Anne Storey, University of Victoria, Canada

  • Paolo Tell, IT University of Copenhagen, Denmark

  • Igor Wiese, Federal University of Technology, Paraná, Brazil

  • Mansooreh Zahedi, IT University of Copenhagen, Denmark

Open Science Practices

CHASE 2019 continues its previous years' experimentation with encouraging authors to use open science to make their research, data and dissemination accessible to anybody in the world with an Internet connection. Here follow our guidelines and recommendations for open access, open data and open source, and signed peer review.

The following guidelines are recommendations and not mandatory. Your choice to use open science or not will not affect the review process for your paper.

Open Access

We encourage CHASE authors to self-archive their pre- and postprints in open, preserved repositories. This is legal and allowed by all major publishers including ACM and IEEE (granted in the copyright transfer agreement), and it lets anybody in the world reach your paper.

If the authors of your paper wish to do this, we recommend:

• 1. Upon submission to CHASE, submit your paper to arXiv.org and choose the arXiv.org perpetual, non-exclusive license to distribute. The paper version at this point is before peer-reviewed, and it is called preprint.

  2. Upon acceptance to CHASE, revise your article according to the peers comments, generate a PDF version of it, and submit it to arXiv.org, which supports article versioning.

  3. Note that you are not allowed to self-archive the PDF of the published article, that is the one you can find in ACM DL or IEEE Xplore. Only self-archive your own generated PDFs.

We encourage you to use a preserved, archived repository instead of your personal website. Personal websites are prone to changes and errors, and more than 30% of them will not work in a 4 years period.

Open Data and Open Source

We encourage authors of accepted papers to make their data public, in order to enhance the transparency of the process and the reproducibility of the results.

If the authors of your paper wish to do this, we recommend:

• 1. Archive their data on preserved archives such as zenodo.org and figshare.com, so that the data will receive a DOI and become citable.

  2. Use the CC0 dedication when publishing the data (automatic when using zenodo and figshare), as explained here.

Similarly, we encourage authors to make their research software accessible as open source and citable.

Similarly to our open access, we encourage you to avoid putting the data on your own websites or systems like Dropbox, since more than 30% of them will not work in a 4 years period.

Signed Peer Review

Reviewers of CHASE are allowed to sign their reports as a first step to experiment an open peer review process at ICSE venues.