CHASE 2014

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

(CHASE 2014)

ICSE 2014 Workshop

Hyderabad, India

June 2 - 3 2014

Attendees at CHASE 2014

CHASE Programme

June 2, 2014

June 3, 2014

Keynote Talk

Innovating in India: Designing for constraint, computing for inclusion

Ed Cutrell

Technology for Emerging Markets (TEM) group

Microsoft Research, India


A fundamental tenet of user-centered design is that the needs, wants, limitations, and contexts of end users are central to the process of creating products and services that can be used and understood by the people who will use them. Most of the time these end users aren’t all that different from the people designing the technology. But as the differences increase between designers and the people they’re designing for, understanding and empathizing with users becomes harder and even more important. As we build software for people and communities with vastly diverse backgrounds, cultures, languages, and education, we need to stretch our ideas of what users want and need and how best to serve them.

The Technology for Emerging Markets (TEM) group at Microsoft Research India seeks to address the needs and aspirations of people in the developing world who are just beginning to use computing technologies and services as well as those for whom access to computing still remains largely out of reach. Much of this work can be described as designing for constraint: constraints in education, in infrastructure, in financial resources, in languages and in many other areas. In this talk, I will describe some work from our group that explores how we have tried to manage these constraints to create software and systems for people and communities often overlooked by technologists.


Ed Cutrell manages the Technology for Emerging Markets (TEM) group at Microsoft Research India. TEM is a multidisciplinary group that strives to study, design, build, and evaluate technologies and systems that are useful for people living in underserved rural and urban communities. The goal of this work is to understand how people in the world's poor and developing communities interact with information technologies and to invent new ways for technology to meet their needs and aspirations. Ed has been working in the field of human-computer interaction (HCI) since 2000; he is trained in cognitive neuropsychology, with a PhD from the University of Oregon.

Accepted Papers

Full papers (8 pages)

Short papers (4 pages)

Note papers (2 pages)

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 constantly-changing human and cooperative aspects of software development, 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. 

Workshop Organizers 

Local Advisory Board

Workshop Theme and Goals 

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);

- Models of 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; and

- Processes and tools to support communication and cooperation between 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: 8-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 poster 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 attendees will be asked to present an aspect of their work. If appropriate, we will expand the number of participants in the workshop in response to a large number of quality submissions. 


Submissions should be made in the following website:

- Papers should follow ICSE formatting guidelines for technical research: 

Important Dates 

Workshop paper submissions due                     January 31, 2014 (extended deadline)

Notification of workshop paper authors            February 24, 2014

Camera Ready deadline                                     March 14th, 2014

Workshop                                                          June 2nd and 3rd 2014


Program Committee