Forms2Net – Migrating Oracle Forms to Microsoft .NET

  • Luis Andrade
  • João Gouveia
  • Miguel Antunes
  • Mohammad El-Ramly
  • Georgios Koutsoukos
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4143)


Forms2Net is an ATX Software commercial reengineering tool that automatically converts Oracle Forms applications to the equivalent .NET (C#) ones, with approximately 75% rate of automatic conversion. From the reengineering and transformation theoretical viewpoint, Forms2Net falls in the general category of language-platform conversion tools. As theory and practice indicate, for such tools to be effective, there are two major issues that must be handled: (a) the resolution of the semantic gap between the pair of source-target languages and (b) the resolution of the dependencies (e.g., API dependencies) on functionalities provided by default by the source platform or on programming idiosyncrasies of the source platform (in this case Oracle Forms). This paper presents the important practical aspects of Forms2Net and the underlying technology. We discuss the semantic gap between Oracle Forms and .NET forms and the design principles and solution strategies used to bridge this gap.


Event Handler Target Architecture Code Pattern Converted Code Architectural Mapping 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    ATX Software, Forms2Net, Available at:
  2. 2.
    Baxter, I., Pidgeon, P., Mehlich, M.: DMS: Program Transformations for Practical Scalable Software Evolution. In: Proceedings of the International Conference on Software Engineering. IEEE Press, Los Alamitos (2004)Google Scholar
  3. 3.
    Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P.: Pattern-Oriented Software Architecture, A System of Patterns, vol. 1. John Wiley & Sons, Chichester (1996)Google Scholar
  4. 4.
    Klusener, A., Lämmel, R., Verhoef, C.: Architectural Modifications to Deployed Software. Science of Computer Programming 54(2-3), 143–211 (2005)MATHCrossRefMathSciNetGoogle Scholar
  5. 5.
    Microsoft Patterns and Practices Center: Application Blocks and Libraries, Available at:
  6. 6.
    Microsoft: Solution Guide for Migrating Oracle on UNIX to SQL Server on Windows, ch. 17 - Developing: Applications - Migrating Oracle Forms. Microsoft TechNet (2005) Google Scholar
  7. 7.
    Mossienko, M.: Automated Cobol to Java recycling. In: Proceedings of the 7th European Conference on Software Maintenance and Reengineering (CSMR), pp. 40–50. IEEE Computer Society, Los Alamitos (2003)CrossRefGoogle Scholar
  8. 8.
    Object Management Group (OMG): Architecture-Driven Modernization Scenarios (2006), Available at:
  9. 9.
    Oracle: Oracle Forms Developer’s Guide, Release 4.5. Oracle Corporation (1994)Google Scholar
  10. 10.
    Seacord, R., Plakosh, D., Lewis, G.: Modernizing Legacy Systems: Software Technologies, Engineering Processes, and Business Practices. Addison Wesley, Reading (2003)Google Scholar
  11. 11.
    Sneed, H.: Risks Involved in Reengineering Projects. In: Proceedings of the 6th Working Conference on Reverse Engineering (WCRE), pp. 204–211. IEEE Computer Society, Los Alamitos (1999)Google Scholar
  12. 12.
    Ulrich, W.: Legacy Systems: Transformation Strategies. Prentice Hall, Englewood Cliffs (2002)Google Scholar
  13. 13.
    Zoufaly, F., Dermody, P.: Issues & Challenges Facing Oracle Forms to J2EE Evolution (2003), Available at:

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Luis Andrade
    • 1
  • João Gouveia
    • 1
  • Miguel Antunes
    • 1
  • Mohammad El-Ramly
    • 2
  • Georgios Koutsoukos
    • 1
  1. 1.ATX Software S.ALisbonPortugal
  2. 2.Department of Computer ScienceUniversity of LeicesterLeicesterUK

Personalised recommendations