Use the AppDNA Effort Calculator to estimate the time, cost, and effort associated with migrating a portfolio to a new platform – for example, that it will take five people six months and cost $500,000. Effort Calculator uses a number of variables that define, for example, the cost of a tester per day, the number of working hours in the day, and the time to test an application of a given complexity. You can configure the variables to reflect the specifics of your organization. AppDNA produces a detailed breakdown of the cost and how much time it will take to remediate the applications as well as the potential savings that AppDNA can provide.
To open the Effort Calculator, from the side bar choose.
Using Effort Calculator involves the following steps:
The first step in using Effort Calculator is to select the report that represents the project for which you want to calculate the effort. For example, if you want to calculate the effort for a Windows 7 migration project, select the Windows 7 report. AppDNA lists the available reports on the left side of the screen.
When you select a report, the right side of the screen provides a summary that shows the overall status of the currently selected applications that have been analyzed for that report.
To change the applications that are selected, click Change Selection on the right side of the toolbar. In the Application List, select the applications you want to include and then click Select to apply them.
Click Next to move to the next step.
The main Effort Calculator screen provides a summary that gives an estimate of the effort required to remediate the applications in the portfolio for which there are known remediations while highlighting applications that require further testing or need to be treated as exceptions. Applications are considered exceptions if remediation is not possible. This means that the application may need to be redeveloped or decommissioned.
The summary includes two pie charts:
Below the summary there are four tabs.
|Number of applications in the full portfolio||Defaults to the number of applications already imported. You can increase this to reflect the size of your actual application portfolio. AppDNA then extrapolates the effort to migrate the entire portfolio, based on the sample results.|
|Currency||See http://www.xe.com/iso4217.php for a list of international currency codes.|
|Smoke testing time||The time in hours to perform an initial install and run test, commonly known as a smoke test. This is not usually an in-depth test.
|Applications that are expected to have issues||The number of applications that are expected to have issues as a percentage of the portfolio. The default value is derived from a variety of market sources, from analysts to technical engagement feedback. The value can vary based on enterprise-specific processes and application readiness.|
|Applications that are expected to be exceptions||The percentage of applications that cannot be remediated, or where a decision has been made not to remediate. This variable can change dramatically based on the application portfolio's age. An older portfolio typically has a greater percentage of incompatible applications.
|Time to identify the cause of a failure and resolve it||A per-application estimate of how long in hours it generally takes to identify a failure and fix it when AppDNA is not in use.
|Staging time||The average number of hours to install an application in the target environment and ensure it is running.|
|Size of remediation team||This depends on the size of the application portfolio. Typically, there is one remediation specialist for every 250 applications.|
|Size of testing/staging team||This depends on the size of the application portfolio. Typically, there is one tester/stager for every 100 applications.|
The rows represent the complexity of applications. AppDNA measures application complexity in terms of the number of files and registry entries. Configurable thresholds define whether an application is considered simple, normal or complex. You can configure the thresholds in Reporting Settings. For more information, see Reporting settings.
The columns represent the complexity of the remediation. AppDNA identifies issues in applications by running sophisticated heuristic algorithms during the analysis process. Each algorithm identifies a specific issue and has a recommended remediation action to mitigate that issue. The effort associated with these actions is categorized as easy, medium, or hard. The overall remediation effort for an application is based on the highest effort associated with the algorithms that the application triggers. You can optionally configure the remediation actions in the Algorithm Groups screen. For more information, see Configure algorithms.
You can export all of the Effort Calculator results (along with explanatory information) to a Word document. This requires Microsoft Word to be installed on the same computer as the AppDNA client.
To export this report, click Export on the main toolbar. After a short delay, Microsoft Word opens and displays the exported report.
You can export your Effort Calculator variables – as an XML file for later retrieval. This makes it easy to compare different scenarios.
To export your Effort Calculator settings:
To import the settings: