Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: 13th System Design Language Forum - Extended CFP

13th System Design Language Forum - Extended CFP 27 Apr 2007 16:40 #7095

Note: This email is being set to several lists,
so you may receive it multiple times.

It has come to the attention of the Programme Committee for this event
that the previous short title (SDL2007) gave the wrong impression that
the event is concerned only with the ITU Specification and Description
Language. In fact the invite was to submit papers on topics related to
System Design Languages in general that are or could be used for real
time systems, such as Telecommunications. This is a broader scope.

Fortunately since issuing the original call for papers, the timescale
for producing the proceedings for the event have become much clearer,
and it is now possible to extend the call for papers. You are encouraged
to read the revised call for papers with the scope 'System Design
Languages' in mind and consider submitting any suitable papers by 15th
May 2007.

Authors need to be available between 16th June and 30th June for
revision of their papers and submission of final versions. As the
deadline has been extended, the many authors who have already submitted
papers are allowed to revise their submissions up to 15th May 2007.

While preference will be given to full papers, short papers
(particularly experience reports) will be considered.

Experience reports are inherently different from research papers, with
respect the criteria of scientific merit, novelty, and research
contribution. The main criteria is to share experience for the benefit
of others. For example to provide citable evidence of the effectiveness
(positive of negative) of particular approaches, or particular effective
techniques or obstacles in practice when applying a language or set of
languages. Anecdotal evidence is acceptable provided if well argued and
the author explains efforts made to gather evidence. Material should
contain comparisons and measurements of effectiveness wherever possible.
A report that simply states that System Z was successfully developed
using technique Y is a little use to others. A useful report would be
something like: the technique Y was used (in this case on the real
example System Z) and to be able to meet the requirements it was
necessary to "..." otherwise "...", or "..." was particularly
effective/ineffective because "...". Other do not want to know all the
details of your project and its implementation, but what helped or
hindered the engineering that might be relevant to their own projects,
in particular unusual aspects of the project. It is suggested the title
starts with the words `Experience Report'.

The extended call for papers is attached and can be found as a pdf file
at www.pragmadev.com/news/Extended_SDL07_CfP.pdf or at
www.pragmadev.com/sdl07/index.html



--
======================================================================
Prof. Dr. Jens Grabowski
Institute for Informatics phone: +49 551 39 14690
University of Goettingen fax: +49 551 39 14415
Lotzestrasse 16-18
DE-37083 Göttingen This email address is being protected from spambots. You need JavaScript enabled to view it.
(Germany) www.swe.informatik.uni-goettingen.de
======================================================================
Attachments:
The administrator has disabled public write access.
  • Page:
  • 1

FacebookTwitterGoogle BookmarksRedditNewsvineTechnoratiLinkedin