Identificação de valores referência para métricas de softwares orientados por objetos

Exportado OPUSMade available in DSpace on 2019-08-11T00:28:13Z (GMT). No. of bitstreams: 1 tarcisiofilo.pdf: 4208476 bytes, checksum: 4beeb9f74394cf64dda51f0fa16f7fbd (MD5) Previous issue date: 15Valores referência para a maioria das métricas de software ainda não são conhecidos. Neste trabalho, identificamos valores referência para 18 métricas de softwares orientados por objetos. Diferentemente de trabalhos anteriores, propusemos um catálogo de valores referência que agrupa uma quantidade maior de métricas, possibilitando a avaliação de métodos, classes e pacotes. Nossa abordagem sugere três faixas nos valores referência: Bom/Frequente, Regular/Ocasional e Ruim/Raro. A faixa Bom/Frequente corresponde aos valores que apresentam alta frequência. A faixa Ruim/Raro corresponde aos valores de baixa frequência, enquanto a faixa Regular/Ocasional corresponde a valores que não são muito frequentes e nem são de baixa frequência. Apesar desses valores não expressarem necessariamente as melhores práticas da Engenharia de Software, eles refletem um padrão de qualidade seguido pela maioria dos software avaliados.Thresholds for the majority of software metrics are still not known. This might be the reason why a measurement method that should be part of a software quality assessment process is still not there in software industry. In this work, we applied a predefined empirical method to an 111 system dataset, identifying thresholds for 18 object-oriented software metrics. Furthermore, we proposed some improvements in that method. Differently from previous work, we have defined a catalogue of thresholds that gathers a greater amount of object-oriented software metrics, allowing the assessment of methods, classes and packages. Our approach suggests three ranges in the thresholds: Good/Common, Regular/Casual and Bad/Uncommon. The Good/Common range corresponds to values with high frequency. The Bad/Uncommon range corresponds to values with quite low frequency, and the Regular/Casual range is an intermediate one, which corresponds to values that are not too frequent neither have very low frequency. Although they do not necessarily express the best practices in Software Engineering, they reflect a quality standard followed by most of the evaluated software. To evaluate the effectiveness of the defined thresholds to indicate the real panorama of the software quality, we conducted three case studies and an experiment. The results suggest that the proposed thresholds can indicate the quality of the software, providing a benchmark for the quantitative assessment of the internal quality of object-oriented software, considering methods, classes and packages