Supporting simultaneous versions for software evolution assessment

Laval, Jannik; Denier, Simon; Ducasse, Sté́phane; Falleri, Jean‐Rémy

doi:10.1016/j.scico.2010.11.014

Cited by 16 publications

(10 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We use ORION [8] to perform changes on the FAMIX model extracted in the previous step. ORION is a reengineering tool that simulates changes in multiple versions of the same source code model.…”

Section: B Versioningmentioning

confidence: 99%

OrionPlanning: Improving modularization and checking consistency on software architecture

Santos

Anquetil

Etien

et al. 2015

2015 IEEE 3rd Working Conference on Software Visualization (VISSOFT)

View full text Add to dashboard Cite

Many techniques have been proposed in the literature to support architecture definition, conformance, and analysis. However, there is a lack of adoption of such techniques by the industry. Previous work have analyzed this poor support. Specifically, former approaches lack proper analysis techniques (e.g., detection of architectural inconsistencies), and they do not provide extension and addition of new features. In this paper, we present ORIONPLANNING, a prototype tool to assist refactorings at large scale. The tool provides support for modelbased refactoring operations. These operations are performed in an interactive visualization. The contributions of the tool consist in: (i) providing iterative modifications in the architecture, and (ii) providing an environment for architecture inspection and definition of dependency rules. We evaluate ORIONPLANNING against practitioners' requirements on architecture definition listed in a previous survey. We also evaluate the tool in a concrete example of software remodularization.Demonstration video URL: http://youtu.be/TWWPgjRIljk

show abstract

Section: B Versioningmentioning

confidence: 99%

OrionPlanning: Improving modularization and checking consistency on software architecture

Santos

Anquetil

Etien

et al. 2015

2015 IEEE 3rd Working Conference on Software Visualization (VISSOFT)

View full text Add to dashboard Cite

show abstract

“…RGHistoryWrapper supports optimized navigation and queries between versions (an explanation of this concept lies outside the scope of this paper. For more information we refer to [15]). …”

Section: Definitions For Sequence Of Change Modelingmentioning

confidence: 99%

Supporting streams of changes during branch integration

Gómez

Ducasse

Kellens

2014

Science of Computer Programming

Self Cite

View full text Add to dashboard Cite

When developing large applications, integrators face the problem of integrating changes between branches or forks. While version control systems provide support for merging changes, this support is mostly text-based, and does not take the program entities into account. Furthermore, there exists no support for assessing which other changes a particular change depends on have to be integrated. Consequently, integrators are left to perform a manual and tedious comparison of the changes within the sequence of their branch and to successfully integrate them.In this paper, we present an approach that analyzes changes within a sequence of changes (stream of changes): such analysis identifies and characterizes dependencies between the changes. The approach identifies changes as autonomous, only used by others, only using other changes, or both. Such a characterization aims at easing the integrator's work. In addition, the approach supports important queries that an integrator otherwise has to perform manually. We applied the approach to a stream of changes representing 5 years of development work on an opensource project and report our experiences.

show abstract

“…As a result, version snapshots share implementation objects for entities that remain unchanged. The actual implementation strategy is inspired by the work of Laval et al [11].…”

Section: History Representationmentioning

confidence: 99%

A logic foundation for a general-purpose history querying tool

Stevens

Roover

Noguera

et al. 2014

Science of Computer Programming

View full text Add to dashboard Cite

Version control systems (VCS) have become indispensable software development tools. The version snapshots they store to provide support for change coordination and release management, effectively track the evolution of the versioned software and its development process. Despite this wealth of historical information, it has only been leveraged by tools that are dedicated to a specific task such as empirical validation of software engineering practices or fault prediction. General-purpose tool support for reasoning about the historical information stored in a version control system is limited. This paper provides a comprehensive description of a logic-based, general-purpose history query tool called Absinthe. Absinthe supports querying versioned Smalltalk system using logic queries in which quantified regular path expressions are embedded. These expressions lend themselves to specifying the properties that each individual version in a sequence of successive software versions ought to exhibit. To demonstrate the general-purpose nature of our history query tool, we use it to verify development process constraints, to identify temporal bad smells and to answer questions that developers commonly ask. Finally, we compare a query written in Absinthe to an equivalent one written in Smalltalk.

show abstract

Supporting simultaneous versions for software evolution assessment

Cited by 16 publications

References 28 publications

OrionPlanning: Improving modularization and checking consistency on software architecture

OrionPlanning: Improving modularization and checking consistency on software architecture

Supporting streams of changes during branch integration

A logic foundation for a general-purpose history querying tool

Contact Info

Product

Resources

About