Software Correctness Technology

  in Special Issue   Posted on December 8, 2020

Information for the Special Issue

Submission Deadline: Thu 11 Mar 2021
Journal Impact Factor : 3.700
Journal Name : IT Professional
Journal Publisher:
Website for the Special Issue: https://www.computer.org/digital-library/magazines/it/call-for-papers-special-issue-on-software-correctness-technology
Journal & Submission Website: https://www.computer.org/csdl/magazine/it

Special Issue Call for Papers:

Guest editors

* Markus Schordan (Lawrence Livermore National Laboratory, CA, USA)
* Ignacio Laguna (Lawrence Livermore National Laboratory, CA, USA)
* Cindy Rubio-González (UC Davis, CA, USA)

Please direct any correspondence before submission to the guest editors at it5-2021@computer.org.

Aims and Scope:
It has been said that software is “eating the world.” Many of today’s major companies are built entirely around information systems. More and more, systems are controlled by software and rely on correct operation of software. It has enabled us to make the most intricate machines that have ever existed. In today’s world, with its increasing number of autonomous systems, services, and devices, correctness of software definitely cannot be an afterthought. Ensuring correctness in software has become the major challenge in software engineering.

This special issue of IT Professional seeks to provide readers with an overview and applications of modern software technology to establish and ensure correctness in software and its potential applications in government, business, healthcare, and commercial products and services. We seek high-quality contributions from academia, business, industry, and government that present recent advances in software technology for engineering software with correctness guarantees. Visionary papers describing futuristic applications are also welcome.

Topics of interest include, but are not limited to, the following:
* Certifying the correctness of software
* Model checking
* Program analysis
* Proof carrying code
* Compiler correctness
* Validating static analysis reports
* Metrics to measure the degree of correctness of software
* Specifications to check the correctness of runtime systems
* Vulnerability assessment for code
* Secure code analysis
* Fuzz testing
* Concolic testing
* Automated bug triage
* Automated input minimization (test case reduction)
* Large databases of bug reports and/or reproducible test cases
* Benchmarks to test the effectiveness of correctness tools
* Artificial intelligence techniques (e.g. machine learning) for anomaly detection
* Formal verification techniques applied to real-world production systems
* Scalable tools for model checking, verification, certification, or symbolic execution
* Scalable debugging solutions for large-scale applications
* Approaches for the specification of algorithms with the goal of correctness checking

Important Dates:
Opens for submissions: August 1, 2020
Deadline for paper submission: March 11, 2021
Notification of results: May 13, 2021
Deadline for revisions: June 17, 2021
Final acceptance: July 22, 2021
Publication: September/October Issue 2021

Submission Guidelines:
Only submissions that describe previously unpublished, original, state-of-the-art research and that are not currently under review by a conference or another journal will be considered. Extended versions of conference papers must be at least 30 percent different from the original conference works. Feature articles should be no longer than 4,200 words and have no more than 20 references (with tables and figures counting as 300 words each). For author guidelines, see our peer review page. All manuscripts must be submitted to ScholarOne Manuscripts by the deadline in order to be considered. Submissions are subject to peer review on both technical merit and relevance to IT Pro’s readership. Articles should be understandable by a broad audience of computer science and engineering professionals, avoiding unnecessary theory, mathematics, jargon, or abstract concepts. Figures and tables should be placed in the appropriate location within the template, ideally in files that are 300 dpi or higher using the dimensions defined in the document template.

Closed Special Issues