Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


ScalableThe GMM works equally well with small efforts to upgrade a single, simple VBP on up to mammoth-size programs involving hundreds of inter-related VBPs and millions of lines of code. Of course, the ROI for using migration tools increases as the size of the codebase. Very large, mature codebases (>500K lines of code) can contain 100s of person-years of investment and leveraging migration tools to help you rewrite the code can dramatically reduce the cost, risk, and disruption of a migration effort. 
IterativeThe migration is done via a series of tuning cycles. Each tuning cycle produces a more effective conversion process by resolving a (diminishing) number of migration issues with each iteration. The end result is a highly efficient process that balances manual work with automated re-engineering. When the Migration Team agrees that the automated translation is "good enough" and the only manual issues left are those that were identified as being easier to do by hand, they do a final Cut-Over translation. Cut-Over is followed by a short Fit & Finish phase to certify the new system and deploy it to production. 
Test-DrivenTesting is a crucial activity in each iteration. The effort required to do a migration is driven by the issues found and resolved during the tuning process. 
AdaptiveWe assume a working source codebase, not a frozen codebase. Throughout the migration, the legacy application may be maintained and enhanced for ongoing maintenance. Updated versions of the VB6/ASP/COM codebase may enter the migration process as they become available – typically on the established release cycle of the legacy application. 
MeasurableThe use of automated translation, build, and code-review procedures (along with test-driven refinement of the process) facilitates an ongoing collection of metrics relating to code quality and progress. Migration progress is predictable, incremental, and easy to track. 
RepeatableThe gmStudio can be calibrated to produce a variety of .NET outputs by a user-defined configuration. The configuration files, translation scripts, and other artifacts provide a detailed record of the rewrite rules and other information that document the transformation and make it repeatable.

Repeatability is an extremely valuable capability if you have many components to migrate and you want to eliminate repetitive tasks or if you must be able to redo conversions on a changing source codebase. 

BalancedWe certainly do not expect the toolset any to completely automate every aspect of your rewrite project. The tuned migration process also integrates code that was written manually by the migration team or acquired from other sources. everyone's possible upgrade requirements a general way. Instead of pursuing impossible goal, we have developed an extremely fast, flexible, and extensible upgrade solution development platform. gmStudio can help you produce customized translations that automatically integrates hand-written code developed manually or acquired from various sources. This makes repeatable the process of producing an upgrade process that integrates manual and automated transformation.
Tool-AssistedWe leverage gmStudio -- our proprietary software re-engineering tool -- to facilitate work in all phases of a migration effort.