Workshops‎ > ‎

CHASE 2016

Collocated with ICSE 2016, 
Austin, Texas, USA

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. 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. Thus, 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. In turn, this enables us to design tools and support mechanisms that improve software creation, software maintenance, and customer communication.

Researchers and practitioners have long recognized the need to investigate these aspects, however, their articles are scattered across conferences and communities. This workshop will provide a unified forum for discussing high quality research studies, models, methods, and tools for human and cooperative aspects of software engineering.

Collaboration Website: http://132.75.252.108/~chase16/wp-login.php

Workshop Agenda

May 16, 2016
Time Activity
9:00am-9:05am Introduction
9:05am-9:50am Introductions via Speed Dating
9:50am-10:30am

Paper Presentations:

  • An Initial Analysis of Differences in Software Engineers' Attitudes Towards Organizational Change
  • Finding Relationships Between Socio-Technical Aspects and Personality Traits by Mining Developer E-mails
  • Beliefs, Practices and Personalities of Software Engineers: A Survey in a Large Software Company
10:30am-11:00am Break
11:00am-12:30pm

Paper Presentations:

  • Do open projects "break the mirror"? Re-conceptualization of organizational configurations in Open Source Software (OSS) production
  • Decision-Making in Software Project Management: A Qualitative Case Study of a Private Organization
  • Can a Team Coordination Game Help Student Software Project Teams?
  • ScrumLint: Identifying Violations of Agile Practices Using Development Artifacts
  • On the Randori Training Dynamics
  • Augmenting Requirements Gathering for People with Special Needs using IoT: A Position Paper
  • Among the agilists: Participant observation in a rapidly evolving workplace
  • Sociodrama: One More Technique to Foster Collaboration in Software Engineering
12:30pm-2:00pm
Lunch
2:00pm-2:45pm

Small Group Brainstorming Sessions

  • What is difficult about doing CHASE research?
2:45pm-3:30pm Poster Session: Part 1
3:30pm-4:00pm Break
4:00pm-4:30pm Poster Session: Part 2
4:30pm-5:00pm Small Group Brainstorming Sessions
  • How can we overcome the challenges in doing CHASE research?
  • What new ideas have you been inspired with today?
7:00pm-9:00pm Dinner?

Workshop Organizers 

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 include, but are not limited to, the following:

  • Software design philosophies, engineering practices, and tools that leverage human and cooperative aspects of software engineering;
  • Adapting tools and processes to accommodate a range of organizational and cultural situations;
  • Sociological and cultural characterizations of software engineering (e.g. trust, conflicts, norms);
  • Psychological and cognitive aspects of software engineering (e.g. motivation, rewards, personality types);
  • Managerial and organizational aspects of software engineering that focus on people and their interactions;
  • Software engineering as collaborative work, including behavioral incentives, social networking, communication, coordination, and decision-support tools;
  • Teamwork and cooperation in various development methodologies (e.g. agile, spiral, lean, waterfall, RAD);
  • Community-based software development, such as Open Source, crowdsourcing, and public-private partnerships, and attributes of these models (e.g. recruitment and retention of contributors, risk management);
  • Coordination, mutual awareness, and knowledge sharing in small-scale and large-scale software development, e.g. distributed software development, semi-anonymous collaboration, and “borderless” software teams;
  • Stakeholder participation in regard to design, ownership, training, degree of involvement, communication, interplay, and influence with developers, sustainability, and deployment;
  • Processes and tools to support communication and cooperation among stakeholders, including software developers, professionals, and customers over the lifetime of a system (requirements, design, development, testing, and maintenance).

Possible contributions include:

  • Empirical studies of software engineering teams or individuals in situ, using methods such as ethnographies, surveys, interviews, contextual inquiries, data mining, etc;
  • Laboratory studies of individual or team software engineering behavior;
  • Novel tools motivated by observed needs, such as new ways of capturing and accessing software-related knowledge, software orienteering systems, communication, collaboration, awareness tools, visualizations, etc;
  • Novel processes motivated by empirical investigations; and
  • Meta-research topics, such as effective validation of interventions or research methods.

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 and Presentation: Papers should be submitted to the workshop's EasyChair site. Please follow the ICSE formatting guidelines. Accepted papers will be published as an ICSE 2016 Workshop (companion) Proceedings in the ACM and IEEE Digital Libraries. Papers should be written in English. Papers must not have been previously accepted for publication nor concurrently submitted for review in another journal, book, conference, or workshop. Accepted preprints 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 Digital Library. This date may be up to two weeks prior to the first day of ICSE 2016. The official publication date affects the deadline for any patent filings related to published work. Only a subset of papers will be selected for presentations based on their representativeness and potential for generating discussion.

Submissions should be made at the following website:
https://easychair.org/conferences/?conf=chase2016

Papers should follow ICSE formatting guidelines for technical research:
All papers must conform, at time of submission, to the ACM Formatting Guidelines (LaTeX users, please use the "Option 2" style). All submissions must be in PDF format. All submissions must use the US Letter page format.

Important Dates

Workshop paper submissions due:  Jan 22nd, 2016. Now Jan 29, 2016

Notification of workshop paper authors: Feb 19th, 2016

Camera Ready deadline: Feb 26th, 2016

Workshop: May 16th, 2016

Program Committee

Vivek Balaraman, Tata Research Development and Design Centre
Cleidson Desouza, Federal University of Pará
Yvonne Dittrich, IT University of Copenhagen
Neil Ernst, Software Engineering Institute
Tor Erlend Fægri, SINTEF ICT
Fabian Fagerholm, Department of Computer Science, University of Helsinki
Fernando Figueira Filho, Federal University of Rio Grande do Norte
Marco Gerosa, University of São Paulo
Smita Ghaisas, Tata Research Design and Development Center
Irit Hadar, University of Haifa
Hideaki Hata, Nara Institute of Science and Technology
Sandeep Kuttal, University of Tulsa
Filippo Lanubile, University of Bari
Thomas D. Latoza, George Mason University
Sabrina Marczak, PUCRS
Daniel Méndez-Fernández, Technische Universität München
Leonardo Murta, UFF
James Noble, Victoria University of Wellington
Chris Parnin, North Carolina State University (NCSU)
Rafael Prikladnicki, PUCRS
Leif Singer, 
University of Victoria
Alexander Serebrenik, Eindhoven University of Technology
Helen Sharp, The Open University
Leif Singer, University of Victoria, Canada
Christoph Treude, University of São Paulo
Minghui Zhou, Peking University

Open Science Practices

CHASE 2016 is experimenting 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,
Feb 3, 2016, 1:22 PM
ċ
CHASE_2016-CFP.txt
(7k)
Daniel Graziotin,
Feb 3, 2016, 1:22 PM
Comments