New Failure Rate Model for Iterative Software Development Life Cycle Process

Citation Author(s):
Sangeeta
Phogat
Submitted by:
Kapil Sharma
Last updated:
Wed, 12/12/2018 - 10:01
DOI:
10.21227/tafr-c403
Links:
License:
507 Views
Categories:
Keywords:
0
0 ratings - Please login to submit your rating.

Abstract 

Data has been extracted from Tera Promise repository bug report files of Eclipse and Java Development Tools (JDT) open source software at https://zenodo.org/record/268486#.W-QsPpMzY2w. These data sets have been given by An Ngoc Lam. The bug reports contain table having contents as bug_id, summary, description, report time, report time status, commit, and commit time files. Datasets have been extracted from these bug reports and reformatted in time domain format. Eight minor releases and four major releases starting from the year 2001 to the year 2013 have been obtained from Eclipse. For JDT software three major releases and six minor releases starting from the year 2002 to the year 2014 have been obtained.

Instructions: 

Attribute Information

  • bug\_id– refers to the bug report id.
  • summary– refers to the bug report summary.
  • description– refers to the bug report description.
  • report\_time– refers to the bug report report time.
  • report\_timestamp– refers to the bug report report timestamp.
  • status– refers to the status of the bug report.
  • commit– refers to the SHA-1 hash id for the commit that fixed the bug report.
  • commit\_timestamp– refers to the commit timestamp.
  • files– contains the full path of every Java file that was fixed in this commit.
  • result– contains the position of every positive instance in our ranked list result.

How to obtain the source code

A before-fix version of the source code package needs to be checked out for each bug report. Taking Eclipse Bug 420972 for example, this bug was fixed at commit 657bd90. To check out the before-fix version 2143203 of the source code package, use the commandgit checkout 657bd90~1.