|
||
| Abstract |
|
||
| Submission |
|
||
| Notification |
|
||
| Camera-Ready |
Uppsala Konsert & Kongress, Uppsala, Uppsala County, Sweden
The 20. International Conference on Fundamental Approaches to Software Engineering (FASE) 2017
Topics
- Software engineering as an engineering discipline, including its interaction with and impact on society;
- Requirements engineering: capture, consistency, and change management of software requirements;
- Software architectures: description and analysis of the architecture of individual systems or classes of applications;
- Specification, design, and implementation of particular classes of systems: adaptive, collaborative, embedded, distributed, mobile, pervasive, or service-oriented applications;
- Software quality: validation and verification of software using theorem proving, model checking, testing, analysis, refinement methods, metrics or visualisation techniques;
- Model-driven development and model transformation: meta-modelling, design and semantics of domain-specific languages, consistency and transformation of models, generative architectures;
- Software processes: support for iterative, agile, and open source development;
- Software evolution: refactoring, reverse and re-engineering, configuration management and architectural change, or aspect-orientation.
Submissions
FASE accepts 3 types of submissions: research papers, tool papers, and tool demo papers (4+6 pp).
Research papers clearly identify and justify a principled advance to the fundamentals of software engineering. Papers should clearly articulate their contribution, and provide sufficient evidence for the validity and applicability of the proposed approach. Research papers that combine the development of conceptual and methodological advances with their formal foundations and tool support are particularly encouraged. Research papers can have a maximum of 15 pp (excluding bibliography of max 2 pp).
Regular tool papers present a new tool, a new tool component, or novel extensions to an existing tool. They should provide a short description of the theoretical foundations with relevant citations, and emphasize the design and implementation concerns, including software architecture . A regular tool paper should give a clear account of the tool's functionality, discuss the tool's practical capabilities with reference to the type and size of problems it can handle, describe experience with realistic case studies, and where applicable, provide a rigorous experimental evaluation. Papers that present extensions to existing tools should clearly focus on the improvements or extensions with respect to previously published versions of the tool, preferably substantiated by data on enhancements in terms of resources and capabilities. Authors are strongly encouraged to make their tools publicly available, preferably on the web, even if only for the evaluation process. Tool papers can have a maximum of 15 pp (excluding bibliography of max 2 pp).
Tool demonstration papers focus on the usage aspects of tools. As with regular tool papers, authors are strongly encouraged to make their tools publicly available, preferably on the web. Theoretical foundations and experimental evaluation are not required, however, a motivation as to why the tool is interesting and significant should be provided. Tool demonstration papers can have a maximum of 4 pages. They should have an appendix of up to 6 additional pages with details on the actual demonstration.
Important Dates
Abstracts due (ESOP, FASE, FoSSaCS, TACAS): 14 October 2016 23:59 AoE (=GMT-12)
Papers due: 21 October 2016 23:59 AoE (=GMT-12)
Rebuttal (ESOP and FoSSaCS only): 7-9 December 2016
Author notification: 22 December 2016
Camera-ready versions: 20 January 2017
