|
 Experience
Reports
Important
Dates | Goal | Scope| Evaluation | Submission
Publication / Presentation | Committee
Members | Contact Information
> Important Dates
| Submission |
1 September 2004 |
| Notification of Acceptance |
15 November 2004 |
| Camera-ready Copy Due |
28 January 2005 |
> Goal
The technical program of ICSE
2005 will include an Experience Reports Track. The objective of the track
is to establish a dialogue between software practitioners and software
engineering researchers on the benefits, obstacles, and weaknesses of applying
software engineering principles, techniques, methods, processes, and tools
in an industrial or organizational setting for embedded software systems,
high assurance software systems, and information systems.
^ Top
> Scope
Submissions are solicited which precisely identify
and discuss lessons learned and experiences of benefit to other researchers
and
practitioners. We invite four classes of original unpublished
submissions:
> Case Studies describe the application of a software engineering
technique, tool, or process in an industrial or organizational setting.
A case study provides the rationale for the key decisions made during
the development of a software or software-intensive product along with
the accomplished qualitative results.
> Experience Reports describe the history of a software project
accompanied by a critical review of experience with the software during
more or one development phases. An experience report describes lessons
learned from the experience.
> Experimental Reports In
contrast to an experience report and a case study, an experiment systematically
controls the influencing
factors and results in quantitative data about some aspect of software
development.
> Problem Statements describe problems encountered during the
development or use of software or a software-intensive system. A good
problem statement clearly describes the problem and includes a
discussion of why state-of-the-art principles, techniques, methods,
processes or tools are not able to solve the problem.
^ Top
> Evaluation
At least three members of the Experience Track
Program Committee will review each submission. The program committee as
a whole will meet to review and discuss the submissions and make final
acceptance decisions.
Submissions will be evaluated based on the
following criteria:
> Clarity
of the motivation for the work,
> Relevance of the object of the study,
> Validity of the study procedure,
> Significance of the lessons learned,
> The significance of the contribution,
the soundness of the rationale or demonstration, the quality of the
written presentation, and
a comparison with relevant research and other literature.
^ Top
> Submission
Papers should be submitted in PDF format.
The results described must be unpublished and should not be under review
elsewhere.
Submitted papers must conform to the ICSE 2005 proceedings publication
format and
should not exceed ten pages (including all text, figures, references and
appendices). The submission deadline is firm! If you are unable to submit
a paper electronically over the network, please contact one of the two
chairs at least two weeks prior to the submission deadline.
Submissions for this category are closed.
^ Top
> Publication
/ Presentation
All accepted papers will be allotted a maximum
of ten pages in the
conference proceedings and will be given a slot for formal oral
presentation.
^ Top
> Committee
Members
For the full
list of program committee members, click here.
^ Top
> Contact
Information
Constance Heitmeyer and Klaus Pohl at
e-mail address: ert-icse05@sse.uni-essen.de
^ Top
|
