<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>Lanza, Michele</dc:contributor>
  <dc:creator>Dal Sasso, Tommaso</dc:creator>
  <dc:date>2018-06-14</dc:date>
  <dc:description xmlns:ns0="xml" ns0:lang="en">Software development has become more and more pervasive,  with influence in almost every human activity. To be able to fit in  so many different scenarios and constantly implement new  features, software developers adopted methodologies with tight  development cycles, sometimes with more than one release per  day. With the constant growth of modern software projects and  the consequent expansion of development teams,  understanding all the components of a system becomes a task  too big to handle. In this context understanding the cause of an  error or identifying its source is not an easy task, and correcting  the erroneous behavior can lead to unexpected downtime of  vital services. Being able to keep track of software defects,  usually referred to as bugs, is crucial in the development of a  project and in containing maintenance costs. For this purpose,  the correctness and completeness of the information available  has a great impact on the time required to understand and solve  a problem. In this thesis we present an overview of the current  techniques commonly used to report software defects. We show  why we believe that the state of the art needs to be improved,  and present a set of approaches and tools to collect data from  software failures, model it, and turn it into actionable knowledge.  Our goal is to show that data generated from errors can have a  great impact on daily software development, and how it can be  employed to augment the development environment to assist  software engineers to build and maintain software systems.</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:identifier>https://susi.usi.ch/global/documents/319017</dc:identifier>
  <dc:identifier>https://n2t.net/ark:/12658/srd1319017</dc:identifier>
  <dc:identifier>https://susi.usi.ch/documents/319017/files/2018INFO014.pdf</dc:identifier>
  <dc:language>eng</dc:language>
  <dc:relation>info:eu-repo/semantics/altIdentifier/urn/urn:nbn:ch:rero-006-117912</dc:relation>
  <dc:relation>info:eu-repo/semantics/altIdentifier/ark/12658/srd1319017</dc:relation>
  <dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
  <dc:rights>License undefined</dc:rights>
  <dc:subject xmlns:ns1="xml" ns1:lang="en">bug reports</dc:subject>
  <dc:subject xmlns:ns2="xml" ns2:lang="en">issue tracking systems</dc:subject>
  <dc:subject xmlns:ns3="xml" ns3:lang="en">reification</dc:subject>
  <dc:subject xmlns:ns4="xml" ns4:lang="en">software development</dc:subject>
  <dc:subject xmlns:ns5="xml" ns5:lang="en">error collection</dc:subject>
  <dc:subject xmlns:ns6="xml" ns6:lang="en">software failure</dc:subject>
  <dc:subject xmlns:ns7="xml" ns7:lang="en">stack traces</dc:subject>
  <dc:subject>info:eu-repo/classification/udc/004</dc:subject>
  <dc:title xmlns:ns8="xml" ns8:lang="en">Reification as the key to augmenting software development : an object is worth a thousand words</dc:title>
  <dc:type>http://purl.org/coar/resource_type/c_db06</dc:type>
</oai_dc:dc>