|
|
Guidelines
for Workshop Proposals
|
|
 |
Workshops
provide a forum for the exchange of ideas and results
and one which is at the same time more issue centred
and less formal than the main conference. Workshops
typically consist of groups of between 15 to 30 researchers
and practitioners, and last for one full day. All topics
related to UML or other modeling languages are potential
subjects for workshops. Workshops will typically fall
into the following categories:
-
A workshop may address a specific
sub-area of UML in depth.
Examples of such sub-areas include:
modifications to UML, advanced automated tool support,
extension mechanisms, constraint languages, formal
semantics of UML, transformations of UML models,
animation of UML models.
-
A
workshop may cover areas that spread over multiple
sub-areas in computer science, software engineering
and related fields. Examples of such areas include:
process modeling with UML, process improvement with
UML, management of projects with UML, software architecture
with UML, teaching UML, requirements engineering,
or aspect-orientation.
-
A workshop may focus on the applications and deployment
of UML in areas such as telecommunications,
e-commerce, mobile computing or real-time systems.
Workshops reporting on industrial experiences are
particularly welcome.
Workshop
topics are by no means limited to the examples mentioned
above. However, in each case the proposed area is expected
to have enough impetus to yield new results that can
be considered important and worthy of more detailed
investigation.
How
should the Proposal be presented?
Workshop proposals should be electronically sent in
Postscript or PDF format. Please, use the "title
of the workshop" as subject area, and identify
the file with the proposal using the name of the contact
person.
A workshop proposal should include the following information:
-
Name of the workshop.
-
Names and affiliations of the organizers, indicating
the main contact.
-
Abstract of the workshop (no more than 200 words),
including major topics, goals and expected outcomes.
- Motivation:
relevance of the workshop to UML community; references
to other workshops organized by the proposers at
UML or related conferences. Is the workshop a continuation
of other workshops?
- The
desired, minimum and maximum number of workshop
participants. Explain why this workshop should attract
sufficient participants.
- Requested
Audio/Video equipment, room capacity and organization,
and materials.
- Workshops
will be held on Monday (October 11) and Tuesday
(October 12). Please indicate if you have a strong
preference for either of these dates.
- A
preliminary version of the Call for Papers that
the organizers must prepare if the workshop is accepted.
This should address:
-
A brief overview of the proposed workshop, including
a description of the goals of the workshop and
the work methods. This overview should be targeted
specifically to potential workshop participants
and provide some information about who should
participate in the workshop.
- Maximum
number of participants; participant solicitation
and selection process.
- Workshop
activities: this includes a schedule of activities
the organizers plan for the workshop. Besides
the expected format of the workshop, it may
include pre and post workshop activities.
- Authors
of position papers need to be notified about
acceptance of their papers at least two weeks
before early registration deadline. Important
dates for authors will be discussed and agreed
between the WC and the organizers of accepted
workshops.
- References
to previous workshops on the same or related
topics, including web sites, where participants
may find additional information.
- Organizers
biography.
Proposal
review and acceptance
The proposals will be reviewed and acceptance will
be primarily based on an evaluation of the workshop's
potential for generating useful results, relevance
and expected level of interest in the topic, and the
organizers' capacity to lead a successful workshop.
Organizers
of accepted workshops will be requested to prepare
a web page that will contain the latest information
about the workshop. The URL of each workshop will
be added to the UML 2004 workshop web site.
Additional
recommendations
- Workshop organizers should foster the creative
potential that is tentatively present in a workshop.
- Remember that a workshop is NOT a conference!
- Ideally, the number of workshop participants will
range from 15 up to 30.
Time
allocation
- The success of a workshop depends greatly on
the results generated on-site. Consequently, enough
time should be reserved for collaborative work during
the workshop.
- Such creative sessions should have a precise topic
and goal. The results of such sessions are fundamental
if you want to produce any post-workshop results,
such as a report.
Reasonable
expectations
- The organizers should not assume people's instantaneous
and proactive participation.
- For many reasons, participants tend to prefer
a passive, consumer role to an active, producer
role during a workshop.
- Thus pre-screened presentations, even formally
reviewed papers, should usually precede any creative
sessions.
Task
forces
- Large groups tend to behave like an audience,
whereas groups of four to eight people are much
more likely to interact.
- When planning collaborative sessions, consider
having several smaller groups rather than one large
group in order to foster the generation of new ideas.
Presentation
selection
- If you decide to allow presentations during the
workshop, quality should obviously be the primary
criterion for selection of these presentations.
- Nevertheless, in order for a workshop to be productive,
consider also having presentations on some new,
controversial topics to spark discussion.
- For additional questions or clarification, or
for your suggestions, please feel free to contact
the UML 2004 Workshop Chair:
Ambrosio Toval,
e-mail: atoval[at]um.es ("[at]" replaces
"@", to prevent spam)
UML 2004 Workshop Chair
University of Murcia, Spain
|
|