From MDA Platform-Specific Model to Code Generation Coupling….pptVIP

A Model-Driven Approach For Information System Migration Raymonde Le Delliou1, Nicolas Ploquin2, Mariano Belaunde3, Reda Bendraou4, Louis Féraud5 1 Electricité de France, 2 SOFT-MAINT, 3 France Télécom, 4 LIP6, 5 IRIT 1 juliette.le-delliou@edf.fr, 2 nploquin@sodifrance.fr, 3 mariano.belaunde@, 4 Reda.Bendraou@lip6.fr, 5 Louis.Feraud@irit.fr Outline The TRAMs project (2002-2003) RM-ODP Standard as an Intermediate Metamodel (IMM) The COBOL to JAVA Demonstrator Coupling RM-ODP and Action Semantics standards Conclusion and further works Aims Define a methodology Provide an open and modular migration framework In order to Insure IS migrations in a cost effective manner Experiment metamodels and model transformation techniques TRAMs: a methodology and a Framework The preparing migration phase Identify the migration nature (business or technologic) Identify the Metamodels to be used Model the migration process (eg. in SPEM) Specify the transformation components The execution phase Monitored by a management component Insured by several tools and components Includes the execution of manual actions/interactions The TRAMs generic migration-process Why an Intermediate Metamodel? To decrease significantly the number of model transformers to be developed To decrease time and cost for further migrations of the Information System IMM Specification : RM-ODP standard RM-ODP (Reference Model Open Distributed Processing) as an Intermediate Metamodel Why RM-ODP? - Generic, stable and rigorous concepts - Concern separation based System Specification: the Viewpoints (Enterprise, Information, Computational, Engineering et Technology) - Used in several domains. The COBOL to Java Demonstrator Migration of a sample of an insurance company application Focusing on the user interface with limited business features Choice of RM-ODP Computational Viewpoint as an Intermediate Model The ODP Computational viewpoint UML Action Semantics standard Action Semantics: an extens