This service is divided into two parts: code analysis and specialized consulting. For each of these, a Mobilize.Net migration architect applies different tools and methodologies. It normally involves a 5-day visit to the customer facilities:

Interviews with key staff

  • Architect
  • Project manager
  • Senior developer
  • Experienced end users

Review of the working application

  • “How-it-works” fast track review
  • Real-life use cases

Project environment and client process analysis

    • Organization Analysis
      • Technical resources structure (IT personnel)
    • Management metrics
      • Current project status
      • Allocated resources
      • Quality control process
      • Configuration management (change control and version control process)
    • Development environment analysis
      • Resources experience (programming languages, development methods, management)
      • Resource costs
      • Software environment (operating systems, development environments, testing and deployment software, use of third party software, third party components, integration with other OS and platforms)
      • Software licensing and maintenance costs
      • Hardware environment
      • Hardware licensing and maintenance costs
      • Cost/benefit analysis (ROI)

Application role and dependency analysis

Code analysis

  • Size metrics
    • Lines of code
    • Number of statements
    • Number of components
    • Number of comment lines
  • Usage metrics
    • Frequency of use for each statement (in each source file and function, and global total)
    • Frequency of use for types (e.g. variable types, user type, file types, function types, etc.)
    • Frequency of use for each function, by source file and global total
    • Frequency of use for each data file, data field and source file (e.g. Data Definition Source, Screen Definition Source, etc.)
    • Calls Fan-in and Fan-out for each function and each source file
    • Structure metrics
    • Taxonomy tree of each component
    • Partonomy tree of each component
    • Tree structure metrics (in the taxonomy)
    • Tree functional metrics (in the partonomy)
    • Average connection level (of fan-in and fan-out)
    • Average compositional level (in the partonomy)
  • Complexity metrics
    • Structural complexity (taxonomical and partonomical complexity)
    • Cyclomatic complexity
    • Functional topological complexity
    • Architectural metrics
    • Batch process identifying (if applicable)

Migration project analysis

  • Project goals definition
  • Motivations - main issues that the customer wants addressed
  • Alternatives currently under consideration
  • Desired timeframe
    • Start date
    • Duration or end date
  • Identification of critical success factors (performance or other requirements)
  • Solution priorities:
    • Minimize short term costs
    • Minimize long term costs
    • Maximize scalability and flexibility
    • Minimize company disruption
  • Target platform analysis
    • Strategic IT business plans analysis
    • Initial analysis of the customer’s personnel for the possible target platforms: current knowledge and training plan
    • General software analysis for the possible target platforms (OS, third party software, server applications, etc.)
    • General hardware analysis for the possible target platforms (servers, routers, etc.)

Let us help you move to .NET. Call us today at 888 – MIG - TOOL (888 644 8665) or email us at