posted by user: versager || 2237 views || tracked by 14 users: [display]

SANER 2019 : IEEE International Conference on Software Analysis, Evolution and Reengineering

FacebookTwitterLinkedInGoogle

Link: https://saner2019.github.io/cfp/ResearchTrackCFP.html
 
When Feb 24, 2019 - Feb 27, 2019
Where Zhejiang University in Hangzhou
Abstract Registration Due Oct 12, 2018
Submission Deadline Oct 19, 2018
Notification Due Nov 30, 2018
Final Version Due Dec 21, 2018
 

Call For Papers

Research Track - Call for Papers
The SANER 2019 technical track invites high quality submissions of papers describing original and unpublished research results. We encourage submissions describing various types of research, such as, empirical, theoretical, tool-oriented, etc.

The topics of the submissions should be of direct interest to the software analysis, evolution, and reengineering community. Topics of interest include, but are not limited to:

Software Analysis, Parsing, and Fact Extraction
Software Reverse Engineering and Reengineering
Program Comprehension
Software Evolution Analysis
Software Architecture Recovery and Reverse Architecting
Program Transformation and Refactoring
Mining Software Repositories and Software Analytics
Software Visualization
Software Reconstruction and Migration
Software Maintenance and Evolution
Program Repair
Software Release Engineering, Continuous Integration and Delivery
Education related to all of the above topics
Legal aspects

Evaluation Criteria
Submissions will be evaluated by at least three program committee members. The evaluation will focus on the novelty, originality, importance to the field, proper use of research methods, and presentation of the submissions. We strongly encourage authors to make available all data and software they use in their work, in order to allow for verification and replication of their results.


Submission Instructions
Submitted papers must have been neither previously accepted for publication nor concurrently submitted for review in another journal, book, conference, or workshop.

All submissions must come in PDF format and conform, at time of submission, to the IEEE Conference Proceedings Formatting Guidelines(title in 24pt font and full text in 10pt font, LaTEX users must use \documentclass[10pt,conference]{IEEEtran} without including the compsoc or compsocconf option. Also, papers must comply with the IEEE Policy on Authorship.

All submissions must be in English. Submissions should not exceed 12 pages (the last 2 pages can be used for references only), and should be uploaded electronically in PDF format via EasyChair. Submissions that do not adhere to these limits or that violate the formatting guidelines will be desk-rejected without review.

Important note: SANER 2019 follows a full double-blind review process. In order to be compliant with the double-blind policy, submitted papers must adhere to the following rules (largely reused from SANER 2018 double-blind instructions):

Author names and affiliations must be omitted.

References to authors' own related work must be in the third person. (For example, not "We build on our previous work..." but rather "We build on the work of...")

There may be cases in which the current submission is clear follow up of one of your previous work, and despite what recommended in the previous point, reviewers will clearly associate authorship of such a previous work to the current submission. In this case, you may decide to anonymize the reference itself at submission time. For example: "based on previous results [10]" .. where the reference is reported as "[10] Anonymous Authors. Omitted per double blind reviewing." In doing so, however, please make sure that the Saner 2019 submission is self-contained and its content can be reviewed and understood without accessing the previous paper.

Do not include acknowledgements of people, grants, organizations, etc. that would give away your identity. You may, of course, add these acknowledgements in the camera-ready version.

If you use an identifiable naming convention for your work, such as a project name, use a different name for your submission, which you may indicate has been changed for the purposes of double-blind reviewing. This includes names that may unblind individual authors and their institutions. For example, if your project is called GoogleDeveloperHelper, which makes it clear the work was done at Google, for the submission version, use the name DeveloperHelper or BigCompanyDeveloperHelper instead.

Avoid revealing the institution affiliations of authors or at which the work was performed. For example, if the evaluation includes a user study conducted with undergraduates from the CS 101 class that you teach, you might say "The study participants consist of 200 students in an introductory CS course." You can of course add the institutional information in the camera-ready. Similar suggestions apply for work conducted in specific organizations (e.g., industrial studies). In such cases, avoid to mention the organization's name. Instead, you may just refer the organization as "Org" or "Company", etc. When appropriate and when this does not help too much in revealing the company's name, you might mention the context (e.g., financial organization, videogame development company, etc.).

Avoid linking directly to code repositories or tool deployments which can reveal your identity. Whenever possible, please use the EasyChair additional material field to submit a .zip or .tgz file including additional material. This is of course possible for small attachments. In other cases, you may post anonymized links (with a warning that following said link may reveal authors' identities), include links to anonymized code or deployments. When creating such repositories, a good practice can be asking somebody in your team to test the anonymization of the repository and of its content. In case anonymization is difficult to be achieved and you still want to provide availability of data/tools, you can simply state that you will link to the code or deployment in the camera-ready version. Program committee members are asked to keep into account the double-blind policy when reviewing papers, and therefore not requiring full availability of artifacts at submission time.

Special Issue
Authors of selected research papers accepted at SANER 2019 will be invited to submit revised, extended versions of their manuscripts for a special issue of the Empirical Software Engineering journal (EMSE), edited by Springer.


Important Dates
Abstract submission deadline: October 12, 2018 AoE
Paper submission deadline: October 19, 2018 AoE
Notifications: November 30, 2018
Camera Ready: December 21, 2018
Submission Page: https://easychair.org/conferences/?conf=saner2019

Related Resources

SANER 2020   27th IEEE International Conference on Software Analysis, Evolution and Reengineering
IEEE--ICCSN--Ei and Scopus 2020   2020 IEEE 12th International Conference on Communication Software and Networks (ICCSN 2020)--Ei Compendex, Scopus
ICCSN--IEEE, Ei Compendex and Scopus 2020   2020 IEEE 12th International Conference on Communication Software and Networks (ICCSN 2020)--Ei Compendex, Scopus
IEEE--ICCIA--Ei Compendex, Scopus 2020   IEEE--2020 5th International Conference on Computational Intelligence and Applications (ICCIA 2020)--Ei Compendex, Scopus
Social Media 2020   IEEE International Conference on Social Media, Wearable and Web Analytics
ICICT 2020   5th Scopus- Indexed IEEE International Conference on Inventive Computation Technologies
ICSME 2019   International Conference on Software Maintenance and Evolution
SP 2020   IEEE Symposium on Security and Privacy
IDA 2020   The 18th International Symposium on Intelligent Data Analysis (IDA 2020)
TMPA 2019   Software Testing, Machine Learning and Complex Process Analysis