<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 18px; font-family: Calibri, sans-serif; "><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; "><br></span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; ">******** Paper submission deadline extended to June 12, 2011 ********<br><br>International Conference on Runtime Verification (RV 2011)<br>September 27 - 30, 2011<br>San Francisco, California, USA</span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; ">at the Historic Fairmont Hotel</span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; "><br><a href="http://rv2011.eecs.berkeley.edu/" target="_blank" style="color: rgb(195, 57, 11); "></a></span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; "><a href="http://rv2011.eecs.berkeley.edu/" target="_blank" style="color: rgb(195, 57, 11); ">http://rv2011.eecs.berkeley.<wbr>edu/</a><br><br>Runtime verification (RV) is concerned with monitoring and<br>analysis of software or hardware system executions. The field is<br>often referred to under different names, such as runtime<br>verification, runtime monitoring, runtime checking, runtime<br>reflection, runtime analysis, dynamic analysis, runtime symbolic<br>analysis, trace analysis, log file analysis, etc. RV can be used<br>for many purposes, such as security or safety policy monitoring,<br>debugging, testing, verification, validation, profiling, fault<br>protection, behavior modification (e.g., recovery), etc. A<br>running system can be abstractly regarded as a generator of<br>execution traces, i.e., sequences of relevant states or<br>events. Traces can be processed in various ways, e.g., checked<br>against formal specifications, analyzed with special algorithms,<br>visualized, etc. Topics of interest include, but are not limited<br>to:<br><br>* program instrumentation techniques<br>* specification languages for writing monitors<br>* dynamic program slicing<br>* record-and-replay<br>* trace simplification for debugging<br>* extraction of monitors from specifications<br>* APIs for writing monitors<br>* programming language constructs for monitoring<br>* model-based monitoring and reconfiguration<br>* the use of aspect oriented programming for dynamic analysis<br>* algorithmic solutions to minimize runtime monitoring impact<br>* combination of static and dynamic analysis<br>* full program verification based on runtime verification<br>* intrusion detection, security policies, policy enforcement<br>* log file analysis<br>* model-based test oracles<br>* observation-based debugging techniques<br>* fault detection and recovery<br>* model-based integrated health management and diagnosis<br>* program steering and adaptation<br>* dynamic concurrency analysis<br>* dynamic specification mining<br>* metrics and statistical information gathered during runtime<br>* program execution visualization<br>* data structure repair for error recovery<br>* parallel algorithms for efficient monitoring<br>* monitoring for effective fault localization and program repair<br><br>The RV series of events started in 2001, as an annual workshop.<br>The RV'01 to RV'05 proceedings were published in ENTCS. Since<br>2006, the RV proceedings have been published in LNCS. In year<br>2010, RV became an international conference. Links to past RV<br>events can be found at the permanent URL:</span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; "><br> <a href="http://runtime-verification.org/" target="_blank" style="color: rgb(195, 57, 11); ">http://runtime-verification.<wbr>org</a><br><br><br>INVITED SPEAKERS<br><br>Dawson Engler, Stanford University<br> Title: "Making Finite Verification of Raw C Code Easier than Writing a Test Case"<br><br>Cormac Flanagan, University of California, Santa Cruz<br> Title: "Efficient and Precise Dynamic Detection of Destructive Races"<br><br>Wolfgang Grieskamp, Google<br> Title: "Utilizing Protocol Contracts for Verifying Services in the Cloud"<br><br>Sharad Malik, Princeton University<br> Title: "Runtime Verification: A Computer Architecture Perspective"<br><br>Vern Paxson, University of California, Berkeley<br> Title: "Approaches and Challenges for Detecting Network Attacks in Real-Time"<br><br>Steven P. Reiss, Brown University<br> Title: "What is My Program Doing? Program Dynamics in Programmer's Terms"<br><br><br>PAPER SUBMISSION<br><br>RV will have two research paper categories: regular and short<br>papers. Papers in both categories will be reviewed by the<br>conference Program Committee.<br><br>* Regular papers (up to 15 pages) should present original<br> unpublished results. Applications of runtime verification are<br> particularly welcome. A Best Paper Award (USD 300) will be<br> offered.<br><br>* Short papers (up to 5 pages) may present novel but not<br> necessarily thoroughly worked out ideas, for example emerging<br> runtime verification techniques and applications, or techniques<br> and applications that establish relationships between runtime<br> verification and other domains. Accepted short papers will be<br> presented in special short talk (5-10 minutes) and poster<br> sessions.<br><br>In addition to short and regular papers, tool demonstration papers<br>and tutorial proposals are welcome.<br><br>* Tool demonstration papers (up to 5 pages) should briefly<br> introduce the problem solved by the tool and give the outline<br> of the demonstration. A Best Tool Award (USD 200) will be<br> offered.<br><br>* Tutorial proposals (up to 2 pages) on any of the topics above,<br> as well as on topics at the boundary between RV and other<br> domains, are welcome. Accepted tutorials will be allocated up<br> to 15 pages in the conference proceedings. Tutorial<br> presentations will be at least 2 hours.<br><br>All accepted papers, including tutorial and tool papers, will<br>appear in the LNCS proceedings. Submitted papers must use the<br>LNCS style. At least one author of each accepted paper must<br>attend RV'11 to present the paper. Papers must be submitted<br>electronically using the EasyChair system. A link to the<br>electronic submission page will be made available on the RV'11<br>web page.<br><br><br>IMPORTANT DATES<br><br>June 12, 2011 - Submission of regular and short papers (Firm Deadline)<br>June 12, 2011 - Submission of tutorial and tool demonstration proposals<br>July 24, 2011 - Notification for regular, short, and tool papers<br>August 21, 2011 - Submission of camera-ready versions of accepted papers<br>September 27-30, 2011 - RV 2011 Conference and tutorials<br><br><br>ORGANIZERS<br><br>Programme committee chairs:<br>Sarfraz Khurshid (University of Texas at Austin, USA)<br>Koushik Sen (University of California at Berkeley, USA)<br><br>Local organization chairs:<br>Jacob Burnim (University of California at Berkeley, USA)<br>Nicholas Jalbert (University of California at Berkeley, USA)<br><br><br>PROGRAM COMMITTEE<br><br>Howard Barringer (University of Manchester, UK)<br>Eric Bodden (Technical University Darmstadt, Germany)<br>Rance Cleaveland (University of Maryland, USA)<br>Mads Dam (Kungliga Tekniska högskolan, Sweden)<br>Brian Demsky (University of California at Irvine, USA)<br>Bernd Finkbeiner (Saarland University, Germany)<br>Cormac Flanagan (University of California at Santa Cruz, USA)<br>Patrice Godefroid (Microsoft Research Redmond, USA)<br>Jean Goubault-Larrecq (ENS Cachan, France)<br>Susanne Graf (Verimag, France)<br>Radu Grosu (State University of New York at Stony Brook, USA)<br>Lars Grunske (University of Kaiserslautern, Germany)<br>Aarti Gupta (NEC Laboratories America, USA)<br>Rajiv Gupta (University of California at Riverside, USA)<br>Klaus Havelund (NASA/JPL, USA)<br>Mats Heimdahl (University of Minnesota, USA)<br>Gerard Holzmann (NASA/JPL, USA)<br>Sarfraz Khurshid (University of Texas at Austin, USA) (co-chair)<br>Viktor Kuncak (École Polytechnique Fédérale De Lausanne, Switzerland)<br>Kim Larsen (Aalborg University, Denmark)<br>Martin Leucker (University of Luebeck, Germany)<br>Rupak Majumdar (Max Planck Institute Germany and University of California<br>at Los Angeles USA)<br>Greg Morrisett (Harvard University, USA)<br>Mayur Naik (Intel Berkeley Labs, USA)<br>Brian Nielsen (Aalborg University, Denmark)<br>Klaus Ostermann (University of Marburg, Germany)<br>Corina Pasareanu (NASA Ames, USA)<br>Wim De Pauw (IBM T. J. Watson, USA)<br>Doron Peled (Bar Ilan University, Israel)<br>Suzette Person (NASA Langley, USA)<br>Gilles Pokam (Intel, Santa Clara, USA)<br>Shaz Qadeer (Microsoft Research Redmond, USA)<br>Derek Rayside (University of Waterloo, Canada)<br>Grigore Rosu (University of Illinois at Urbana-Champaign, USA)<br>Wolfram Schulte (Microsoft Research Redmond, USA)<br>Manu Sridharan (IBM T. J. Watson, USA)<br>Koushik Sen (University of California, Berkeley, USA) (co-chair)<br>Peter Sestoft (IT University of Copenhagen, Denmark)<br>Scott Smolka (State University of New York at Stony Brook, USA)<br>Oleg Sokolsky (University of Pennsylvania, USA)<br>Mana Taghdiri (Karlsruhe Institute of Technology, Germany)<br>Serdar Tasiran (Koc University, Turkey)<br>Nikolai Tillmann (Microsoft Research Redmond, USA)<br>Shmuel Ur (Shmuel Ur Innovation, Israel)<br>Willem Visser (University of Stellenbosch, South Africa)<br>Mahesh Viswanathan (University of Illinois at Urbana-Champaign, USA)<br>Xiangyu Zhang (Purdue University, USA)<br><br><br>RV STEERING COMMITTEE<br><br>Howard Barringer (University of Manchester, UK)<br>Klaus Havelund (NASA/JPL, USA)<br>Gerard Holzmann (NASA/JPL, USA)<br>Insup Lee (University of Pennsylvania, USA)<br>Grigore Rosu (University of Illinois at Urbana-Champaign, USA)<br>Oleg Sokolsky (University of Pennsylvania, USA)<br></span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; "><br></span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; font-family: arial, sans-serif; "><br></span></div></body></html>