Splash Experience reports are all about how we create practical software systems that solve real-world problems. Meant to be strongly aligned with the focus of the Wavefront program, we seek papers discussing the use of those technologies as opposed to their creation. How have they made you more successful? What do you differently now? This is your chance to convince your peers that you have found a better way. Preference will be given to papers that report on production software in use by real customers.
While this year’s main focus is on using the forward looking technologies in the Wavefront program, we all know that experience is broader than that. Realistically, many of us are creating functional systems in other areas using today’s tools. And doing so quite successfully. What have you learned that may help your peers avoid obstacles? What stories do you have to tell? We anticipate offering one or more sessions on more traditional software development and encourage you to share your experiences.
All accepted papers will be presented at the Splash conference, published in the Splash conference proceedings and will become permanent entires in the ACM Digital Library.
Call for papers
We seek submissions from practicing developers describing solutions and techniques they have put into use in real-world systems. This is your chance to communicate with your peers and help them overcome their own obstacles. In that spirit the selection process has been designed to aid authors who have little or no experience in presenting at conferences while at the same time smoothing the path for those that have presented before.
This process starts with your submission. We will accept outlines, extended abstracts, or complete papers. Please include a primary contact with your submission including e-mail address, postal address, and telephone numbers. After a brief review we will conduct a short phone interview with you to discuss your paper and answer any questions you may have. Your paper will then be reviewed in detail by several committee members. Acceptance will be based on relevance, technical quality, applicability of your work, and so on. If accepted you will be notified by the date shown in the summary box. At that time you will be assigned a mentor familiar with the conference and the style of presentation we expect. Make good use of your mentor! Your mentor is there to help you craft a professional paper and an enjoyable and informative presentation. This is an iterative process that will culminate in a final paper that is typically 5 to 10 pages in length and a presentation that is typically 20 minutes long.
Authors may choose to submit either a detailed outline, extended abstract or complete paper. All submissions are evaluated for conditional acceptance subject to successful participation in a shepherding process that produces a final paper. A program committee member will act as mentor to authors as they prepare their final paper. The mentor must approve the final paper. Authors who have not previously published conference papers are strongly encouraged to submit their work and join us in this process. Your submission is your chance to convince us of the relevance of your work. An extended abstract followed by the shepherding process is an excellent way for less experienced authors to get their works published and presented.
Submissions must conform to both the ACM Policy on Prior Publication and Simultaneous Submissions and the SIGPLAN Republication Policy.
For additional information, clarification, or answers to questions please contact the Experience Reports Chair, Tim O’Connor, at firstname.lastname@example.org.
|A Case Study for Prioritizing Features in Environments with Multiple Stakeholders|
|A Regression Testing Framework for Financial Time-Series Databases|
|Classifiers: A simple framework for accelerating application development|
A: David RaalDOI
|Coping with Distance: An Empirical Study of Communication on the Jazz Platform|
|Crossfire - Multiprocess, Cross-Browser, Open-Web Debugging Protocol|
|Harnessing Collective Software Development|
A: Luis ArtolaDOI
|Moving back to Scrum and scaling to Scrum of Scrums in less than one year|
|Virtual Machines with Sharable Operating System|