Deadline approaching: IEEE Software SI on CHASE

Deadline is April 8th, so get busy writing.

Details here:

CFP:IEEE Software SI on Cooperative and Human Aspects of SE

IEEE Software Special Issue on the Cooperative and Human Aspects of Software Engineering
Submission Deadline: April 8, 2009.
Publication: Nov./Dec. 2009

We are soliciting papers for a special issue of IEEE Software focusing on the cooperative and human aspects of software engineering (CHASE).  We seek high quality examples of multi-disciplinary research and practice that explore how cooperative and human aspects affect how software is created and evolved, both in terms of the challenges and the successes which arise when the human aspect is considered. We are looking for papers with practical reliable insights that can be applied in real-world software development contexts.  We are interested in papers across the domain of software engineering (e.g., requirements, development, testing).  All papers, however, must address either cooperative or human aspects as they relate to software engineering.  Possible topics include, but are not limited to:

  • Software engineering as cooperative work
  • Industrial experience reports examining the influence of CHASE in software projects, such as the influence of personality, leadership or effective teamwork in software development teams;
  • Social and cultural aspects of software engineering;
  • Psychological and cognitive aspects of software engineering;
  • Coordination in large scale software development; and
  • Cooperation between software developers and other professionals over the lifetime of a system.

Examples of types of contribution include:

  • Case studies of industrial practice with respect to CHASE,
  • Experience reports of how CHASE issues challenged or were addressed in the context of a software development project,
  • Empirical studies of software engineering teams and individual software engineers in situ, using approaches such as ethnographies, surveys, interviews, contextual inquiries, data mining, etc.,
  • Lab studies of individual and team software engineering behavior as long as the insights can be applied in real-world settings,
  • Novel tools motivated by observed needs such as new ways of capturing and accessing software-related knowledge, navigational systems, communication, collaboration, and awareness tools, visualizations, etc.  The motivation for such tools must be clearly linked to the cooperative and/or human aspects of software engineering, and
  • Novel processes motivated by observed issues in cooperation and/or human aspects.

Manuscripts must not exceed 5,400 words including figures and tables, which count for 200 words each. Submissions in excess of these limits may be rejected without refereeing. The articles we deem within the theme’s scope will be peer-reviewed and are subject to editing for magazine style, clarity, organization, and space. We reserve the right to edit the title of all submissions. Be sure to include the name of the theme or special issue you are submitting for.

Articles should have a practical orientation, and be written in a style accessible to practitioners. Overly complex, purely research-oriented or theoretical treatments are not appropriate. Articles should be novel. IEEE Software does not re-publish material published previously in other venues, including other periodicals and formal conference/workshop proceedings, whether previous publication was in print or in electronic form.

Interested authors can contact with questions about appropriate content.  For questions about author guidelines or submission details, please contact IEEE Software at

Guest Editors:
–    Janice Singer, National Research Council Canada
–    Cleidson de Souza, Universidade Federal do Pará, Brazil
–    Li-Te Cheng, IBM Research, USA
–    Gina Venolia, Microsoft Research, USA

Upcoming workshops

There are number of upcoming workshops which are of interest to the CHASE community, mostly at ICSE, but one in Vancouver at the same time not associated with ICSE.

The links are below:

Cooperative and Human Aspects of Software Engineering (of course : ) – )

Qualitative Research in Software Engineering

Search-Driven Development – Users, Infrastructure, Tools and Evaluation

Socio-Technical Congruence

Software Engineering Foundations for End User Programming

In addition to all of these interesting workshops, there may be other ICSE workshops which address a specific domain you’re interested in.  Check out the ICSE workshop webpage for more info.


Call for Papers
Cooperative and Human Aspects of Software Engineering-Workshop at ICSE 08
– Sunday, May 17th, 2009

Software is created by people – software engineers working in varied environments, under various conditions. Thus understanding the cooperative and human aspects of software development is crucial to understanding how methods and tools are used, and thereby improving both the creation and maintenance of software. Recently, a renaissance is occurring in this research area, with a large amount of research being published in software engineering venues as well as other research discourses. Thus the time is ripe to bring together researchers to share knowledge, and further build the research area.

The goal of this workshop is therefore to provide a forum for discussing high quality research on the cooperative and human aspects of software engineering, as well as a meeting place for the nascent community that is currently distributed over several research domains (e.g. HCI, SE, CSCW, and IS).

Topics of Interest
include but are not limited to:

* Software engineering as cooperative work,
* Social and cultural aspects of software engineering,
* Psychological and cognitive aspects of software engineering,
* Managerial and organizational aspects of software engineering
* Coordination of large scale software development,
* Cooperation between software developers and other professionals over the lifetime of a system.
* Knowledge management in software engineering.

Prospective participants are invited to submit position papers on a topic of relevance using the same format required for the ICSE technical papers (posted at Three types of submissions are invited. Eight-page Research papers go into detail about the research, 4-page Notes papers discuss preliminary findings, and 1-page Topic papers should cover very preliminary results or research ideas. Please see
for additional submission instructions.

Important Dates
* 21 January – deadline for workshop paper submission
* 12 February – notification of acceptance by workshop chairs
* 19 February – camera-ready deadline for workshop papers

Workshop Organisers and Program Committee

* Li-Te Cheng, IBM, li-te_cheng at
* Cleidson de Souza, UFPA, cdesouza at
* Yvonne Dittrich, IT University of Copenhagen, ydi at
* Michael John, Fraunhofer, Michael.John at
* Orit Hazzan, Technion, oritha at
* Frank Maurer, University of Calgary, frank.maurer at
* Helen Sharp, Open University, H.C.Sharp at
* Janice Singer, NRC, janice.singer at
* Susan Elliot Sim, University of California Irvine, ses at
* Jonathan Sillito, University of Calgary, sillito at
* Margaret-Anne Storey, University of Victoria, mastorey at
* Bjornar Tessem, University of Bergen, Bjornar.Tessem at
* Gina Venolia, Microsoft Research,Gina.Venolia at

CFP: SofTEAM ’09

**************  Call for Papers *************************

European Workshop on “Collaboration and Knowledge Sharing in Software Development Teams (SofTEAM ’09)”

In Conjunction with SE09, Kaiserslautern, Germany, March 2nd

Submissions deadline 20th December 2008



ìThese are indeed interesting times. The challenges of software development are certainly not going to go away, for we as an industry are continually being driven to do more with less. Methods and processes help; so do languages, frameworks, and tools. However, software development is ultimately a human endeavor, and as such it’s ultimately the efforts of the software development team that enable us to deliver quality systems in a predictable and sustainable fashion.î (Booch, 1999)

Almost ten years after Booch emphasized the importance of development team productivity, the underlying research topics are only slowly becoming part of mainstream Software Engineering. Research on software development teams requires interdisciplinary approaches to study the interplay of technologies, tools, processes and human factors appropriately. Although the body of research is growing, it is often scattered across different communities such as Software Engineering, Computer-Supported Collaborative Work (CSCW) and Knowledge Management.
On the other hand, the trend towards distributed software development ñ which comes in different flavours such as off-shore- and near-shore development, Open Source communities and inter-organizational project teams ñ presses researchers to deliver results which help to improve the efficiency of development teams.
In the past, research and practice have often taken different directions ñ research targeting fancy prototypes, while practitioners adopted pragmatic solutions such as instant messaging, Wikis or agile methodologies to increase team productivity. While such hands-on solutions worked quite well for many teams, they lack scientific backing and guidance and have problems to scale up in large and complex project settings. Thus, solutions are sought which embed development methodologies, lightweight approaches for collaboration and knowledge sharing into software development work processes. An example for such an effort is the IBM Jazz platform [Cheng et al. 2004], which intends to seamlessly integrate common collaboration features into IDEs. Thereby, open development platforms such as Eclipse make it easier to transfer research into practice (e.g. the Eclipse mylyn project [Kersten and Murphy 2006]).


In this workshop we would like to bring together researchers and practitioners working on different aspects of collaboration and knowledge sharing in software development to discuss new results and future research challenges. Major topics addressed at the workshop include (but are not limited to):
– Collaboration and knowledge sharing in development teams and communities.
– Lightweight and unobtrusive tools, Web 2.0 and Social Semantic Web applications, supporting development teams.
– Concerns of individual developers in collaboration settings, such as learning, personal productivity, usability and incentives.
– Approaches and tools for context-aware development and collaboration environments.
– Assistance and recommendation tools based on team experience.
– Research methods and approaches for analyzing and designing successful collaboration support.
– Empirical studies on collaboration and information behavior in development teams.
– Scientific analysis of the relation between methods/processes, tools and collaborative development practice.


Andreas Abecker, FZI Karlsruhe
Lilith Al-Jadiri, T-Systems
Bernd Bruegge, TU Muenchen
Bjˆrn Decker, Empolis GmbH
Robert DeLine, Microsoft Research
Paul Gr¸nbacher, Johannes Kepler University
Hans-Joerg Happel, FZI Karlsruhe
Wolfgang Kaltz, Die Schweizerische Post
Steffen Lohmann, University of Duisburg-Essen
Walid Maalej, TU M¸nchen
Karsten Nebe, University of Paderborn
Jasminko Novak, University of Zurich
Barbara Paech, University of Heidelberg
Dirk Riehle, SAP Research
Hans Schlichter, TU M¸nchen
Janice Singer, National Research Council Canada
Anil Kumar Thurimella, Harman/Becker Automotive Systems GmbH
Denny Vrandecic, University of Karlsruhe (TH)
J¸rgen Ziegler, University of Duisburg-Essen
Thomas Zimmermann, University of Calgary


Hans-Joerg Happel, FZI Karlsruhe
Steffen Lohmann, University of Duisburg-Essen
Walid Maalej, TU M¸nchen

*** CONTACT ***

*** DEADLINE ***

– 20th December: Paper submission
– 17th January: Author’s notification
– 31th January: Camera-ready version
– 2nd March: Workshop


Position, tool-demonstration and experience papers (max 10 pages) are equally welcome for the workshop. They can be submitted via the workshop website ( Accepted contributions will be published in the GI-Edition ÑLecture Notes in Informatics”. Papers must follow the instructions and templates provided at publikationen/lni/. At least one author should participate in the workshop and register for the SE2009 conference.

Do end-users need software engineering skills?

I’ve been asked to write a Point, or maybe it’s a Counterpoint for a special issue of IEEE Software on End-user Software Engineering. I’ll be writing it jointly with my colleague, Mark Vigder.  Our point is that end-users need to have some software engineering skills.  Mark had a good analogy.  Thirty years or so ago, noone would have thought it was necessary for managers or executives to have typing skills, and now it’s almost unthinkable to not be able to do your own typing.  To me, software engineers have perfected, or at least advanced, many of the skills necessary to store and manipulate information in a digital context.

The skills that I think are most useful include debugging which more generally means problem solving in the sense of figuring out the cause for some effect and then being able to change things to get the desired effect.  I guess this actually translates more generally to testing practices in different contexts as well – such as making sure that you meet your requirements.  Another important skill is versioning.  I mean, isn’t it shocking that tools like Word still do not have effective versioning control.  But especially when you’re working in a team, you need to have a way to control documents.  Usually, we just use a “talk lock” meaning telling people not to work on it, and saving past drafts.  Probably in the future, not too distant, I hope, versioning will be embeded into all sorts of activities, and people will then need to have some cognitive model of how versioning works.  I think another important skill be based on creating useful widgets by combining components.  We can already see this in the proliferation of mash-ups.  I believe that the cognitive skill associated to this has to do with understanding things like information flow related to things like APIs.  Anyhow, you can see I’m just starting to think this through, so any thoughts or comments?  We’re thinking of calling the column something like, “Reading, Writing, Arithmetic…Software Engineering.”

CHASE 2009 is on

I just heard from the ICSE committee.  CHASE 2009 is on. This year’s organizers are me, Cleidson de Souza, Yvonne Dittrich and Helen Sharp. This year, we will be accepting 3 types of papers – 8 pages, 4 pages, and short 1 page research reports.  The idea is to span the spectrum of research activities, and let people at all stages of their research report their results.  We will also have a keynote from Daniel German of the University of Victoria. We’ll have our coffee table rounds which were such a success last year from the hard work of Yvonne and Helen, and finally, we’ll arrange a social evening for fun.  So, start thinking about your topics.  I’m not sure about days or deadlines yet, but will update as soon as we have a formal CFP.