Workshops‎ > ‎

CHASE 2017


10th International Workshop on Cooperative and Human Aspects of Software Engineering
(CHASE 2017)
An ICSE 2017 Workshop
Buenos Aires, Argentina
May 23, 2017

Workshop Overview

*Notice: submission deadline extended (Jan 27), but abstract required by Jan 20*

Software is created for and with a wide range of stakeholders, from customers to management, from value- added providers to customer service personnel. These stakeholders work with teams of software engineers to develop and evolve software systems that support their activities. All of these people and their interactions are central to software development. It is crucial to investigate the dynamic and frequently changing Cooperative and Human Aspects of Software Engineering (CHASE), both before and after deployment, in order to understand current 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, software maintenance, customer communication, and the cooperative and human aspects of the use and evolution of the deployed software systems. 

Researchers and practitioners have long recognized the need to investigate these aspects, however, their articles are scattered across conferences and communities. CHASE will provide a unified forum for discussing high quality research studies, models, methods, and tools for human and cooperative aspects of software engineering. This will be the 10th in a series of workshops held at ICSE focusing on this theme. Based on our experience, we believe 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.

List of Accepted Papers

Full papers

  • Paul Li, Andrew J. Ko and Andrew Begel:  
    Cross-disciplinary Perspectives on Collaborations with Software Engineers
  • Martina Kolpondinos Huber and Martin Glinz:  
    Tailoring Gamification to Requirements Elicitation: A Stakeholder Centric Motivation Concept
  • Olivier Liechti, Jacques Pasquier and Rodney Reis:  
    Beyond dashboards: on the many facets of metrics and feedback in agile organizations
  • Christoph Becker, Dawn Walker and Curtis McCord:
    Intertemporal choice: Decision making and Time in Software Engineering
  • Magne Jørgensen: Software development contracts:
    The impact of the provider’s risk of financial loss on project success
  • Guilherme Castro Diniz, Marco Aurélio Graciotto Silva, Marco Gerosa and Igor Steinmacher:    
    Using Gamification to Orient and Motivate Students to Contribute to OSS projects
  • Denae Ford, Titus Barik, Leslie Rand-Pickett and Chris Parnin:
    The Tech-Talk Balance: What Technical Interviewers Expect from Technical Candidates
  • Yasuhiro Watanabe, Hironori Washizaki, Kiyoshi Honda, Yuki Noyori, Yoshiaki Fukazawa, Aoi Morizuki, Hiroyuki Shibata, Kentaro Ogawa, Mikako Ishigaki, Satiyo Shiizaki, Teppei Yamaguchi and Tomoaki Yagi:
    ID3P: Iterative Data-Driven Development of Persona based on quantitative evaluation and revision
  • Lucas Gren, Richard Berntsson Svensson and Michael Unterkalmsteiner:
    Is it Possible to Disregard Obsolete Requirements? - An Initial Experiment on a Potentially New Bias in Software Effort Estimation

Short papers

  • Rafael de Mello, Roberto Oliveira, Leonardo Da Silva Sousa and Alessandro Garcia: Towards Effective Teams for the Identification of Code Smells
  • Marcela Oliveira, Priscila Reis, Itanauã Barbosa, Tancicleide Gomes and Fabio Q. B. Da Silva:
    Towards Understanding the Relationships between Interdependence and Trust in Software Development: A Qualitative Research
  • Diana Pereira, George Marsicano Corrêa, Fabio Q. B. Da Silva and Danilo Ribeiro:
    Team Maturity in Software Engineering Teams: a Work in Progress
  • Gustavo Pinto, Marcel De S. C. Rebouças and Fernando Castor:
    Inadequate Testing, Time Pressure  Inadequate Testing, Time Pressure, and (Over) Confidence: A Tale from CI Users
  • Vibhu Saujanya Sharma, Rohit Mehra and Vikrant Kaulgud:
    What do developers want ? An Advisor approach for Developer Priorities
  • Marcela Oliveira, Itanauã Barbosa, Karla Silva, Priscila Reis and Fabio Q. B. Da Silva:
    Characterization of Autonomy and Interdependence in Software Engineering
  • Lucas Gren:
    A fourth explanation to Brooks' Law - The aspect of group developmental psychology

Notes  

  • Flávio Steffens, Sabrina Marczak, Fernando Figueira Filho, Christoph Treude and Cleidson de Souza:
    A Preliminary Evaluation of a Gamification Framework to Jump Start Collaboration Behavior Change
  • Zainab Masood, Rashina Hoda and Kelly Blincoe:
    Motivation for Self-Assignment: Factors Agile Software Developers Consider

Important Dates

  • Workshop abstract submission due: January 20, 2017.
  • Workshop paper submissions due: January 20, 2017 January 27, 2017.
  • Notification of workshop paper authors: February 17, 2017.
  • Camera Ready deadline: February 27, 2017.
  • Workshop: May 23rd, 2017

Workshop Themes                                                      

Software engineering is about making choices and decisions. Some of the critical decisions are informed by multiple viewpoints and experiences acquired from stakeholders. Methods, tools, and techniques have been shaped over many years by best practices learned from experience, but software engineers continually face new challenges and constraints. Addressing these challenges benefits from diverse perspectives, and this workshop welcomes submissions that embrace this variety.

Topics of interest are about the human, cooperative, and collaborative aspects of software engineering and include, but are not limited to:

  • Software design or engineering philosophies, practices, and tools;
  • Adapting tools or processes to accommodate a range of organizational and cultural situations;
  • Sociological or cultural characterizations of software engineering (e.g., trust, conflicts, norms);
  • Psychological or cognitive aspects of software design or engineering (e.g., motivation, rewards, personality);
  • Managerial or organizational aspects focused on people and their interactions;
  • Collaborative or cooperative aspects of design or engineering within multidisciplinary teams;
  • Teamwork, collaboration, or cooperation in or across various development methodologies;
  • Community-based software development (e.g., Open Source, crowdsourcing, and public-private partnerships); 
  • Coordination, mutual awareness, 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 over the lifetime of a system. 
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;
  • Meta-research topics.

Participation Solicitation and Selection Process: We will have three paper categories: 7-page full papers, 4-page short papers, and 2-page notes. 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: 

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

Papers should follow ICSE'17 formatting guidelines for technical research (IEEE Formatting Guidelines).

Workshop Organizers 

Program Committee

  • Maurício Aniche, Delft University of Technology
  • Sandeep Athavale, TCS TRDDC
  • Andrew Begel, Microsoft Research
  • Tayana Conte, UFAM
  • Steve Counsell, Brunel University
  • Cleidson De Souza, Vale Institute of Technology and UFPA
  • Giuseppe Destefanis, Brunel University London
  • Yvonne Dittrich, IT University of Copenhagen
  • Neil Ernst, Software Engineering Institute
  • Fabian Fagerholm, University of Helsinki
  • Robert Feldt, Blekinge Institute of Technology;  Chalmers University of Technology
  • Fernando Figueira Filho, Federal University of Rio Grande do Norte
  • Marco Gerosa, University of São Paulo
  • Irit Hadar, University of Haifa
  • Hideaki Hata, Nara Institute of Science and Technology
  • Sandeep Kaur Kuttal, University of Tulsa
  • Filippo Lanubile, University of Bari
  • Thomas  Latoza, George Mason University
  • Sabrina Marczak, PUCRS
  • Daniel  Méndez Fernández, Technische Universität München
  • Nicole  Novielli, University of Bari
  • Alexander Serebrenik, Eindhoven University of Technology
  • Helen Sharp, The Open University
  • Leif Singer, University of Victoria
  • Igor Steinmacher, Universidade Tecnológica Federal do Paraná
  • Xiaofeng Wang, Free University of Bozen-Bolzano
  • Minghui Zhou, Peking University

    Open Science Practices

    CHASE 2017 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.


    Ċ
    Daniel Graziotin,
    Dec 17, 2016, 3:01 AM
    ċ
    CHASE_2017-CFP.txt
    (6k)
    Daniel Graziotin,
    Jan 28, 2017, 12:03 AM
    Comments