SPLASH 2013
Sat 26 - Thu 31 October 2013 Indianapolis, United States

OOPSLA is the premier conference on Object-Oriented Programming, having been the forum for some of the most important software developments over the last couple of decades. OOPSLA was the incubator for CRC cards, CLOS, design patterns, Self, agile methodologies, service-oriented architectures, wikis, UML, test driven design, refactoring, Java, dynamic compilation, and aspect-oriented programming, to name a few. OOPSLA is not only about objects but it never strays far from them.

New this year, authors of OOPSLA papers were invited to submit supporting materials to the Artifact Evaluation process. The goal of the Artifact Evaluation process is to empower others to build upon the contributions of a paper. Papers that went through the Artifact Evaluation process received a seal of approval.

Accepted Papers

Title
Ball-Larus Path Profiling Across Multiple Loop Iterations
OOPSLA
DOI
Barrier Invariants: A Shared State Abstraction for the Analysis of Data-Dependent GPU Kernels
OOPSLA
DOI
Bottle Graphs: Visualizing Scalability Bottlenecks in Multi-Threaded Applications
OOPSLA
DOI
Bounded Partial-Order Reduction
OOPSLA
DOI
CDSChecker: Checking Concurrent Data Structures Written with C/C++ Atomics
OOPSLA
DOI
Class Hierarchy Complementation: Soundly Completing a Partial Type Graph
OOPSLA
DOI
Code Optimizations Using Formally Verified Properties
OOPSLA
DOI
Combining Concern Input with Program Analysis for Bloat Detection
OOPSLA
DOI
Data-Driven Equivalence Checking
OOPSLA
DOI
Detecting API Documentation Errors
OOPSLA
DOI
Do Developers Benefit from Generic Types?: An Empirical Comparison of Generic and Raw Types in Java
OOPSLA
DOI
Effective Race Detection for Event-Driven Programs
OOPSLA
DOI
Efficient Concurrency-Bug Detection Across Inputs
OOPSLA
DOI
Efficient Context Sensitivity for Dynamic Analyses via Calling Context Uptrees and Customized Memory Management
OOPSLA
DOI
Empirical Analysis of Programming Language Adoption
OOPSLA
DOI
Flexible Access Control for Javascript
OOPSLA
DOI
Forsaking Inheritance: Supercharged Delegation in DelphJ
OOPSLA
DOI
Fully Concurrent Garbage Collection of Actors on Many-Core Machines
OOPSLA
DOI
Guided GUI Testing of Android Apps with Minimal Restart and Approximate Learning
OOPSLA
DOI
Inductive Invariant Generation via Abductive Inference
OOPSLA
DOI
Injecting Mechanical Faults to Localize Developer Faults for Evolving Software
OOPSLA
DOI
Input-Covering Schedules for Multithreaded Programs
OOPSLA
DOI
Instant Pickles: Generating Object-Oriented Pickler Combinators for Fast and Extensible Serialization
OOPSLA
DOI
Interacting with Dead Objects
OOPSLA
DOI
Ironclad C++: A Library-Augmented Type-Safe Subset of C++
OOPSLA
DOI
Isolation for Nested Task Parallelism
OOPSLA
DOI
Language Support for Dynamic, Hierarchical Data Partitioning
OOPSLA
DOI
Miniboxing: Improving the Speed to Code Size Tradeoff in Parametric Polymorphism Translations
OOPSLA
DOI
MrCrypt: Static Analysis for Secure Cloud Computations
OOPSLA
DOI
Multiverse: Efficiently supporting distributed high-level speculation
OOPSLA
DOI
Octet: Capturing and Controlling Cross-Thread Dependences Efficiently
OOPSLA
DOI
On-the-fly Capacity Planning
OOPSLA
DOI
On-the-fly Detection of Instability Problems in Floating-Point Program Execution
OOPSLA
DOI
Online Feedback-Directed Optimizations for Parallel Java Code
OOPSLA
DOI
Option Contracts
OOPSLA
DOI
Python: The Full Monty; A Tested Semantics for the Python Programming Language
OOPSLA
DOI
Refactoring with Synthesis
OOPSLA
DOI
Relaxed Separation Logic: A Program Logic for C11 Concurrency
OOPSLA
DOI
Resurrector: A Tunable Object Lifetime Profiling Technique for Optimizing Real-World Programs
OOPSLA
DOI
River Trail: A Path to Parallelism in JavaScript
OOPSLA
DOI
Semi-Automatic Rename Refactoring for JavaScript
OOPSLA
DOI
Set-Based Pre-Processing for Points-To Analysis
OOPSLA
DOI
Steering Symbolic Execution to Less Traveled Paths
OOPSLA
DOI
Storage Strategies for Collections in Dynamically Typed Languages
OOPSLA
DOI
Synthesis Modulo Recursive Functions
OOPSLA
DOI
Taking Off the Gloves with Reference Counting Immix
OOPSLA
DOI
Targeted and Depth-first Exploration for Systematic Testing of Android Apps
OOPSLA
DOI
The Latency, Accuracy, and Battery (LAB) Abstraction: Programmer Productivity and Energy Efficiency for Continuous Mobile Context Sensing
OOPSLA
DOI
Turning Nondeterminism into Parallelism
OOPSLA
DOI
Verifying Quantitative Reliability for Programs That Execute on Unreliable Hardware
OOPSLA
DOI

General Information

OOPSLA (formerly the ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications), now part of SPLASH, is the premier ACM research conference on Object-Oriented Programming, having been the forum for some of the most important software developments over the last couple of decades. OOPSLA was the incubator for CRC cards, CLOS, design patterns, Self, the agile methodologies, service-oriented architectures, wikis, Unified Modeling Language (UML), test driven design (TDD), refactoring, Java, dynamic compilation, and aspect-oriented programming, just to name a few. OOPSLA is not only about objects but it never strays far from them.

Submission Summary
Due on: March 28, 2013
Abstract: March 22, 2013
First-Phase Notification: May 25, 2013
Revisions: July 20, 2013
Final Notification: July 29, 2013
Camera-Ready: August 05, 2013
Format: ACM SIGPLAN Proceedings format
Submit to: http://cyberchair.acm.org/oopslapapers/submit/
Contact: Cristina V. Lopes (chair)

The ACM International Conference on Systems, Programming, Languages and Applications: Software for Humanity (SPLASH) is sponsored by ACM SIGPLAN.

SPLASH is the home of OOPSLA Research Papers, Onward!, and the Dynamic Languages Symposium, among other events.

Call for Papers

OOPSLA invites submissions of original research papers covering any aspect of programming, systems, languages, and applications. Work that explores objects and beyond on matters of programming in the large, reusability, design and programmer productivity is strongly encouraged.

Please read carefully, as some important details of the submission procedure have changed from previous years.

Scope

Papers may address any aspect of software development, including requirements, modeling, prototyping, design, implementation, generation, analysis, verification, testing, evaluation, maintenance, reuse, replacement, and retirement of software systems. Papers on studies of large-scale software repositories are in scope. Papers on tools (such as new languages, program analyses, or runtime systems) or on techniques (such as new methodologies, design processes, code organization approaches, and management techniques) that go beyond objects in interesting ways are also in scope.

Paper Selection

Selection Criteria

The program committee will consider the following criteria when evaluating submitted papers:

Originality: The paper presents new ideas and/or results that haven't been known before and places these ideas and results appropriately within the context established by previous research in the field.

Importance: The paper contributes significantly to the advancement of knowledge in the field.

Evidence: The paper presents sufficient evidence supporting its claims. Examples of evidence include formalizations and proofs, implemented systems, experimental results, statistical analyses, and case studies.

Clarity: The paper presents its contributions, methodology and results clearly.

Selection Process

OOPSLA 2013 will follow a two-phase review process. The first reviewing phase assesses the papers using the criteria stated above and results in the selection of a subset of submissions that are either accepted as-is or deemed potentially acceptable. All other papers will be rejected in this phase.

Authors of potentially accepted papers will be requested to improve specific aspects of the work and the papers. Authors will be given 2 months to perform the revisions, after which a second submission will occur.

The second submission should unequivocally reflect the revision requests sent to the authors. To that end, the second submission must be accompanied by a cover letter mapping each revision request to specific parts of the paper. The absence of this cover letter is basis for the paper's rejection.

The second and final reviewing phase assesses how the concrete revision requests have been acted upon by the authors, and whether the final paper maintains, or even improves, the level of contributions of the original submission. Revisions that significantly lessen the contributions of the work may lead to the paper's rejection.

Submission

OOPSLA 2013 submissions must conform to both the ACM Policy on Prior Publication and Simultaneous Submissions and the SIGPLAN Republication Policy.

Format, Typesetting

Submissions should use the SIGPLAN Proceedings Format, 10 point font. Note that by default the SIGPLAN Proceedings Format produces papers in 9 point font. If you are formatting your paper using LaTeX, you will need to set the 10pt option in the \documentclass command. If you are formatting your paper using Word, you may wish to use the provided Word template that provides support for this font size. Please include page numbers in your submission. Setting the preprint option in the LaTeX \documentclass command generates page numbers. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible.

Page Limit

To ensure that papers stay focused on their core contributions, the main part of the paper (including bibliographic references) should be no longer than 14 pages. There is no page limit for appendices, and, therefore, for the overall submission. If the paper is accepted, the final submission will be limited to 20 pages, including appendices.

Additional Supporting Materials

Authors are strongly encouraged to provide addenda that support the claims and findings in the papers. These addenda can take the following forms:

  • Spreadsheets with data
  • R/Matlab/Shell Scripts
  • Raw survey answers (properly anonymized)
  • Virtual boxes with all necessary software installed for running prototypes
  • Instructions for installing and running prototypes off of code repositories

Additionally, papers submitted to OOPSLA that were previously rejected in other conferences can include as addenda the reviews from those previous submissions. In case the reviewers disclosed their identities in those reviews, that information must be removed.

Addenda can be submitted in two ways: (1) as appendices in the paper; (2) in a URL provided in the paper to one single file hosted in a 3rd party service, such as Google Docs or Dropbox.

These additional supporting materials are to be seen by the paper reviewers, if they wish to do so. Like the papers themselves, these addenda will remain confidential and will not be used beyond the purpose of reviewing and verifying the claims and findings in the papers.

Artifact Evaluation

Authors of papers accepted in the first phase will be invited to formally submit these supporting materials to the Artifact Evaluation process. The Artifact Evaluation process, also new this year, is run by a separate committee whose task is to assess how the artifacts support the work described in the papers. This submission is voluntary and will not influence the final decision regarding the papers. Papers that go through the Artifact Evaluation process successfully will receive a seal of approval printed on the papers themselves.

Authors of accepted papers are encouraged to make these materials publicly available upon publication of the proceedings, by including them as "source materials" in the ACM Digital Library.

For More Information

For additional information, clarification, or answers to questions please contact the OOPSLA Chair, Cristina V. Lopes