AOSD Conference  
Program Overview
Technical Program
Industry Track
Student Extravaganza
Conference Venue
Chicago Photos
Chicago History
Student Volunteers
AOSD-Europe Sponsorships

Practitioner Reports

Important Dates

Summary submission (optional but recommended): September 7, 2004
Report submission: October 25, 2004
Notification of acceptance: December 6, 2004
Final revision due: January 17, 2005


With AOSD gaining popularity, many potential new users are somewhat cautious about adoption. As the basic understanding of AOP improves among developers, perhaps the most common question asked is "who is using it, and how it has worked for them?" Practitioner reports at AOSD.05 provide a platform to answer these questions.

Practitioner reports provide an opportunity for the industry leaders in applying AOSD to share their experiences with the community and for the community to learn lessons to guide their adoption. AOSD.05 attendees will want an objective analysis of AOSD applications in real life. What kinds of problems have you tackled with AOSD? Did it meet your expectations? What issues did you face? How did your colleagues who weren’t familiar with AOSD respond? Did you uncover any patterns, anti-patterns, and best practices?

With the increased focus on industry participation in AOSD.05, practitioner reports will form an important part of the conference. This year we are encouraging new participants to submit a summary of their experience, so they can receive early feedback and support in producing a good practitioner’s report.

Submission Guidelines

Practitioner reports should be submitted to A practitioner feedback committee (separate from the program committee) will evaluate the submissions. The review process may require a phone interview to understand the report better and help the authors improve it to better meet participant expectations. Therefore, your submission must name a primary contact including postal address, telephone and fax numbers, and email address.

We encourage interested practitioners to take advantage of the summary submission deadline to get early feedback. This option allows submitters to describe an application of AOSD, and to get assistance in what to emphasize and in structuring and writing an experience report about it.

Authors of accepted papers will present a 30 minute presentation at the AOSD conference. The audience will include experts from both industry and academia. Accepted submissions will also be posted on

Practitioner reports should be 3-10 pages in length, including an abstract not to exceed 300 words. The authors’ names, affiliations and e-mail addresses must be clearly stated on the first page.

A references section should list all publications that have been referenced in the report, and references should be complete and consistent in style. It is not a requirement to follow the technical paper submission guidelines, though you may do so if convenient. A single column layout is acceptable if this better suits your material. The ICSE 2003 conference site provided quality criteria and guidelines for experience reports which you may find helpful in preparing your submission. With thanks to the ICSE 2003 Experience Reports Committee, a subset of those guidelines is reproduced here for convenience:

Structure and content of report

The structure and content of a good experience report is characterized as follows.

  • The introduction
    • presents the background and the context of the contribution
    • makes clear which roles the authors of the contribution play in the work that is being reported
    • summarizes results and insight in a few sentences
    • gives an overview of the structure of the paper
  • The main sections
    • of a "classic" experience report describe the approach and its results in terms of the methods, techniques, languages, tools, processes, prerequisites, problems, and people involved, as appropriate
    • of a case study describe a product and give rationale for the key decisions shaping the product
  • The conclusion
    • evaluates the results and derives experience and insight that is valuable for the intended audience of the paper
    • reports both positive and negative observations (nothing is perfect!)
    • discusses limitations and the range of applicability
    • refers to related experience by others and discusses it (if such experience exists and if this has not been discussed in the introduction)
    • summarizes the state of work and sketches future work (if applicable)
  • The references
    • list all publications that have been referenced in the paper are complete and consistent in style


For additional information, clarifications, or questions please contact the AOSD.05 Industrial Chairs: Ron Bodkin and Ramnivas Laddad (

Edited by the AOSD Conference Committee.  Send comments to: