gmStudio was initially created to help us deliver large-scale custom migration services to our clients. Early in our discussions with these clients, we were always asked two questions:
Creating Estimates from metrics looks simple enough:
R = X * Y where: R = total amount of resources needed to "do the migration" X = number of "units" to be migrated (applications, components, fields, lines of code, etc.) Y = per unit cost (amount of resources needed to complete one unit of migration)
|You cannot know how far you have to travel until you know where you are starting from and decide where you are going.Beware that assessment work alone does not tell you how to solve your problems, it only helps you understand them better. You must still develop an understanding of what the new platform has to offer -- both the good and the bad -- and agree on which designs will work well with that platform. You will have to do this design work no matter if you plan to use tools or start from scratch. The source code assessment helps you know what you are getting into. Using tools helps you implement and experiment with new designs in a more systematic and efficient fashion.|
gmStudio Reporting Overview
gmStudio can produce a variety of useful reports to help you plan, execute, and measure the progress of your migration effort. There are four classes of reports:
The gmStudio report titles and output file names are listed below:
|Code Scan Reports|
|Source GUI Scan||[MigName]-SrcGUI.tab|
|Source Code Scan||[MigName]-SrcScan.tab|
|.NET Build Logs||[MigName]-BldLog.tab|
|Interface File Headers||[MigName]-LibHeaders.tab|
|Interface File ProgIds||[MigName]-LibProgIds.tab|
|Semantic Model Reports|
|Migration Project List||gmProjects.tab|
|Target Code Scan||[MigName]-BndScan.tab|
|Target Code Chanfges||[MigName]-BndChanges.txt|
Most reports are driven off selected tasks in the Migration Project. You indicate which migration tasks to include in a report by selecting them in the migration panel.
Most reports are written to the report folder in your migration workspace.
There are three ways to run gmStudio reports:
Once you have your code into .NET, Visual Studio offers several useful reports. See Code Analysis and Code Metrics in the Visual Studio documentation.