<?xml version="1.0" ?>
<!-- This file was exported from BibSonomy, http://www.bibsonomy.org -->

<bibliography>

<biblioentry xreflabel="citeulike:896153" id="citeulike:896153">
   <authorgroup>
       <author><firstname>A.</firstname><surname>Wilson</surname></author>
       <author><firstname>M.</firstname><surname>Burnett</surname></author>
       <author><firstname>L.</firstname><surname>Beckwith</surname></author>
       <author><firstname>O.</firstname><surname>Granatir</surname></author>
       <author><firstname>L.</firstname><surname>Casburn</surname></author>
       <author><firstname>C.</firstname><surname>Cook</surname></author>
       <author><firstname>M.</firstname><surname>Durham</surname></author>
       <author><firstname>G.</firstname><surname>Rothermel</surname></author> 
   </authorgroup>
<citetitle pubwork="article">Harnessing curiosity to increase correctness in end&#45;user programming</citetitle>





   <pubdate>2003</pubdate>  
   <abstract>
      <para>Despite their ability to help with program correctness&#44; assertions have been notoriously unpopular&#38;&#35;x2013;&#45;even with professional programmers. End&#45;user programmers seem even less likely to appreciate the value of assertions; yet end&#45;user programs suffer from serious correctness problems that assertions could help detect. This leads to the following question: can end users be enticed to enter assertions&#63; To investigate this question&#44; we have devised a curiosity&#45;centered approach to eliciting...
      </para>
   </abstract>
</biblioentry>
</bibliography>
