Workshops‎ > ‎

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: http://chasevis.azurewebsites.net/.

Important Dates

  • Workshop paper submissions due: February 5th, 2018.
  • Notification of workshop paper authors: March 5th, 2018.
  • Camera Ready deadline: March 19th, 2018.
  • Workshop: May TBD. 2018.

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: 

  • TBD.
  • TBD.
  • TBD.
These different categories offer researchers who are at different stages in their research maturity the opportunity to benefit from workshop participation.

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: 

TBD.

Papers should follow ICSE'18 formatting guidelines for technical research (ACM Formatting Guidelines).

Workshop Organizers 

Program Committee

  • TBD.

    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:

    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.


    Comments