The 17th IEEE International Symposium on Software Reliability Engineering (ISSRE 2006)

7-10 November 2006 - Raleigh, North Carolina, USA



Detailed Track Information

Submission for select ISSRE 06 tracks is NOW OPEN!

Extended Submission Deadline: April 21 2006
Acceptance Notification: July 1 2006
Camera-Ready Copy Due: August 1 2006

Co-Chairs:
Amit Paradkar, IBM T.J.Watson Research Center (paradkar@us.ibm.com)
Carol Smidts, University of Maryland, College Park (csmidts@eng.umd.edu)

Submit to the Research Track!

Submissions are closed.
Submission Structure:
Your paper can be either twenty pages double-spaced or follow the IEEE Format and Submission Guidelines and not exceed ten pages (including all text, figures, references and appendices). The results described must be unpublished and should not be under review elsewhere.

Students are encouraged to submit papers to the regular track. Papers with a student as a first authors will automatically be considered for a travel award to present the paper at the conference

Accepted Papers:
Each accepted submission will be allotted a maximum of ten pages in the ISSRE 2006 conference proceedings. The final version of accepted papers must conform to the IEEE Format and Submission Guidelines.

Double Submission Policy:
Papers submitted at ISSRE may not be submitted in parallel to other conferences, symposia or workshops.

Research Papers - Regular

Goal:
The goal of ISSRE’s research track is to present the latest, best, and most important research results in the area of software reliability engineering and related fields such as software testing, software security, software safety and quality assurance.

Scope:
High quality research submissions are invited for technical papers describing original, unpublished results of theoretical, empirical, conceptual, or experimental research. Papers should describe a novel contribution to software reliability engineering and should carefully support claims of novelty with citations to the relevant literature. Papers emphasizing well documented case studies should be considered for the Experience Reports track.

Review and Evaluation Criteria:
Papers will be evaluated by the ISSRE Program committee with respect to the following criteria: novelty, significance, technical soundness and accuracy, relevance to ISSRE’s focus and readability.

Research Papers - Experience Reports

Goal:
The objective of the Experience Reports is to establish a meaningful dialog between software practitioners and software engineering researchers on the results (both good and bad), obstacles, and lessons learned associated with applying software development practices in various environments. The Experience Reports will provide accounts of the application of software engineering practices (which may be principles, techniques, tools, methods, processes, etc.) to a specific domain or to the development of a significant software system.

Scope:
Submissions are solicited which discuss lessons learned and experiences of benefit to researchers and practitioners. We invite original, unpublished submissions in the following categories:
  • Case studies of practices describe the application of one or more software engineering practice(s) in an industrial or organizational setting. A case study provides a detailed description of how the practice was applied and why (what problems it was intended to address), along with the results achieved.
  • Experience reports of projects provide a critical review of experiences during one or more phases of a software development project, and draw lessons learned from that experience. A good experience report describes as completely as possible the factors that influenced those experiences and reports the final results as rigorously as possible, so that the impact of those experiences on project success or failure can be understood. Experience reports may focus on problems encountered during development along with discussions of what principles, techniques, methods, processes, or tools were used and whether they were sufficient for solving the problem.
Review and Evaluation Criteria:
Each submission will be reviewed by at least three members of the Experience Track program committee. The program committee as a whole will make final decisions about which submissions to accept for presentation at the conference.
Submissions will be evaluated based on the following criteria:
  • Clarity of the motivation for the report
  • Soundness of the report, which should include:
    1. A description of the context in which the experiences were observed (e.g. problem domain, size of system, size of project team, etc.);
    2. A clear demonstration that the experiences and lessons described are based on observation and analysis, rather than opinion;
    3. Measurement as accurately as possible of important phenomena rather than unsupported estimates.
  • Significance and relevance of the lessons learned;
  • Quality and clarity of the written presentation.
A well-structured experience report will not only describe in appropriate detail the experiences encountered on a software project, but will include rationales for any lessons learned put forward and describe clearly the circumstances under which those lessons held.

Extended Submission Deadline: August 31 2006
Acceptance Notification: September 1 2006
Final Presentations and Panelist Statements Due: October 1 2006

Submit to the Government Track!

Submissions are closed.
Co-Chairs:
Lisa Montgomery, NASA, USA (Lisa.P.Montgomery@nasa.gov)
Carol Smidts, University of Maryland, College Park (csmidts@eng.umd.edu)

Goal:
The goal of the Government Track Program is to increase the synergy between government agencies, software engineers, and the research community in the domain of software reliability engineering, especially as it pertains to government high assurance development efforts. The objectives are to identify and discuss:
  • What software reliability engineering means.
  • The current challenges of establishing a comprehensive software reliability engineering program given the challenges inherent to government development efforts.
  • The anticipated needs for employing software reliability engineering in the future.
The scope of this track is focused on software reliability engineering as it relates to government projects that are of the highest criticality and demand the highest reliability. Its objectives strive to establish what it means to have a software reliability engineering program as well as what the current and future challenges are going to be.

There are two components of the Government Practice program: individual presentations and panel discussions.

Individual Presentations:
We seek submissions of one page abstract on the expected relevant topics in technology, tools and practices related to software testing, reliability, safety, security, availability, and dependability from the perspective of doing, managing, monitoring, or verifying government sponsored development. 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;
  • outstanding issues that need resolution.
Though not restricted solely to government employees, our preference is to hear from authors representing a variety of perspectives from government agencies whose focus is on high reliability software.

The abstracts will be reviewed by the Government Program Committee and the selected authors will have a chance to present a talk (20 to 25 minutes) at the ISSRE 2006 conference. There is no need to write a paper and the authors only need to submit a presentation (Microsoft Powerpoint or PDF format) for publication in the conference proceedings. The maximum number of slides in the presentation is 20. Each accepted submission will be allotted a maximum of ten pages (two slides per page) in the ISSRE 2006 Supplemental conference 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.

Government Relevant Panels:
We seek submissions of proposals for panels on topics relevant to the challenges associated with critical software development activities in and for government.

Some examples of potential topics are: Reliability implications of Embedded Software, COTS, and reliability of SW development tools and models. The proposal must contain:
  • Name and address of the author of the proposal;
  • Title of the panel and an explanation of the relevant area;
  • Names of participants (with one moderator) and their qualifications;
  • Five key questions that will be addressed by the panel.
The proposals will be reviewed by the Government Program Committee and the selected panels will have 60 to 90 minutes at the ISSRE 2006 conference. There is no need to write a paper. The panelists need to submit a page (Microsoft Word or PDF format) for publication in the conference proceedings.

Submission Deadline: May 15 2006

Submit a Workshop Proposal!

Submissions are closed.
Co-Chairs:
Swapna Gokhale, U. of Connecticut, USA (ssg@engr.uconn.edu)
Veena B. Mendiratta, Bell Labs, Lucent Technologies, USA
Mikhail Auguston (A-MOST), NPS, USA

We are soliciting workshop proposals from the community. A workshop proposal submission should not exceed 3-4 pages and will consist of the following details:
  • Title of the workshop;
  • Theme, objectives and main challenges of the workshop;
  • Number of participants, how they will be solicited and selected;
  • Pre-workshop activities;
  • Activities during the workshop;
  • Length of time and required rooms;
  • Expected outcomes of the workshop;
  • Organizer’s background and experience with workshops;
  • Previous context/history of the workshop (if any).

Submission Deadline: May 15 2006

Submit a Tutorial Proposal!

Submissions are closed.
Co-Chairs:
Swapna Gokhale, U. of Connecticut, USA (ssg@engr.uconn.edu)
Veena B. Mendiratta, Bell Labs, Lucent Technologies, USA
Mikhail Auguston (A-MOST), NPS, USA

Objectives:
The objectives of tutorials presented at ISSRE are to expose the attendees to the theory, tools and techniques and state-of-the-art in SRE. The tutorials draw a healthy mix of participants, from the industry, academia and government agencies.

Scope:
We solicit tutorial proposals on current topics that will draw significant interest from a large number of attendees. A tutorial proposal should consist of the following:
  • Title;
  • Objectives;
  • Names of speaker(s);
  • Length of the tutorial (half day/full day);
  • Bio data of speaker(s), including contact information;
  • Prior history at ISSRE (if any);
  • A short position paper (or a list of burning issues);
  • Outline of tutorial contents;
  • Representative slides;
  • Activities to be carried out in the tutorial;
  • Audience level (basic, intermediate, advanced);
  • Expected background knowledge.
Review and evaluation criteria:
Each tutorial proposal will be reviewed by the program committee and evaluated based on the following criteria: relevance and timeliness of the topic to ISSRE, interest to the ISSRE attendees, and past experience and qualifications of the instructors.

Submission Deadline: May 15 2006

Submit a Panel Proposal!

Submissions are closed.
Contact Swapna Gokhale (ssg@engr.uconn.edu) for more information.




Submission Deadline: July 7, 2006
Acceptance Notification: September 1 2006
Final Presentations and Panelest Statements Due: October 1 2006

Submit to the Industry Track!

Submissions are closed.
Industry Practice Co-Chairs:
Brendan Murphy, Microsoft, UK (bmurphy@microsoft.com)
Steve Kan, IBM, USA (skan@us.ibm.com)
Mod Marathe, Cisco Systems, USA (mmarathe@cisco.com)

Goal:
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.

There are two components of the Industry Practice program: individual presentations and panel discussions.

Individual Presentations:
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. 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 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 2005 conference . There is no need to write a paper and the authors only need to submit a presentation (Microsoft 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 2006 conference 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 Relevant Panels:
We seek submissions of proposals for panels that will be interesting to the industry and academic participants alike on topics relevant to today's fast moving software industry. Some examples of the topics are: Reliability implications of Embedded Software, Packaged Applications, Extreme Programming, Internet security, Testing and Reliability of Network based Software Services, etc. The proposal must contain:
  • Name and address of the author of the proposal;
  • Title of the panel and an explanation of the relevant area;
  • Names of participants (with one moderator) and their qualifications;
  • Five key questions that will be addressed by the panel.
The proposals will be reviewed by the Industry Program Committee and the selected panels will have 60 to 90 minutes at the ISSRE 2005 conference. There is no need to write a paper. The panelists need to submit a page (Microsoft Word or PDF format) for publication in the conference proceedings.

Extended Submission Deadline: August 11 2006
Acceptance Notification: September 15 2006
Camera-Ready Copy Due: October 1 2006

Submit a Fast Abstract!

Submissions are closed.
Chair:
Sudipto Ghosh, Colorado State U., USA (ghosh@cs.colostate.edu)

Goal:
A Fast Abstract is a lightly reviewed, two-page technical article that requires a short talk at the conference. The goal is to promote current work, research, practices, opinions, experiences, and issues. This is an early communication of technical work and does not always require completed results like that of a journal publication. Authors can introduce new ideas to the community or state positions on controversial issues. The history and the genesis of Fast Abstracts and past archives can be found at http://www.chillarege.com/fastabstracts.

Fast Abstracts are an integral and important part of ISSRE. Accepted contributions will be published in the Supplementary Proceedings of the 17th International Symposium on Software Reliability Engineering and authors will present a short talk at the symposium. Fast Abstracts sessions have been among the most attended in past ISSRE editions, with contributors as diverse as young students and distinguished members of the community.

Scope:
Authors should explain the contribution to the field and the novelty of the work, making clear the current status of the work. Topics of interest include, but are not limited to:
Reliable model-driven engineering Software test effectiveness
Testable model-driven engineering Analysis and prevention of virus attacks
Network system reliability Fault-tolerant and robust software
Network system security Dependable Web services
Internet reliability engineering Survivability of large systems
Software reliability models Electronic commerce reliability
Software architecture reliability Empirical studies and metrics
Secure software engineering Tools and automation
Reliability measurement Reliable adaptive and autonomous systems
QoS of distributed systems Formal reliability assurance methods
Software testing and verification Software safety analysis
Reliability and performance of mobile systems

Review and Evaluation Criteria:
Each submission will be lightly reviewed by two to three members of the program committee. The program committee as a whole will make final decisions about which submissions to accept for presentation at the conference. Submissions will be evaluated based on the technical merit, relevance, and significance.

Submission Structure:
Your paper must conform to the IEEE Format and Submission Guidelines and should not exceed two pages (including all text, figures, references and appendices). The results described must be unpublished and should not be under review elsewhere. Each accepted submission will be allotted a maximum of two pages in the ISSRE 2006 supplementary proceedings and must be presented by one of the authors. The final version of accepted papers must conform to the IEEE Format and Submission Guidelines.

Extended Submission Deadline: August 11 2006
Acceptance Notification: September 10 2006
Extended Camera-Ready Copy Due Deadline: October 6 2006

Submit to the Student Program!

Submissions are closed.
Chair:
Katerina Goseva-Popstojanova, West Virginia U., USA (katerina@csee.wvu.edu)

Goal:
The goal of the Student papers program is to encourage students to attend ISSRE and present their work, exchange ideas with researchers and practitioners, and get early feedback on their research efforts.

This years Student paper program will continue the successful tradition, started in 1999, of awarding student travel grants. To date, the program allowed over 80 students from degree granting institutions to attend ISSRE, and has become one of the most popular features of the symposium. The student travel awards are made possible by generous support from industry sponsors.

Many thanks to our ISSRE 2006 sponsors!


Scope:
We invite original papers reporting research and practical results related to reliability, availability and dependability of software and software-based systems. For detailed list of topics authors are referred to the ISSRE 2006 Call for Papers. Student papers are short technical articles that promote early communication of technical work and allow students to report on work in progress and introduce new ideas to the community.

Review and Evaluation Criteria:
Student papers will be reviewed by the members of the Student paper Program Committee. The selection will be based on the following criteria:
  1. Relevance to the technical content of the conference;
  2. Originality;
  3. Technical soundness;
  4. Quality and clarity of the written presentation.
Submission Structure:
Student papers should not exceed 4 single-column one-and-half spaced pages (including all text, figures, and references). If the two-column camera-ready IEEE format is used, the student paper should not exceed 2 pages. Submissions must be unpublished and must not be submitted for publication elsewhere (including papers submitted to ISSRE 2006). The student must be the first author of the paper. The papers must be submitted electronically, through ISSRE submission page, either in PDF or postscript format.

All degree candidates are eligible for student paper submission, but only full time students will be considered for travel awards which will cover student registration and travel expenses up to specified limits.

Accepted Papers:
Each accepted student paper will be allotted a maximum of two pages in the ISSRE 2006 supplemental conference proceedings. The final version of accepted papers must conform to the IEEE Format and Submission Guidelines. Each accepted student paper will be awarded one student travel grant. The recipients of the student travel grants will be required to present their work in a short talk and as a poster during the conference. Further details will be provided upon the acceptance of the student paper.

Last modified: October 18 2006 15:44:35.