Modernization Console
For Optimization, Modernization, Transformation & Migration of Systems

| Optimization & Modernization Screen-Shots |----| FAQs |----| User Guide |----| Executive Summary |


Discovery and extraction of business rules embedded in an organization’s legacy application is the first step to solving the legacy problem. Next the IT Department must decide whether that application should be retired, replaced or migrated.

Each option must be weighed with care as neither option is without risk or cost. To understand the risk and rewards of each option click here.

If embedded business rules in a legacy application are relevant for the foreseeable future, migrating that application to C#, VB.Net or Java running on a distributed platform is possibly the most viable option. However, the application has most likely evolved over time and includes “dead” and inefficiently implemented rules. Hence migration “as-is” will not result in the most efficient target. Additionally, to generate target that is understandable, it is important that variable and entity names in the target are descriptive, not cryptic as in the source code.

Such optimization and modernization at the code level will only result in target code that is “bloated” and difficult to maintain. This task is best accomplished at the business rules’  level using a workbench.

S2T’s Modernization Console serves as just such a workbench, allowing its users to:
  • Optimize & Modernize business rules extracted by EvolveWare’s Modernization products like Legacy Rejuvenator
  • Transform and Migrate the modified rules into native target code in C#, VB.Net and Java; or into models for code-generation products like CA Gen
During the optimization and modernization phase, the console users may:
  • Generate program linkages
  • Generate business rule linkages
  • Annotate business rules
  • Export business rule into MSWord and any Graphics Modeling Language (GML) editor
  • Dynamically replace variables and entities in business rules with descriptive keywords
  • Change names of business rules to reflect their individual functionality
  • Deactivate individual business rule statements (Slicing)
  • Deactivate entire business rules
  • Merge business rules
| Legal | Careers | Investor Relations | Sitemap |
| Top | Home |