交流群见文末
会议全称：International Symposium on Software Reliability Engineering
录用率：2021年27.51%
CCF分级：软件工程/系统软件/程序设计语言B
截稿时间：2024/5/3
录用通知时间：2024/7/26
官网链接：https://issre.github.io/2024/index.html
征稿范围：
Topics of Interest
Topics
of interest include development, analysis methods and models throughout
the software development lifecycle, and are not limited to:
-
Dependability
attributes (i.e., security, safety, maintainability, 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)
-
Software testing and formal methods
-
Software fault localization, debugging, root-cause analysis
-
Metrics, measurements and threat estimation for reliability prediction and the interplay with safety/security
-
Reliability of autonomous systems and (self-)adaptive systems
-
Reliability of AI-based systems, AI for Reliability Engineering
-
Reliability of Large Language/Foundational Model (LLM) and LLM for software reliability
-
Reliability of software services and Software as a Service (SaaS)
-
Reliability of model-based and auto-generated software
-
Reliability of open-source software
-
Reliability of software dealing with Big Data
-
Reliability of model-based and auto-generated software
-
Reliability of green and sustainable systems
-
Reliability of mobile systems
-
Reliability
of software within specific technological spaces (e.g., Internet of
Things, Cloud, Semantic Web/Web 3.0, Virtualization, Blockchain,
networks softwarization, 5G/6G, edge-to-cloud computing)
-
Normative/regulatory/ethical spaces about software reliability
-
Societal aspects of software reliability
Anonymizing Rules
Authors
shall anonymize their papers. As an author, you should not identify
yourself in the paper either explicitly or by implication (e.g., through
references or acknowledgements). However, only non-destructive
anonymization is required. For example, the names of case study subjects
may be left un-anonymized, if the subject name is important for a
reviewer to be able to evaluate the work. In that case, they should
avoid mentioning that a specific tool has been conceived and developed
by them, as well as a paper that has been co-authored by them. The
authors can provide the name of a case study subject software and the
name of the entity developing it (private company or foundations); in
case some of the authors are employees of the developing entity, the
authors should not explicitly mention their affiliation but clarify
potential threats to validity (e.g., familiarity with the subject), as
appropriate.
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.
