International Symposium on Software Reliability Engineering
会议地点: Berlin, Germany
The annual International Symposium on Software Reliability Engineering (ISSRE) is focused on innovative techniques and tools for assessing, predicting, and improving the reliability, safety, and security of software products. ISSRE will be celebrating its 30th edition in Berlin, Germany, and will continue to emphasize scientific methods, industrial relevance, rigorous empirical validation and shared value of practical tools and experiences as paper selection criteria.
The research track at ISSRE 2019 is soliciting original, unpublished research papers in three categories: (1) full research regular (REG) papers, (2) practical experience reports (PER), and (3) tools and artifact (TAR) papers. Papers will be assessed with criteria appropriate to each category. ISSRE looks for original research exploring new scientific ideas, contributing new evidence to established research directions, or reflecting on practical experience.
Authors of the best REG papers accepted and presented at ISSRE will be encouraged to submit an extended version of their papers to a special section of the Information and Software Technology journal.
REG papers should describe a novel contribution to reliability of software systems. Extensions of reliability research into adaptive AI systems, blockchains and large sensor infrastructures are particularly welcome. Regardless of the domain, novelty should be argued via concrete evidence and appropriate positioning within the state of the art. REG papers are also expected to clearly explain validation process and its limitations.
PER are expected to provide an in-depth exposition of practical experiences and empirical studies collected through the application of known research tools and methods related to ISSRE topics. PER need to identify and discuss relevant lessons learned. The goal of PER is to offer evidence of reduced risk for future tech transition of the same or similar technology. ISSRE strongly encourages PERs that combine the efforts of researchers and industry practitioners.
TAR papers should describe a new tool or artifact. Tool-focused TAR papers must present either a new tool, a new tool component, or novel extensions to an existing tool. Tool-focused TAR papers should include a description of: 1) the theoretical foundations, 2) the design and implementation concerns, such as software architecture and core data structures, 3) experience with realistic case studies and observed advantages over similar tools. Making the tool publicly available is strongly encouraged to allow continued evaluation process. Artifact-focused TAR papers should cover 1) a working copy of a software and 2) experimental data sets.
Topics of interest include development, analysis methods and models throughout the software development lifecycle, and are not limited to:
Primary dependability attributes (i.e., security, safety, maintainability) impacting software reliability
Secondary dependability attributes (i.e., survivability, resilience, robustness) impacting software reliability
Reliability threats, i.e. faults (defects, bugs, etc.), errors, failures
Reliability means (fault prevention, fault removal, fault tolerance, fault forecasting)
Metrics, measurements and threat estimation for reliability prediction and the interplay with safety/security
Reliability of software services
Reliability of open source software
Reliability of Software as a Service (SaaS)
Reliability of software dealing with Big Data
Reliability of model-based and auto-generated software
Reliability of software within specific types of systems (e.g., autonomous and adaptive, green and sustainable, mobile systems)
Reliability of software within specific technological spaces (e.g., Internet of Things, Cloud, Semantic Web/Web 3.0, Virtualization, Blockchain)
Normative/regulatory/ethical spaces pertaining to software reliability
Societal aspects of software reliability