CHASE 2018

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

(CHASE 2018)

An ICSE 2018 Workshop

Gothenburg, Sweden

Workshop Overview

Software is created for and with a wide range of stakeholders, from customers to management from value-added providers to customer service personnel, and from engineers to designers. These stakeholders work with teams of software engineers to develop and evolve software systems. All of these people and their interactions are central to software development. It is crucial to investigate the human and cooperative aspects of software development to understand current software practices, processes, and tools as well as their impact. In turn, this enables us to design and build support mechanisms (e.g., tools, processes) to improve all aspects of software development, and the use and evolution of deployed software systems. 

Researchers and practitioners have long recognized the need to investigate these aspects. However, their articles have been scattered across many conferences and communities. This workshop provides a unified forum for discussing high quality research studies, models, methods, and tools for human and cooperative aspects of software engineering. We provide a meeting place for academic, industry, and practitioner communities interested in this area, and for those who are curious to see what it is all about. 

This will be the 11th 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:

Workshop Program

May 27th, 2018, Congress center Gothia Towers (R11/12)

List of Accepted Papers

Lucas Gren. On Gender, Ethnicity, and Culture in Empirical Software Engineering Research

Jinghui Cheng, Micayla Goodrum, Ronald Metoyer and Jane Cleland-Huang. How Do Practitioners Perceive Assurance Cases in Safety-Critical Software Systems?

Helena Barke and Lutz Prechelt. Some reasons why actual cross-fertilization in cross-functional agile teams is difficult

Wiesław Kopeć, Kinga Skorupska, Anna Jaskulska, Radoslaw Nielek and Adam Wierzbicki. Guidelines Towards Better Participation of Older Adults in Software Development Processes using a new SPIRAL Method and Participatory Approach

Giovanni Viviani, Calahan Janik-Jones, Michalis Famelis and Gail Murphy. The Structure of So ware Design Discussions

Vladimir Kovalenko and Alberto Bacchelli. Code review for newcomers: is it different?

Naomi Unkelos-Shpigel and Irit Hadar. Leveraging motivational theories for designing gamification for RE

Rafael Chanin, Afonso Sales, Alan Santos, Leandro Pompermaier and Rafael Prikladnicki. A Collaborative Approach to Teaching Software Startups: Findings From a Study Using Challenge Based Learning

Robert Biddle, Martin Kropp, Andreas Meier and Craig Anslow. MyAgile: Sociological and Cultural Effects of Agile on Teams and their Members

Elizabeth Bjarnason, Baldvin Gislason Bern and Linda Svedberg. A Case Study of Distances in a Large Co-Located Software Development Organisation

Per Lenberg and Robert Feldt. Psychological Safety and Norm Clarity in Software Engineering Teams

Jailton Coelho, Luciana Silva, Marco Tulio Valente and André Hora. How to Attract Core Developers to FLOSS?

Torgeir Dingsøyr, Finn Olav Bjørnson, Nils Brede Moe, Knut H. Rolland and Eva Amdahl Seim. Rethinking Coordination in Large-Scale Software Development

George Marsicano, Victor Oliveira, Leila Mariz and Fabio Da Silva. An Initial Understanding of Task Interdependence in So ware Engineering: A Case Study

Marta Cecilia Camacho Ojeda, Julio Ariel Hurtado Alegría and Francisco Javier Alvarez. An Exploratory Case Study for Scoping Software Product Lines in a Collaborative Way

Adam Alami, Yvonne Dittrich and Andrzej Wasowski. Influencers of Quality Assurance in an Open Source Community

Matthias Book and André van der Hoek. Sketching with a Purpose: Moving from Supporting Modeling to Supporting Engineering Activities

Sai Datta Vishnubhotla, Emilia Mendes and Lars Lundberg. Designing a capability-centric web tool to support agile team composition and task allocation: A work in progress

Yvonne Dittrich, Jacob Nørbjerg, Paolo Tell and Lars Bendix. Researching Cooperation and Communication in Continuous Software Engineering

Álvaro Menezes and Rafael Prikladnicki. Diversity in Software Engineering

Gustavo Pinto, Luiz Felipe Fronchetti Dias and Igor Steinmacher. Who Gets a Patch Accepted First? Comparing the Contributions of Employees and Volunteers

Elahe Paikari and Andre van der Hoek. A Framework for Understanding Chatbots and their Future

Adriana Meza-Soria and André van der Hoek. Toward Collecting and Delivering Knowledge for Software Design at the Whiteboard

Souti Chattopadhyay, Nicholas Nelson, Thien Nam, Mckenzie Calvert and Anita Sarma. Context in Programming: An Investigation of How Programmers Create Context

Lalit Sanagavarapu and Y. Raghu Reddy. Crowdsourcing Security - Opportunities and Challenges

Important Dates

Workshop Themes                                                      

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

Possible contributions include:


We have three paper categories: 

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:

Workshop proceedings will be prepared by IEEE CPS and published by ACM. Workshop papers must follow the ACM formatting instructions. 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 2018. 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 2017 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 

Program Committee

Open Science Practices

CHASE 2018 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:

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:

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.