Important Dates

Paper Submissions can be in the form of regular papers, experience reports, industry practice abstracts, panel proposals, tutorial proposals, and tools fair proposals. Topics of interest include, but are not limited to:

• Methods of developing reliable software, including management methods and rigorous specification, design, and implementation techniques
• Data collection and analysis for software reliability assessment
• Software reliability models
• Testing and verification for software reliability measurement
• Software safety
• Fault-tolerant and robust software
• SRE tools, education, and technology transfer methods
• Software reliability standards and legal issues
• Building high-integrity mobile code systems
• The problems associated with embedding COTS software into business-critical, enterprise-critical, and safety-critical systems
• Security issues related to Web-based systems

Regular Papers should not exceed 20 pages, including figures and text (typed with 1.5 spacing and 12 point font). Papers published, accepted for publication, or submitted elsewhere are not eligible and will be rejected without review. The cover page must include (1) the title, (2) the names, complete mailing addresses, e-mail, telephone, and fax numbers of all authors, (3) the name of the contact author, (4) an abstract not exceeding 250 words, and (5) a list of around 5 keywords. The first page of the paper should have the paper title and the beginning text of the document. If the paper is accepted, one of the authors is expected to pre-register for the symposium and present the paper at ISSRE99.

Experience Reports are intended to provide exposure to practical experiences with the application and conduct of software reliability engineering methods, models, and tools. The contributors should submit an abstract and a 5-10 page description of the experience or case study, and a one page summary of the project for a short presentation at the conference. The paper should be clearly identified as an experience report.

Please submit an abstract (250 words maximum in plain ASCII text) and a list of keywords to the Program Chair

J. Voas: jmvoas@rstcorp.com

before March 1, 1999 to enable proper referee assignment.

Six hardcopies of the complete papers and experience reports should be submitted to the Program Chair by April 12, 1999. All the accepted papers and experience reports will be published in the conference proceedings.

Industry Practice Abstracts: Submit an abstract (250 words maximum) to one of the Industry Track Chairs by June 1, 1999.

Panel Proposals should include the title, proposed chair, proposed panelists (include short vitae), two or three paragraphs describing the panel subject matter and the rationale for it. Panelists must have agreed to participate prior to the submission of the panel proposal. Six hard copies of panel proposals should be submitted to the Industry Practices Chair by April 1, 1999.

Tutorial Proposals: Both full-day and half-day tutorial proposals should be submitted to one of the Tutorials Chairs by April 12, 1999.

Tools Fair Proposals should include a description of the software product to be demonstrated and the relevance of the product to the field of software reliability engineering. Tools fair proposals should be submitted to one of the Tools Fair Chairs by April 12, 1999.

Regular Papers

• Abstract Deadline: March 1, 1999;
• Submission: April 12, 1999;
• Acceptance Notification: July 7, 1999;
• Camera-Ready Due: August 17, 1999

• Industry Track Abstracts: June 1, 1999;
• Panel Proposals: April 12, 1999

Tools and Exhibition Proposals: June 1, 1999

Invitations begin to arrive: June 10, 1999

Advanced program poster: July 16, 1999

Final program poster: September 17, 1999

Conference proceedings sent to the printer: Oct 1, 1999