ASE 2012

2) Experience Papers should describe a significant experience in applying automated software engineering technology and should carefully identify and discuss important lessons learned so that other researchers and/or practitioners can benefit from the experience. Of special interest are experience papers that report on industrial applications of automated software engineering.

Submissions under both categories should not exceed 10 pages in the two-column conference format (see note below). Papers will be administratively rejected and will not be reviewed if they exceed the 10-page limit or use condensed formatting. For guidelines and formatting files, see here.

Papers submitted to ASE 2012 must not have been previously published and must not be under review for publication elsewhere. Papers must strictly adhere to submission guidelines. Authors are strongly encouraged to explain the relationship between the submission and any other related works from the authors, including ones under review elsewhere, in the appropriate place in the submitted paper.All papers that conform to submission guidelines will be peer-reviewed by PC members. Papers may be accepted either as full papers or as short papers. In this last case the camera-ready should be no longer than 4 pages. All accepted short papers will be presented in a poster session.

Abstract Submission	February 24th, 2012 (Friday)
Paper Submission	March 2nd, 2012 (Friday)
Author Notification	June 18th, 2012 (Monday)
Camera-ready Papers	tbd

 

Tool Demonstrations

The ASE tool demonstrations track provides an opportunity for researchers and practitioners to present and discuss the most recent advances, experiences, and challenges in the field of automated software engineering with the goal of allowing live presentation of new research tools. Tools can range from research prototypes to in-house or pre-commercialized products.

The tool demonstrations are intended to highlight underlying scientific contributions. Whereas a regular research paper is intended to give background information and point out the scientific contribution of a new software engineering approach, a tool demonstration paper provides a good opportunity to show how the scientific approach has been transferred into a working tool. Authors of regular research papers are thus encouraged to submit an accompanying tool demonstration paper.

The Tool Demonstration Committee will review each submission to assess the relevance and quality of the proposed tool demonstration in terms of usefulness of the tool, presentation quality, and appropriate discussion of related tools.

Accepted tool demonstrations will be allocated 4 pages in the conference proceedings. Demonstrators will be invited to give a presentation that will be scheduled into the conference program. There will also be a demonstration area open to attendees at scheduled times during the conference, during which demonstrators are expected to be available. Presentation at the conference is a requirement for publication.

Submissions of proposals for formal tool demonstrations must:

• adhere to the ASE 2012 proceedings format (ACM proceedings style);
• have a maximum of 4 pages that describe the technology or approach, how it relates to other industrial or research efforts, including references, and describe what the expected benefits are;
• have an appendix (not included in the 4 page count) that provides a brief description of how the demonstration will be conducted (possibly illustrated with further screen shots);
• provide a URL from which the tool can be downloaded, with clear installation steps. If the tool cannot be made available, the authors must clearly state their reasons in the paper. All examples and scenarios presented in the paper and appendix should be replicable directly.
• be submitted via the EasyChair system by May 14, 2012.

Tool Demonstration Co-Chairs

• Ewen Denney SGT / NASA Ames, United States
• Bernd Fischer University of Southampton, United Kingdom

Contact: ase2012tools@easychair.org

Submission	May 14th, 2012 (Monday)
Author Notification	June 22nd, 2012 (Friday)
Camera-ready Papers	July 9th, 2012 (Monday)

 

Doctoral Symposium

Submission site for the ASE 2012 Doctoral Symposium

Goal The goal of the ASE 2012 Doctoral Symposium is to provide a supportive yet questioning setting in which the PhD students have an opportunity to present and discuss their research with other researchers in the ASE community. The Symposium aims to provide students with useful guidance and feedback on their research and to facilitate their networking within the scientific community by interacting with established researchers and with their peers at a similar stage in their careers.

Scope The technical scope of the Symposium is that of ASE. Students should consider participating in the Doctoral Symposium after they have settled on a dissertation topic with some initial research results. Students should be at least a year from completion of their dissertation (at the time of the Symposium), to obtain maximum benefit from participation. The Doctoral Symposium is open to Ph.D. students at any stage of their research, whereby students at the initial stage (first or second year) will be able to challenge their ideas and current research directions, while students at a more mature stage (third or fourth year) will be able to present their thesis and get advice for improvement and for better exposition of their contributions and conclusions.

Evaluation The Doctoral Symposium Committee will select participants using the following criteria:

• The potential quality of the research and its relevance to automated software engineering.
• Quality of the research abstract.
• Diversity of background, research topics and approaches.

Students should not infer that a list of prior publications is in any way expected or required; we welcome submissions from students for whom this will be their first formal submission as well as those who have previously published.

How to Submit To apply as a student participant in the Doctoral Symposium, you should prepare a submission package consisting of two parts, both of which must be submitted by the submission deadline.

Part 1: Research Abstract (max. 4 pages). Your research abstract must conform to the ASE 2012 formatting and submission instructions and should cover:

• The research problem that you are targeting with justification of its importance
• Discussion on related and prior work explaining why this has not solved the problem
• A sketch of the proposed approach or solution
• The expected contributions of your dissertation research
• Progress you have made so far in solving the stated problem
• The methods you are using or will use to carry out your research
• A plan for evaluating your work and presenting credible evidence of your results to the research community
• A list of any publications either appeared, accepted or submitted for which the student is an author.

Students at the initial stage of their research might have some difficulty in addressing some of these areas, but should make the best attempt. The research abstract should include the title of your work, your name, your advisor, your email address, postal address, personal website, and a one paragraph short summary in the style of an abstract for a regular paper.

Part 2: Letter of Recommendation. Please ask your dissertation advisor for a letter of recommendation. This letter should include your name and a candid assessment of the current status of your dissertation research and an expected date for dissertation submission. The letter should be in Adobe Portable Document Format (PDF), and sent to: Tevfik Bultan and Andreas Zeller with the subject: ASE 2012 DOCTORAL SYMPOSIUM RECOMMENDATION.

Acceptance All authors of accepted contributions will receive further instructions for preparing their camera ready versions. Authors must register for the ASE 2012 Doctoral Symposium and present their work at the Symposium.

Doctoral Symposium Co-Chairs

• Tevfik Bultan University of California, Santa Barbara, United States
• Andreas Zeller Universitaet des Saarlandes, Germany

Submission	May 7th, 2012 June 25th, 2012 (Monday)
Author Notification	June 16th, 2012 July 23rd, 2012 (Monday)

 

Tutorials

Tutorials may address a wide range of mature topics from theoretical foundations to practical techniques and tools for automated software engineering. The tutorials can be organized either before (Mon, Tue) or after (Sat) the main conference, but the preference would be to have all tutorials before the main conference. The organizers will decide about this after the proposals have been reviewed and accepted. Tutorials are intended to provide independent instruction on a relevant theme; therefore, no commercial or sales-oriented proposals will be accepted.

Instructors are invited to submit proposals for half-day and full-day tutorials and, upon selection, are required to provide tutorial notes or a survey paper on the topic of presentation in PDF. Proposals for organizing tutorials should be written in English, limited to 5 pages (in ACM format), and submitted in PDF to both tutorials co-chairs Gabriele Taentzer and Darko Marinov (find emails below). They should include the following information:

• Name and affiliation of the proposer/organizer (including postal address, phone number, fax number, e-mail address)
• Name and affiliation of each additional instructor
• Instructors’ experience in the area, including other tutorials, courses, etc.
• Title, objective, abstract, duration
• Outline with approximate timings
• Target audience, including indication of level (novice, intermediate, expert)
• Assumed background of attendees
• Brief biography of each instructor (for later inclusion in publicity materials)
• Indication of whether a survey paper will be provided (max. 30 ACM-formatted pages)
• History of the tutorial (if it has been already presented; provide location, approximate attendance, etc.)
• Justification for full day (if a full day is proposed)
• Audio-visual and technical requirements
• References including the proposers’ papers on the subject
• Preferences for tutorial date, duration (half-day or full-day), and any other scheduling constraints

Review Process Tutorial proposals will be reviewed by the ASE 2012 tutorials and workshop co-chairs. Acceptance will be based on the timeliness and expected interest in the topic, the proposer’s ability to present an interesting tutorial, and the potential for attracting a sufficient number of participants.

Workshop and Tutorial Co-Chairs

• Gabriele Taentzer Philipps-Universitaet Marburg, Germany
• Darko Marinov University of Illinois at Urbana-Champaign, United States

Submission	April 23rd, 2012 April 26th, 2012 (Thursday)
Author Notification	May 21st, 2012 (Monday)

 

Workshops

A workshop co-located with the ASE 2012 conference should provide an opportunity for exchanging views, advancing ideas, and discussing preliminary results on topics related to Automated Software Engineering. Workshops may also serve as incubators for new scientific communities. Workshops should not be seen as an alternative forum for presenting full research papers. The workshops co-located with the conference can be organized either before (Mon, Tue) or after (Sat) the main conference, but the preference would be to have all workshops before the main conference. The organizers will decide about this after the proposals have been reviewed and accepted. A workshop may last one or two days.

Proposals for organizing workshops should be written in English, limited to 5 pages (in ACM format), and submitted in PDF to both workshop co-chairs Gabriele Taentzer and Darko Marinov (find emails below). They should include the following information:

• Theme and goals of the workshop including its relevance to the field of Automated Software Engineering
• Targeted audience and the desired minimum and maximum number of participants
• Workshop format (e.g., paper presentations, breakout sessions, panel-like discussions, combination of formats)
• The equipment, room capacity, and any other resource necessary for the organization of the workshop
• Participant solicitation and selection process
• Publicity strategy that will be used by the workshop organizers to promote the workshop
• Brief description of the organizer’s background, including relevant past experience on organizing workshops and contact information
• Initial version of the call for papers that the workshop organizers intend to use
• Preferences for workshop dates, duration (1 or 2 days), and any other scheduling constraints

Note that the workshop co-chairs will consider the preference of workshop dates specified by the organizers, but the acceptance of a workshop proposal does not guarantee adherence to the requested date/time. The workshop co-chairs will assume that workshop proposers will be able to run a workshop on either of the dates that ASE 2012 has reserved for workshops.

Review Process Workshop proposals will be reviewed by the ASE 2012 tutorials and workshop co-chairs. Acceptance will be based on an evaluation of the workshop’s potential for generating useful results, the timeliness and expected interest in the topic, the organizer’s ability to lead a successful workshop, and the potential for attracting a sufficient number of participants. Accepted workshops must adhere to the common deadlines listed below for submissions of papers, acceptance of papers, and preparation of proceedings.

For 2012, the ASE organizers offer to publish workshop proceedings in the local technical report series (which has an ISSN) but only electronically not to print them. The workshop organizers have to do the editing of the workshop proceedings.

Workshop and Tutorial Co-Chairs

• Gabriele Taentzer Philipps-Universitaet Marburg, Germany
• Darko Marinov University of Illinois at Urbana-Champaign, United States

Workshop Proposal Submission	March 28th, 2012 April 26th, 2012 (Thu)
Notification for Workshop Proposal	April 16th, 2012 May 4th, 2012 (Fri)
Call for Workshop Papers	April 30th, 2012 May 15th (Tue)
Workshop Paper Submission	July 2nd, 2012 (Monday)
Notification for Workshop Papers	August 6th, 2012 (Monday)