{"id":338813,"date":"2009-07-19T16:01:54","date_gmt":"2009-07-19T23:01:54","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/research\/?post_type=msr-event&#038;p=338813"},"modified":"2025-08-06T12:03:02","modified_gmt":"2025-08-06T19:03:02","slug":"international-workshop-defects-large-software-systems-defects-2009","status":"publish","type":"msr-event","link":"https:\/\/www.microsoft.com\/en-us\/research\/event\/international-workshop-defects-large-software-systems-defects-2009\/","title":{"rendered":"International Workshop on Defects in Large Software Systems (DEFECTS 2009)"},"content":{"rendered":"\n\n<div class=\"conM \">\n<div class=\"conM \">\n<p align=\"left\"><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.martplaza.com\/\" target=\"_blank\">Holiday Inn Chicago Mart Plaza<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><br \/>\n350 West Mart Center Drive <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/maps.live.com\/?v=2&where1=350 W Mart Center Dr, Chicago, IL 60654&encType=1\" target=\"_blank\">(map)<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><br \/>\nChicago, IL 60654, USA<br \/>\nCo-located with <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.cse.msu.edu\/issta09\" target=\"_blank\">ISSTA 2009<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>.<\/p>\n<\/div>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<div class=\"conM \">\n<p align=\"left\"><em>This page is for archival purposes. Some links might be broken.<\/em><\/p>\n<h1>News<\/h1>\n<p>Registration is open.\u00a0<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.cse.msu.edu\/issta09\/#Registration\" target=\"_blank\">Early registration<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> ends on 2009-06-19. Register now!<br \/>\nProgram is\u00a0online. (2009-06-05)<\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Program<\/h1>\n<h3>9:00-10:30\u00a0 \u00a0Keynote<\/h3>\n<p>Bill Pugh. Defects that matter: Lessons from the Trenches<\/p>\n<p dir=\"ltr\" align=\"left\">&#8220;As part of the talk, I&#8217;ll summarize the May 2009 FindBugs fixit in which 700 engineers at Google looked at 4,000 FindBugs warnings on Google&#8217;s java codebase. 300 of the engineers supplied a total of more than 9,000 classifications of issues, and more than 80% of the classifications were should fix or must fix. More than 1,500 of the issues were removed from Google&#8217;s code base over several days. I&#8217;ll talk about how we designed and conducted the fixit, and what we expected and learned about cost effective removal of defects at Google.&#8221; <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/rmc-stage\/en-us\/events\/defects2009\/keynote.aspx\" target=\"_blank\">read the full abstract&#8230;<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><\/p>\n<p><em>To find out more about the creator of FindBugs and five-time JavaOne rock star, visit <\/em><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.cs.umd.edu\/~pugh\/\" target=\"_blank\"><em>Bill Pugh&#8217;s homepage<\/em><span class=\"sr-only\"> (opens in new tab)<\/span><\/a><em>.\u00a0<\/em><\/p>\n<h3>10:30-11:00\u00a0\u00a0\u00a0Coffee Break<\/h3>\n<h3>11:00-12:30\u00a0 \u00a0Empirical Studies<\/h3>\n<p>Wes Masri, Rawad Abou-Assi, Marwa El-Ghali and Nour AL-Fatairi. An Empirical Study of the Factors that Reduce the Effectiveness of Coverage-based Fault Localization<\/p>\n<p>Thomas Panas and Daniel Quinlan.\u00a0Techniques for Software Quality Analysis of Binaries: Applied to Windows and Linux<\/p>\n<p>Nathaniel Ayewah and Bill Pugh. Using Checklists to Review Static Analysis Warnings<\/p>\n<p>Prasanth Anbalagan and Mladen Vouk. &#8220;Days of the Week&#8221; Effect in Predicting the Time taken to Fix Defects [Short Paper]<\/p>\n<p class=\"smallText\">(Regular paper = 25 minutes. Short paper = 15 minutes)<\/p>\n<h3>12:30-14:00\u00a0\u00a0\u00a0Lunch Break<\/h3>\n<h3>14:00-15:30\u00a0 \u00a0&#8220;Unconference&#8221;<\/h3>\n<p>More details soon.<\/p>\n<h3>15:30-16:00\u00a0 \u00a0Coffee Break<\/h3>\n<h3>16:00-17:30\u00a0 \u00a0Program Analysis<\/h3>\n<p>Cristina Cifuentes, Christian Hoermann, Nathan Keynes, Lian Li, Simon Long, Erica Mealy, Michael Mounteney and Bernhard Scholz. BegBunch &#8212; Benchmarking for C Bug Detection Tools<\/p>\n<p>Ian Darwin. AnnaBot: A Static Verifier for Java Annotation Usages<\/p>\n<p>Daryl Shannon, Indradeep Ghosh, Sree Rajan and Sarfraz Khurshid. Efficient Symbolic Execution of Strings for Validating Web Applications<\/p>\n<p>Fadi Zaraket and Wes Masri. Property Based Coverage Criterion [Short Paper]<\/p>\n<p class=\"smallText\">(Regular paper = 25 minutes. Short paper = 15 minutes)<\/p>\n<h3>17:30-17:35\u00a0\u00a0 Workshop Wrap-up<\/h3>\n<\/div>\n<div class=\"conM \">\n<h1>Call for Papers<\/h1>\n<p>Bugs are everywhere in today&#8217;s software and because of the huge economic damage they are actively studied by research. In program analysis, researchers develop defect detection tools that identify anomalies in programs and report them as possible defects. Defect localization takes a given failure and identifies the cause of the defect. In empirical software engineering, researchers identify factors that correlate with defects and build prediction models to effectively allocate resources for quality assurance to the parts of the software that need it most. Most of this research is conducted on medium-sized open-source projects and rarely used in industry. In the long-term human and social issues will gain importance when analyzing defects, however, there is only little research in this area so far.<\/p>\n<p>The goal of this one-day workshop is to connect the different research communities with each other and with industry. The workshop will provide a forum for researchers as well as practitioners to discuss issues related to all aspects of bugs. Researchers can present their tools and techniques and make them accessible to industry. Participants from industry can share their experiences and help identifying new and promising research directions.<\/p>\n<p>Papers may address issues along the general themes, including but not limited to the following:<\/p>\n<ul>\n<li>Techniques to detect, locate, or predict defects<\/li>\n<li>Evaluation and comparison of techniques and models related to defects<\/li>\n<li>Empirical studies of defects<\/li>\n<li>Types of defects that occur in software<\/li>\n<li>Evolution of defects over time<\/li>\n<li>Tools for post-deployment defect detection and reporting<\/li>\n<li>Defect prioritization and presentation<\/li>\n<li>Prevalence of false positives or benign defects<\/li>\n<li>Cost models for defects<\/li>\n<li>Mining information from defect databases and version control archives<\/li>\n<li>User interface issues for defect tools<\/li>\n<li>Experience using certain techniques to identify or predict defects<\/li>\n<li>Human and social issues related to defects<\/li>\n<\/ul>\n<p>We expect the workshop to be a forum for exploratory work as well as continuing work. The workshop will also cover a broad range of topics and thus be an ideal venue for newcomers to research on defects. Also we expect several practitioners from industry and hope to foster collaboration between academia and industry.<\/p>\n<p>Accepted papers will be included in the DEFECTS proceedings published in the ACM Digital Library.<\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Submissions<\/h1>\n<p>For presentation at the workshop, we will solicit three kinds of submissions:<\/p>\n<ul>\n<li><b>Short papers (2 pages)<\/b> will be expected to discuss controversial issues in the field, or describe interesting or thought-provoking ideas that are not yet fully developed.<\/li>\n<li><b>Research papers (5 pages)<\/b> will be expected to describe new research results and have a higher degree of technical rigor than short papers.<\/li>\n<li><b>Experience papers (5 pages)<\/b> should describe case studies in an industrial setting or provide a critical discussion of experiences gained in software development projects.<\/li>\n<\/ul>\n<p>Papers must follow the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/sigs\/publications\/proceedings-templates\">ACM conference format<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> and must not exceed the page limits mentioned above, including figures and references. All submissions must be in English. Papers must be submitted electronically, in PDF format, using the\u00a0<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.easychair.org\/conferences\/?conf=defects2009\" target=\"_blank\">submission site<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> hosted by EasyChair.<\/p>\n<p>Three members of the program committee will review each submission and select the papers to be presented at the workshop.<\/p>\n<p>It is the desire of the organizers that discussion of research at the workshop does not preclude publication of closely related material at conferences or journals. Authors of accepted papers will be able to choose an <b>&#8220;abstract only&#8221;<\/b> option, where only the abstract of the paper will be published in the workshop proceedings.<\/p>\n<\/div>\n<p>&nbsp;<span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<div>\n<h1>Defects that matter: Lessons from the Trenches<\/h1>\n<p><em>Bill Pugh, University of Maryland & Google<\/em><\/p>\n<p>Except for limited, rare circumstances, software is never perfect. Large production scale software contains numerous defects\/mistakes, and bug databases contain hundreds or thousands of open bug reports. Despite this, software mostly satisfies the needs of its users, many defects do not actually cause the application to significantly misbehave, and developers find that the pressure to develop and ship new software and features is as strong as the pressure to lower the number of defects in the software.<\/p>\n<p>This basic point isn&#8217;t appreciated by much of the research in the field of software defect detection. The key question is not whether or not a tool can find a potential mistake or defect software. Rather, the question is whether having developers spend time using a new tool or technique, rather than spending that time on other software quality efforts, will result in a net improvement in the quality and timeliness of the software.<\/p>\n<p>The key using tools to improve software quality is to understand the potential cost of different kinds of defects, the cost of using a tool to find those defects, and the cost and ability of other software quality techniques (e.g., testing) to find those defects instead. All of these questions\/issues vary by project\/situation.<\/p>\n<p>As part of the talk, I&#8217;ll summarize the May 2009 FindBugs fixit in which 700 engineers at Google looked at 4,000 FindBugs warnings on Google&#8217;s java codebase. 300 of the engineers supplied a total of more than 9,000 classifications of issues, and more than 80% of the classifications were should fix or must fix. More than 1,500 of the issues were removed from Google&#8217;s code base over several days. I&#8217;ll talk about how we designed and conducted the fixit, and what we expected and learned about cost effective removal of defects at Google.<\/p>\n<p><em>To find out more about the creator of FindBugs and five-time JavaOne rock star, visit <\/em><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.cs.umd.edu\/~pugh\/\"><em>Bill Pugh&#8217;s homepage<\/em><span class=\"sr-only\"> (opens in new tab)<\/span><\/a><em>.<\/em><\/p>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<div class=\"conM \">\n<h1>Important Dates<\/h1>\n<\/div>\n<div class=\"conM \">\n<p>Early registration (<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.cse.msu.edu\/issta09\/#Registration\">registration site<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>):<br \/>\nFriday, June 19, 2009<\/p>\n<p>Workshop:<br \/>\nSunday, July 19, 2009<\/p>\n<h1>Past Dates<\/h1>\n<p>Submissions (<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.easychair.org\/conferences\/?conf=defects2009\">submission site<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>):<br \/>\nThursday, April 23, 2009 <b>*extended*<\/b><\/p>\n<p>Author notfication:<br \/>\nFriday, May 8, 2009 <b>*sent*<\/b><\/p>\n<p>Camera-ready (<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/rmc-stage\/en-us\/events\/defects2009\/cameraready.aspx\">instructions<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>):<br \/>\nFriday, May 15, 2009 <b>*updated*<\/b><\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Workshop Organizers<\/h1>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/pages.cs.wisc.edu\/~liblit\/\" target=\"_blank\">Ben Liblit<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, University of Wisconsin\u2013Madison, USA<\/p>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/rmc-stage\/en-us\/people\/nachin\/default.aspx\" target=\"_blank\">Nachiappan Nagappan<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, Microsoft Research, USA<\/p>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/rmc-stage\/en-us\/people\/tzimmer\/default.aspx\" target=\"_blank\">Thomas Zimmermann<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, Microsoft Research, USA <b>(contact)<\/b><\/p>\n<h1>Program Committee<\/h1>\n<p>Lionel C. Briand, Simula Research Laboratory\u00a0& University of Oslo, Norway<\/p>\n<p>Bojan Cukic, West Virginia University, USA<\/p>\n<p>Stephen Freund, Williams College, USA<\/p>\n<p>Ahmed E. Hassan, Queen&#8217;s University, Canada<\/p>\n<p>Sung Kim, Hong Kong University of Science and Technology, China<\/p>\n<p>Lucas Layman, NRC Institute for Information Technology, Canada<\/p>\n<p>Audris Mockus, Avaya Labs Research, USA<\/p>\n<p>Mangala Gowri Nanda, IBM India Research Laboratory, India<\/p>\n<p>Thomas Ostrand, AT&T Labs &#8211; Research, USA<\/p>\n<p>Martin Pinzger, Delft University of Technology, The Netherlands<\/p>\n<p>Rahul Premraj, Vrije Universiteit Amsterdam, The Netherlands<\/p>\n<p>Bill Pugh, University of Maryland & Google, USA<\/p>\n<p>Koushik Sen, University of California, Berkeley, USA<\/p>\n<p>Eran Yahav, IBM T.J. Watson Research Center, USA<\/p>\n<p>Andreas Zeller, Saarland University, Germany<\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Earlier Workshops<\/h1>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/pages.cpsc.ucalgary.ca\/~zimmerth\/defects-2008\/\" target=\"_blank\">DEFECTS 2008<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><\/p>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<div>\n<div class=\"title deM \">Camera-ready copy<\/div>\n<div class=\"conM \">\n<p>In addition to all details described below, we remind you to incorporate the suggestions from the reviewers. The PC members took time away from their busy schedules to help improve the content and presentation of your submissions. Please respect their work and revise your papers accordingly.<\/p>\n<p>The submission of the camera-ready copy consists of the following <b>three steps<\/b>.<\/p>\n<h1>STEP 1: Formatting Your Paper<\/h1>\n<p>Prepare your paper using the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.sheridanprinting.com\/typedept\/issta.htm\">ISSTA formatting instructions<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> from Sheridan Printing. Use these instructions only with respect to formatting guidelines, not with respect to what files to submit, how to submit them, etc. In particular, you <b>should not submit anything to Sheridan Printing<\/b>.<\/p>\n<h4>Classification information<\/h4>\n<p>Per Sheridan\u2019s standard instructions, all papers must include complete <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/class\/1998\/\">ACM classification information<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, with categories & subject descriptors, general terms, and keywords. You may have omitted this in your original submission, but it is required for all final papers.<\/p>\n<h4>LaTeX document class<\/h4>\n<p>LaTeX users: use the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.sheridanprinting.com\/typedept\/sig-alternate.cls\">sig-alternate.cls<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> class file. Do not use ACM\u2019s strict acm_proc_article-sp.cls. Because sig-alternate.cls is slightly more compact, you may find that you have a bit more room than expected.<\/p>\n<h4>Page limit<\/h4>\n<p>The page limit for regular papers is\u00a05 pages including everything.<br \/>\nThe page limit for short papers is 2 pages including everything.<\/p>\n<h4>No page numbers<\/h4>\n<p>Do not include page numbers. We will add these later.<\/p>\n<h4>Copyright statement and conference information<\/h4>\n<p>Add the standard ACM copyright statement and conference information to the lower-left corner of your first page. LaTeX users can do this by adding the following lines after begin{document}:<\/p>\n<blockquote>\n<pre>conferenceinfo{DEFECTS'09,} {July 19, 2009, Chicago, Illinois, USA.}<\/pre>\n<p>CopyrightYear{2009}<br \/>\ncrdata{978-1-60558-654-0\/09\/07}<\/p>\n<p>&nbsp;<\/p><\/blockquote>\n<p>Word users, please insert the ACM copyright statement (see below) in position at the bottom\/left of the first page of your submission. This statement should appear in 8 pt. Times New Roman, justified text, with the conference name DEFECTS&#8217;09 italicized.<\/p>\n<blockquote><p>Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and\/or a fee.<br \/>\n<em>DEFECTS&#8217;09<\/em>, July 19, 2009, Chicago, Illinois, USA.<br \/>\nCopyright 2009 ACM 978-1-60558-654-0\/08\/07&#8230;$5.00.<\/p><\/blockquote>\n<h4>Paper size<\/h4>\n<p>The DEFECTS proceedings will be printed on US letter paper, not A4. Set your page size accordingly.<\/p>\n<p><b>PDFLaTeX<\/b> users can do this by adding the following lines before begin{document}:<\/p>\n<blockquote>\n<pre>pdfpagewidth=8.5in\r\npdfpageheight=11in<\/pre>\n<\/blockquote>\n<pre><\/pre>\n<p><b>Dvips<\/b> users can do this by adding the following lines before begin{document}:<\/p>\n<blockquote>\n<pre>special{papersize=11in,8.5in}<\/pre>\n<\/blockquote>\n<pre><\/pre>\n<h4>Font embedding<\/h4>\n<p>Pay special attention to the issues related to Type 1 fonts when creating your PostScript file, as described in the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/sigs\/publications\/sigfaq#a14\">ACM Proceedings <span class=\"sr-only\"> (opens in new tab)<\/span><\/a><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/sigs\/publications\/sigfaq#a14\">FAQ<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>.<\/p>\n<h1>STEP 2: Submitting Your Final Paper<\/h1>\n<h4>Naming your files<\/h4>\n<p>The final PostScript rendering of your paper must be named<\/p>\n<blockquote>\n<pre>\u201cfirst_author_last_name.ps\u201d.<\/pre>\n<\/blockquote>\n<pre><\/pre>\n<p>For example: smith.ps where smith is the first author\u2019s last name, no caps. Use lower case throughout file names; <b>do not capitalize<\/b>. There are special rules for special names:<\/p>\n<ol>\n<li>A hyphenated last name remains hyphenated, e.g., Wu Yen-Tse \u21d2 yen-tse.<\/li>\n<li>A compound last name takes an underscore, e.g., Robert van Gulik \u21d2 van_gulik.<\/li>\n<li>Accents in last names are omitted, e.g., Wolfgang Schr\u00f5der \u21d2 schroder (not schroeder) or Jean Ren\u00e9 \u21d2 rene (not renee).<\/li>\n<li>Apostrophes in last names are replaced by an underscore, e.g., Elizabeth O\u2019Neill \u21d2 o_neill.<\/li>\n<li>Retain periods after abbreviated name elements, e.g. Melissa St. Thomas \u21d2 st._thomas.<\/li>\n<li>Drop suffixes from file names, e.g., Corbin Jones Jr. \u21d2 jones.<\/li>\n<\/ol>\n<p><b>Note:<\/b> Middle names are not used in the file names. There may be cases that are ambiguous, and you\u2019ll have to decide whether a word is a middle name or a piece of the last name. For example: Jose Perez Garcia \u21d2 perez_garcia.<\/p>\n<h4>Submission<\/h4>\n<p><b>E-mail your final paper to tzimmer AT microsoft DOT com<\/b>.<\/p>\n<p>Set the subject of your message to<\/p>\n<blockquote><p>\u201cDEFECTS 2009 paper: first_author_last_name.ps\u201d<\/p><\/blockquote>\n<p>where first_author_last_name is the first author\u2019s last name as described above. Include a <b>PostScript rendering<\/b> of your paper as an attachment. Do not send PDF, Word, LaTeX, or other formats. The camera-ready final copy of your paper is due by <b>Friday, May 15, 2009.<\/b><\/p>\n<p>Do not submit your paper to Sheridan or ACM directly.<\/p>\n<h1>STEP 3: Copyright Forms<\/h1>\n<p>You must also submit a signed <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/publications\/copyright_form\">ACM copyright form<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, using one of the following methods. Either<\/p>\n<ul>\n<li><b>fax<\/b> completed forms to +1 (425) 936-7329, <b>attn: TZIMMER,<\/b> or<\/li>\n<li><b>e-mail<\/b> completed forms to tzimmer AT microsoft DOT com<\/li>\n<\/ul>\n<p><b>Copyright forms are due by Friday, May 15, 2009.<\/b><\/p>\n<p class=\"smallText\">(These instructions are based on original work by <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/pages.cs.wisc.edu\/~liblit\/\" target=\"_blank\">Ben Liblit<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>.)<\/p>\n<\/div>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Holiday Inn Chicago Mart Plaza (opens in new tab) 350 West Mart Center Drive (map) (opens in new tab) Chicago, IL 60654, USA Co-located with ISSTA 2009 (opens in new tab). Opens in a new tab This page is for archival purposes. Some links might be broken. News Registration is open.\u00a0Early registration (opens in new [&hellip;]<\/p>\n","protected":false},"featured_media":0,"template":"","meta":{"msr-url-field":"","msr-podcast-episode":"","msrModifiedDate":"","msrModifiedDateEnabled":false,"ep_exclude_from_search":false,"_classifai_error":"","msr_startdate":"2009-07-19","msr_enddate":"","msr_location":"Chicago, IL","msr_expirationdate":"","msr_event_recording_link":"","msr_event_link":"","msr_event_link_redirect":false,"msr_event_time":"","msr_hide_region":false,"msr_private_event":true,"msr_hide_image_in_river":0,"footnotes":""},"research-area":[13560],"msr-region":[197900],"msr-event-type":[197941],"msr-video-type":[],"msr-locale":[268875],"msr-program-audience":[],"msr-post-option":[],"msr-impact-theme":[],"class_list":["post-338813","msr-event","type-msr-event","status-publish","hentry","msr-research-area-programming-languages-software-engineering","msr-region-north-america","msr-event-type-conferences","msr-locale-en_us"],"msr_about":"<!-- wp:msr\/event-details {\"title\":\"International Workshop on Defects in Large Software Systems (DEFECTS 2009)\",\"backgroundColor\":\"grey\"} \/-->\n\n<!-- wp:msr\/content-tabs --><!-- wp:msr\/content-tab {\"title\":\"About\"} --><!-- wp:freeform --><div class=\"conM \">\n<div class=\"conM \">\n<p align=\"left\"><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.martplaza.com\/\" target=\"_blank\">Holiday Inn Chicago Mart Plaza<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><br \/>\n350 West Mart Center Drive <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/maps.live.com\/?v=2&amp;where1=350 W Mart Center Dr, Chicago, IL 60654&amp;encType=1\" target=\"_blank\">(map)<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><br \/>\nChicago, IL 60654, USA<br \/>\nCo-located with <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.cse.msu.edu\/issta09\" target=\"_blank\">ISSTA 2009<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>.<\/p>\n<\/div>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<div class=\"conM \">\n<p align=\"left\"><em>This page is for archival purposes. Some links might be broken.<\/em><\/p>\n<h1>News<\/h1>\n<p>Registration is open.\u00a0<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.cse.msu.edu\/issta09\/#Registration\" target=\"_blank\">Early registration<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> ends on 2009-06-19. Register now!<br \/>\nProgram is\u00a0online. (2009-06-05)<\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Program<\/h1>\n<h3>9:00-10:30\u00a0 \u00a0Keynote<\/h3>\n<p>Bill Pugh. Defects that matter: Lessons from the Trenches<\/p>\n<p dir=\"ltr\" align=\"left\">&#8220;As part of the talk, I&#8217;ll summarize the May 2009 FindBugs fixit in which 700 engineers at Google looked at 4,000 FindBugs warnings on Google&#8217;s java codebase. 300 of the engineers supplied a total of more than 9,000 classifications of issues, and more than 80% of the classifications were should fix or must fix. More than 1,500 of the issues were removed from Google&#8217;s code base over several days. I&#8217;ll talk about how we designed and conducted the fixit, and what we expected and learned about cost effective removal of defects at Google.&#8221; <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/rmc-stage\/en-us\/events\/defects2009\/keynote.aspx\" target=\"_blank\">read the full abstract&#8230;<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><\/p>\n<p><em>To find out more about the creator of FindBugs and five-time JavaOne rock star, visit <\/em><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.cs.umd.edu\/~pugh\/\" target=\"_blank\"><em>Bill Pugh&#8217;s homepage<\/em><span class=\"sr-only\"> (opens in new tab)<\/span><\/a><em>.\u00a0<\/em><\/p>\n<h3>10:30-11:00\u00a0\u00a0\u00a0Coffee Break<\/h3>\n<h3>11:00-12:30\u00a0 \u00a0Empirical Studies<\/h3>\n<p>Wes Masri, Rawad Abou-Assi, Marwa El-Ghali and Nour AL-Fatairi. An Empirical Study of the Factors that Reduce the Effectiveness of Coverage-based Fault Localization<\/p>\n<p>Thomas Panas and Daniel Quinlan.\u00a0Techniques for Software Quality Analysis of Binaries: Applied to Windows and Linux<\/p>\n<p>Nathaniel Ayewah and Bill Pugh. Using Checklists to Review Static Analysis Warnings<\/p>\n<p>Prasanth Anbalagan and Mladen Vouk. &#8220;Days of the Week&#8221; Effect in Predicting the Time taken to Fix Defects [Short Paper]<\/p>\n<p class=\"smallText\">(Regular paper = 25 minutes. Short paper = 15 minutes)<\/p>\n<h3>12:30-14:00\u00a0\u00a0\u00a0Lunch Break<\/h3>\n<h3>14:00-15:30\u00a0 \u00a0&#8220;Unconference&#8221;<\/h3>\n<p>More details soon.<\/p>\n<h3>15:30-16:00\u00a0 \u00a0Coffee Break<\/h3>\n<h3>16:00-17:30\u00a0 \u00a0Program Analysis<\/h3>\n<p>Cristina Cifuentes, Christian Hoermann, Nathan Keynes, Lian Li, Simon Long, Erica Mealy, Michael Mounteney and Bernhard Scholz. BegBunch &#8212; Benchmarking for C Bug Detection Tools<\/p>\n<p>Ian Darwin. AnnaBot: A Static Verifier for Java Annotation Usages<\/p>\n<p>Daryl Shannon, Indradeep Ghosh, Sree Rajan and Sarfraz Khurshid. Efficient Symbolic Execution of Strings for Validating Web Applications<\/p>\n<p>Fadi Zaraket and Wes Masri. Property Based Coverage Criterion [Short Paper]<\/p>\n<p class=\"smallText\">(Regular paper = 25 minutes. Short paper = 15 minutes)<\/p>\n<h3>17:30-17:35\u00a0\u00a0 Workshop Wrap-up<\/h3>\n<\/div>\n<div class=\"conM \">\n<h1>Call for Papers<\/h1>\n<p>Bugs are everywhere in today&#8217;s software and because of the huge economic damage they are actively studied by research. In program analysis, researchers develop defect detection tools that identify anomalies in programs and report them as possible defects. Defect localization takes a given failure and identifies the cause of the defect. In empirical software engineering, researchers identify factors that correlate with defects and build prediction models to effectively allocate resources for quality assurance to the parts of the software that need it most. Most of this research is conducted on medium-sized open-source projects and rarely used in industry. In the long-term human and social issues will gain importance when analyzing defects, however, there is only little research in this area so far.<\/p>\n<p>The goal of this one-day workshop is to connect the different research communities with each other and with industry. The workshop will provide a forum for researchers as well as practitioners to discuss issues related to all aspects of bugs. Researchers can present their tools and techniques and make them accessible to industry. Participants from industry can share their experiences and help identifying new and promising research directions.<\/p>\n<p>Papers may address issues along the general themes, including but not limited to the following:<\/p>\n<ul>\n<li>Techniques to detect, locate, or predict defects<\/li>\n<li>Evaluation and comparison of techniques and models related to defects<\/li>\n<li>Empirical studies of defects<\/li>\n<li>Types of defects that occur in software<\/li>\n<li>Evolution of defects over time<\/li>\n<li>Tools for post-deployment defect detection and reporting<\/li>\n<li>Defect prioritization and presentation<\/li>\n<li>Prevalence of false positives or benign defects<\/li>\n<li>Cost models for defects<\/li>\n<li>Mining information from defect databases and version control archives<\/li>\n<li>User interface issues for defect tools<\/li>\n<li>Experience using certain techniques to identify or predict defects<\/li>\n<li>Human and social issues related to defects<\/li>\n<\/ul>\n<p>We expect the workshop to be a forum for exploratory work as well as continuing work. The workshop will also cover a broad range of topics and thus be an ideal venue for newcomers to research on defects. Also we expect several practitioners from industry and hope to foster collaboration between academia and industry.<\/p>\n<p>Accepted papers will be included in the DEFECTS proceedings published in the ACM Digital Library.<\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Submissions<\/h1>\n<p>For presentation at the workshop, we will solicit three kinds of submissions:<\/p>\n<ul>\n<li><b>Short papers (2 pages)<\/b> will be expected to discuss controversial issues in the field, or describe interesting or thought-provoking ideas that are not yet fully developed.<\/li>\n<li><b>Research papers (5 pages)<\/b> will be expected to describe new research results and have a higher degree of technical rigor than short papers.<\/li>\n<li><b>Experience papers (5 pages)<\/b> should describe case studies in an industrial setting or provide a critical discussion of experiences gained in software development projects.<\/li>\n<\/ul>\n<p>Papers must follow the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/sigs\/publications\/proceedings-templates\">ACM conference format<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> and must not exceed the page limits mentioned above, including figures and references. All submissions must be in English. Papers must be submitted electronically, in PDF format, using the\u00a0<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/www.easychair.org\/conferences\/?conf=defects2009\" target=\"_blank\">submission site<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> hosted by EasyChair.<\/p>\n<p>Three members of the program committee will review each submission and select the papers to be presented at the workshop.<\/p>\n<p>It is the desire of the organizers that discussion of research at the workshop does not preclude publication of closely related material at conferences or journals. Authors of accepted papers will be able to choose an <b>&#8220;abstract only&#8221;<\/b> option, where only the abstract of the paper will be published in the workshop proceedings.<\/p>\n<\/div>\n<p>&nbsp;<span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<!-- \/wp:freeform --><!-- \/wp:msr\/content-tab --><!-- wp:msr\/content-tab {\"title\":\"Keynote\"} --><!-- wp:freeform --><div>\n<h1>Defects that matter: Lessons from the Trenches<\/h1>\n<p><em>Bill Pugh, University of Maryland &amp; Google<\/em><\/p>\n<p>Except for limited, rare circumstances, software is never perfect. Large production scale software contains numerous defects\/mistakes, and bug databases contain hundreds or thousands of open bug reports. Despite this, software mostly satisfies the needs of its users, many defects do not actually cause the application to significantly misbehave, and developers find that the pressure to develop and ship new software and features is as strong as the pressure to lower the number of defects in the software.<\/p>\n<p>This basic point isn&#8217;t appreciated by much of the research in the field of software defect detection. The key question is not whether or not a tool can find a potential mistake or defect software. Rather, the question is whether having developers spend time using a new tool or technique, rather than spending that time on other software quality efforts, will result in a net improvement in the quality and timeliness of the software.<\/p>\n<p>The key using tools to improve software quality is to understand the potential cost of different kinds of defects, the cost of using a tool to find those defects, and the cost and ability of other software quality techniques (e.g., testing) to find those defects instead. All of these questions\/issues vary by project\/situation.<\/p>\n<p>As part of the talk, I&#8217;ll summarize the May 2009 FindBugs fixit in which 700 engineers at Google looked at 4,000 FindBugs warnings on Google&#8217;s java codebase. 300 of the engineers supplied a total of more than 9,000 classifications of issues, and more than 80% of the classifications were should fix or must fix. More than 1,500 of the issues were removed from Google&#8217;s code base over several days. I&#8217;ll talk about how we designed and conducted the fixit, and what we expected and learned about cost effective removal of defects at Google.<\/p>\n<p><em>To find out more about the creator of FindBugs and five-time JavaOne rock star, visit <\/em><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.cs.umd.edu\/~pugh\/\"><em>Bill Pugh&#8217;s homepage<\/em><span class=\"sr-only\"> (opens in new tab)<\/span><\/a><em>.<\/em><\/p>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<!-- \/wp:freeform --><!-- \/wp:msr\/content-tab --><!-- wp:msr\/content-tab {\"title\":\"Dates \/ Organization\"} --><!-- wp:freeform --><div class=\"conM \">\n<h1>Important Dates<\/h1>\n<\/div>\n<div class=\"conM \">\n<p>Early registration (<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.cse.msu.edu\/issta09\/#Registration\">registration site<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>):<br \/>\nFriday, June 19, 2009<\/p>\n<p>Workshop:<br \/>\nSunday, July 19, 2009<\/p>\n<h1>Past Dates<\/h1>\n<p>Submissions (<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.easychair.org\/conferences\/?conf=defects2009\">submission site<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>):<br \/>\nThursday, April 23, 2009 <b>*extended*<\/b><\/p>\n<p>Author notfication:<br \/>\nFriday, May 8, 2009 <b>*sent*<\/b><\/p>\n<p>Camera-ready (<a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/rmc-stage\/en-us\/events\/defects2009\/cameraready.aspx\">instructions<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>):<br \/>\nFriday, May 15, 2009 <b>*updated*<\/b><\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Workshop Organizers<\/h1>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/pages.cs.wisc.edu\/~liblit\/\" target=\"_blank\">Ben Liblit<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, University of Wisconsin\u2013Madison, USA<\/p>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/rmc-stage\/en-us\/people\/nachin\/default.aspx\" target=\"_blank\">Nachiappan Nagappan<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, Microsoft Research, USA<\/p>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/rmc-stage\/en-us\/people\/tzimmer\/default.aspx\" target=\"_blank\">Thomas Zimmermann<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, Microsoft Research, USA <b>(contact)<\/b><\/p>\n<h1>Program Committee<\/h1>\n<p>Lionel C. Briand, Simula Research Laboratory\u00a0&amp; University of Oslo, Norway<\/p>\n<p>Bojan Cukic, West Virginia University, USA<\/p>\n<p>Stephen Freund, Williams College, USA<\/p>\n<p>Ahmed E. Hassan, Queen&#8217;s University, Canada<\/p>\n<p>Sung Kim, Hong Kong University of Science and Technology, China<\/p>\n<p>Lucas Layman, NRC Institute for Information Technology, Canada<\/p>\n<p>Audris Mockus, Avaya Labs Research, USA<\/p>\n<p>Mangala Gowri Nanda, IBM India Research Laboratory, India<\/p>\n<p>Thomas Ostrand, AT&amp;T Labs &#8211; Research, USA<\/p>\n<p>Martin Pinzger, Delft University of Technology, The Netherlands<\/p>\n<p>Rahul Premraj, Vrije Universiteit Amsterdam, The Netherlands<\/p>\n<p>Bill Pugh, University of Maryland &amp; Google, USA<\/p>\n<p>Koushik Sen, University of California, Berkeley, USA<\/p>\n<p>Eran Yahav, IBM T.J. Watson Research Center, USA<\/p>\n<p>Andreas Zeller, Saarland University, Germany<\/p>\n<\/div>\n<div><\/div>\n<div class=\"conM \">\n<h1>Earlier Workshops<\/h1>\n<p><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/pages.cpsc.ucalgary.ca\/~zimmerth\/defects-2008\/\" target=\"_blank\">DEFECTS 2008<span class=\"sr-only\"> (opens in new tab)<\/span><\/a><\/p>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<!-- \/wp:freeform --><!-- \/wp:msr\/content-tab --><!-- wp:msr\/content-tab {\"title\":\"Camera Ready Instructions\"} --><!-- wp:freeform --><div>\n<div class=\"title deM \">Camera-ready copy<\/div>\n<div class=\"conM \">\n<p>In addition to all details described below, we remind you to incorporate the suggestions from the reviewers. The PC members took time away from their busy schedules to help improve the content and presentation of your submissions. Please respect their work and revise your papers accordingly.<\/p>\n<p>The submission of the camera-ready copy consists of the following <b>three steps<\/b>.<\/p>\n<h1>STEP 1: Formatting Your Paper<\/h1>\n<p>Prepare your paper using the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.sheridanprinting.com\/typedept\/issta.htm\">ISSTA formatting instructions<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> from Sheridan Printing. Use these instructions only with respect to formatting guidelines, not with respect to what files to submit, how to submit them, etc. In particular, you <b>should not submit anything to Sheridan Printing<\/b>.<\/p>\n<h4>Classification information<\/h4>\n<p>Per Sheridan\u2019s standard instructions, all papers must include complete <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/class\/1998\/\">ACM classification information<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, with categories &amp; subject descriptors, general terms, and keywords. You may have omitted this in your original submission, but it is required for all final papers.<\/p>\n<h4>LaTeX document class<\/h4>\n<p>LaTeX users: use the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.sheridanprinting.com\/typedept\/sig-alternate.cls\">sig-alternate.cls<span class=\"sr-only\"> (opens in new tab)<\/span><\/a> class file. Do not use ACM\u2019s strict acm_proc_article-sp.cls. Because sig-alternate.cls is slightly more compact, you may find that you have a bit more room than expected.<\/p>\n<h4>Page limit<\/h4>\n<p>The page limit for regular papers is\u00a05 pages including everything.<br \/>\nThe page limit for short papers is 2 pages including everything.<\/p>\n<h4>No page numbers<\/h4>\n<p>Do not include page numbers. We will add these later.<\/p>\n<h4>Copyright statement and conference information<\/h4>\n<p>Add the standard ACM copyright statement and conference information to the lower-left corner of your first page. LaTeX users can do this by adding the following lines after begin{document}:<\/p>\n<blockquote>\n<pre>conferenceinfo{DEFECTS'09,} {July 19, 2009, Chicago, Illinois, USA.}<\/pre>\n<p>CopyrightYear{2009}<br \/>\ncrdata{978-1-60558-654-0\/09\/07}<\/p>\n<p>&nbsp;<\/p><\/blockquote>\n<p>Word users, please insert the ACM copyright statement (see below) in position at the bottom\/left of the first page of your submission. This statement should appear in 8 pt. Times New Roman, justified text, with the conference name DEFECTS&#8217;09 italicized.<\/p>\n<blockquote><p>Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and\/or a fee.<br \/>\n<em>DEFECTS&#8217;09<\/em>, July 19, 2009, Chicago, Illinois, USA.<br \/>\nCopyright 2009 ACM 978-1-60558-654-0\/08\/07&#8230;$5.00.<\/p><\/blockquote>\n<h4>Paper size<\/h4>\n<p>The DEFECTS proceedings will be printed on US letter paper, not A4. Set your page size accordingly.<\/p>\n<p><b>PDFLaTeX<\/b> users can do this by adding the following lines before begin{document}:<\/p>\n<blockquote>\n<pre>pdfpagewidth=8.5in\r\npdfpageheight=11in<\/pre>\n<\/blockquote>\n<pre><\/pre>\n<p><b>Dvips<\/b> users can do this by adding the following lines before begin{document}:<\/p>\n<blockquote>\n<pre>special{papersize=11in,8.5in}<\/pre>\n<\/blockquote>\n<pre><\/pre>\n<h4>Font embedding<\/h4>\n<p>Pay special attention to the issues related to Type 1 fonts when creating your PostScript file, as described in the <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/sigs\/publications\/sigfaq#a14\">ACM Proceedings <span class=\"sr-only\"> (opens in new tab)<\/span><\/a><a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/sigs\/publications\/sigfaq#a14\">FAQ<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>.<\/p>\n<h1>STEP 2: Submitting Your Final Paper<\/h1>\n<h4>Naming your files<\/h4>\n<p>The final PostScript rendering of your paper must be named<\/p>\n<blockquote>\n<pre>\u201cfirst_author_last_name.ps\u201d.<\/pre>\n<\/blockquote>\n<pre><\/pre>\n<p>For example: smith.ps where smith is the first author\u2019s last name, no caps. Use lower case throughout file names; <b>do not capitalize<\/b>. There are special rules for special names:<\/p>\n<ol>\n<li>A hyphenated last name remains hyphenated, e.g., Wu Yen-Tse \u21d2 yen-tse.<\/li>\n<li>A compound last name takes an underscore, e.g., Robert van Gulik \u21d2 van_gulik.<\/li>\n<li>Accents in last names are omitted, e.g., Wolfgang Schr\u00f5der \u21d2 schroder (not schroeder) or Jean Ren\u00e9 \u21d2 rene (not renee).<\/li>\n<li>Apostrophes in last names are replaced by an underscore, e.g., Elizabeth O\u2019Neill \u21d2 o_neill.<\/li>\n<li>Retain periods after abbreviated name elements, e.g. Melissa St. Thomas \u21d2 st._thomas.<\/li>\n<li>Drop suffixes from file names, e.g., Corbin Jones Jr. \u21d2 jones.<\/li>\n<\/ol>\n<p><b>Note:<\/b> Middle names are not used in the file names. There may be cases that are ambiguous, and you\u2019ll have to decide whether a word is a middle name or a piece of the last name. For example: Jose Perez Garcia \u21d2 perez_garcia.<\/p>\n<h4>Submission<\/h4>\n<p><b>E-mail your final paper to tzimmer AT microsoft DOT com<\/b>.<\/p>\n<p>Set the subject of your message to<\/p>\n<blockquote><p>\u201cDEFECTS 2009 paper: first_author_last_name.ps\u201d<\/p><\/blockquote>\n<p>where first_author_last_name is the first author\u2019s last name as described above. Include a <b>PostScript rendering<\/b> of your paper as an attachment. Do not send PDF, Word, LaTeX, or other formats. The camera-ready final copy of your paper is due by <b>Friday, May 15, 2009.<\/b><\/p>\n<p>Do not submit your paper to Sheridan or ACM directly.<\/p>\n<h1>STEP 3: Copyright Forms<\/h1>\n<p>You must also submit a signed <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" target=\"_blank\" href=\"http:\/\/www.acm.org\/publications\/copyright_form\">ACM copyright form<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>, using one of the following methods. Either<\/p>\n<ul>\n<li><b>fax<\/b> completed forms to +1 (425) 936-7329, <b>attn: TZIMMER,<\/b> or<\/li>\n<li><b>e-mail<\/b> completed forms to tzimmer AT microsoft DOT com<\/li>\n<\/ul>\n<p><b>Copyright forms are due by Friday, May 15, 2009.<\/b><\/p>\n<p class=\"smallText\">(These instructions are based on original work by <a class=\"msr-external-link glyph-append glyph-append-open-in-new-tab glyph-append-xsmall\" href=\"http:\/\/pages.cs.wisc.edu\/~liblit\/\" target=\"_blank\">Ben Liblit<span class=\"sr-only\"> (opens in new tab)<\/span><\/a>.)<\/p>\n<\/div>\n<\/div>\n<p><span id=\"label-external-link\" class=\"sr-only\" aria-hidden=\"true\">Opens in a new tab<\/span><\/p>\n<!-- \/wp:freeform --><!-- \/wp:msr\/content-tab --><!-- \/wp:msr\/content-tabs -->","tab-content":[{"id":0,"name":"About","content":"<div class=\"conM \">\r\n<p align=\"left\"><em>This page is for archival purposes. Some links might be broken.<\/em><\/p>\r\n\r\n<h1>News<\/h1>\r\nRegistration is open.\u00a0<a href=\"http:\/\/www.cse.msu.edu\/issta09\/#Registration\" target=\"_self\">Early registration<\/a> ends on 2009-06-19. Register now!\r\nProgram is\u00a0online. (2009-06-05)\r\n\r\n<\/div>\r\n<div><\/div>\r\n<div class=\"conM \">\r\n<h1>Program<\/h1>\r\n<h3>9:00-10:30\u00a0 \u00a0Keynote<\/h3>\r\nBill Pugh. Defects that matter: Lessons from the Trenches\r\n<p dir=\"ltr\" align=\"left\">\"As part of the talk, I'll summarize the May 2009 FindBugs fixit in which 700 engineers at Google looked at 4,000 FindBugs warnings on Google's java codebase. 300 of the engineers supplied a total of more than 9,000 classifications of issues, and more than 80% of the classifications were should fix or must fix. More than 1,500 of the issues were removed from Google's code base over several days. I'll talk about how we designed and conducted the fixit, and what we expected and learned about cost effective removal of defects at Google.\" <a href=\"http:\/\/rmc-stage\/en-us\/events\/defects2009\/keynote.aspx\" target=\"_self\">read the full abstract...<\/a><\/p>\r\n<em>To find out more about the creator of FindBugs and five-time JavaOne rock star, visit <\/em><a href=\"http:\/\/www.cs.umd.edu\/~pugh\/\" target=\"_self\"><em>Bill Pugh's homepage<\/em><\/a><em>.\u00a0<\/em>\r\n<h3>10:30-11:00\u00a0\u00a0\u00a0Coffee Break<\/h3>\r\n<h3>11:00-12:30\u00a0 \u00a0Empirical Studies<\/h3>\r\nWes Masri, Rawad Abou-Assi, Marwa El-Ghali and Nour AL-Fatairi. An Empirical Study of the Factors that Reduce the Effectiveness of Coverage-based Fault Localization\r\n\r\nThomas Panas and Daniel Quinlan.\u00a0Techniques for Software Quality Analysis of Binaries: Applied to Windows and Linux\r\n\r\nNathaniel Ayewah and Bill Pugh. Using Checklists to Review Static Analysis Warnings\r\n\r\nPrasanth Anbalagan and Mladen Vouk. \"Days of the Week\" Effect in Predicting the Time taken to Fix Defects [Short Paper]\r\n<p class=\"smallText\">(Regular paper = 25 minutes. Short paper = 15 minutes)<\/p>\r\n\r\n<h3>12:30-14:00\u00a0\u00a0\u00a0Lunch Break<\/h3>\r\n<h3>14:00-15:30\u00a0 \u00a0\"Unconference\"<\/h3>\r\nMore details soon.\r\n<h3>15:30-16:00\u00a0 \u00a0Coffee Break<\/h3>\r\n<h3>16:00-17:30\u00a0 \u00a0Program Analysis<\/h3>\r\nCristina Cifuentes, Christian Hoermann, Nathan Keynes, Lian Li, Simon Long, Erica Mealy, Michael Mounteney and Bernhard Scholz. BegBunch -- Benchmarking for C Bug Detection Tools\r\n\r\nIan Darwin. AnnaBot: A Static Verifier for Java Annotation Usages\r\n\r\nDaryl Shannon, Indradeep Ghosh, Sree Rajan and Sarfraz Khurshid. Efficient Symbolic Execution of Strings for Validating Web Applications\r\n\r\nFadi Zaraket and Wes Masri. Property Based Coverage Criterion [Short Paper]\r\n<p class=\"smallText\">(Regular paper = 25 minutes. Short paper = 15 minutes)<\/p>\r\n\r\n<h3>17:30-17:35\u00a0\u00a0 Workshop Wrap-up<\/h3>\r\n<\/div>\r\n<div class=\"conM \">\r\n<h1>Call for Papers<\/h1>\r\nBugs are everywhere in today's software and because of the huge economic damage they are actively studied by research. In program analysis, researchers develop defect detection tools that identify anomalies in programs and report them as possible defects. Defect localization takes a given failure and identifies the cause of the defect. In empirical software engineering, researchers identify factors that correlate with defects and build prediction models to effectively allocate resources for quality assurance to the parts of the software that need it most. Most of this research is conducted on medium-sized open-source projects and rarely used in industry. In the long-term human and social issues will gain importance when analyzing defects, however, there is only little research in this area so far.\r\n\r\nThe goal of this one-day workshop is to connect the different research communities with each other and with industry. The workshop will provide a forum for researchers as well as practitioners to discuss issues related to all aspects of bugs. Researchers can present their tools and techniques and make them accessible to industry. Participants from industry can share their experiences and help identifying new and promising research directions.\r\n\r\nPapers may address issues along the general themes, including but not limited to the following:\r\n<ul>\r\n \t<li>Techniques to detect, locate, or predict defects<\/li>\r\n \t<li>Evaluation and comparison of techniques and models related to defects<\/li>\r\n \t<li>Empirical studies of defects<\/li>\r\n \t<li>Types of defects that occur in software<\/li>\r\n \t<li>Evolution of defects over time<\/li>\r\n \t<li>Tools for post-deployment defect detection and reporting<\/li>\r\n \t<li>Defect prioritization and presentation<\/li>\r\n \t<li>Prevalence of false positives or benign defects<\/li>\r\n \t<li>Cost models for defects<\/li>\r\n \t<li>Mining information from defect databases and version control archives<\/li>\r\n \t<li>User interface issues for defect tools<\/li>\r\n \t<li>Experience using certain techniques to identify or predict defects<\/li>\r\n \t<li>Human and social issues related to defects<\/li>\r\n<\/ul>\r\nWe expect the workshop to be a forum for exploratory work as well as continuing work. The workshop will also cover a broad range of topics and thus be an ideal venue for newcomers to research on defects. Also we expect several practitioners from industry and hope to foster collaboration between academia and industry.\r\n\r\nAccepted papers will be included in the DEFECTS proceedings published in the ACM Digital Library.\r\n\r\n<\/div>\r\n<div><\/div>\r\n<div class=\"conM \">\r\n<h1>Submissions<\/h1>\r\nFor presentation at the workshop, we will solicit three kinds of submissions:\r\n<ul>\r\n \t<li><b>Short papers (2 pages)<\/b> will be expected to discuss controversial issues in the field, or describe interesting or thought-provoking ideas that are not yet fully developed.<\/li>\r\n \t<li><b>Research papers (5 pages)<\/b> will be expected to describe new research results and have a higher degree of technical rigor than short papers.<\/li>\r\n \t<li><b>Experience papers (5 pages)<\/b> should describe case studies in an industrial setting or provide a critical discussion of experiences gained in software development projects.<\/li>\r\n<\/ul>\r\nPapers must follow the <a href=\"http:\/\/www.acm.org\/sigs\/publications\/proceedings-templates\">ACM conference format<\/a> and must not exceed the page limits mentioned above, including figures and references. All submissions must be in English. Papers must be submitted electronically, in PDF format, using the\u00a0<a href=\"http:\/\/www.easychair.org\/conferences\/?conf=defects2009\" target=\"_self\">submission site<\/a> hosted by EasyChair.\r\n\r\nThree members of the program committee will review each submission and select the papers to be presented at the workshop.\r\n\r\nIt is the desire of the organizers that discussion of research at the workshop does not preclude publication of closely related material at conferences or journals. Authors of accepted papers will be able to choose an <b>\"abstract only\"<\/b> option, where only the abstract of the paper will be published in the workshop proceedings.\r\n\r\n<\/div>\r\n&nbsp;"},{"id":1,"name":"Keynote","content":"<div>\r\n<h1>Defects that matter: Lessons from the Trenches<\/h1>\r\n<em>Bill Pugh, University of Maryland &amp; Google<\/em>\r\n\r\nExcept for limited, rare circumstances, software is never perfect. Large production scale software contains numerous defects\/mistakes, and bug databases contain hundreds or thousands of open bug reports. Despite this, software mostly satisfies the needs of its users, many defects do not actually cause the application to significantly misbehave, and developers find that the pressure to develop and ship new software and features is as strong as the pressure to lower the number of defects in the software.\r\n\r\nThis basic point isn't appreciated by much of the research in the field of software defect detection. The key question is not whether or not a tool can find a potential mistake or defect software. Rather, the question is whether having developers spend time using a new tool or technique, rather than spending that time on other software quality efforts, will result in a net improvement in the quality and timeliness of the software.\r\n\r\nThe key using tools to improve software quality is to understand the potential cost of different kinds of defects, the cost of using a tool to find those defects, and the cost and ability of other software quality techniques (e.g., testing) to find those defects instead. All of these questions\/issues vary by project\/situation.\r\n\r\nAs part of the talk, I'll summarize the May 2009 FindBugs fixit in which 700 engineers at Google looked at 4,000 FindBugs warnings on Google's java codebase. 300 of the engineers supplied a total of more than 9,000 classifications of issues, and more than 80% of the classifications were should fix or must fix. More than 1,500 of the issues were removed from Google's code base over several days. I'll talk about how we designed and conducted the fixit, and what we expected and learned about cost effective removal of defects at Google.\r\n\r\n<em>To find out more about the creator of FindBugs and five-time JavaOne rock star, visit <\/em><a href=\"http:\/\/www.cs.umd.edu\/~pugh\/\"><em>Bill Pugh's homepage<\/em><\/a><em>.<\/em>\r\n\r\n<\/div>"},{"id":2,"name":"Dates \/ Organization","content":"<div class=\"conM \">\r\n<h1>Important Dates<\/h1>\r\n<\/div>\r\n<div class=\"conM \">\r\n\r\nEarly registration (<a href=\"http:\/\/www.cse.msu.edu\/issta09\/#Registration\">registration site<\/a>):\r\nFriday, June 19, 2009\r\n\r\nWorkshop:\r\nSunday, July 19, 2009\r\n<h1>Past Dates<\/h1>\r\nSubmissions (<a href=\"http:\/\/www.easychair.org\/conferences\/?conf=defects2009\">submission site<\/a>):\r\nThursday, April 23, 2009 <b>*extended*<\/b>\r\n\r\nAuthor notfication:\r\nFriday, May 8, 2009 <b>*sent*<\/b>\r\n\r\nCamera-ready (<a href=\"http:\/\/rmc-stage\/en-us\/events\/defects2009\/cameraready.aspx\">instructions<\/a>):\r\nFriday, May 15, 2009 <b>*updated*<\/b>\r\n\r\n<\/div>\r\n<div><\/div>\r\n<div class=\"conM \">\r\n<h1>Workshop Organizers<\/h1>\r\n<a href=\"http:\/\/pages.cs.wisc.edu\/~liblit\/\" target=\"_self\">Ben Liblit<\/a>, University of Wisconsin\u2013Madison, USA\r\n\r\n<a href=\"http:\/\/rmc-stage\/en-us\/people\/nachin\/default.aspx\" target=\"_self\">Nachiappan Nagappan<\/a>, Microsoft Research, USA\r\n\r\n<a href=\"http:\/\/rmc-stage\/en-us\/people\/tzimmer\/default.aspx\" target=\"_self\">Thomas Zimmermann<\/a>, Microsoft Research, USA <b>(contact)<\/b>\r\n<h1>Program Committee<\/h1>\r\nLionel C. Briand, Simula Research Laboratory\u00a0&amp; University of Oslo, Norway\r\n\r\nBojan Cukic, West Virginia University, USA\r\n\r\nStephen Freund, Williams College, USA\r\n\r\nAhmed E. Hassan, Queen's University, Canada\r\n\r\nSung Kim, Hong Kong University of Science and Technology, China\r\n\r\nLucas Layman, NRC Institute for Information Technology, Canada\r\n\r\nAudris Mockus, Avaya Labs Research, USA\r\n\r\nMangala Gowri Nanda, IBM India Research Laboratory, India\r\n\r\nThomas Ostrand, AT&amp;T Labs - Research, USA\r\n\r\nMartin Pinzger, Delft University of Technology, The Netherlands\r\n\r\nRahul Premraj, Vrije Universiteit Amsterdam, The Netherlands\r\n\r\nBill Pugh, University of Maryland &amp; Google, USA\r\n\r\nKoushik Sen, University of California, Berkeley, USA\r\n\r\nEran Yahav, IBM T.J. Watson Research Center, USA\r\n\r\nAndreas Zeller, Saarland University, Germany\r\n\r\n<\/div>\r\n<div><\/div>\r\n<div class=\"conM \">\r\n<h1>Earlier Workshops<\/h1>\r\n<a href=\"http:\/\/pages.cpsc.ucalgary.ca\/~zimmerth\/defects-2008\/\" target=\"_self\">DEFECTS 2008<\/a>\r\n\r\n<\/div>"},{"id":3,"name":"Camera Ready Instructions","content":"<div>\r\n<div class=\"title deM \">Camera-ready copy<\/div>\r\n<div class=\"conM \">\r\n\r\nIn addition to all details described below, we remind you to incorporate the suggestions from the reviewers. The PC members took time away from their busy schedules to help improve the content and presentation of your submissions. Please respect their work and revise your papers accordingly.\r\n\r\nThe submission of the camera-ready copy consists of the following <b>three steps<\/b>.\r\n<h1>STEP 1: Formatting Your Paper<\/h1>\r\nPrepare your paper using the <a href=\"http:\/\/www.sheridanprinting.com\/typedept\/issta.htm\">ISSTA formatting instructions<\/a> from Sheridan Printing. Use these instructions only with respect to formatting guidelines, not with respect to what files to submit, how to submit them, etc. In particular, you <b>should not submit anything to Sheridan Printing<\/b>.\r\n<h4>Classification information<\/h4>\r\nPer Sheridan\u2019s standard instructions, all papers must include complete <a href=\"http:\/\/www.acm.org\/class\/1998\/\">ACM classification information<\/a>, with categories &amp; subject descriptors, general terms, and keywords. You may have omitted this in your original submission, but it is required for all final papers.\r\n<h4>LaTeX document class<\/h4>\r\nLaTeX users: use the <a href=\"http:\/\/www.sheridanprinting.com\/typedept\/sig-alternate.cls\">sig-alternate.cls<\/a> class file. Do not use ACM\u2019s strict acm_proc_article-sp.cls. Because sig-alternate.cls is slightly more compact, you may find that you have a bit more room than expected.\r\n<h4>Page limit<\/h4>\r\nThe page limit for regular papers is\u00a05 pages including everything.\r\nThe page limit for short papers is 2 pages including everything.\r\n<h4>No page numbers<\/h4>\r\nDo not include page numbers. We will add these later.\r\n<h4>Copyright statement and conference information<\/h4>\r\nAdd the standard ACM copyright statement and conference information to the lower-left corner of your first page. LaTeX users can do this by adding the following lines after \\begin{document}:\r\n<blockquote>\r\n<pre>\\conferenceinfo{DEFECTS'09,} {July 19, 2009, Chicago, Illinois, USA.}<\/pre>\r\n\\CopyrightYear{2009}\r\n\\crdata{978-1-60558-654-0\/09\/07}\r\n\r\n&nbsp;<\/blockquote>\r\nWord users, please insert the ACM copyright statement (see below) in position at the bottom\/left of the first page of your submission. This statement should appear in 8 pt. Times New Roman, justified text, with the conference name DEFECTS'09 italicized.\r\n<blockquote>Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and\/or a fee.\r\n<em>DEFECTS'09<\/em>, July 19, 2009, Chicago, Illinois, USA.\r\nCopyright 2009 ACM 978-1-60558-654-0\/08\/07...$5.00.<\/blockquote>\r\n<h4>Paper size<\/h4>\r\nThe DEFECTS proceedings will be printed on US letter paper, not A4. Set your page size accordingly.\r\n\r\n<b>PDFLaTeX<\/b> users can do this by adding the following lines before \\begin{document}:\r\n<blockquote>\r\n<pre>\\pdfpagewidth=8.5in\r\n\\pdfpageheight=11in<\/pre>\r\n<\/blockquote>\r\n<pre><\/pre>\r\n<b>Dvips<\/b> users can do this by adding the following lines before \\begin{document}:\r\n<blockquote>\r\n<pre>\\special{papersize=11in,8.5in}<\/pre>\r\n<\/blockquote>\r\n<pre><\/pre>\r\n<h4>Font embedding<\/h4>\r\nPay special attention to the issues related to Type 1 fonts when creating your PostScript file, as described in the <a href=\"http:\/\/www.acm.org\/sigs\/publications\/sigfaq#a14\">ACM Proceedings <\/a><a href=\"http:\/\/www.acm.org\/sigs\/publications\/sigfaq#a14\">FAQ<\/a>.\r\n<h1>STEP 2: Submitting Your Final Paper<\/h1>\r\n<h4>Naming your files<\/h4>\r\nThe final PostScript rendering of your paper must be named\r\n<blockquote>\r\n<pre>\u201cfirst_author_last_name.ps\u201d.<\/pre>\r\n<\/blockquote>\r\n<pre><\/pre>\r\nFor example: smith.ps where smith is the first author\u2019s last name, no caps. Use lower case throughout file names; <b>do not capitalize<\/b>. There are special rules for special names:\r\n<ol>\r\n \t<li>A hyphenated last name remains hyphenated, e.g., Wu Yen-Tse \u21d2 yen-tse.<\/li>\r\n \t<li>A compound last name takes an underscore, e.g., Robert van Gulik \u21d2 van_gulik.<\/li>\r\n \t<li>Accents in last names are omitted, e.g., Wolfgang Schr\u00f5der \u21d2 schroder (not schroeder) or Jean Ren\u00e9 \u21d2 rene (not renee).<\/li>\r\n \t<li>Apostrophes in last names are replaced by an underscore, e.g., Elizabeth O\u2019Neill \u21d2 o_neill.<\/li>\r\n \t<li>Retain periods after abbreviated name elements, e.g. Melissa St. Thomas \u21d2 st._thomas.<\/li>\r\n \t<li>Drop suffixes from file names, e.g., Corbin Jones Jr. \u21d2 jones.<\/li>\r\n<\/ol>\r\n<b>Note:<\/b> Middle names are not used in the file names. There may be cases that are ambiguous, and you\u2019ll have to decide whether a word is a middle name or a piece of the last name. For example: Jose Perez Garcia \u21d2 perez_garcia.\r\n<h4>Submission<\/h4>\r\n<b>E-mail your final paper to tzimmer AT microsoft DOT com<\/b>.\r\n\r\nSet the subject of your message to\r\n<blockquote>\u201cDEFECTS 2009 paper: first_author_last_name.ps\u201d<\/blockquote>\r\nwhere first_author_last_name is the first author\u2019s last name as described above. Include a <b>PostScript rendering<\/b> of your paper as an attachment. Do not send PDF, Word, LaTeX, or other formats. The camera-ready final copy of your paper is due by <b>Friday, May 15, 2009.<\/b>\r\n\r\nDo not submit your paper to Sheridan or ACM directly.\r\n<h1>STEP 3: Copyright Forms<\/h1>\r\nYou must also submit a signed <a href=\"http:\/\/www.acm.org\/publications\/copyright_form\">ACM copyright form<\/a>, using one of the following methods. Either\r\n<ul>\r\n \t<li><b>fax<\/b> completed forms to +1 (425) 936-7329, <b>attn: TZIMMER,<\/b> or<\/li>\r\n \t<li><b>e-mail<\/b> completed forms to tzimmer AT microsoft DOT com<\/li>\r\n<\/ul>\r\n<b>Copyright forms are due by Friday, May 15, 2009.<\/b>\r\n<p class=\"smallText\">(These instructions are based on original work by <a href=\"http:\/\/pages.cs.wisc.edu\/~liblit\/\" target=\"_self\">Ben Liblit<\/a>.)<\/p>\r\n\r\n<\/div>\r\n<\/div>"}],"msr_startdate":"2009-07-19","msr_enddate":"","msr_event_time":"","msr_location":"Chicago, IL","msr_event_link":"","msr_event_recording_link":"","msr_startdate_formatted":"July 19, 2009","msr_register_text":"Watch now","msr_cta_link":"","msr_cta_text":"","msr_cta_bi_name":"","featured_image_thumbnail":null,"event_excerpt":"This page is for archival purposes. Some links might be broken. News Registration is open.\u00a0Early registration ends on 2009-06-19. Register now! Program is\u00a0online. (2009-06-05) Program 9:00-10:30\u00a0 \u00a0Keynote Bill Pugh. Defects that matter: Lessons from the Trenches \"As part of the talk, I'll summarize the May 2009 FindBugs fixit in which 700 engineers at Google looked at 4,000 FindBugs warnings on Google's java codebase. 300 of the engineers supplied a total of more than 9,000 classifications&hellip;","msr_research_lab":[199565],"related-researchers":[],"msr_impact_theme":[],"related-academic-programs":[],"related-groups":[144860],"related-projects":[],"related-opportunities":[],"related-publications":[],"related-videos":[],"related-posts":[],"_links":{"self":[{"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-event\/338813","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-event"}],"about":[{"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/types\/msr-event"}],"version-history":[{"count":2,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-event\/338813\/revisions"}],"predecessor-version":[{"id":1147451,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-event\/338813\/revisions\/1147451"}],"wp:attachment":[{"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/media?parent=338813"}],"wp:term":[{"taxonomy":"msr-research-area","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/research-area?post=338813"},{"taxonomy":"msr-region","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-region?post=338813"},{"taxonomy":"msr-event-type","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-event-type?post=338813"},{"taxonomy":"msr-video-type","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-video-type?post=338813"},{"taxonomy":"msr-locale","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-locale?post=338813"},{"taxonomy":"msr-program-audience","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-program-audience?post=338813"},{"taxonomy":"msr-post-option","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-post-option?post=338813"},{"taxonomy":"msr-impact-theme","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/research\/wp-json\/wp\/v2\/msr-impact-theme?post=338813"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}