Introduction

Continuous software evolution and delivery refers to the organizational capability to innovate and release software in fast parallel cycles, typically hours, days or very small numbers of weeks. This requires not only adoption of more agile processes in development teams or large investments in automated release pipelines, but changes in potentially the entire research and development organization in terms of technology and practices. Furthermore, automatic live monitoring and experimentation of different system alternatives enables fast evaluation and decision making. Finally, best practices and success stories should be documented and exchanged. The proposed workshop, which grew out of the successful RELENG and RCoSE workshops, aims to bring together the research communities of the aforementioned areas to exchange challenges, ideas, and solutions to bring continuous software evolution and delivery a step further to being a holistic continuous process. The workshop will be run in a highly interactive manner to stimulate discussions, featuring presentations of practitioner abstracts and academic papers, as well as break-out groups focusing on lively interactions to identify challenges, existing approaches and potential directions for solutions.

Call for paper

Submission Topics

Topics relevant to the scope of the workshop include continuous software evolution and delivery as described above and specifically the following:

  • best practices for code movement (branching/integration)
  • continuous integration and testing
  • build and configuration of software
  • package and dependency management
  • continuous delivery, deployment, installation and software update
  • release management for different domains, e.g., cloud services, mobile apps, embedded systems
  • principles and automated techniques for release planning
  • devops and interaction with developers, end users, etc.
  • bizdev, connecting business strategy and development
  • process aspects and agile practices supporting continous *
  • organizational and human aspects
  • rapid cycles in e.g., requirements engineering, architectural design, programming languages, validation and verification
  • application / system monitoring
  • live and automatic experimentation, and quick feedback of experimental results
Submit Comment
Verify Code Change Another
All Comments
Important Date
  • Conference Date

    May 14

    2016

    to

    May 15

    2016

  • May 15 2016

    Registration deadline