Revolutive IT™




Key Reasons & Benefits:

Lower costs
Better leverage past IT investments (for automated processes)
Eliminate dead code and redundant code
Fixed Price Projects (for automation processes)
Reduction of the HW and SW Total Cost of Ownership
No need for external staff (=> no additional PC, SW licences, rooms, access cards and other material)
Immediate result
project schedule dramatically compressed
Our ability to compress your project schedule minimizes operational disruptions
Proven low-risk technology (transformed code 100% functionally equivalent to the source code functionality) and 99+% automated
Avoid long-term commitments
No extra-budgets
Software's maintainability and operational performance improvement
Timely High-Capacity Production-Ready Service Providing Code that is Compiler-ready, Testable, Documented
Uniformity of translated code
The result is known in advance since the starting point is an existing system (for automated processes)
Revelation of business rules (for automated processes)
Incremental development
You will have the flexibility to tailor your system's architecture and functionality
Better use of existing staff
Increased motivation of staff
Perception of safety and trust
Access to modern support applications
You can set and keep the focus on your core business

System Migration - Modernization

T he Intermediate Object Model is the relatively complete transformation of the input source code in the intermediate model that is a language neutral hybrid between the structure of legacy and object-oriented language from which either C, C#, Java or C++ can be generated automatically. The classes, relationships, attributes and operations of the derived IOM model conform to Universal Modeling Language (UML) standards and can be exported to UML modeling tools. The mapping from the IOM into target OO language creates a fully complete, modernized object-oriented code for the system. The newly generated code possesses a design architecture and control structure consistent with the OO programming paradigm.

The system transformation processes is comprised of a wide range of tasks, including the physical transformation of the application software, user interface, databases and platform adaptation. A typical transformation is highly automated. The user interface is automatically transformed into a functionally equivalent user interface in the target environment. The database is converted using information derived from the system database descriptions that drives database conversion programs. Platform and operating system calls are transformed into equivalent target environment services.

The difference between transformation and migration is that the migration implies a platform change (new HW and SW, and/or database system, language, etc.). The modernization process is mainly used for Quality purpose, re-factoring the code is the process of changing a software system to improve the software's structure and performance without altering its functional behaviour. Re-factoring is used to eliminate, replace, or rewrite code to improve its efficiency and understandability or to transform applications to use a suitable set of modern infrastructure support functions.

Our services are the most efficient, flexible, quality-based and cheaper of the market, due to our fully innovative and customer-driven approach. Discover them and compare them to the solutions provided you by our competitors.

Copyright 2002 Atlantis Technologies. All rights reserved.