Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników

Znaleziono wyników: 6

Liczba wyników na stronie
first rewind previous Strona / 1 next fast forward last
Wyniki wyszukiwania
Wyszukiwano:
w słowach kluczowych:  model transformation
help Sortuj według:

help Ogranicz wyniki do:
first rewind previous Strona / 1 next fast forward last
EN
Background: Model transformations play a key role in Model-Driven Engineering (MDE). Testing model transformation is an important activity to ensure the quality and correctness of the generated models. However, during the evolution and maintenance of these model transformation programs, frequently testing them by running a large number of test cases can be costly. Regression test selection is a form of testing, which selects tests from an existing test suite to test a modified program. Aim: The aim of the paper is to present a test selection approach for the regression testing of model transformations. The selected test case suite should be smaller in size than the full test suite, thereby reducing the testing overhead, while at the same time the fault detection capability of the full test suite should not be compromised. Method: approach is based on the use of a traceability mapping of test cases with their corresponding rules to select the affected test items. The approach is complemented with a tool that automates the proposed process. Results: Our experiments show that the proposed approach succeeds in reducing the size of the selected test case suite, and hence its execution time, while not compromising the fault detection capability of the full test suite. Conclusion: The experimental results confirm that our regression test selection approach is cost-effective compared to a retest strategy.
2
Content available remote Methodology for Application Logic Recovery from Existing Systems
EN
Newly emerging software design paradigms necessitate changes in legacy enterprise applications. For many such legacy systems their transition to the new paradigms becomes problematic or even impossible due to obsolescence of technologies they use. Replacement of the old system with the new one, built from scratch, is usually economically unacceptable. Therefore, there is a growing interest in methods for automated migration of legacy systems into a new paradigm. In this paper we propose a methodology for extraction and migration of application logic information from existing systems. The information extracted from a legacy application is stored in the form of precise requirement-level models enabling automated transformation into a new system structure.
PL
Rozwijane obecnie nowe paradygmaty projektowania systemów oprogramowania, wymuszają wprowadzanie zmian w istniejących aplikacjach korporacyjnych. W przypadku wielu takich systemów, ich dostosowanie do nowych paradygmatów jest problematyczne a nawet niemożliwe ze względu na przestarzałe technologie, przy użyciu których zostały zbudowane. Zastąpienie starego systemu nowym, wytworzonym od podstaw, jest zazwyczaj ekonomicznie nieuzasadnione. Wynikiem tego jest rosnące zainteresowanie metodami automatycznej migracji istniejących systemów do nowych paradygmatów. Niniejsza praca przedstawia metodykę odzyskiwania oraz migracji logiki aplikacji z istniejących systemów. Odzyskane informacje są przechowywana w postaci precyzyjnego modelu na poziomie wymagań oprogramowania, który następnie może posłużyć jako źródło automatycznej transformacji do nowej struktury systemu.
3
Content available remote An Algebraic Semantics for QVT-Relations Check-only Transformations
EN
QVT is the standard for model transformation defined by the OMG in the context of the Model-Driven Architecture. It is made of several transformation languages. Among them, QVTRelations is the one with the highest level of abstraction, as it permits developing bidirectional transformations in a declarative, relational style. Unfortunately, the standard only provides a semiformal description of its semantics, which hinders analysis and has given rise to ambiguities in existing tool implementations. In order to improve this situation, we propose a formal, algebraic semantics for QVT-Relations check-only transformations, defining a notion of satisfaction of QVT-Relations specifications by models.
4
Content available Translation of use case scenarios to Java code
EN
Use cases are usually treated as second class citizens in the software development chain based on models. Their textual descriptions (scenarios) are treated as informal input to more formal design models that can then be (semi-)automatically transformed down to code. In this paper we will show that use case scenarios can gain precise metamodel-based notation and semantics enabling automatic processing. What is more, we will show transformation algorithms that can transform use case scenarios directly to dynamic code in Java. The presented transformation can generate the full structure of the system following the MVP architectural pattern, including complete method contents for the application logic (Presenter) and presentation (View) layers. It also provides a code skeleton for the domain logic (Model) layer. The use case notation and the transformation were implemented within a sophisticated tool suite. Based on this, the paper discusses the evaluation efforts based on a case study.
EN
Future Internet technologies necessitate dramatic changes in system design, delivery and usage patterns. For many legacy applications it means that their further development and transition to the Internet becomes problematic or even impossible due to the obsolescence of technologies they use. Replacement of the old system with the new one, built from scratch, is usually economically unacceptable. Therefore, there is a call for methods and tools supporting the automated migration of legacy systems into a new paradigm. This paper proposes a tool supported method for recovery and migration of application logic information from legacy systems. The information extracted from a legacy application is stored in the form of precise requirement-level models enabling automated transformation into a new system structure in a model-driven way. Evaluation of the approach is based on a case study legacy system.
EN
This article presents an overview and a case study example of a software development system where families of similar systems can be created, based on their requirements specifications. The presented tool suite allows for specifying requirements in a precise grammar and then transforming them automatically into design models and code. Requirements, design and code of a system form a so-called “software case” which can be sought for in a software case repository. The system allows for merging “slices” of past software cases into the current system.
PL
Artykuł przedstawia przegląd oraz studium przypadku systemu wytwarzania oprogramowania, który umożliwia tworzenie rodzin podobnych systemów oprogramowania w oparciu o ich specyfikacje wymagań. Prezentowany zestaw narzędzi pozwala specyfikować wymagania w precyzyjnie zdefiniowanej gramatyce oraz dokonywać ich automatycznej transformacji w modele projektowe oraz kod. Wymagania, projekt oraz kod systemu tworzą razem tzw. „przypadek oprogramowania”, który może być przechowywany i wyszukiwany w specjalnym repozytorium. System umożliwia tworzenie „wycinków” przypadków oprogramowania stworzonych wcześniej i łączenie ich z bieżącym projektem.
first rewind previous Strona / 1 next fast forward last
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.