The Code Generation conference is the leading event on the practical applications of Model-Driven Software Development (MDSD). Each year the conference is recognised by participants as a high-quality, high-value learning experience. This reputation is built on attracting industry-recognised experts to speak at the conference.

CODE GENERATION 2012 CALL FOR SPEAKERS - NOW CLOSED (DEADLINE DECEMBER 9th 2011)

We sought high-quality session proposals covering any aspect of MDSD (including Domain-Specific Languages (DSLs), Model-Driven Architecture (MDA), Domain-Specific Modelling, Generative Programming, Software Product Lines and related areas).

Sessions could cover topics such as:

• Defining and implementing modelling languages
• Code Generation and Model Transformation tools and approaches
• Language evolution and modularization
• Domain Analysis and Domain Engineering
• Tool and technology adoption
• Meta Modeling
• Runtime virtual machines versus direct code generation
• Approaches to code generation
• Approaches to combined development (partial code generation with partial handwritten code)
• Flexibility in code generation

Hands-on sessions, experience reports, tutorials, panels and other interactive sessions based on any aspect of these and related approaches are particularly encouraged although more theoretical sessions are also welcome.

In addition to paying no conference fees, being a speaker gives you a unique opportunity to present your viewpoint to our audience.

MAKING A PROPOSAL

Making a session proposal isn't difficult. All we require is some basic information on the session you plan to run - enough to judge that it would be of value to our participants. We've come up with some suggested session types, but feel free to propose your own:

Session Types

Case Study / Experience Report

A presentation and discussion of real-life (not theoretical) experiences of the application (or mis-application) of any of the above tools and techniques. Case studies and experience reports must include some discussion of lessons learned and an indication of how novel the work is.

Tutorial

A session focused around some specific tool, technique or issue. Primarily led by the speaker but should include some elements of interactivity or individual / group exercise.

Hands-On Session

Participants learn a new tool or technology through using it to solve one or more practical exercises. We recommend that hands-on sessions are run by two session leaders. Please include a description of required hardware and software for the session and how you will distribute any software to participants.

Goldfish bowl

A facilitated discussion session based around a well-defined topic or question related to the conference themes. The session leader introduces the topic and may seed the session with particular questions or subtopics. A small number of 'experts' then debate the topic or question. However, participants are free to join in the discussion by taking the 'experts' places as they relinquish their seats. We can provide contact details for people who could make good initial 'experts'.

Panel

A small group of 'experts' presents their views on some defined conference topic. Audience members may ask questions of the panel.

Think-Tank

There are many open issues related to the conference themes. A think-tank considers one or more such issues and aims to produce some outputs of value to the community. The session leader is responsible for managing the Think Tank and completing the session outputs.

Workshop

An in-depth working session on a specific topic. May include paper presentations.

SUBMITTING A SESSION

Please read our Terms and Conditions before submitting a session proposal.

Please include your session title, your name(s) and brief (< 100 words) biographical information, a contact email address and telephone number and/or Skype name.

If there are multiple session leaders then please include biographical and contact information for all speakers and indicate who the main point of contact is.

Session proposals should be made using one of our standard templates available as PDF, word , open office and plain text. You can make as many session proposals as you like.

These include the following information:

• Session title: a short title that sums up your session's content
• Session type: one of the above or some other type
• Session duration: (typically 45, 60, 75 or 90 minutes but longer proposals are welcome)
• Session abstract: a brief description outlining the key objectives and content of the session
• Session description: a fuller description of the session content including details about whether the session has been run before
• Intended audience: roles / experience levels (any prior knowledge / skills required)
• Session outputs: Does the session have outputs that would be of interest to non-participants? Electronic outputs such as recordings will be placed on The Model Driven Software Network at the organiser's discretion.
• Availability: Whether there are any constraints in your participation or whether it makes sense to run your session before or after another session you've proposed.

SUBMITTING A PROPOSAL

After preparing a proposal you should upload it into our submission and review system. We are using EasyChair again this year which will be familiar to many regular conference speakers. We cannot accept proposals that haven't been submitted through EasyChair. If you have submitted to other conferences that use EasyChair, then you can reuse your existing Easychair login for CG2012 submission. If not, then you first need to create an account. Full instructions on the submission process are available here.

Please note that sessions must be submitted no later than Friday December 9th 2011. Sessions submitted after this date will be considered at the organisers discretion.