<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
   xmlns="http://purl.org/rss/1.0/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/"
   xmlns:dcterms="http://purl.org/dc/terms/"

>
<channel rdf:about="http://www.citeulike.org/about">
<pubDate>Thu, 21 Aug 2008 14:42:49 BST</pubDate>


	<title>CiteULike: lucaspanjer's Murphy</title>
	<description>CiteULike: lucaspanjer's Murphy</description>


	<link>http://www.citeulike.org/user/lucaspanjer/author/Murphy</link>
	<dc:publisher>CiteULike.org</dc:publisher>
	<dc:language>en-gb</dc:language>
	<dc:rights>Copyright &#169; 2004-2008 citeulike.org</dc:rights>
	<items>
    <rdf:Seq>
        <rdf:li rdf:resource="http://www.citeulike.org/user/lucaspanjer/article/1680925"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/lucaspanjer/article/1227998"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/lucaspanjer/article/952369"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/lucaspanjer/article/678834"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/lucaspanjer/article/882039"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/lucaspanjer/article/682724"/>

	</rdf:Seq>
	</items>
	</channel>


<item rdf:about="http://www.citeulike.org/user/lucaspanjer/article/1680925">
    <title>Recommending Emergent Teams</title>
    <link>http://www.citeulike.org/user/lucaspanjer/article/1680925</link>
    <description>&lt;i&gt;Mining Software Repositories, 2007. ICSE Workshops MSR '07. Fourth International Workshop on (2007), pp. 5-5.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To build successful complex software systems, developers must collaborate with each other to solve issues. To facilitate this collaboration, specialized tools, such as chat and screen sharing, are being integrated into development environments. Currently, these tools require a developer to maintain a list of other developers with whom they may wish to communicate and to determine who within this list has expertise for a specific situation. For large, dynamic projects, like several successful open-source projects, these requirements place an unreasonable burden on the developer. In this paper, we show how the structure of a team emerges from how developers change software artifacts. We introduce the Emergent Expertise Locator (EEL) that uses emergent team information to propose experts to a developer within their development environment as the developer works. We found that EEL produces, on average, results with higher precision and higher recall than an existing heuristic for expertise recommendation.</description>
    <dc:title>Recommending Emergent Teams</dc:title>

    <dc:creator>Shawn Minto</dc:creator>
    <dc:creator>Gail Murphy</dc:creator>
    <dc:identifier>doi:10.1109/MSR.2007.27</dc:identifier>
    <dc:source>Mining Software Repositories, 2007. ICSE Workshops MSR '07. Fourth International Workshop on (2007), pp. 5-5.</dc:source>
    <dc:date>2007-09-20T22:44:33-00:00</dc:date>
    <prism:publicationYear>2007</prism:publicationYear>
    <prism:publicationName>Mining Software Repositories, 2007. ICSE Workshops MSR '07. Fourth International Workshop on</prism:publicationName>
    <prism:startingPage>5</prism:startingPage>
    <prism:endingPage>5</prism:endingPage>
    <prism:category>emergent-team</prism:category>
    <prism:category>recommendation</prism:category>
    <prism:category>recommender</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/lucaspanjer/article/1227998">
    <title>Hipikat: recommending pertinent software development artifacts</title>
    <link>http://www.citeulike.org/user/lucaspanjer/article/1227998</link>
    <description>&lt;i&gt;(2003), pp. 408-418.&lt;/i&gt;</description>
    <dc:title>Hipikat: recommending pertinent software development artifacts</dc:title>

    <dc:creator>Davor Cubranic</dc:creator>
    <dc:creator>Gail Murphy</dc:creator>
    <dc:identifier>doi:10.1145/332040.332475</dc:identifier>
    <dc:source>(2003), pp. 408-418.</dc:source>
    <dc:date>2007-04-15T18:08:01-00:00</dc:date>
    <prism:publicationYear>2003</prism:publicationYear>
    <prism:startingPage>408</prism:startingPage>
    <prism:endingPage>418</prism:endingPage>
    <prism:publisher>IEEE Computer Society</prism:publisher>
    <prism:category>artifacts</prism:category>
    <prism:category>csc591-spring2007</prism:category>
    <prism:category>recommender</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/lucaspanjer/article/952369">
    <title>Using task context to improve programmer productivity</title>
    <link>http://www.citeulike.org/user/lucaspanjer/article/952369</link>
    <description>&lt;i&gt;(2006), pp. 1-11.&lt;/i&gt;</description>
    <dc:title>Using task context to improve programmer productivity</dc:title>

    <dc:creator>Mik Kersten</dc:creator>
    <dc:creator>Gail Murphy</dc:creator>
    <dc:identifier>doi:10.1145/1181775.1181777</dc:identifier>
    <dc:source>(2006), pp. 1-11.</dc:source>
    <dc:date>2006-11-20T00:03:16-00:00</dc:date>
    <prism:publicationYear>2006</prism:publicationYear>
    <prism:startingPage>1</prism:startingPage>
    <prism:endingPage>11</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>context</prism:category>
    <prism:category>csc591-spring2007</prism:category>
    <prism:category>doi</prism:category>
    <prism:category>filtering</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/lucaspanjer/article/678834">
    <title>Mylar: a degree-of-interest model for IDEs</title>
    <link>http://www.citeulike.org/user/lucaspanjer/article/678834</link>
    <description>&lt;i&gt;(2005), pp. 159-168.&lt;/i&gt;</description>
    <dc:title>Mylar: a degree-of-interest model for IDEs</dc:title>

    <dc:creator>Mik Kersten</dc:creator>
    <dc:creator>Gail Murphy</dc:creator>
    <dc:identifier>doi:10.1145/1052898.1052912</dc:identifier>
    <dc:source>(2005), pp. 159-168.</dc:source>
    <dc:date>2006-05-31T19:44:22-00:00</dc:date>
    <prism:publicationYear>2005</prism:publicationYear>
    <prism:startingPage>159</prism:startingPage>
    <prism:endingPage>168</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>csc591-spring2007</prism:category>
    <prism:category>doi</prism:category>
    <prism:category>filtering</prism:category>
    <prism:category>software-engineering</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/lucaspanjer/article/882039">
    <title>Hipikat: a project memory for software development</title>
    <link>http://www.citeulike.org/user/lucaspanjer/article/882039</link>
    <description>&lt;i&gt;Software Engineering, IEEE Transactions on, Vol. 31, No. 6. (2005), pp. 446-465.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Sociological and technical difficulties, such as a lack of informal encounters, can make it difficult for new members of noncollocated software development teams to learn from their more experienced colleagues. To address this situation, we have developed a tool, named Hipikat that provides developers with efficient and effective access to the group memory for a software development project that is implicitly formed by all of the artifacts produced during the development. This project memory is built automatically with little or no change to existing work practices. After describing the Hipikat tool, we present two studies investigating Hipikat's usefulness in software modification tasks. One study evaluated the usefulness of Hipikat's recommendations on a sample of 20 modification tasks performed on the Eclipse Java IDE during the development of release 2.1 of the Eclipse software. We describe the study, present quantitative measures of Hipikat's performance, and describe in detail three cases that illustrate a range of issues that we have identified in the results. In the other study, we evaluated whether software developers who are new to a project can benefit from the artifacts that Hipikat recommends from the project memory. We describe the study, present qualitative observations, and suggest implications of using project memory as a learning aid for project newcomers.</description>
    <dc:title>Hipikat: a project memory for software development</dc:title>

    <dc:creator>D Cubranic</dc:creator>
    <dc:creator>GC Murphy</dc:creator>
    <dc:creator>J Singer</dc:creator>
    <dc:creator>KS Booth</dc:creator>
    <dc:source>Software Engineering, IEEE Transactions on, Vol. 31, No. 6. (2005), pp. 446-465.</dc:source>
    <dc:date>2006-10-02T19:51:03-00:00</dc:date>
    <prism:publicationYear>2005</prism:publicationYear>
    <prism:publicationName>Software Engineering, IEEE Transactions on</prism:publicationName>
    <prism:volume>31</prism:volume>
    <prism:number>6</prism:number>
    <prism:startingPage>446</prism:startingPage>
    <prism:endingPage>465</prism:endingPage>
    <prism:category>csc591-spring2007</prism:category>
    <prism:category>data-mining</prism:category>
    <prism:category>elec669</prism:category>
    <prism:category>software-engineering</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/lucaspanjer/article/682724">
    <title>Who should fix this bug?</title>
    <link>http://www.citeulike.org/user/lucaspanjer/article/682724</link>
    <description>&lt;i&gt;(2006), pp. 361-370.&lt;/i&gt;</description>
    <dc:title>Who should fix this bug?</dc:title>

    <dc:creator>John Anvik</dc:creator>
    <dc:creator>Lyndon Hiew</dc:creator>
    <dc:creator>Gail Murphy</dc:creator>
    <dc:identifier>doi:10.1145/1134285.1134336</dc:identifier>
    <dc:source>(2006), pp. 361-370.</dc:source>
    <dc:date>2006-06-03T09:46:49-00:00</dc:date>
    <prism:publicationYear>2006</prism:publicationYear>
    <prism:startingPage>361</prism:startingPage>
    <prism:endingPage>370</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>elec669</prism:category>
    <prism:category>guiding-development</prism:category>
</item>



</rdf:RDF>

