20th IEEE International Working Conference on Source Code Analysis and Manipulation

Accepted Papers

Research Track

1. Roger Scott, Joseph Ranieri, Lucja Kot and Vineeth Kashyap. Out of Sight, Out of Place: Detecting and Assessing Swapped Arguments
2. Noah Van Es, Quentin Stiévenart, Jens Van der Plas and Coen De Roover. A Parallel Worklist Algorithm for Modular Analyses
3. Ruben Opdebeeck, Ahmed Zerouali, Camilo Velázquez-Rodríguez and Coen De Roover. Does Infrastructure as Code Adhere to Semantic Versioning? An Analysis of Ansible Role Evolution
4. Ajay Kumar Jha and Sarah Nadi. Annotation practices in Android apps
5. Anthony Saieva, Gail Kaiser and Shirish Singh. Ad hoc Test Generation Through Binary Rewriting
6. Bernhard J. Berger, Rodrigue Wete Nguempnang, Karsten Sohr and Rainer Koschke. Static Extraction of Enforced Authorization Policies - SeeAuthZ
7. Donggyun Han, Chaiyong Ragkhitwetsagul, Jens Krinke, Matheus Paixao and Giovanni Rosa. Does code review really remove coding convention violations?
8. Sara Moshtari, Joanna Cecilia da Silva Santos, Mehdi Mirakhorli and Ahmet Okutan. Looking for Software Defects? First Find the Nonconformists - An Outlier-Based Defect Prediction Approach
9. Quentin Stievenart and Coen De Roover. Compositional Information Flow Analysis for WebAssembly Programs
10. Rafi Almhana, Thiago Ferreira, Marouane Kessentini and Tushar Sharma. Understanding and Characterizing Changes in Bugs Priority : The Practitioners' Perceptive
11. Geanderson Esteves dos Santos and Eduardo Figueiredo. The Failure of One, the Fall of Many: An Exploratory Study of Software Features for Defect Prediction
12. Felix Dobslaw, Morgan Vallin and Robin Sundström. Free the Bugs: Disclosing Blocking Violations in Reactive Programming
13. Richárd Szalay, Ábel Sinkovics and Zoltán Porkoláb. The Role of Implicit Conversions in Erroneous Function Argument Swapping in C++
14. Jens Van der Plas, Quentin Stiévenart, Noah Van Es and Coen De Roover. Incremental Flow Analysis through Computational Dependency Reification
15. Naser Ezzati Jivan, Quentin Fournier, Michel Dagenais and Abdelwahab Hamou-Lhadj. DepGraph: Localizing Performance Bottlenecks in Multi-Core Applications Using Resource Dependency Graphs and Software Tracing
16. Rungroj Maipradit, Bin Lin, Csaba Nagy, Gabriele Bavota, Michele Lanza, Hideaki Hata and Kenichi Matsumoto. Automated Identification of On-hold Self-admitted Technical Debt

REproducibility Studies and NEgative Results Track

1. David Binkley, James Glenn, Abdullah Alsharif and Phil McMinn. An Investigation into the Effect of Control and Data Dependence Paths on Predicate Testability

Engineering Track

1. Johan Fabry, Ynes Jaradin and Aynel Gul. Engineering a Converter between two Domain-Specific Languages for Sorting
2. Noah Van Es, Jens Van der Plas, Quentin Stiévenart and Coen De Roover. MAF: A Framework for Modular Static Analysis of Higher-Order Languages
3. Adrian Herrera. Optimizing Away JavaScript Obfuscation
4. Ana Paula Tarchetti, Luis Amaral, Marcos Oliveira, Rodrigo Bonifácio, Gustavo Pinto and David Lo. DCT: An Scalable Multi-Objective Module Clustering Tool
5. Francisco Handrick da Costa, Ismael Medeiros, Pedro Costa, Thales Menezes, Marcos Vinícius Pereira Marques, Rodrigo Bonifácio and Edna Dias Canedo. DroidXP: A Benchmark for Supporting the Research on Mining Android Sandboxes

New Ideas and Emerging Results (NIER) Track

1. João P. Diniz, Daniel Cruz, Fábio Ferreira, Cleiton Silva and Eduardo Figueiredo. GitHub Label Embeddings
2. Thomas Schweizer, Vassilis Zafeiris, Marios Fokaefs and Michalis Famelis. Can Refactorings Indicate Design Tradeoffs?
3. Nataliia Stulova, Arianna Blasi, Alessandra Gorla and Oscar Nierstrasz. Towards Detecting Inconsistent Comments in Java Source Code Automatically
4. Jérôme Fink, Maxime Gobert and Anthony Cleve. Adapting Queries to Database Schema Changes in Hybrid Polystores
5. Camilo Velázquez-Rodríguez and Coen De Roover. MUTAMA: An Automated Multi-label Tagging Approach for Software Libraries on Maven
6. Abdul Moiz and Manar Alalfi. An Approach for the identification of information leakage in Automotive Infotainment systems
7. Tukaram Muske and Alexander Serebrenik. Techniques for Efficient Automated Elimination of False Positives
8. Vinuri Bandara, Nipuna Weerasekara, Thisura Rathnayake, Primal Wijesekera, Charitha Elvitigala, Kenneth Thilakarathna and Chamath Keppitiyagama. Fix that Fix Commit: A real-world remediation analysis of JavaScript projects

Conference Format

SCAM 2020 will follow the working conference format that is meant to stimulate thought-provoking discussions by keeping presentations short and focused, while reserving time slot at the end of each session for a plenary discussion about the session's topic.

For research track, presentations must therefore respect a time limit of 12 minutes. For Engineering, RENE, and NIER tracks, presentations must respect a time limit of 7 minutes. There will be 3 minutes of time for one or two clarification questions after each presentation. Longer questions will be postponed till the end of the session.

The session chair will help respect the time limits, and will manage discussion and questions from the audience. The list of session chairs is available here

If you have further questions, please do not hesitate to contact the program chairs

We will use slack to organize the discussion and questions.

Call for Research Track Papers

The 20th IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2020) aims to bring together researchers and practitioners working on theory, techniques, and applications that concern analysis and/or manipulation of the source code of software systems. The term "source code" refers to any fully executable description of a software system, such as machine code, (very) high-level languages, and executable graphical representations of systems. The term "analysis" refers to any (semi-)automated procedure that yields insight into source code, while "manipulation" refers to any automated or semi-automated procedure that takes and returns source code. While much attention in the wider software engineering community is directed towards other aspects of systems development and evolution, such as specification, design, and requirements engineering, it is the source code that contains the only precise description of the behavior of a system. Hence, the analysis and manipulation of source code remains a pressing concern for which SCAM 2020 solicits high quality paper submissions.

Covered Topics and Paper Formats

We welcome submission of papers that describe original and significant work in the field of source code analysis and manipulation. Topics of interest include, but are not limited to:

• program transformation and refactoring
• static and dynamic analysis
• natural language analysis of source code artifacts
• repository, revision, and change analysis
• source level metrics
• decompilation
• bug location and prediction
• security vulnerability analysis
• source-level testing and verification
• clone detection
• concern, concept, and feature localization and mining
• program comprehension
• bad smell detection
• abstract interpretation
• program slicing
• source level optimization
• energy efficient source code

SCAM explicitly solicits results from any theoretical or technological domain that can be applied to these and similar topics. Submitted papers should describe original, unpublished, and significant work and must not have been previously accepted for publication nor be concurrently submitted for review in another journal, book, conference, or workshop. Papers must not exceed 12 pages (the last 2 pages can be used for references only) and must conform to the IEEE proceedings paper format guidelines. Templates in Latex and Word are available on IEEE's website. All submissions must be in English.

The papers should be submitted electronically in PDF format via EasyChair. Submission will be reviewed by at least three members of the program committee, judging the paper on its novelty, quality, importance, evaluation, and scientific rigor. If the paper is accepted, at least one author must attend the conference and present the paper.

SCAM 2020 also features a replication and negative results paper track for soliciting reproductibility and negative results papers and an engineering paper track for papers that report on the design and implementation of tools for source code analysis and manipulation.

Proceedings

All accepted papers will appear in the proceedings which will be available through the IEEE Digital Library.

Special Issue

We encourage to submit extended papers from SCAM 2020, including papers from the research, engineering, and RENE tracks, to a special issue of Journal of Systems and Software (Special Issue on Source Code Analysis and Manipulation). It should be extended by at least 30% of new material different from the original work.

Important Dates for Research Papers

Call for Replication and Negative Results Papers

The 20th IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) will be hosting a Replication and Negative Result (RENE) track for the first time in 2020. This track provides a venue for researchers to submit papers reporting (1) replications of previous empirical studies (including controlled experiments, case studies, and surveys) and (2) important and relevant negative or null results (i.e., results that failed to show an effect, but help to eliminate useless hypotheses, therefore reorienting researchers on more promising research paths) related to source code analysis and manipulation (see list of topics in Technical Research Track).

*Replications studies*: The papers in this category must go beyond simply re-implementing an algorithm and/or re-running the artifacts provided by the original paper. Such submissions should apply the approach on at least a partially new data sets (open-source or proprietary). This also means that it is possible to use available infrastructures to conduct measurements and experiments but with different/extended datasets and different conditions, scenarios, etc. Replication studies can either strengthen the results of the original study by increasing external validity with additional data or provide new insights into the variables that may impact the results. A replication paper should clearly report on results that the authors were able to reproduce as well as on the aspects of the work that were irreproducible.

*Negative results papers*: In this category we seek papers that report on negative results. We seek negative results for all types of software engineering research related to source code and manipulation (qualitative, quantitative, case study, experiment, etc.). Negative results are important contributions to scientific knowledge because they allow us to prune our hypothesis space. As Walter Tichy writes, "Negative results, if trustworthy, are extremely important for narrowing down the search space. They eliminate useless hypotheses and thus reorient and speed up the search for better approaches."

Evaluation Criteria

Both Reproducibility Studies and Negative Results submissions will be evaluated according to the following standards:

• Depth and breadth of the empirical studies
• Clarity of writing
• Appropriateness of conclusions
• Amount of useful, actionable insights
• Deep discussion regarding the implications of the negative results or new results obtained with reproducibility studies
• Availability of artifacts
• Underlying methodological rigor and detailed description of procedures. For example, a negative result due primarily to misaligned expectations or due to lack of statistical power (small samples) is not a good submission. The negative result should be a result of a lack of effect, not lack of methodological rigor.
• Clear descriptions of the differences between the original setup and the one used in the study (for the case of reproducibility studies).
•  
• Most importantly, we expect that replication studies clearly point out the artifacts the study is built upon, and to provide the links to all the artifacts in the submission (the only exception will be given to those papers that reproduce the results on proprietary datasets that can not be publicly released).The paper should describe any changes to the original study design made during the replication, along with a justification for each change. The papers should contain a discussion section that compares the findings of the original and replication studies and describe the new knowledge gained from the replication along with any lessons learned from performing the replication. Partial replications are also welcome as long as the paper clearly states which parts of the study were replicated and which parts are new.

Submission Instructions

Submissions must be original, in the sense that the findings and writing have not been previously published or under consideration elsewhere. Papers must not exceed 10 pages for the main text, inclusive of figures, tables, appendices; references only may be included on up to 2 additional pages. The paper must conform to the IEEE proceedings paper format guidelines and must be clearly marked as a RENE paper. Templates in Latex and Word are available on IEEE's website. All submissions must be in English.

The papers should be submitted electronically in PDF format via EasyChair. Submission will be reviewed by at least three members of the program committee, judging the paper on its novelty, quality, importance, evaluation, and scientific rigor. If the paper is accepted, at least one author must attend the conference and present the paper.

This year, we follow a double-blind reviewing process. Submitted papers must adhere to the following rules:

• Author names and affiliations must be omitted. (The track co-chairs will check compliance before reviewing begins.)
• 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...")

Proceedings

All accepted papers will appear in the proceedings which will be available through the IEEE Digital Library

Special Issue

We encourage to submit extended papers from SCAM 2020, including papers from the research, engineering, and RENE tracks, to a special issue of Journal of Systems and Software (Special Issue on Source Code Analysis and Manipulation). It should be extended by at least 30% of new material different from the original work.

Important Dates

Call for Engineering Track Papers

In addition to the research track (see separate CFP), the 20th IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2020) will also feature an Engineering track. This track welcomes six-page papers that report on the design and implementation of tools for source code analysis and manipulation, as well as libraries, infrastructure, and the real world studies enabled by these advances. To be clear, this is not the addition of a new track to SCAM but rather a significant expansion to the scope of the tools track of previous SCAMs.

What artefacts qualify as “engineering track” material?

• tools: software (or hardware!) programs that facilitate SCAMmy activities.
• libraries: reusable API-enabled frameworks for the above.
• infrastructure: while libraries are purely software, infrastructure can include projects that provide/facilitate access to data and analysis.
• data: reusable datasets for other researchers to replicated and innovate with.
• real world studies enabled by these advances. Here the focus is on how the {tool,infrastructure, etc} enabled the study, and not so much the study itself. The novelty of the research question is less important than the engineering challenges faced in the study.

A successful SCAM engineering track paper should:

1. Fall under the topics mentioned for the SCAM 2020 research track.
2. Discuss engineering work artefacts that have NOT been published before. However, previous work involving the tool, but for which the tool was not the main contribution, are acceptable.
3. Motivate the use cases (and hence the existence) of the engineering work.
4. Relate the engineering project to earlier work, if any.
5. Describe the experiences gained in developing this contribution.

Optionally (and encouraged):

6. Any empirical results or user feedback is welcome.
7. Contain the URL of a website where the tool/library/data etcetera can be downloaded, together with example data and clear installation guidelines, preferably but not necessarily open source.
8. Contain the URL to a video demonstrating the usage of the contribution.

Note that the submission length has a limit of six pages, in contrast to the two to four pages of traditional tool demo papers. The expectation is that authors use the space to discuss artefact motivation, design, and use cases in much more detail. For example, a use case would be well illustrated by a demo scenario with screenshots.

Each submission will be reviewed by members of the engineering track program committee. Authors of accepted papers will be required to present their artefacts at the conference. All accepted engineering track papers will be published in the conference proceedings. The key criterion for acceptance is that the paper should (a) follow the above mentioned guidelines and (b) make an original contribution that can benefit practitioners in the field now and/or others designing and building artefacts for source code analysis and manipulation. The artefacts can range from an early research prototype to a polished product ready for deployment. Papers about commercial products are allowed, as long as the guidelines described above are followed.

Videos and other demo material may be taken into account by reviewers as they review the paper. However, such material will not become part of the permanent record of the conference, so the paper should be self contained. In order to preserve the anonymity of the reviewers, such material should be hosted on an anonymous public source (e.g., Tube), or made available in such a way that the tools chair can download them once and redistribute them to reviewers

Proceedings

All accepted papers will appear in the proceedings which will be published by the IEEE Computer Society Press.

Special Issue

We encourage to submit extended papers from SCAM 2020, including papers from the research, engineering, and RENE tracks, to a special issue of Journal of Systems and Software (Special Issue on Source Code Analysis and Manipulation). It should be extended by at least 30% of new material different from the original work.

Important Dates

Submission

The submission should be maximum six pages, in IEEE format, submitted via EasyChair. Please use the IEEE templates in preparing your manuscripts:

• Latex template: use \documentclass[conference]{IEEEtran}
• Microsoft Word template

Goal and Scope

The 20th IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) will host a New Ideas and Emerging Results (NIER) track. The goal of this track is to provide a place for researchers and practitioners to present, discuss, and polish early-stage research. This early-stage research should be innovative and have the potential to make a strong future impact on the research or practice of software engineering. However, as it concerns early-stage research, the NIER track does not require submissions to have a strong evaluation. Instead, submissions should contain preliminary results that indicate the future potential of the research as well as a discussion of the challenges which must be overcome in the pursuit of the given research goals. These challenges should act as both future research directions as well as topics which the authors feel require discussion within the community. The topics of interest for this track are the same as for the main research track and are listed below.

Topics of Interest

We welcome the submission of papers that describe original and significant work in the field of source code analysis and manipulation. Topics of interest include, but are not limited to:

• program transformation and refactoring
• static and dynamic analysis
• natural language analysis of source code artifacts
• repository, revision, and change analysis
• source-level metrics
• decompilation
• bug location and prediction
• security vulnerability analysis
• source-level testing and verification
• clone detection
• concern, concept, and feature localization and mining
• program comprehension
• bad smell detection
• abstract interpretation
• program slicing
• source-level optimization
• energy efficient source code

Submission Instructions

Submissions must be original, in the sense that the findings and writing have not been previously published or under consideration elsewhere. Papers must not exceed 5 pages for the main text, which includes figures, tables, appendices, and references. Papers must conform to the IEEE proceedings paper format guidelines and must be clearly marked as a NIER paper. Templates in Latex and Word are available on IEEE's website. All submissions must be in English.

The papers should be submitted electronically in PDF format via EasyChair. Submission will be reviewed by at least three members of the program committee. If the paper is accepted, at least one author must attend the conference and present the paper.

This year, we follow a double-blind reviewing process. Submitted papers must adhere to the following rules:

• Author names and affiliations must be omitted. (The track co-chairs will check compliance before reviewing begins.)
• 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...")

Please see the Double-Blind Reviewing FAQ, for more information and guidance.

Evaluation

Submissions will be evaluated on the basis of their originality, the importance of their contribution, the challenges highlighted, and their potential future significance. In addition, reviewers are asked to consider the soundness, overall quality, clarity and consistency of presentation, and whether the submission appropriately contextualizes itself with respect to related work. Again, the NIER track does not require a full evaluation to be present within the submission. Preliminary data, as well as a discussion of the challenges and future research directions supported by this preliminary data, is encouraged.

Important Dates

**All submission dates are at 23:59 AoE (Anywhere on Earth, UTC-12)**

General Chair

• Foutse Khomh, École Polytechnique Montréal, Canada

Research Track Program Co-Chairs

• Cristina Cifuentes, Oracle Labs, Australia
• Nikolaos Tsantalis, Concordia University, Canada

Engineering Track Program Co-Chairs

• Hironori WASHIZAKI, Waseda University, Japan
• Sandro Schulze, Otto-von-Guericke Univeristät Magdeburg, Germany

RENE Track PC Co-chairs

• Fenia E. Aivaloglou, University of Leiden, Netherlands
• Banani Roy, University of Saskatchewan, Canada

New Ideas and Emerging Results (NIER) co-chairs

• Eleni Constantinou, Eindhoven University of Technology, Netherlands
• Christian Newman, Rochester Institute of Technology, USA

Most Influential Paper Chair

• Massimiliano Di Penta, University of Sannio, Italy

Publicity Co-Chairs

• Naser Ezzati-Jivan, Brock University, Canada

Finance Chair

• Dave Binkley, Loyola University Maryland, USA

Proceedings chair

• Masud Rahman, Dalhousie University, Canada

Web and Virtualization Chair

• Mouna Abidi, École Polytechnique Montréal, Canada

Research Track

Chairs

• Cristina Cifuentes, Oracle Labs, Australia
• Nikolaos Tsantalis, Concordia University, Canada

Members

• Jinqiu Yang, Concordia University, Canada
• Fernando Castor, Federal University of Pernambuco, Brazil
• Coen De Roover, Vrije Universiteit Brussel, Belgium
• Jens Krinke, University College London, United Kingdom
• Mariano Ceccato, University of Verona, Italy
• Fabio Palomba, University of Salerno, Italy
• Jeffrey Svajlenko, Microsoft, United States
• David Lo, Singapore Management University, Singapore
• Nicolas Anquetil, University of Lille-1, France
• Lingxiao Jiang, Singapore Management University, Singapore
• Latifa Guerrouj, École de Technologie Supérieure, Canada
• Ewan Tempero, The University of Auckland, New Zealand
• Neil Ernst, University of Victoria, Canada
• Maurício Aniche, Delft University of Technology, The Netherlands
• Venera Arnaoudova, Washington State University, United States
• Mario Linares Vasquez, Universidad de los Andes, Colombia
• Saba Alimadadi, Simon Fraser University, Canada
• Tony Sloane, Macquarie University, Australia
• Bernhard Scholz, University of Sydney, Australia
• Behnaz Hassanshahi, Oracle Labs, Australia
• Jens Dietrich, University of Wellington, New Zealand
• Neville Grech, University of Athens, Greece
• Jens Palsberg, University of California, USA
• Magnus Madsen, Aarhus University, Denmark
• Harald Sondergaard, University of Melbourne, Australia
• Tse-Hsun Peter Chen, Concordia University, Canada
• Antony Hosking, Australian National University, Australia
• Thierry Lavoie, Synopsys, USA
• Yuval Yarom, The University of Adelaide, Australia
• Li Li, Monash University, Australia
• Ali Ouni, École de Technologie Supérieure, Canada
• Ben Hermann, Paderborn University, Germany
• Benjamin Barslev Nielsen, Aarhus University, Denmark
• George Fourtounis, University of Athens, Greece
• Yulei Sui, University of Technology Sydney, Australia
• Erica Mealy, The University of Queensland, Australia
• Alexander Jordan, Oracle Labs, Australia
• Kirsten Winter, University of Queensland, Australia
• Ameya Ketkar, Oregon State University, USA
• Abu Naser Masud, Mälardalen University, Sweden
• Hoa Khanh Dam, University of Wollongong, Australia

RENE Track

Chairs

• Fenia E. Aivaloglou, University of Leiden, Netherlands
• Banani Roy, University of Saskatchewan, Canada

Members

• Maria Kechagia, University College London, United Kingdom
• Ayushi Rastogi, Delft University of Technology, Netherlands
• Eleni Constantinou, Eindhoven University of Technology, Netherlands
• Gias Uddin, University of Calgary, Canada
• Abu Naser Masud, Mälardalen University, Sweden
• Bihuan Chen, Fudan University, China
• Lingfeng Bao, Zhejiang University, China
• Mark Hills, East Carolina University, United States
• Eric J.Rapos, Miami University, United States
• Jeffrey Svajlenko, Microsoft, United States
• Shinpei Hayashi, Tokyo Institute of Technology, Japan

Engineering Track

Chairs

• Hironori Washizaki, Waseda University, Japan
• Sandro Schulze, Universität Magdeburg, Germany

Members

• Jochen Quante, Robert Bosch GmbH, Germany
• Fabio Palomba, University of Salerno, Italy
• Ali Ouni, ETS Montreal, University of Quebec, Canada
• Vadim Zaytsev, University of Twente, Netherlands
• Csaba Nagy, Software Institute, Università della Svizzera italiana, Switzerland
• Andre Hora, UFMG, Brazil
• Eleni Constantinou, Eindhoven University of Technology, Netherlands
• Wolfram Fenske, pure::systems, Germany
• Vipin Balachandran, San Francisco, United States

New Ideas and Emerging Results (NIER) Track

Chairs

• Eleni Constantinou, Eindhoven University of Technology, Netherlands
• Christian Newman, Rochester Institute of Technology, USA

Members

• Mike Papadakis, University of Luxembourg, Luxembourg
• Michael J. Decker, Bowling Green State University, USA
• Boyang Li, Linkedin Inc, USA
• Zhe Yu, North Carolina State University, USA
• Dario Di Nucci, Jheronimus Academy of Data Science, Netherlands
• Tukaram Muske, TCS Research, India
• Fabio Palomba, University of Salerno, Italy
• Marouane Kessentini, University of Michigan, USA
• Damian Andrew Tamburri, Technical University of Eindhoven - Jeronimus Academy of Data Science, Netherlands
• Igor Steinmacher, Northern Arizona University, USA
• Naser Ezzati-Jivan, Brock University, Canada
• Jesus Gonzalez-Barahona, Universidad Rey Juan Carlos, Spain
• Mohamed Wiem Mkaouer, Rochester Institute of Technology, USA
• Alexander Serebrenik, Eindhoven University of Technology, Netherlands
• Jonathan Maletic, Kent State University, USA
• Diomidis Spinellis, Athens University of Economics and Business, Greece
• Bram Adams, Queen's University, Canada

SCAM Steering Committee

• Árpád Beszédes, 2018 - 2021, 1st term. SC Chair
• Paige Rodeghero, 2019-2022, 1st term
• Johan Fabry, 2019-2022, 1st term
• Coen De Roover, 2020 - 2023, 2nd term
• Mark Hills, 2018 - 2021, 1st term
• Vadim Zaytsev, 2020 - 2023, 1st term

Charter

The International Working Conference on Source Code Analysis & Manipulation (SCAM) is governed by the steering committee following a community ratified steering committee charter (v1.2, adopted in 2012).

Adelaide, Australia

More info via ICSME

Fun & Merchandise

2001, Florence, Italy

2002, Montreal, Canada

2003, Amsterdam, The Netherlands

2004, Chicago, USA

2005, Budapest, Hungary

2006, Philadelphia, PA

2007, Paris, France

2008, Beijing, China

2009, Edmonton, Canada

2010, Timișoara, Rumania

Previous Next

Sponsorship Opportunities

What is SCAM?

• Flagship gathering of the source code analysis community
• Attended by a focused gathering of 50 to 80 members of academia, industry, and government
• Professional development: keynotes by field leaders, latest research, engineering track

Benefits to Supporters

• Excellent recruiting venue for highly qualified software engineers
• Invitation to Social Gatherings
• Organization's logo on SCAM publicity materials including:
  • Conference website, proceedings, and program
  • Signage and banners at the conference
• Provide corporate information to attendees

Support Level Opportunities

• Three levels of support:
  • Silver
  • Gold
  • Platinum
• Sponsorship can be associated with a specific conference activity.

Banquet Address

• An opportunity at the conference banquet to give a brief introduction to your company.

For further information, please contact the general chair, Chanchal K. Roy