[ecoop-info] ECOOP 2012 Doctoral Symposium CfP
gkrichar at purdue.edu
Wed Apr 4 19:27:07 CEST 2012
ECOOP 2012 in Beijing, China hosts the 22nd edition of the Doctoral
Symposium and PhD Student Workshop. As the name suggests, this is a
two-session event: a Doctoral Symposium and a PhD Student Workshop. The
Doctoral Symposium and PhD Student Workshop provides a forum for both
early and late-stage PhD students to present their research and get
detailed feedback and advice. The main objectives of this event are:
to allow PhD students to practice writing clearly and to present
effectively their research proposal
to get constructive feedback from other researchers
to build bridges for potential research collaboration
to contribute to the conference goals through interaction with
other researchers at the main conference
Full information is at
This is an excellent venue for PhD students to get feedback, and also a
good opportunity to get to this year's ECOOP in China.
Potential topics are those of the main conference, i.e. all topics
related to object technology. The following list of suggested topics is
by no means exclusive:
Analysis and design methods and patterns
Databases, persistence, transactions
Distributed, concurrent, mobile, real-time systems
Empirical and application studies
Frameworks, product lines, software architectures
Language design and implementation
Modularity, aspects, features, components, services, reflection
Software development environments and tools
Static and dynamic software analysis, testing, and metrics
Theoretical foundations, type systems, formal methods
Versioning, compatibility, software evolution
== Doctoral Symposium
The goal of the doctoral symposium session is to provide PhD students
with useful feedback towards the successful completion of their
dissertation research. Each student is assigned an academic panel, based
on the specifics of that student's research. The student will give a
presentation of 15-20 minutes (exact time will be announced later),
followed by 15-20 minutes of questions and feedback. The experience is
meant to mimic a "mini-" defense interview. Aside from the actual
feedback, this helps the student gain familiarity with the style and
mechanics of such an interview (advisors of student presenters will not
be allowed to attend their student's presentations). To participate, the
students should be far enough in their research to be able to present:
the importance of the problem
a clear research proposal
some preliminary work/results
an evaluation plan
The students should still have at least 12 months before defending their
dissertation. We believe that students that are defending within a year
would not be able to incorporate the feedback they receive.
To participate, please submit:
a 3-4 page abstract in the llncs format.
a letter from your advisor. This letter should include an
assessment of the
current status of your dissertation research and an expected date for
The abstract should focus on the following:
what is the problem?
what is the significance of this problem?
why the current state of the art can not solve this problem?
what is the goal of your research?
what artifacts (tools, theories, methods) will be produced,
and how do they address the stated problem? How are the artifacts going
to help reach the stated goal?
what experiments, prototypes, or studies need to be
what is the validation strategy? How will it demonstrate
that the goal was reached?
Note that this is not a typical technical paper submission, and that the
focus is not on technical details, but rather on research method.
== PhD Student Workshop
This session is addressed primarily to PhD students in the early stages
of their PhD work. The goal is to allow participants to present their
research ideas and obtain feedback from the rest of the workshop
attendees. Each participant will give a 10-15 minute presentation,
followed by 10-15 minutes of discussions (exact times will be announced
To participate, please submit:
6-10 page position paper in the llncs format, presenting your idea
or current work
Position paper submission details will be provided as soon as they are
The position paper should contain (at least):
a problem description
a detailed sketch of a proposed approach
As this is earlier-stage research, it is not necessary to have concrete
results from this research presented in the paper. Instead, the goal of
the paper is to inform the reader of a (well-motivated) problem and to
present a high level (possible) solution.
If accepted for presentation, the student's advisor must email the chair
no later than 8 June, 2012 and confirm that the advisor attended at
least one of the student's presentation rehearsals.
More information about the ecoop-info