<node id="51721">
  <nid>51721</nid>
  <type>news</type>
  <uid>
    <user id="27154"><![CDATA[27154]]></user>
  </uid>
  <created>1265752014</created>
  <changed>1475895912</changed>
  <title><![CDATA[CSS Wins Distinguished Paper Award At ISSTA'06]]></title>
  <body><![CDATA[<p><strong>(July 26, 2006)--</strong>Computing Science &amp; Systems (CSS) Assistant Professor Yannis Smaragdakis and Ph.D. student Christoph Csallner wrote "DSD-Crasher: a Hybrid Analysis Tool for Bug Finding," and won one of only two distinguished paper awards at this year's International Symposium on Software Testing and Analysis (ISSTA).</p>
<p>DSD-Crasher is a bug finding tool that follows a three-step approach to program analysis:<br />(D) Captures the program’s intended execution behavior with dynamic invariant detection.            <br />(S) Statically analyzes the program within the restricted input domain to explore many paths.<br />(D) Automatically generates test cases that focus on verifying the results of the static analysis.</p>
<p>Therefore, DSD-Crasher's confirmed results are never false positives as opposed to the high false positive rate inherent in conservative static analysis. Smaragdakis and Csallner say their three-step approach yields benefits compared to past two-step combinations in the literature. "In our evaluation with third-party applications, we demonstrate higher precision over tools that lack a dynamic step and higher efficiency over tools that lack a static step."</p>
<p>ISSTA'06 is a premier conference in software testing and software analysis, and included over 150 attendees and 100 submissions this year. To view CSS' distinguished paper, <a href="http://www.cc.gatech.edu/~yannis/issta06.pdf" target="_blank">click here</a>.</p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2006-07-26T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>Computing Science &amp; Systems Assistant Professor Yannis Smaragdakis and Ph.D. student Christoph Csallner won one of only two distinguished paper awards at the International Symposium on Software Testing and Analysis.</p>]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>47223</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>47223</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[College of Computing]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata>
      <![CDATA[]]>
  </field_userdata>
</node>
