Call for Participation: Technical Papers - Research and Experience

Dates
Note: All deadlines are 11:59PM (Apia Time) on the dates indicated. All submission deadlines are firm!

Check your local submissions deadline with the World Clock.

22nd September 2003 - deadline for submission of abstract and full paper
15th December 2003 - notification of acceptance
2nd February 2004 - submission of final copy of accepted paper for proceedings

Goal

Technical papers should describe innovative and significant work in the research and practice of software engineering. We welcome both research papers and experience reports. Research papers should describe a novel contribution to software engineering and should carefully support claims of novelty with citations to the relevant literature. Experience papers should describe a significant experience in applying software engineering technology and should carefully identify and discuss important lessons learned so that other researchers and/or practitioners can benefit from the experience. Papers will be collected in an archival, refereed conference proceedings, published by IEEE/ACM, whose literature is cited and read by researchers and practitioners worldwide.

While there will not be a separate Education and Training track at ICSE 2004, authors are strongly encouraged to submit papers on education and training to the main track of technical papers. Past experience with education and training papers suggests that most such submissions should be designated as "experience" papers in the submission form used on the submission Web site.

Scope

The software engineering community broadly consists of researchers and practitioners from many different disciplines and intellectual traditions, and has strong ties with other related scientific communities (including programming languages, distributed systems, databases, and networks). Technical papers report on a full range of topics relevant to this community, including software engineering principles, theories, techniques, tools, and empirical evaluations.

Review Process

At least three members of the program committee will review each submitted paper, and the program committee as a whole will meet to review and discuss the recommendations made by the reviewers and to make final decisions of which papers to accept for the conference. Papers will be evaluated on the basis of originality, significance of contribution, soundness of rationale or demonstration, quality of written and graphical presentation, and appropriate comparison of results to relevant research and literature.

How to Submit

In brief, you must follow the following steps to submit a paper.

Your paper must conform to the proceedings publication format and may be no longer than ten pages, including all text, references, appendices, and figures. Your submissions should be in PDF format. If you are unable to submit in PDF format, contact the address below. You will also separately enter an abstract, keywords, author information, and contact information at the time you upload your PDF file.

You should submit your completed technical paper here

Accepted Papers

Each accepted technical paper will be given up to ten pages in the conference proceedings. The final version of accepted papers must conform to the proceedings publication format.

Contact

For more information about technical papers, contact one or both Program Co-Chairs:

Jacky Estublier (Jacky.Estublier@imag.fr)
David S. Rosenblum (dsrosenblum@stanfordalumni.org)