Building an expert system to assist system refactorization

Vidal, Santiago; Marcos, Claudia

doi:10.1016/j.eswa.2011.09.084

Cited by 6 publications

(4 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For instance, in Health Watcher the changes range from functionality increments and enhancements on error handling policies to the incorporation of design patterns as means to improve the system modularity. Our third application is the Subscribers DB [22], which is large software of a publishing house. The Subscribers DB system manages data related with the subscribers of its publications and it supports complex queries on several types of data.…”

Section: Target Applicationsmentioning

confidence: 99%

“…When combining the scores, a deficit index is calculated for the entire system -considering different source code metrics, such as code complexity, module coupling and cohesion metrics. The second approach is realized by the JSpIRIT tool [22], which supports semi-automated refactoring of the most critical design problems in a software system. The tool suggests a ranked list of the most critical code anomalies -based on a combination of different criteria -and intends to reduce the time spent on code anomaly prioritization.…”

Section: Detection and Prioritization Of Critical Code Anomaliesmentioning

confidence: 99%

See 1 more Smart Citation

Architecture-sensitive heuristics for prioritizing critical code anomalies

Guimarães

Garcia

Cai

2015

Proceedings of the 14th International Conference on Modularity

View full text Add to dashboard Cite

The progressive insertion of code anomalies in evolving software systems might lead to architecture degradation symptoms. Code anomalies are particularly harmful when they contribute to the architecture degradation. Although several approaches have been proposed aiming to detect anomalies in the source code, most of them fail to assist developers when prioritizing code anomalies critical to the architectural design. Blueprints of the architecture design are artifacts often available in industry software projects. However, such blueprints are rarely explored to support the prioritization of code anomalies in terms of their architecture relevance. This paper proposes and evaluates 2 sets of blueprintbased heuristics for supporting the prioritization of critical code anomalies. The prioritization is based on their potential impact on revealing architectural drift problems. The heuristics allow developers prioritizing critical code anomalies by exploiting architectural information provided in the blueprint. The contributions of this paper include: (i) a set of architecture sensitive heuristics to support developers when prioritizing critical code anomalies; (ii) an evaluation of the proposed heuristics in terms of their prioritization accuracy in 3 systems; and (iii) an empirical analysis on how the blueprints' information might enhance the prioritization of critical code anomalies, as opposed to existing heuristics strictly based on source code analysis.

show abstract

Section: Target Applicationsmentioning

confidence: 99%

Section: Detection and Prioritization Of Critical Code Anomaliesmentioning

confidence: 99%

Architecture-sensitive heuristics for prioritizing critical code anomalies

Guimarães

Garcia

Cai

2015

Proceedings of the 14th International Conference on Modularity

View full text Add to dashboard Cite

show abstract

“…In addition, we remove works on transformations for a too specific problem (stylized edits) [Meng et al 2013]. For instance, works in concurrent transformations [Brown et al 2013, Wloka et al 2009, Schäfer et al 2011, removal of security issues [Joiner et al 2014, Ma et al 2016, refactoring of web applications [Nguyen et al 2013c], refactoring to aspects [Vidal and Marcos 2013, Vidal and Marcos 2012, Marin et al 2009, refactoring C macros [Medeiros et al 2014, Overbey et al 2014, refactoring product lines [Schulze et al 2013], among others. Table 4 shows our quality criteria.…”

Section: Quality Assessmentmentioning

confidence: 99%

A Systematic Review of the Literature of the Techniques to Perform Transformations in Software Engineering

Sousa

2020

BJD

View full text Add to dashboard Cite

Along with software evolution, developers may do repetitive edits. These edits can be identical or similar to different codebase locations, which may occur as developers add features, refactor, or fix a bug. Since some of these edits are not present in Integrated Development Environments (IDEs), they are often performed manually, which is time-consuming and error-prone. In order to help developers to apply repetitive edits, some techniques were proposed. In this work, we present a systematic review of the literature of the techniques to do transformations in software engineering. As a result, this systematic review returned 51 works ranging from the domains programming-byexamples, linked editing, API usage, bug fixing, complex refactoring, and complex transformations, which can be used to help tools' designer in the proposition of new approaches.

show abstract

“…Indeed, as argued in [17], some domain variability should be implemented as crosscutting concerns. When a template engine does not support Aspect Oriented Programming (AOP) [18,19,20], templates may suffer metacode tangling (multiple variable concerns implemented simultaneously in a template) or metacode scattering (a variable concern implemented in multiple templates).…”

Section: Introductionmentioning

confidence: 99%

Exemplar driven development of software product lines

Heradio

Fernández-Amorós

Torre

et al. 2012

Expert Systems with Applications

View full text Add to dashboard Cite

The benefits of following a product line approach to develop similar software systems are well documented. Nevertheless, some case studies have revealed significant barriers to adopt such approach. In order to minimize the paradigm shift between conventional software engineering and software product line engineering, this paper presents a new development process where the products of a domain are made by analogy to an existing product. Furthermore, this paper discusses the capabilities and limitations of different techniques to implement the analogy relation and proposes a new language to overcome such limitations.

show abstract

Building an expert system to assist system refactorization

Cited by 6 publications

References 27 publications

Architecture-sensitive heuristics for prioritizing critical code anomalies

Architecture-sensitive heuristics for prioritizing critical code anomalies

A Systematic Review of the Literature of the Techniques to Perform Transformations in Software Engineering

Exemplar driven development of software product lines

Contact Info

Product

Resources

About