FASE 2011
Event Rating
| median | worst |
|---|---|
|
|
List of all ratings can be found at FASE 2011/rating
| FASE 2011 | |
|---|---|
International Conference on Fundamental Approaches to Software Engineering
| |
| Ordinal | 14 |
| Event in series | FASE |
| Subevent of | ETAPS 2011 |
| Dates | 2011-03-26 (iCal) - 2011-04-03 |
| Presence | presence |
| Homepage: | https://www.cs.upc.edu/~orejas/FASE.html#cfp |
| Submitting link: | http://www.easychair.org/conferences/?conf=fase2011 |
| Location | |
| Location: | DE/SL/Saarbrücken, DE/SL, DE |
| Important dates | |
| Abstracts: | 2010/10/01 |
| Submissions: | 2010/10/08 |
| Notification: | 2010/12/10 |
| Camera ready due: | 2011/01/03 |
| Papers: | Submitted 116 / Accepted 29 (25 %) |
| Committees | |
| PC chairs: | Dimitra Giannakopoulou, Fernando Orejas |
| Keynote speaker: | Marta Kwiatkowska |
| Table of Contents | |
The 14. International Conference on Fundamental Approaches to Software Engineering (FASE) 2011
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: design and semantics of semi-formal visual languages, consistency and transformation of models;
- Software quality: validation and verification of software using theorem proving, model-checking, testing, analysis, metrics or visualisation techniques;
- 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
ETAPS conferences accept two types of contributions: research papers and tool demonstration papers. Both types of contributions will appear in the proceedings and have presentations during the conference.
Submitted papers must be in English presenting original research. They must be unpublished and not submitted for publication elsewhere (neither conference nor journal). In particular, simultaneous submission of the same contribution to multiple ETAPS conferences is forbidden. All papers, especially research papers, should clearly identify their novel contributions to the domain of fundamental approaches to software engineering. One author of each accepted paper must attend the conference to present the paper.
Papers should be submitted electronically in PDF (preferably) or PS (using Type 1 fonts). The proceedings will be published in the Springer-Verlag Lecture Notes in Computer Science series. Final papers will be in the format specified by Springer-Verlag at the URL: http://www.springer.de/comp/lncs/authors.html Submissions not adhering to the specified format and length may be rejected immediately, without review. As electronical submission system we use EasyChair. Please use http://www.easychair.org/conferences/?conf=fase2011 to submit your paper.
Research papers:
Research papers will be not more than 15 pages long (including figures and references). Additional material intended for the referee but not for publication in the final version - for example details of proofs - may be placed in a clearly marked appendix that is not included in the page limit. ETAPS referees are at liberty to ignore appendices, and papers must be understandable without them.
Tool demonstration papers:
Tool demonstration papers should describe novel and state-of-the-art tools. Submissions should consist of two parts. The first part, no more than 4 pages, should describe the tool presented. Please include the URL of the tool (if available) and provide information that illustrates the maturity and robustness of the tool. This part will be included in the proceedings. The second part, no more than 6 pages, should explain how the demonstration will be carried out and what it will show, including screen dumps and examples. This part will not be included in the proceedings, but will be evaluated.
Important Dates
1 October 2010: Submission deadline for abstracts (strict)
8 October 2010: Submission deadline for full papers (strict)
10 December 2010: Notification of acceptance/rejection
3 January 2011: Camera-ready versions due (strict)
26 March - 3 April 2011: ETAPS 2011