Yes, the console allows the user to select programs from a single application to generate a target.

Yes, the console does not limit the user from generating each target in a different language like C#, VB.Net, Java or CA Gen models.

Yes, the console creates a single repository of all the business rules transferred to the console. No distinction is made with respect to the languages that were used to program these rules. Once these rules have been optimized and modernized, the console can generate a single target application or multiple target applications in one or multiple languages.

No any rule that was deactivated is not transformed or migrated to target. Statements within rules that were deactivated are also not included in transformation and migration.

The annotations placed by the user are shown as method level comments in the target code.

The console generates the target code using a defined structure for the selected platform. The structures have been adopted from Microsoft’s and Oracle’s architecture standards which clearly distinguish the business logic layer from the data access and logging/security layers. Even the screen access layer depicting a MVC framework is generated. To view a typical target architecture Click here.

The .Net code generated uses Microsoft’s Enterprise Library Framework while the Java code generated uses Log4J Framework.

- When generating .Net code the user may select the Namespace attribute and the Visual Studio version (Visual Studio 2003 or 2005) in which the target must be generated
- When generating Java code the user may select the Package Name attribute that will be used to define the hierarchy in which the target will be generated

The user interface or screens are generated as ASP.Net forms for .Net (both C# and VB) and as plain JSPs for Java.

The console maps the data access statements as standard SQL queries and may be used with any database. The target code data access layer consists of abstract classes that can be easily wrapped around pre-existing data access components available to the user.

The target code will contain standard comment blocks that contain information about the source paragraph or procedure or sub-routine from which the target is derived. The comment header will include the procedure name to facilitate the understanding of source to target mapping. Other items in the comment blocks include annotations, and the history tag.

The target code generated is "native". It contains no proprietary APIs or Libraries and hence there is no recurring cost to maintain this code.

The automation rate for transformation and migration is 75-95%.

The unconverted source statements are placed as comments in the target code. These statements are placed at the exact same location as they appeared in the original source code. An Unconverted Source Statements report is provided as a map to their location in the target code.

The console is licensed based on the number of concurrent users that will access the console. A one-user license is included when licensing EvolveWare’s Legacy Rejuvenator. For details Contact Us.

While this is dependent upon the scope of the initiative, it is very feasible to achieve a time and cost savings of between 40-60% as compared to manually executing the same initiative.