Industry Practices Submission: July 25, 2009 September 1, 2009
Acceptance Notification: August 15, 2009 September 23, 2009;
Camera Ready Copy: October 1, 2009

SUBMIT PAPERS HERE

Note: We are extending the deadline for submission to September 1 to accomodate the Europe vacation period. However, papers submitted by the original date of July 25th, will be processed early. Given the later deadline, please submit both the abstract and the presentation by September 1, 2009, to shorten the feedback loop.

We seek submissions of one page abstract by authors in the software reliability community on industry relevant topics in technology, tools and practices related to software testing, reliability, safety, security, availability, and dependability. In addition to the one page abstract, we would like to receive most of the slide presentation that is planned.
Typically this will contain:

• a problem definition and its importance
• any potential solution tried to address the problem
• analysis of the results of applying the solution to the problem

The objective of the Industry Practice program is to establish a meaningful dialog among software practitioners and with software engineering researchers on the results (both good and bad), obstacles, and lessons learned associated with applying software development practices in various environments. The Industry Practice presentations will provide accounts of the application of software engineering practices (which may be principles, techniques, tools, methods, processes, testing techniques etc.) to a specific domain or to the development of a significant software system. In particular, we are interested in software development techniques that prevent bugs or detect bugs early during development in addition to various downstream bug metrics and reliability growth curves etc. We would like the Industry presentations to be of interest to software development professionals as well as software quality groups.

We list a few areas that are of current interest as suggestions for Case studies

Development:

Software failure mode analysis, SW defect prediction, use of techniques such as (static analysis, code reviews, unit testing), defect classification and root cause analysis, remedies based on root cause, effectiveness of remedies, reliability of SW produced using various development methodologies like waterfall, agile, extreme etc.

Metrics:

Defect density, different kinds of bugs per KLOC, reliability improvement achieved with different development and test techniques, measured availability, user perception studies

Testing:

Test automation, log file analysis, test platforms, automatic test case generation, code coverage, prioritization and targeting of tests, estimating remaining defects and when to stop testing, HW and SW fault insertion testing, techniques for performance testing,

Safety and Security:

Attack surface measurement, source code or binary static analysis for security, fuzzing tests, Safety considerations and proofs of safe operation.

Review Process

The abstracts will be reviewed by the Industry Program Committee and the selected authors will have a chance to present a talk (20 to 30 minutes) at the ISSRE 2009 conference. There is no need to write a paper and the authors only need to submit a presentation (PowerPoint or PDF format) for publication in the conference proceedings. The maximum number of slides in the presentation is 20 pages. Each accepted submission will be allotted a maximum of ten pages (two slides per page) in the ISSRE 2009 supplemental proceedings. For those authors who would like to submit a paper for the conference proceedings, they have the option to do so when their abstract is accepted. The final version of accepted papers must conform to the IEEE Format and Submission Guidelines.

Industry Practices First Draft Presentations due: August 15, 2009 (for those that submitted by July 25th).

Industry Practices Final Presentations due: September 1, 2009 (for those that submitted by July 25th).

Example Papers
Please look at some of the examples from past years. These give one an idea of the type of contribution that is desired - depth, length, and format.

ISSRE 2006 Supplemental Proceedings

The objective of the Industry Practice program is to establish a meaningful dialog among software practitioners and with software engineering researchers on the results (both good and bad), obstacles, and lessons learned associated with applying software development practices in various environments. The Industry Practice presentations will provide accounts of the application of software engineering practices (which may be principles, techniques, tools, methods, processes, testing techniques etc.) to a specific domain or to the development of a significant software system. In particular, we are interested in software development techniques that prevent bugs or detect bugs early during development in addition to various downstream bug metrics and reliability growth curves etc. We would like the Industry presentations to be of interest to software development professionals as well as software quality groups.

We list a few areas that are of current interest as suggestions for Case studies

Development:

Software failure mode analysis, SW defect prediction, use of techniques such as (static analysis, code reviews, unit testing), defect classification and root cause analysis, remedies based on root cause, effectiveness of remedies, reliability of SW produced using various development methodologies like waterfall, agile, extreme etc.

Metrics:

Defect density, different kinds of bugs per KLOC, reliability improvement achieved with different development and test techniques, measured availability, user perception studies

Testing:

Test automation, log file analysis, test platforms, automatic test case generation, code coverage, prioritization and targeting of tests, estimating remaining defects and when to stop testing, HW and SW fault insertion testing, techniques for performance testing,

Safety and Security:

Attack surface measurement, source code or binary static analysis for security, fuzzing tests, Safety considerations and proofs of safe operation.

Review Process

The abstracts will be reviewed by the Industry Program Committee and the selected authors will have a chance to present a talk (20 to 30 minutes) at the ISSRE 2009 conference. There is no need to write a paper and the authors only need to submit a presentation (PowerPoint or PDF format) for publication in the conference proceedings. The maximum number of slides in the presentation is 20 pages. Each accepted submission will be allotted a maximum of ten pages (two slides per page) in the ISSRE 2009 supplemental proceedings. For those authors who would like to submit a paper for the conference proceedings, they have the option to do so when their abstract is accepted. The final version of accepted papers must conform to the IEEE Format and Submission Guidelines.

Industry Practices First Draft Presentations due: August 15, 2009 TBD

Industry Practices Final Presentations due: September 1, 2009 TBD

Example Papers
Please look at some of the examples from past years. These give one an idea of the type of contribution that is desired - depth, length, and format.

ISSRE 2006 Supplemental Proceedings