<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>DSpace Collection:</title>
    <link>http://hdl.handle.net/1880/45347</link>
    <description />
    <pubDate>Fri, 24 May 2013 09:42:02 GMT</pubDate>
    <dc:date>2013-05-24T09:42:02Z</dc:date>
    <item>
      <title>Refactoring References for Library Migration - Appendix</title>
      <link>http://hdl.handle.net/1880/47840</link>
      <description>Title: Refactoring References for Library Migration - Appendix
Authors: Kapur, Puneet; Cossette, Brad; Walker, Robert J.
Abstract: This report is a companion to the paper “Refactoring&#xD;
References for Library Migration” published at the ACM&#xD;
SIGPLAN International Conference on Systems, Programming,&#xD;
Languages, and Applications: Software for Humanity&#xD;
(SPLASH) 2010. It provides the detailed results mentioned&#xD;
therein.</description>
      <pubDate>Wed, 09 Jun 2010 17:24:11 GMT</pubDate>
      <guid isPermaLink="false">http://hdl.handle.net/1880/47840</guid>
      <dc:date>2010-06-09T17:24:11Z</dc:date>
    </item>
    <item>
      <title>Communication, Collaboration, and Bugs:  The Social Nature of Issue Tracking in Software Engineering</title>
      <link>http://hdl.handle.net/1880/47309</link>
      <description>Title: Communication, Collaboration, and Bugs:  The Social Nature of Issue Tracking in Software Engineering
Authors: Bertram, Dane; Voida, Amy; Greenberg, Saul; Walker, Robert
Abstract: Issue tracking systems help organizations manage issue&#xD;
reporting, assignment, tracking, resolution, and archiving.&#xD;
Traditionally, it is the Software Engineering community&#xD;
that researches issue tracking systems, where software&#xD;
defects are reported and tracked as ‘bug reports’ within an&#xD;
archival database. Yet issue tracking is fundamentally a&#xD;
social process and, as such, it is important to understand the&#xD;
design and use of issue tracking systems from that&#xD;
perspective. Consequently, we conducted a qualitative&#xD;
study of the use of issue tracking systems by small,&#xD;
collocated software development teams. We found that an&#xD;
issue tracker is not just a database for tracking bugs,&#xD;
features, and inquiries, but also a focal point for&#xD;
communication and coordination for many stakeholders&#xD;
within and beyond the software team. Customers, project&#xD;
managers, quality assurance personnel, and programmers&#xD;
all contribute to the shared knowledge and persistent&#xD;
communication that exists within the issue tracking system.&#xD;
We articulate various real-world practices surrounding issue&#xD;
trackers and offer design implications for future systems.</description>
      <pubDate>Tue, 16 Jun 2009 15:50:52 GMT</pubDate>
      <guid isPermaLink="false">http://hdl.handle.net/1880/47309</guid>
      <dc:date>2009-06-16T15:50:52Z</dc:date>
    </item>
    <item>
      <title>The End-to-End Use of Source Code Examples: An Exploratory Study - Appendix</title>
      <link>http://hdl.handle.net/1880/47297</link>
      <description>Title: The End-to-End Use of Source Code Examples: An Exploratory Study - Appendix
Authors: Holmes, Reid; Cottrell, Rylan; Walker, Robert; Denzinger, Joerg
Abstract: This appendix contains the details of our case studies outlined&#xD;
in our paper for the 2009 International Conference on&#xD;
Software Maintenance, as well as an expanded discussion&#xD;
section. The reader is directed to the main paper for introduction,&#xD;
motivation, and related work.</description>
      <pubDate>Mon, 15 Jun 2009 17:54:07 GMT</pubDate>
      <guid isPermaLink="false">http://hdl.handle.net/1880/47297</guid>
      <dc:date>2009-06-15T17:54:07Z</dc:date>
    </item>
    <item>
      <title>A Lightweight Approach to Technical Risk Estimation via  Probabilistic 
Impact Analysis</title>
      <link>http://hdl.handle.net/1880/46089</link>
      <description>Title: A Lightweight Approach to Technical Risk Estimation via  Probabilistic 
Impact Analysis
Authors: Walker, Robert J.; Holmes, Reid; Hedgeland, Ian; Kapur, Puneet; Smith, Andrew
Abstract: An evolutionary development approach is increasingly commonplace in 
industry but presents increased difficulties in risk management,  for both 
technical and organizational reasons. In this context, technical  risk is the 
product of the probability of a technical event and the cost of  that event. 
This paper presents a technique for more objectively assessing and 
communicating technical risk in an evolutionary development  setting that (1) 
operates atop weaklyestimated knowledge of the changes to be  made, (2)
analyzes  the past change history and current structure of a system to 
estimate the  probability of change propagation, and (3) can be discussed 
vertically within  an organization both with development staff and high-level 
management. A tool  realizing this technique has been developed for the Eclipse
IDE.</description>
      <pubDate>Wed, 15 Feb 2006 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://hdl.handle.net/1880/46089</guid>
      <dc:date>2006-02-15T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

