GUI Migration using MDE from GWT to Angular 6: An Industrial Case

Verhaeghe, Benoit Mja; Etien, Anne; Anquetil, Nicolas; Seriai, Abdelhak-Djamel; Deruelle, Laurent; Ducasse, Sté́phane; Derras, Mustapha

doi:10.1109/saner.2019.8667989

Cited by 16 publications

(23 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[8] proposes to parse all the files representing an Oracle Forms for obtaining a model the article does not specify the kind of file they used for analyzing But according to [16] and to the existence of Oracle exporting tools 14 from Form to XML we suspect that they follow the same path. [22] proposes the usage of Famix [5]. Famix extraction for Java applications is achieved by using VervaineJ 15 .…”

Section: Related Workmentioning

confidence: 99%

“…Migration has been a research topic for a long time. The scientific community has proposed many different ways of tackling down this problem [3,6,8,9,10,11,16,22]. Nevertheless, migration is hard, tightly related with its circumstances and therefore, still challenging and not completely solved [20].…”

Section: Introductionmentioning

confidence: 99%

“…Most of the programming language compilers use plain text files as input for the programs they should compile or for configuration, such as XML, YML, properties, etc. Therefore, reengineering tools [12] often use the same approach for producing their internal models [6,8,11,13,16,21,22]. Work has already been done to mix static and dynamic analysis 3 [7,15,18,19].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Analysing Microsoft Access Projects: Building a Model in a Partially Observable Domain

Bragagnolo

Anquetil

Ducasse

et al. 2020

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Due to the technology evolution, every IT Company migrates their software systems at least once. Reengineering tools build system models which are used for running software analysis. These models are traditionally built from source code analysis and information accessible by data extractors (that we call such information observable). In this article we present the case of Microsoft Access projects and how this kind of project is partially observable due to proprietary storing formats. We propose a novel approach for building models that allows us to overcome this problem by reverse engineering the development environment runtime through the usage of Microsoft COM interface. We validate our approach and implementation by fully replicating 10 projects, 8 of them industrial, based only on our model information. We measure the replication performance by measuring the errors during the process and completeness of the product. We measure the replication error, by tracking replication operations. We used the scope and completeness measure to enact this error. Completeness is measured by the instrumentation of a simple and scoped diff based on a third source of information. We present extensive results and interpretations. We discuss the threats to validity, the possibility of other approaches and the technological restrictions of our solution.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Analysing Microsoft Access Projects: Building a Model in a Partially Observable Domain

Bragagnolo

Anquetil

Ducasse

et al. 2020

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…A new GUI framework will expose different interfaces and trigger different events. This forces developers to rewrite the same GUI in different technologies over the years [8,19].…”

Section: Components To Ease Evolutionmentioning

confidence: 99%

15 Years of Reuse Experience in Evolutionary Prototyping for the Defense Industry

LaBorde¹,

Costiou

Pors³

et al. 2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

At Thales Defense Mission Systems, software products first go through an industrial prototyping phase. We elaborate evolutionary prototypes which implement complete business behavior and fulfill functional requirements. We elaborate and evolve our solutions directly with end-users who act as stake-holders in the products' design. Prototypes also serve as models for the final products development. Because software products in the defense industry are developed over many years, this prototyping phase is crucial. Therefore, reusing software is a high-stakes issue in our activities. Component-oriented development helps us to foster reuse throughout the life cycle of our products. The work presented in this paper stems from 15 years of experience in developing prototypes for the defense industry. We directly reuse component implementations to build new prototypes from existing ones. We reuse component interfaces transparently in multiple prototypes, whatever the underlying implementation solutions. This kind of reuse spans prototypes and final products which are deployed on different execution platforms. We reuse non-component legacy software that we integrate in our component architectures. In this case, we seamlessly augment standard classes with component behavior, while preserving legacy code. In this paper, we present our component programming framework with a focus on component reuse in the context of evolutionary prototyping. We report three scenarios of reuse that we encounter regularly in our prototyping activity.

show abstract

“…With the fast evolution of programming languages and frameworks, companies tend to update their software more and more. This evolution may imply the migration of their application GUI [15]. To ensure the proper software operation after the update, one needs to validate and ensure the correct the migration of GUI.…”

Section: Introductionmentioning

confidence: 99%

Challenges for Layout Validation: Lessons Learned

Bragagnolo

Verhaeghe

Seriai³

et al. 2020

Communications in Computer and Information Science

Self Cite

View full text Add to dashboard Cite

Companies are migrating their software systems. The migration process contemplates many steps, UI migration is one of them. To validate the UI migration, most existing approaches rely on visual structure (DOM) comparison. However, in previous work, we experimented such validation and reported that it is not sufficient to ensure a result that is equivalent or even identical to the visual structure of the interface to be migrated. Indeed, two similar DOM may be rendered completely differently. So, we decide to focus on the layout migration validation. We propose a first visual comparison approach for migrated layout validation and experiment it on an industrial case. Hence, from this first experiment and already existing studies on image comparison field, we highlight challenges for layout comparison. For each challenge, we propose possible solutions, and we detail the three main features we need to create a good layout validation approach.

show abstract

GUI Migration using MDE from GWT to Angular 6: An Industrial Case

Cited by 16 publications

References 13 publications

Analysing Microsoft Access Projects: Building a Model in a Partially Observable Domain

Analysing Microsoft Access Projects: Building a Model in a Partially Observable Domain

15 Years of Reuse Experience in Evolutionary Prototyping for the Defense Industry

Challenges for Layout Validation: Lessons Learned

Contact Info

Product

Resources

About