A Bridge over Troubled Water: Synergies between Model Transformations and Software Maintenance Techniques

A Bridge over Troubled Water:
Synergies between
Model Transformation and
Software Maintenance Techniques
Dániel Varró
Budapest University of Technology and Economics

CSMR 2012
Szeged, Hungary, March 29th, 2012
Budapest University of Technology and Economics
Department of Measurement and Information Systems

Song writing methods of
Simon and Garfunkel

Paul Simon’s technique #1
Bridge Over Troubled Water

When you're weary
Feeling small
When tears are in your eyes
I will dry them all

I'm on your side
When times get rough
And friends just can't be found
Like a bridge over troubled water
I will lay me down
I will lay me down
1. Create music first 2. Write lyrics accordingly
3

Paul Simon’s technique #2
The Boxer
I am just a poor boy
Though my story's seldom told
I have squandered my resistance
For a pocket full of mumbles such are promises
All lies and jests
Still a man hears what he wants to hear
And disregards the rest
When I left my home and my family
I was no more than a boy
In the company of strangers
In the quiet of the railway station running scared
Laying low, seeking out the poorer quarters
Where the ragged people go
Looking for the places only they would know
1. Write lyrics first 2. Compose music accordingly
4

A Combined Technique…
Scarborough Fair (Folk Song) The Side of a Hill (P. Simon)
Tell her to find me an acre of land, On the side of a hill, a little cloud weeps
Parsley, sage, rosemary and thyme; And waters the grave with its silent tears
Between the salt water and the sea strand, While a soldier cleans and polishes a gun
Then she'll be a true love of mine.

Canticle (rearranged by A. Garfunkel)
On the side of a hill a sprinkling of leaves
Washes the grave with silvery tears
A soldier cleans and polishes a gun

5

Naming These Techniques…

When you're weary
Feeling small Music Driven Song Development
I will dry them all (MDSD)
I'm on your side
I will lay me down
I will lay me down
1. Create music first 2. Write lyrics accordingly
The Boxer
I am just a poor boy
Though my story's seldom told
I have squandered my resistance
For a pocket full of mumbles such are promises
Lyrics Driven Song Development All lies and jests
Still a man hears what he wants to hear
And disregards the rest
When I left my home and my family
I was no more than a boy
In the company of strangers
In the quiet of the railway station running scared
Laying low, seeking out the poorer quarters
Where the ragged people go
Looking for the places only they would know
1. Write lyrics first 2. Compose music accordingly
6

Applying the Principle to Software Systems

Model Code
When you're weary
Feeling small
I will dry them all

I'm on your side
I will lay me down
I will lay me down

Music Lyrics
7

Some Well-known Transformations
Code generation Generative programming
Model Code

Model Re-engineering
Query Query
Program comprehension
Model
Refactoring Refactoring
8

A Classification of Transformations
M2T: Model-to-Text
Model Code

T2M:
Text-to-
Model

Model Transformations:
Topic of this talk
M2M: Model-to-Model T2T: Text-to-Text
9

Model-Driven Software Development
M2T: Model-to-Text
Model Code

Conferences:
M2M: Model-to-Model MODELS, ECMFA, ICMT
10

Software Maintenance and Re-engineering

Model Code

T2M:
Text-to-
Model

Conferences:
CSMR, ICSM … T2T: Text-to-Text
11

Objectives: Build More Bridges for Roundtrips
M2T: Model-to-Text
Model Code

T2M:
Text-to-
Model

M2M: Model-to-Model T2T: Text-to-Text
12

Talk Overview
Overview &
Applications of MT
•Basics
•Applications from
own practice

A tool (MTSMR)
• to build your SMR tool
• increm. model queries

Targets (SMRMT)
• future research
• collaboration

13

Model Transformations in
Model Driven Software Development

Development Process for Critical Systems
Unique Development Process
(Traditional V-Model)
Critical Systems Design
 requires a certification process
 to develop justified evidence
 that the system is free of flaws

Software Tool Qualification
 obtain certification credit
 for a software tool
DO-178B  used in critical system design
IEC 61508

Innovative Tool  Better System Qualified Tool  Certified Output

Model-Driven Engineering of Critical Systems
Traditional V-Model Model-Driven Engineering

Main ideas of MDE
• DO-178B/C: Software Considerations in Airborne Systems and • early validation of system models
Equipment Certification (RTCA, EUROCAE)
• Steven P. Miller: Certification Issues in Model Based Development • automatic source code generation
(Rockwell Collins)
 quality++ tools ++ development cost--

Models and Transformations in Critical Systems
Horizontal Model Transformations
Model generation
System Design System V&V
Model Model

Refine Back-Annotation Use
Design Model generation Formal
Vertical Model Transformations

rules Architecture Architecture methods
Design Model V&V Model
Refine Back-Annotation
Use
rules Component Component methods
Design Model V&V Model
Back-Annotation
Design
rules Code
Model Transformations
Test • systematic foundation of
Generation Generation
knowledge transfer:
Related projects theoretical resultstools
Design + V&V Artifacts
• CESAR, SAVI, … • bridge / integrate
(Source code, Glue code,
• HIDE, DECOS, DIANA, Config. Tables, Test Cases, existing languages&tools
MOGENTES, CERTIMOT, Monitors, Fault Trees, etc.)
GENESYS, SENSORIA

Modeling Languages and
Model Transformations

Overview: Foundations of Model Transformations
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Architecture V&V methods
Design
Model
Model
Use
rules Component Component
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
Generation Generation Foundations of
model transformations
Config. Tables, Test Cases, Monitors,
Fault Trees, etc.)

Domain Specific Modeling Languages
Concrete syntax Abstract syntax Well-formedness
(Graphical/Textual) (Metamodel) constraints

Behavioural semantics,
Simulation

Mapping Code
generation

Domain-Specific
Modeling Languages (DSML):
Concrete syntax: • Foundations of many modern tool
Source Code
View
• How the designer sees it (design, analysis, V&V) (Documentation,
• Graphical/textual/both • Domains: avionics, automotive,
Configuration file)
business modeling


Simulation

Mapping Code
generation

Abstract syntax: Source Code
View
• Internal graph representation (Documentation,
• Defined by a metamodel Configuration file)


Simulation

Mapping Code
generation

Well-formedness constraints: Source Code
View
• REQs for valid static models (Documentation,
• Captured declaratively (OCL) Configuration file)


Simulation

Mapping Code
generation

Behavioural Semantics: Source Code
View
• For dynamic MLs only (Documentation,
(statecharts, business processes) Configuration file)
• Enables model simulation/execution


Simulation

Mapping Code
generation

View/Compile/Map: Source Code
View
• View / code generation (Documentation,
• Model transformation exercise Configuration file)

Model Transformation Overview: Metamodels
Metamodel: Precise spec of
a modeling language

Modeling tool
Source Target
MT rule
metamodel metamodel

Source Target
model model

Model Transformation Overview: Models
Eclipse Modeling Framework (EMF):
• De facto modeling standard for
Eclipse based modeling tools
• Design metamodel auto-generate tool
Modeling
interface, implementation, tree editor…
• Examples:Source
MT rule
Target
UML, AADL, SysML,
metamodel BPMN, AUTOSAR metamodel
>30 in a single IBM tool
Source Model: Description Target
model of a concrete system model

a1:PTArc a2:TPArc
t1:Transition

p1:Place tk:Token p2:Place

t2:Transition
a4:TPArc a3:PTArc

Model Transformation Overview: Rules
Model Transformation:
How to generate a target equivalent
of an arbitrary source model
Modeling tool
Source Target
MT rule
metamodel metamodel

Source Target
model model

LHS RHS
a1:inarc a2:outarc a1:inarc a2:outarc
Place Tran. Place Place Tran. Plan
ttn1:tokens tkn2:tokens
Token Token

Model Transformation Overview: Rule Execution
Eclipse Framework
Model Transformation Tool

Modeling tool
Source Target
MT rule
metamodel metamodel

Source Target
MT engine
model model

Transformation engine:
Support for querying and
manipulating large models
ATL
VIATRA2:
http://www.eclipse.org/gmt/VIATRA2/ QVT

Model Transformation by Graph Transfromation
Eclipse Framework

Modeling tool
Source Target
MT rule
metamodel metamodel

Source Target
MT engine
model model
query/match update

LHS RHS
a1:inarc a2:outarc a1:inarc a2:outarc
Place Tran. Place Place Tran. Plan
ttn1:tokens tkn2:tokens
Token Token

Overview of Model Transformations
Eclipse Framework

Modeling tool
Source Target
MT rule
metamodel metamodel
Native source models: Native target models:
• EMF • EMF
• XML Source
documents • App source code
Target
• Databases
model
MT engine • XML deployment descript.
model
• Domain-specific models • Databases
• UML • Analysis tools

Native Native
source model target model

3rd Party Tool

Standalone Model Transformations Plugins
Eclipse Framework

Modeling tool
Source Target
MT rule
metamodel metamodel

Source Target
MT engine
model model
Standalone transformation:
Code generator
Independent of transformation
development environment

Native Native Native
source model MT plugin target model

3rd Party Tool
D. Varró, A. Pataricza: Generic and Meta-Transformations for Model Transformation Engineering . UML 2004

Incremental Model Queries

By EMF-IncQuery

Overview: Early Validation of Design Rules
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
Validation of design rules
by incremental model queries
Fault Trees, etc.)

Challenge: Early validation of design rules
SystemSignalGroup design rule (from AUTOSAR)
o A SystemSignal and its group must be in the same IPdu
AUTOSAR:
o Challenge: find violations quicklyarchitecturemodels
• standardized SW in large
o New difficulties of the automotive industry
• now supported by modern modeling tools
• reverse Design Rule/Well-formedness constraint:
navigation • each valid car architecture needs to respect
• designers are immediately notified if violated
• complex Challenge:
manual • >500 design rules in AUTOSAR tools
solution • >1 million elements in AUTOSAR models
• models constantly evolve by designers

Capturing design rules as model queries
Example: SystemSignalGroup design rule (from AUTOSAR)
 A SystemSignal and its signal group must be in the same IPDU
(Protocol Data Unit)
Our approach
 Capture design rules as model queries
 Incremental re-validation
Others approaches: X. Blanc,
A. Egyed, T. Mens,OCL, …

ModelQuery(A,B):
• tuples of model elements A, B
• satisfying the query condition
• enumerate 1 / all instances
• A,B can be input or output

Graph Patterns as Query Language
 Graph patterns as pattern mappedSignal(S,M,P) = {
declarative query language SignalIPdu(P);
o Attribute constraints signalToPduMapping(R3,P,M);
ISignalToIPduMapping(M);
o Local + global queries
signal(R1,M,S);
o Compositionality + Reusabilility ISignal(S);
o „Arbitrary” Recursion, Negation, }
Transitive Closure pattern systemSignal(S,SS) = {
o Syntax: DATALOG style ISignal(S);
systemSignal(R2,S,SS);
SystemSignal(SS);
}
pattern systemSignalGroup(P) = {
find mappedSignal(S_Child,M_Child,P);
find systemSignal(S_Child,SS_Child);
systemSignal(R7,SS_Parent,SS_Child);
find systemSignal(S_Parent,SS_Parent);
neg find mappedSignal(S_Child,M_Child,P);
}

Incremental Evaluation of Graph Queries
 Graph patterns as pattern mappedSignal(S,M,P) = {
declarative query language SignalIPdu(P);
o Attribute constraints signalToPduMapping(R3,P,M);
ISignalToIPduMapping(M);
o Local + global queries
signal(R1,M,S);
o Compositionality + Reusabilility ISignal(S);
o „Arbitrary” Recursion, Negation, }
Transitive Closure pattern systemSignal(S,SS) = {
o Syntax: DATALOG style ISignal(S);
systemSignal(R2,S,SS);
SystemSignal(SS);
Evaluation: incremental }
cache of matches (RETE) pattern systemSignalGroup(P) = {
find mappedSignal(S_Child,M_Child,P);
• Cheap maintenance of cache
find systemSignal(S_Child,SS_Child);
(only memory overhead) systemSignal(R7,SS_Parent,SS_Child);
• Notify about relevant changes find systemSignal(S_Parent,SS_Parent);
• Enable reactions to complex neg find mappedSignal(S_Child,M_Child,P);
structural events }

G. Bergmann et al.: Incremental evaluation of model queries over EMF models. MODELS 2010.

Scalability of EMF-IncQuery
EMF-IncQuery: available from Context of experiments:
http://viatra.inf.mit.bme.hu/incquery • Generated AUTOSAR models
• > 1,5 million model elements
• #violations << model size

Memory consumption: Time of incremental revalidation:
• < 50 MB for model size • < 10 ms
below 50 000 elements • Depends on size of the change
• < 1GB for largest models • Depends on number of violations but
(grows linearly) • Independent from model sizes

Measured scenarios:
• Read and first check
• Change and revalidate

G. Bergmann et al.: Incremental evaluation of model queries over EMF models. MODELS 2010.

Cross technology benchmarking for
on-the-fly model validation

39

What technology to use for a model validation tool?

Triple stores /
Eclipse Modeling
graph databases
• EMF (&variants, CDO, …) • OWL/RDF, SPARQL
• Proven EMF tools: Plain Java • RacerPro, Pellet, Sesame,
queries, OCL (&variants), EMF Jena, OpenVirtuoso, Allegro,
Query (1-2) StarDog
• New/experimental • But…
technologies: Future plans • Huge, distributed
EMF-IncQuery, (not covered yet) knowledge bases
JBoss Drools, … • Non-EMF • Frequently based upon
modeling Relational DB
frameworks • Optimized SPARQL engines
• Plain XML/Xpath • Expensive commercial tools
• OO DB
• K-V (NoSQL), …

Evaluation Results
Batch validation On-the-fly re-validation
(Read + 1st query) (Update + query)
• Top: • Top:
Eclipse OCL,followed by Incremental EMF engines
EMF-IncQuery • 5-10x faster than OCL
• Dominating: Read time • EMF-IncQuery
• SPARQL tools: frequently outperforms
1-2 orders of magniture JBoss Drools
slower than top EMF • Response time:
tools below 100ms for up to
1.5M elements
• Memory: ~1 GB

41

EMF-IncQuery for Software Maintenance
Existing program query Ongoing application of
tools EMF-IncQuery
• JQuery, CodeQuest, • Interconnection of
PQL, SOUL, JQL, ASTLog software module
• Incremental solutions: • 4 million model
Willis et al. (JQL), elements
Rothamel&Liu08, … (classes + packages)
• coding conventions, • Much larger than
metrics, refactoring Eclipse JDT could
opportunities, handle
design patterns,
run-time errors

42

Incremental Model Transformations

Overview: Incremental Model Synchronization
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test

Incremental model synchronization
Fault Trees, etc.)
by change-driven transformations

Incremental Forward Transformation

MSRC TRACE MTRG

1. First transformation

2. Source model changes

3. Apply changes to
target model

M’SRC TRACE’ M’TRG

Practical application scenarios: Solutions:
• Incremental model synchronization • Bidirectional transformations
• Tool integration • Change-driven transformations

Incremental Backward Transformation

MSRC TRACE MTRG

1. First transformation

2. Target model changes

3. Apply changes to
source model


Challenge: Recent Approaches:
SRCTRG specified A. Schürr, P. Stevens, N. Foster, T. Hettel,
TRGSRC inferred Cicchetti&Pierantonio, Czarnecki&Diskin

Incremental Deployment of Business Processes
Goal:
• Avoid full redeployment of XML
upon changes in BPMN model
• Apply model changes
asynchronously (any time later)
• Send changes via a XML-DOM API

NewAct <action name="NewAct">

Business Process Model Executing business process
• EMF model (BPMN) • XML document (jPDL / JBoss)
• Available in Eclipse IDE 47 • Deployed on a remote server

Change Driven Model Transformations

MSRC TRACE MTRG

Change Driven Model Transformations
Change Change
ModelSRC ModelTRG


Change Driven Transformation Apply Target Change Model
• Input: consumes change model • via an API with little trace info
• Output: produces change model • target model is not materialized!
Ráth, Varró, Varró : Change Driven Transformations- MODELS 2009

Design Space Exploration

Hegedüs et al.: Quick fix generation for DSMLs. VL/HCC 2011

Hegedüs et al.: A Model Driven Framework for Guided Design Space Exploration ASE 2011

Model-Driven Guided Design Space Exploration
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
Generation Generation Model-driven guided
design space exploration
Design + V&V Artifacts • Quick fixes for DSMLs
(Source code, Glue code, • Design of ARINC653 configs
Fault Trees, etc.)

Fixing errors in modern IDEs
Visual Studio Smart Compile Auto Correction
Netbeans Editor Hints
Eclipse Quick Fix

51

Our Context: Validation of BPMN processes
Standard How to fix these
Eclipse BPMN tool inconsistencies?

52

Quick fix generation for BPMN editors

53

Design Space Exploration

Goals Design
Alternative 1

Global
Design
Constraints
Alternative 2

Operations Design
Alternative 3

Initial Design Design
Design Space Exploration Alternative 4

Special state space exploration
• potentially infinite state space
• „dense” solution space
54

Model Driven Guided Design Space Exploration

Model queries Seq of Transf.
as Goals Initial model Rules 1
Operation
Model queries
Modified model Seq of Transf.
as Constraints
Constraints Rules 2
violated
Transf. Rules Goals
as Operations satisfied
Seq of Transf.
Rules 3
Solution model

Initial Seq of Transf.
Model Design Space Exploration Rules 4

Guidance for exploration: Hints
• designer / end user
• formal analysis
55

Result: Quick fix generation for BPMN editors

Sequence of
List of fixes Context
edit operations

56

Back-annotation of
Execution Traces for Model Analysis

Overview: Back-Annotation of Execution Traces
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
Generation Generation Back-annotation of
execution traces
Fault Trees, etc.)

Model Analysis: Motivation for BPEL
Receive request

Event: Cancel
Calculate Rating
Rollback changes

Accept?
Yes No Throw Error

Send offer Send rejection
Requirement:
Receive answer
Receive Every received request
update request must result in a reply!
No Yes
Update?
Will the business
process assure this?
Send reply

Motivating scenario (cont.)
Receive request

Event: Cancel
Calculate Rating
Rollback changes

Accept?
Yes No Throw Error

Requirement:
Receive answer
No Yes
Update?

Send reply

Motivating scenario (cont.)
Receive request
Returns with a web-
service error
Event: Cancel
Calculate Rating
Rollback changes

Accept?
Yes No Throw Error

Requirement:
Receive answer
No Yes
Update?
Not executed =
Send reply No reply

Model Based Analysis
System design Mathematical analysis
Model
High-level
generation Mathematical
System Model
Receive request Fix problem
model
Calculate Rating

Accept?
Yes No

List of
Receive answer
Receive
update request
inconsistencies Analysis
No
Update?
Yes (e.g model checker)
Send reply

Counter-example / Execution traces



Back-Annotation of Counter Example Traces
Model
High-level
System Model
Receive request Replay of
model
source trace
Calculate Rating

Yes
Accept?
No Back-annotation
of target trace
Receive answer
Receive
update request
Analysis
No
Update?
Send reply

MPN TR MBPEL
BPEL Activity Select Transition
map
Startable CHMPN CHMBPEL
Delete Tokens
IF
MPN’ TR MBPEL’ Fire Transition
BPEL Activity
Add Tokens
Runs
Select Transition
BPEL Activity
Executed Fire Transition

Replay Traces in BPEL Simulator
Model
High-level
System Model
Receive request Replay of
model
source trace
Calculate Rating

Accept?
Yes No
Back-annotation
of target trace Analysis
Receive
Receive answer update request
No
Update?
Send reply

Extended BPEL Simulator:
• Current state: coloured
• Intuitive navigation
along the trace 

Software Maintenance Techniques
for Model Transformations

Reengineering and Model Transformations
Graph eXchange Language TTC 2011: Transformation
(GXL) Tool Contest
• R. Holt, A. Schürr, • Case for program
S.E. Sim, A. Winter (2000) understanding /
• Used by >30 tools reengineering (T. Horn)
(from both communities) • Solved by 7 MT tools

parse
Source code Model query

67

Design Patterns and Metrics vs. MT
Design Patterns Design patterns
Metrics for MT
by MT for MTs
• Design pattern / • Good design • Quality assessment
smell captured as a practices for MT for MT
query • Karsai et al, • van Amstel et al.,
• Modifications as Iacob et. al, Vignana, Saeki,
MT rules Lano et al., Kapova et al.,
• Extensive literature • Only since
2009/2010

Design Metrics
Pattern Definition
query query measure

Model Model MT
68

Refactoring vs. Model Transformations
 MT for refactoring
MT
o T. Mens, G. Taentzer,
Model 1 Model 2
o L. Vidács, R. Ferenc,
M. Gogolla
Source Source o Van Eetvelde,
Code 1 Code 2 Janssens
o J. Grey, …
o EMF-Refactor
MT1 MT2  Refactoring of MT
as model as model
o Ehrig et al. 2009
refactor

69

Migration / Evolution
change  Model migration
Metamodel Metamodel o Metamodel
v1 v2 changes to new
version

Model Model Migrate model
instances
update o Tools: COPE/Edapt,
change EPSILON FLOCK,
Metamodel Metamodel (Herrmannsdörfer,
Kolovos, Paige,
v1 v2 Levendovszky et al.)
 MT migration
MT MT o Mendez et al.
o Roser&Bauer
update
70

Slicing of Model Transformations
 Problem:  Idea 
o Erroneous MT invalidates Apply program slicing
formal analysis results o Identify parts of
 Motivation: a MT program
o Debugging of MTs o Causally dependent on
a selected statement
o Focus on specific executions

Transformation Transformation
Program Slice

Models Model Slice

Model Transformation Slicing
Z. Ujhelyi, A. Horvath, D. Varró: Dynamic backward 71
Slicing of MT programs. ICST 2012

Foundations of Model Transformations
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design Foundations:
rules
Code Test • MDSD= early validation +
auto-generation of sources
• DSMLs drive modern tools
• code,
(Source code, GlueMTs drive bridges (integration)
• MT rule = Query + Manipulate
Fault Trees, etc.)

Incremental Validation of Design Rules by Model Queries
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
EMF-IncQuery
(Source code,
•Glue code,
Design + V&V Declarative graph query language
Artifacts

• Incremental caches of result set
Fault Trees, etc.)
• Scalable performance:>1 M elems

Incremental Model Synchronization by Change Driven MT
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
Change driven transfomations (CDT)
Design• Changes stored as change models
+ V&V Artifacts
• CDT: Source
Config. Tables, Test Cases, Monitors, change  Target change
Fault Trees, etc.)
• Non-materialized target models (API)

Model-Driven Guided Design Space Exploration
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
Guided DSE (є Search Based SE)
• Potentially infinite search space
Config. Tables, Test • Frequent solutions
Cases, Monitors,
Fault Trees, etc.)
• Hints to guide exploration

Back-Annotation of Execution Traces
Model generation
Model Model
Back-Annotation
Refine Use
rules Architecture

Design
Model
Model
Use
methods
Design V&V
Model Model
Back-Annotation
Design
rules
Code Test
Back-annotation
• Goal: Hidden formal methods
• TRG execution traces SRC execution traces
• Demonstrate /Monitors, problem in
Config. Tables, Test Cases, Replay
Fault Trees, etc.)
SRC (engineering) model

Future Research Challenges
Many thanks to
Metrics for  Contributors:
MT G. Bergmann,
L. Gönczy
Á. Hegedüs,
Refactoring Slicing of Á. Horváth,
of MT MT B. Izsó,
A. Pataricza,
I. Ráth,
Z. Ujhelyi,
G. Varró
Design
and many more
Migration
patterns
of MT Thanks for your
for MT
kind attention!
78

A Bridge over Troubled Water: Synergies between Model Transformations and Software Maintenance Techniques

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (6)

Similaire à A Bridge over Troubled Water: Synergies between Model Transformations and Software Maintenance Techniques

Similaire à A Bridge over Troubled Water: Synergies between Model Transformations and Software Maintenance Techniques (9)

Dernier

Dernier (20)

A Bridge over Troubled Water: Synergies between Model Transformations and Software Maintenance Techniques