Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method
Autor(a) principal: | |
---|---|
Data de Publicação: | 2013 |
Outros Autores: | |
Tipo de documento: | Artigo |
Idioma: | eng |
Título da fonte: | INFOCOMP: Jornal de Ciência da Computação |
Texto Completo: | https://infocomp.dcc.ufla.br/index.php/infocomp/article/view/372 |
Resumo: | A study that how error severity categories depend on the class level software metrics is presented through statistical method. The main purpose of the study is to classify error categories based on the different number of error occurrences in all the three version of Eclipse Project. The study used the all error type to find the software metrics threshold for the three releases of Eclipse project using Receiver Operating Characteristic curves. These thresholds are responsible for making difference between error-free or error prone classes . But, not all the choosen metrics are able to do that, though some of them are capable for that. In future it is not necessary that these software metric thresholds can predict the class will definitely have errors. This approach only provide a scientific way for software engineers to judge designed class is error prone or error free during design time. |
id |
UFLA-5_443eaa90701bc99b21dfa34ab241d390 |
---|---|
oai_identifier_str |
oai:infocomp.dcc.ufla.br:article/372 |
network_acronym_str |
UFLA-5 |
network_name_str |
INFOCOMP: Jornal de Ciência da Computação |
repository_id_str |
|
spelling |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical methodObject - Oriented metricsobject - oriented designspecificit ysensitivitythresholdsROC curveAUCConfusion MatrixA study that how error severity categories depend on the class level software metrics is presented through statistical method. The main purpose of the study is to classify error categories based on the different number of error occurrences in all the three version of Eclipse Project. The study used the all error type to find the software metrics threshold for the three releases of Eclipse project using Receiver Operating Characteristic curves. These thresholds are responsible for making difference between error-free or error prone classes . But, not all the choosen metrics are able to do that, though some of them are capable for that. In future it is not necessary that these software metric thresholds can predict the class will definitely have errors. This approach only provide a scientific way for software engineers to judge designed class is error prone or error free during design time.Editora da UFLA2013-06-01info:eu-repo/semantics/articleinfo:eu-repo/semantics/publishedVersionapplication/pdfhttps://infocomp.dcc.ufla.br/index.php/infocomp/article/view/372INFOCOMP Journal of Computer Science; Vol. 12 No. 1 (2013): June, 2013; 49-631982-33631807-4545reponame:INFOCOMP: Jornal de Ciência da Computaçãoinstname:Universidade Federal de Lavras (UFLA)instacron:UFLAenghttps://infocomp.dcc.ufla.br/index.php/infocomp/article/view/372/356Copyright (c) 2016 INFOCOMP Journal of Computer Scienceinfo:eu-repo/semantics/openAccessKumari, DiptiRajnish, Kumar2015-07-29T16:46:24Zoai:infocomp.dcc.ufla.br:article/372Revistahttps://infocomp.dcc.ufla.br/index.php/infocompPUBhttps://infocomp.dcc.ufla.br/index.php/infocomp/oaiinfocomp@dcc.ufla.br||apfreire@dcc.ufla.br1982-33631807-4545opendoar:2024-05-21T19:54:35.039560INFOCOMP: Jornal de Ciência da Computação - Universidade Federal de Lavras (UFLA)true |
dc.title.none.fl_str_mv |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method |
title |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method |
spellingShingle |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method Kumari, Dipti Object - Oriented metrics object - oriented design specificit y sensitivity thresholds ROC curve AUC Confusion Matrix |
title_short |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method |
title_full |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method |
title_fullStr |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method |
title_full_unstemmed |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method |
title_sort |
Finding error-prone classes at design time using class based Object-Oriented metrics threshold through statistical method |
author |
Kumari, Dipti |
author_facet |
Kumari, Dipti Rajnish, Kumar |
author_role |
author |
author2 |
Rajnish, Kumar |
author2_role |
author |
dc.contributor.author.fl_str_mv |
Kumari, Dipti Rajnish, Kumar |
dc.subject.por.fl_str_mv |
Object - Oriented metrics object - oriented design specificit y sensitivity thresholds ROC curve AUC Confusion Matrix |
topic |
Object - Oriented metrics object - oriented design specificit y sensitivity thresholds ROC curve AUC Confusion Matrix |
description |
A study that how error severity categories depend on the class level software metrics is presented through statistical method. The main purpose of the study is to classify error categories based on the different number of error occurrences in all the three version of Eclipse Project. The study used the all error type to find the software metrics threshold for the three releases of Eclipse project using Receiver Operating Characteristic curves. These thresholds are responsible for making difference between error-free or error prone classes . But, not all the choosen metrics are able to do that, though some of them are capable for that. In future it is not necessary that these software metric thresholds can predict the class will definitely have errors. This approach only provide a scientific way for software engineers to judge designed class is error prone or error free during design time. |
publishDate |
2013 |
dc.date.none.fl_str_mv |
2013-06-01 |
dc.type.driver.fl_str_mv |
info:eu-repo/semantics/article info:eu-repo/semantics/publishedVersion |
format |
article |
status_str |
publishedVersion |
dc.identifier.uri.fl_str_mv |
https://infocomp.dcc.ufla.br/index.php/infocomp/article/view/372 |
url |
https://infocomp.dcc.ufla.br/index.php/infocomp/article/view/372 |
dc.language.iso.fl_str_mv |
eng |
language |
eng |
dc.relation.none.fl_str_mv |
https://infocomp.dcc.ufla.br/index.php/infocomp/article/view/372/356 |
dc.rights.driver.fl_str_mv |
Copyright (c) 2016 INFOCOMP Journal of Computer Science info:eu-repo/semantics/openAccess |
rights_invalid_str_mv |
Copyright (c) 2016 INFOCOMP Journal of Computer Science |
eu_rights_str_mv |
openAccess |
dc.format.none.fl_str_mv |
application/pdf |
dc.publisher.none.fl_str_mv |
Editora da UFLA |
publisher.none.fl_str_mv |
Editora da UFLA |
dc.source.none.fl_str_mv |
INFOCOMP Journal of Computer Science; Vol. 12 No. 1 (2013): June, 2013; 49-63 1982-3363 1807-4545 reponame:INFOCOMP: Jornal de Ciência da Computação instname:Universidade Federal de Lavras (UFLA) instacron:UFLA |
instname_str |
Universidade Federal de Lavras (UFLA) |
instacron_str |
UFLA |
institution |
UFLA |
reponame_str |
INFOCOMP: Jornal de Ciência da Computação |
collection |
INFOCOMP: Jornal de Ciência da Computação |
repository.name.fl_str_mv |
INFOCOMP: Jornal de Ciência da Computação - Universidade Federal de Lavras (UFLA) |
repository.mail.fl_str_mv |
infocomp@dcc.ufla.br||apfreire@dcc.ufla.br |
_version_ |
1799874741430910976 |