Calls for Contribution > Submission

Paper Categories

Submissions can be made in one of the following categories (authors are required to indicate the category as part of the title):

• Regular papers (max. 12 page submission; 12 pages in proceedings): full paper describing a research contribution to dependable computing, including experimental work focused on implementation and evaluation of existing dependability techniques.
• Practical experience reports (max. 8 page submission; 8 pages in proceedings): a short paper describing practitioner experiences or lessons learned applying tools and techniques to real-world problems.
• Tool descriptions/demonstrations (max. 8 page submission; 8 pages in proceedings): descriptions of the architecture, implementation and usage of substantive tools to aid the research and practice of dependability.

The number of pages indicated above includes everything: title page, text, references, figures, appendices, etc.

Please contact the program chairs in case you have any questions concerning to which category your paper should be submitted.

Paper Submissions

Papers are submitted via the submission website.

The program committee will perform double-blind reviewing of all submissions, with limited use of outside referees. Papers will be held in full confidence during the reviewing process, but papers accompanied by nondisclosure agreement forms are not acceptable and will be rejected without review.

Authors must anonymize their submissions (see below for guidelines). Submissions violating the formatting andanonymization rules will be rejected without review. There will be no extensions for reformatting.

Formatting Rules

Submissions must adhere to the IEEE Computer Society camera-ready 8.5″x11″ two-column camera-ready format (using a 10-point font on 12-point single-spaced leading). The templates are reproduced below for your convenience, and further details can be found here.

• LaTex Package (use bare_conf.tex) (ZIP) (TAR.GZ)
• Word Template (DOC)

Each paper must be submitted as a single Portable Document Format (PDF) file. All fonts must be embedded. We also strongly recommend you print the file and review it for integrity (fonts, symbols, equations etc.) before submitting it. A defective printing of your paper can undermine its chance of success. Please take a note of the following:

• Submissions should be anonymous.
• The first page must include the title of the paper, the type of the paper (Regular / Practical Experience / Tool), and a maximum 150-word abstract. The first page is not a separate page, but is a part of the paper (and thus has technical material in it). Thus, this page counts toward the total page budget for the paper.
• The page limit includes everything: references, title page, figures, appendices, etc.
• Pages should be numbered.
• The use of color for figures and graphs is encouraged, but the paper should be easily readable if printed in grayscale.
• Symbols and labels used in the graphs should be readable as printed, without requiring on-screen magnification.
• Try to limit the file size to less than 15 MB.

Authors of accepted papers will be expected to supply electronic versions of their papers and are encouraged to supply source code and raw data to help others replicate and better understand their results.

Anonymizing Rules

Authors must make a good faith effort to anonymize their paper. As an author, you should not identify yourself in the paper either explicitly or by implication (e.g., through the references or acknowledgments). However, only non-destructive anonymization is required. For example, system names may be left un-anonymized, if the system name is important for a reviewer to be able to evaluate the work. For example, a paper on experiences with the design of .NET should not be re-written to be about “an anonymous but widely used commercial distributed systems platform.”

Additionally, please take the following steps when preparing your submission:

• Remove authors’ names and affiliations from the title page
• Remove acknowledgement of identifying names and funding sources
• Use care in naming your files. Source file names, e.g., Joe.Smith.dvi, are often embedded in the final output as readily accessible comments.
• Use care in referring to related work, particularly your own. Do not omit references to provide anonymity, as this leaves the reviewer unable to grasp the context. Instead, a good solution is to reference your past work in the third person, just as you would any other piece of related work.
• If you have a concurrent submission, reference it as follows: “Closely related work describes a microkernel implementation [Anonymous 2014].” with the corresponding citation: “[Anonymous 2014] Under submission. Details omitted for double-blind reviewing.”
• If you cite anonymous work, you must also send the deanonymized reference(s) to the PC chair in a separate email.

Submissions that do not conform to the above submission deadline, anonymization and formatting guidelines (e.g., are too long, use fonts or line spacing smaller than what is indicated above) or are unoriginal, previously published, or under submission to multiple venues, will be disregarded.

Review Process and Author Response

Authors will have the opportunity to correct, during the rebuttal period, factual inaccuracies in the reviews. After the papers have been reviewed, but prior to the Program Committee meeting, the reviews will be made available to the authors to provide a forum for responding to any factual errors in the reviews. Please note that this is NOT a forum to add any additional information on the paper, to submit an updated or revised paper, or to list changes the authors promise to include in the final version. Author responses will be made available to all PC members before the paper is discussed for selection in the PC meeting. The submissions website will contain full author-response guidelines.