1. 5M lines of code to migrate Howto with Eclipse Modeling tienne Juliot [email_address] Mikal Barbero [email_address]

2. Objective 3. 4. DEMO 5. Migration Step by Step 6. BIRD'S EYE VIEW Parse thecode Definetranslationdictionnary Implementthe translator Processiteratively 7. PARSE THE CODE 8. DEMO 9. ESTABLISH EQUIVALENCE RULES 10. ESTABLISH EQUIVALENCE RULES Specificy and document Define elements to translate first 11. DEMO 12. TEST DRIVEN IMPLEMENTATION Model of source code Transformation templates Source code BEFORE Source code AFTER Metamodel of source code 13. DEMO 14. ITERATIVE PROCESS Equivalencerules definition Migrated code evaluation OBEO PARTNER 15. # compilation errors inmigrated code helpsmesuring output quality Achieving 'good' qualityrequires lots ofback and forth THE LESSON? FOLLOW THE QUALITY 16. BUT WHEN? 17. Defining a target may be somewhat difficult 18. USE INDICATORS TECHNICAL DEBT SOFTWARE MINING 19. DEMO 20. Does it Scale? 21. Project for a Frenchadministration Success THE FACTS 10 years old critical application Made with declared EOL Fort UDS 5,000,000 LOC Iso functional migration Same performance (30,000 users) 4 errors / 10,000 migrated LOC (99.96%) THE GOALS 22. Available technologies COBOL (GCOS / MVS UNIX / CICS) DELPHI C/C++ ASP ABAP JHTML (ATG) JSP Java 5 FORT Flex Omnis OracleForms NSDK NATURAL LTR3 Power Builder Pro C PL1 PL/SQL Pascal VB 6 VB .NET Struts SQL Progress 23. [email_address]