The topics of interest include, but are not restricted to, the following:
- Agile and lean methods and processes
- Continuous deployment
- Continuous experimentation, A/B testing
- Crowdsourcing in software development
- Development approaches using customer feedback
- DevOps, Big data real-time analytics for software process improvement
- Empirical studies in industry about processes and methods
- Global or distributed software development and scaling
- Infrastructure and processes for iterative or incremental software delivery
- Predictive models for software engineering tasks
- Process modeling, management, assessment and improvement
- Processes and methods for commercial or open source development
- Processes for (digital) software product innovation
- Product quality models for software, system, and services
- Project management techniques
- Release planning
- Service engineering processes
- Software analytics with actionable insights on software products and processes
- Software development for Cyber Physical Systems
- Software ecosystems, software business and start-ups
- Value-driven software development
The short papers track provides a forum where work-in-progress and emerging results can be communicated and discussed. We invite submissions of short papers (max. 8 pages) related to all the topics of interest of the conference. The track aims that short paper authors gather early feedback from the software engineering community to continue their work on more solid grounds. The topics of interest for the short papers track are the same than the topics of the full papers track. In addition, the short paper track welcomes also tool demonstrations covering any aspect of the same topics of interest.
- Papers describing work-in-progress should define the long-term objectives, the potential contributions of the research, the current state of the work and the future steps. Validation is unnecessary, although evidence about the feasibility of the research is welcome: pilots, proofs of concept, etc.
- Papers on emerging results should report preliminary research results, backed up by adequate evidence, but a full evaluation is not required. Manuscripts should adopt the usual structure of a full research paper, although details may be overlooked to fit the page count.
- Tool demo papers provide researchers as well as practitioners with the opportunity to show how they support and enable software engineering in practice. We encourage discussing experiences and lessons learned when using the tool in practice.
All papers must be submitted in PDF format through the Submission Procedure.
PC Short Papers
- Luca Ardito, Politecnico di Torino, Italy, firstname.lastname@example.org
- Michael Klaes, Fraunhofer IESE, Germany, email@example.com