Aims and Scope
Today, software development is conducted in increasingly turbulent business environments. Typically, fast-changing and unpredictable markets, complex and changing customer requirements, pressures of shorter time-to-market, and rapidly advancing information technologies are characteristics found in most software development projects.
Continuous software evolution and delivery refers to the organisational capability to evolve and release software in fast parallel cycles, typically hours, days or very small numbers of weeks. For example, lean start-ups release up to 50 times per days. This includes determining new functionality to build, prioritising the most important functionality, evolving and refactoring the architecture, developing the functionality, validating it, releasing it to customers and collecting experimental feedback from the customers to inform the next cycle of development. As reaching the goal of continuous evolution and delivery is a holistic endeavour, it cannot be addressed only by automating the release engineering pipeline, but requires changes across the whole development cycle, both before (even up until requirements) and after release. For example, reducing the scope of a release has to be done during requirements analysis, while prioritization of post-release bugs to resolve in the next release needs to be done once a release has been pushed to the customer.
CSED 2016 will bring together researchers and practitioners to discuss challenges of continuous software evolution and delivery and exchange innovative ideas to solve them. The workshop is co-located with ICSE 2016, the International Conference on Software Engineering, in Austin, Texas. CSED will be a highly interactive workshop with a strong emphasis on discussions.
In summary, topics relevant to the scope of the workshop are 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.
- process aspects and agile practices supporting continuous *
- 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
We are soliciting full research papers (up to 7 pages), position papers (up to 4 pages), and industrial talks (1 page abstract). Full research papers present original and evaluated research whereas position papers describe novel ideas, identified challenges, or experiences related to the workshop’s theme. Industrial talks present challenges from practice and lessons learned. The paper has to follow the ICSE 2016 formatting and submission instructions.
Please submit your abstract and paper using the EasyChair page for the workshop via EasyChair.
Accepted papers will be published as an ICSE 2016 Workshop Proceedings in the ACM and IEEE Digital Libraries. 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.