Please use this identifier to cite or link to this item:
http://10.1.7.192:80/jspui/handle/123456789/8655
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Vasu, Priya | - |
dc.date.accessioned | 2019-08-16T09:02:14Z | - |
dc.date.available | 2019-08-16T09:02:14Z | - |
dc.date.issued | 2018-06-01 | - |
dc.identifier.uri | http://10.1.7.192:80/jspui/handle/123456789/8655 | - |
dc.description.abstract | For a large and advancing Software System, the project group could get numerous bug reports over a long stretch of time. It is critical to accomplish a quantitative comprehension of bug fixing time. The capacity to predict bug fixing time can enable a project group better estimate programming support endeavours and better manage software programming ventures. In addition this time will be used to predict the release date of a minor version i.e. Patch. In industry when a client raises any bug, the undertaking supervisor needs to give them a date till which the minor variant will be released. The procedure for estimating the release date of the version needs to go through numerous stages like bug fixing time, smoke testing time lastly regression testing time. So we exhibit an effort that consequently predicts the fixing time. Our procedure uses existing issue following frameworks i.e. when a new bug report is generated the title and the description is extracted from the report that the bug with the similar title and description is searched from the database and here we have used Lucene framework for finding the bugs that have text similarity with the new bug report and used their time for prediction. In this approach, we have used Support vector Machine technique to query the database of resolved issues for textually similar reports. We also increase the reliability of our predictions by extending the SVM approach to explicitly state when there are no similar issues. Here this approach helps us for the early estimation of the bug fixing time, better assignment of the issues and predicting and scheduling the stable releases. Here we have assessed our approach utilizing the information from the RPAS (Retail Predictive Application Server) Project of an Oracle. Given an adequate number of issues reports, our programmed predictions are near the real exertion. | en_US |
dc.publisher | Institute of Technology | en_US |
dc.relation.ispartofseries | 16MCEC29; | - |
dc.subject | Computer 2016 | en_US |
dc.subject | Project Report 2016 | en_US |
dc.subject | Computer Project Report | en_US |
dc.subject | Project Report | en_US |
dc.subject | 16MCE | en_US |
dc.subject | 16MCEC | en_US |
dc.subject | 16MCEC29 | en_US |
dc.title | Prediction of the Patch Release Date | en_US |
dc.type | Dissertation | en_US |
Appears in Collections: | Dissertation, CE |
Files in This Item:
File | Description | Size | Format | |
---|---|---|---|---|
16MCEC29.pdf | 16MCEC29 | 871.84 kB | Adobe PDF | ![]() View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.