Roberto Pepato Mellado

This paper describes a software framework for identifying the Law of Demeter violations in programs’ source- code. It discusses the main challenges related to language constructs and static code analysis. Its main contribution is the proposition and implementation of an extended version to the Law of Demeter as a software framework for identifying violations in software written in C# language. At the end, a quasi- controlled experiment involving an open-source program and its results is… Mostrar más

This paper describes a software framework for identifying the Law of Demeter violations in programs’ source- code. It discusses the main challenges related to language constructs and static code analysis. Its main contribution is the proposition and implementation of an extended version to the Law of Demeter as a software framework for identifying violations in software written in C# language. At the end, a quasi- controlled experiment involving an open-source program and its results is presented, where a reduction of 89% on reported violations was achieved by eliminating noisy violations. Mostrar menos

In the last two decades, many approaches have been proposed for software maintainability prediction. Some previous papers assess maintainability as a quality factor, while others assess it as an effort needed for maintenance. A number of techniques were experimented for this prediction activity. The most used one has been the Multivariate Regression Analysis (MRA), mainly because of its balance between simplicity and effectiveness. This paper presents a change and error proneness prediction… Mostrar más

In the last two decades, many approaches have been proposed for software maintainability prediction. Some previous papers assess maintainability as a quality factor, while others assess it as an effort needed for maintenance. A number of techniques were experimented for this prediction activity. The most used one has been the Multivariate Regression Analysis (MRA), mainly because of its balance between simplicity and effectiveness. This paper presents a change and error proneness prediction model based on MRA for OO software. Metrics used in the described experiment within this paper were collected from two software systems developed by industry comparing systems changes and defects history. This paper differs from previous works mainly in the following three aspects. First, while in other investigations maintenance volume is calculated only when the whole system is considered on maintenance phase, this one considers a class under maintenance when the use case is validated by the end . This approach allows more realistically dealings with systems that are developed in an iterative manner. Second, this investigation analyzes design and code metrics collected from all software classes on each revision and not only at specific moments. Finally, unlike most related investigations tackle maintenance effort prediction in general, this one focuses on corrective maintenance. Mostrar menos

In this investigation, an empirical analysis on three different industry projects from a Brazilian company was conducted. This company has moved its approach on software processes from ad-hoc to waterfall, followed by RUP based process, and finally agile like processes. To assess software product quality evolution, an experiment was conducted in those three projects which represented the company’s transition from RUP based process towards agile. This paper focus on the use of eXtreme… Mostrar más

In this investigation, an empirical analysis on three different industry projects from a Brazilian company was conducted. This company has moved its approach on software processes from ad-hoc to waterfall, followed by RUP based process, and finally agile like processes. To assess software product quality evolution, an experiment was conducted in those three projects which represented the company’s transition from RUP based process towards agile. This paper focus on the use of eXtreme Programming practices within projects and its impact on the quality of developed software products. At the end, OO design and some code metrics were used for quality assessment. Mostrar menos

Considering that software quality technical characteristics influence its maintenance, this paper presents a Method for Correlation Analysis between Software Product Metrics and Maintenance Proneness named METACOM. The proposed method defines an Extract, Transform, and Load (ETL) process for metrics of object-oriented software and volume of software maintenance. The METACOM involves a correlation analysis model between obtained product measures to identify the most predictive metrics. Besides… Mostrar más

Considering that software quality technical characteristics influence its maintenance, this paper presents a Method for Correlation Analysis between Software Product Metrics and Maintenance Proneness named METACOM. The proposed method defines an Extract, Transform, and Load (ETL) process for metrics of object-oriented software and volume of software maintenance. The METACOM involves a correlation analysis model between obtained product measures to identify the most predictive metrics. Besides, this paper describes the METACOM application on the analysis of some software industry real projects. At the end, some remarks are presented about the main analysis results obtained from specialists. Mostrar menos

This paper describes a framework for a software internal quality measurement program with automatic metrics extraction. This framework was successfully implemented in an Industrial Software Factory. That was possible through the implementation of a proposed Continuous Integration CI) environment to periodically analyze source codes and extract metrics. These metrics were consolidated in a Data Warehouse by allowing On-line Analytical Processing (OLAP) and Key Performance Indicator (KPI)… Mostrar más

This paper describes a framework for a software internal quality measurement program with automatic metrics extraction. This framework was successfully implemented in an Industrial Software Factory. That was possible through the implementation of a proposed Continuous Integration CI) environment to periodically analyze source codes and extract metrics. These metrics were consolidated in a Data Warehouse by allowing On-line Analytical Processing (OLAP) and Key Performance Indicator (KPI) analysis with high-performance and -friendly interface. The measurement program followed GQ(I)M paradigm for metrics selection to ensure that collected metrics are relevant from the Software Factory goals perspective. Finally, the Measurement and Analysis Process Area of the Capability Maturity Model integration - CMMi was used for measurement and analysis planning and implementation. Mostrar menos