SBES 2023
37th Brazilian Symposium on Software Engineering

Call for Papers – Insightful Ideas and Emerging Results Track

• Forward-looking ideas: Exciting new directions or techniques that may have yet to be supported by solid experimental results, but are nonetheless supported by strong and well-argued scientific intuitions as well as concrete plans going forward.
• Thought-provoking reflections: Bold and unexpected results and reflections that can help us look at current research directions under a new light, calling for new directions for future research.

Important Dates

• Paper registration (abstract submission): May 28, 2023
• Paper submission: June 02, 2003
• Author notification: July 10, 2023
• Camera-ready: July 31, 2023

Topics of Interest

• API design and evolution
• Apps and app store analysis
• Configuration management
• Continuous software engineering
• Crow-based software engineering
• Design for quality, including privacy and security by design
• Distributed and collaborative software engineering
• Diversity, inclusion and fairness of software
• Embedded and cyber-physical systems
• Ethics in software engineering
• Evolution and maintenance
• Feedback, user and requirements engineering
• Green and sustainable technologies
• Human and social aspects of software engineering
• Legal aspects of software engineering
• Low-code/no-code
• Machine learning with and for software engineering
• Mining software repositories
• Modeling and model-driven engineering
• Privacy and security
• Productivity in software engineering
• Recommender systems
• Refactoring
• Release engineering and DevOps
• Reliability and safety
• Requirements engineering, modeling and design
• Reverse engineering
• Search-based software engineering
• Software architecture and product design
• Software economics
• Software ecosystems and systems-of-systems
• Software engineering in industrial applications
• Software engineering in society
• Software engineering for new technologies/platforms (e.g., cloud, IoT, mobile)
• Software metrics and prediction models
• Software processes and quality models
• Software reuse
• Software services and cloud-based systems
• Software verification, validation, and testing
• Software visualization
• Technical debt management
• Variability and product lines

Paper Preparation, Submission, and Review

\documentclass[sigconf]{acmart}

\bibliographystyle{ACM-Reference-Format}

Desk Rejection

Evaluation Criteria

• Significance: The extent to which the paper’s contributions can impact the field of software engineering, and under which assumptions (if any);
• Novelty: The extent to which the contributions are cutting-edge, have potential impact for disruption of current practice or are sufficiently original with respect to the state-of-the-art;
• Soundness: The extent to which the paper’s contributions and the authors’ plans for future work are based rigorous application of appropriate research methods;
• Presentation: The extent to which the paper’s quality of writing meets high standards, including clear descriptions, as well as adequate use of the English/Portuguese language, absence of major ambiguity, clearly readable figures and tables, and adherence to the formatting instructions provided below;
• Verifiability: The extent to which the paper includes sufficient information to understand how an innovation works; to understand how data was obtained, analyzed, and interpreted; and how the paper supports independent verification or replication of the paper’s claimed contributions.

Open Science Policies

Double-Anonymous Submission

• Citations to own related work must be written in the third person. For example, one must write "the previous work of Silva et al." as opposed to "our previous work." As a heuristic, occurrences of "we", "our", "ours", "github", "funding", etc. should be looked in the paper and removed prior to submitting.
• In the submitted paper, any artifact in a repository or website that allows identifying the authorship should not be mentioned. If any artifact needs to be made available, it should be anonymized in the repository/website.
• Reviewers will not be encouraged to look for references that identify the authors in other sources on the Internet. Searches in digital libraries or existing artifacts do not break the double-anonymous policy.
• If the submitted paper is a follow up of a previous work, the reference may be anonymized in the submitted paper. For example, "the previous work of Silva et al." should be adapted to "based on the previous work [X]" and the reference at the end of the paper should be presented in full. Please, do not indicate as "[X] Anonymous authors. Not presented due to double-anonymous review." since this might prompt the reviewer.

Outstanding Reviewer Award

Organization