ASWEC 2013

Guidelines for Authors of Tutorial Proposals

Tutorial proposals that have practical appeal to the software engineering community are sought for ASWEC 2013. Tutorials are designed to help software professionals rapidly come up to speed on a specific technology or methodology. They can be lecture-oriented or participatory.

Tutorials are half-day sessions consisting of two 90-minute blocks separated by a 30-minute break, or full-day sessions consisting of four 90-minute blocks, with 30-minute breaks in the morning and afternoon, and a one-hour lunch break. Tutorial rooms are equipped with a data projector; attendees are provided with handouts, to be submitted by presenters one and a half months in advance (in order to allow enough time for printing).

Important Dates:
Proposals due 14 Dec 2012
Acceptance notification 21 Jan 2013
Confirmation of programme 13 Mar 2013
Final versions due 15 April 2013
Final versions due 15 April 2013

Tutorials will be assessed by a panel of academic and industry representatives according to the following criteria :

  • Relevance, interest, and value of the topic to ASWEC attendees;
  • Completeness, clarity, and quality of the tutorial proposal;
  • Expertise and experience of the presenters in the proposed topic and in delivering a successful educational presentation; and
  • Effectiveness of the proposed presentation approach.

The ASWEC Organising Committee reserves the right to cancel tutorials that have not received sufficient registrations by the close of early registration for the conference.

Proposals should be emailed to aswec2013@swin.edu.au, with the subject line "ASWEC2013 Tutorial Proposal", in plain text (preferred) or PDF format. Submissions should include the following information :

  1. Title:
  2. Speaker(s):
  3. Contact Person: (including full physical and electronic contact details)
  4. Level: Introductory / Intermediate / Advanced
  5. Topic Area:
  6. Duration: Half Day / Full Day
  7. Tutorial Description: This will be used to advertise the tutorial and should provide a clear indication of the topic to be covered and the expected outcomes for the participants. (Maximum 300 words)
  8. Presenters' Biographies: (Maximum 200 words)
  9. Content Outline: This should be a detailed description of the tutorial and its content. This is where you are selling your tutorial to the conference organisers. You need to illustrate how this tutorial will benefit attendees and relate to the conference topics and theme. Also included in this description should be an outline indicating time allocated to topics. (Tutorial sessions will be scheduled for three and a half hours, including a half hour tea break. Your running time should be for three hours for a half-day tutorial or six for a full day tutorial.
  10. Presenter Resume: In this section provide evidence of your experience in conducting professional tutorials. Include references to past conference tutorials or professional development courses you have conducted. Also indicate if this tutorial has been presented in the past and if it has been modified since the last presentation.
  11. Technical Experience: Provide evidence that you are qualified to claim you are an expert in the topic area of this tutorial.
  12. Supporting Material: Attach any other material that you believe may support your proposal.