Detecting asynchrony and dephase change patterns by mining software repositories
Explore this paper's citation graph
Summary
This paper introduces two novel change patterns: the asynchrony change pattern, corresponding to macro co‐changes (MC), that is, of files that co‐change within a large time interval (change periods) and the dephase change pattern that always happens with the same shifts in time.
- Type
- article
- Published
- 2014-01-01
- Cited by
- 22
- References
- 45
- OpenAlex
- https://openalex.org/W1925941278
- Semantic Scholar
- https://api.semanticscholar.org/CorpusID:18964767
Keywords
Computer science, Asynchrony (computer programming), Software evolution, Interval (graph theory), Java
References
- Software Repositories: A Source for Traceability Links
- Fast Algorithms for Mining Association Rules in Large Databases
- Program evolution: processes of software change
- Nearest neighbor (NN) norms: NN pattern classification techniques
- Detection of logical coupling based on product release history
- Designing object-oriented software
- Mining additions of method calls in ArgoUML
- Using multivariate time series and association rules to detect logical change coupling: An empirical study
- Recovering binary class relationships: putting icing on the UML cake
- Understanding software evolution using a combination of software visualization and software metrics
- A Methodology for Collecting Valid Software Engineering Data
- Analyzing the evolutionary history of the logical design of object-oriented software
- Linear predictive coding and cepstrum coefficients for mining time variant information from software repositories
- Trust-Based Requirements Traceability
- Two case studies of open source software development: Apache and Mozilla
- Populating a Release History Database from version control and bug tracking systems
- On the Relationship Between Change Coupling and Software Defects
- UMLDiff: an algorithm for object-oriented design differencing
- Extracting Change-patterns from CVS Repositories
- An eclectic approach for change impact analysis
Cited by
- Special issue: a selection of distinguished papers from the 18th Working Conference on Reverse Engineering 2011
- PROPOSTA DE UM ARCABOUÇO CONCEITUAL PARA A INTELIGÊNCIA ANALÍTICA NA ENGENHARIA DE SOFTWARE
- The Effect of GoF Design Patterns on Stability: A Case Study
- Analysing Artefacts Dependencies to Evolving Software Systems
- Practical guidelines for change recommendation using association rule mining
- Exploring the Effects of History Length and Age on Mining Software Change Impact
- Using discriminative feature in software entities for relevance identification of code changes
- Analyzing software evolution and quality by extracting Asynchrony change patterns
- A Method for Assessing Class Change Proneness
- What are the effects of history length and age on mining software change impact?
- Proposing and empirically validating change impact analysis metrics
- Mining version history to predict the class instability
- On Adaptive Change Recommendation
- On the Impact of Interlanguage Dependencies in Multilanguage Systems Empirical Case Study on Java Native Interface Applications (JNI)
- Change impact analysis: A systematic mapping study
- Supporting Change Impact Analysis in System Architecture Design: Towards a Domain-Specific Modeling Method
- Revealing code change propagation channels by evolution history mining
- Enhancing Change Impact Prediction by Integrating Evolutionary Coupling with Software Change Relationships
- A methodology to predict the instable classes: student research abstract
- The Application of Change Indicators in Mining Software Repositories
Related papers
- Ventricular Asynchrony and Heart Failure
- Temporal asynchrony of less than one‐half cycle can be detected in harmonic complexes
- [Electromechanical cardiac asynchrony and heart failure].
- Software evolution and maintenance
- Aspect-oriented software evolution
- Software maintenance versus software evolution: an approach to software systems evolution
- The evolution tree: a maintenance-oriented software development model