Towards Automated Restructuring of Object Oriented Systems

Trifu, A.; Reupke, U.

doi:10.1109/csmr.2007.51

Cited by 23 publications

(29 citation statements)

References 51 publications

(84 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…However, in the case of CSoft, the limited number of 'experts', the high number of new coming developers, and the urgent demands on new functionality, makes that pair programming is not considered a very practical nor scalable solution for spreading knowledge. To improve program comprehension and overcome "the fear of change", we suggest introducing semiautomatic code inspections like those in [5], potentially extended with visualizations and analyses from [6][7][8].…”

Section: Discussionmentioning

confidence: 99%

Maintenance and agile development: Challenges, opportunities and future directions

Hanssen

Yamashita

Conradi

et al. 2009

2009 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 99%

Maintenance and agile development: Challenges, opportunities and future directions

Hanssen

Yamashita

Conradi

et al. 2009

2009 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

show abstract

“…Many researchers in software engineering had carried out some researches on refactoring of high conditional complexity (Demeyer, Ducasse and Nierstrasz, 2002;Van Emden and Moonen, 2002;Trifu and Reupke, 2007;Tsantalis and Chatzigeorgiou, 2010;Christopoulou, Giakoumakis and Zafeiris et al, 2012;Liu, Hu and Liu et al, 2014). Most of the existing methodologies are based on preconditions or suggestions to identify high conditional complexity without analysis and extraction of related information.…”

Section: Introductionmentioning

confidence: 99%

Identification of High Conditional Complexity in Source Code Based on Statistical Analysis

2017

Revista Tecnica De La Facultad De Ingenieria Universidad Del Zu

View full text Add to dashboard Cite

In order to identify the high conditional complexity in source code, a novel approach based on statistical analysis is proposed. According to the statistical analysis of two software metrics which are Method McCabe's Cyclomatic Complexity (MMCC) and Method Average McCabe's Cyclomatic Complexity Per Code Line (MAMCC) in a large number of projects, the probability density functions and cumulative distribution functions for describing distributions of these two metrics are obtained. Moreover, a model for identifying high conditional complexity is built by choosing reasonable threshold of these metrics, and this model can be used for preliminary screening the methods which have high MMCC and high MAMCC. The experimental results show that the proposed approach can identify some candidate methods which need to be refactored accurately.

show abstract

“…In addition, Sales et al demonstrated the possibility of automated refactoring with Move Method with higher accuracy using the similarity of dependency sets [12]. Trifu and Reupke discussed the relationship between a design flaw and the number of directly observable indicators [13]. They defined specifications of design flaws including context and indicators, and a diagnosis strategy using indicators and correction strategies written in a natural language.…”

Section: Related Workmentioning

confidence: 99%

Detecting Architectural Violations Using Responsibility and Dependency Constraints of Components

Hayashi

Minami

Saeki

2018

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYUtilizing software architecture patterns is important for reducing maintenance costs. However, maintaining code according to the constraints defined by the architecture patterns is time-consuming work. As described herein, we propose a technique to detect code fragments that are incompliant to the architecture as fine-grained architectural violations. For this technique, the dependence graph among code fragments extracted from the source code and the inference rules according to the architecture are the inputs. A set of candidate components to which a code fragment can be affiliated is attached to each node of the graph and is updated stepby-step. The inference rules express the components' responsibilities and dependency constraints. They remove candidate components of each node that do not satisfy the constraints from the current estimated state of the surrounding code fragment. If the inferred role of a code fragment does not include the component that the code fragment currently belongs to, then it is detected as a violation. We have implemented our technique for the ModelView-Controller for Web Application architecture pattern. By applying the technique to web applications implemented using Play Framework, we obtained accurate detection results. We also investigated how much does each inference rule contribute to the detection of violations.

show abstract

Towards Automated Restructuring of Object Oriented Systems

Cited by 23 publications

References 51 publications

Maintenance and agile development: Challenges, opportunities and future directions

Maintenance and agile development: Challenges, opportunities and future directions

Identification of High Conditional Complexity in Source Code Based on Statistical Analysis

Detecting Architectural Violations Using Responsibility and Dependency Constraints of Components

Contact Info

Product

Resources

About