Export (0) Print
Expand All
3 out of 3 rated this helpful - Rate this topic

Application Analysis Envisioning Process

 

Topic Last Modified: 2007-04-27

The Application Analysis Envisioning Process (AAEP) for Lotus Domino applications provides you with a process to identify and classify Lotus Domino infrastructure, understand their core components and functionality, and provide accurate guidance for a recommended target solution. The primary goal of this process is to encourage a standard approach that you can use to define migration and target solution recommendations, as well as estimate migration costs and timelines.

New versions of the Application Analyzer and the Application Transporter tool for Lotus Domino have been released as part of the Microsoft Transporter Suite for Lotus Domino. This document contains information about the Microsoft Application Analyzer 2006 for Lotus Domino and the Exchange Transporter versions of the tools.

AAEP concepts fit well with other methodologies such as the Microsoft Solutions Framework (MSF) or Project Management International (PMI) as part of an envisioning or discovery phase. AAEP has four phases:

  • Phase One:   Data Collection
  • Phase Two:   Data Analysis
  • Phase Three:   Target Solution Mapping
  • Phase Four:   Architect and Proof of Concept

Each phase collects and aggregates information and builds upon the data gained from the previous phases. Following is a brief overview of each phase.

In this phase, you eliminate applications from consideration (such as mail and administration applications), identify the applications that are simplest to move because they are based on the default Lotus Domino templates, group applications that share a common design or are replicas, and identify applications that have not been used for extended periods of time.

Based on the information generated during this phase of the analysis, it is possible to identify the applications that can be migrated quickly and easily to Microsoft Windows SharePoint Services and which applications are either replica copies of the same application or share a common design, which minimizes the total number of unique applications that require additional analysis. Information about the Lotus Domino application servers is also collected during Phase One, including server version, location, and replication topology.

Phase One Goals:

  • Determine unused applications
  • Determine replicas
  • Determine applications that can be consolidated
  • Determine applications that have low usage
  • Determine security settings

Phase One Interviews:

  • Architecture team
  • Server administration team
  • Domino Development team
  • Business Process Owners

In Phase Two, you review the applications that are not based on standard Lotus Domino templates and then perform advanced analysis to identify key functional requirements that are essential in determining the appropriate target solution and migration method. Because Phase One of the analysis grouped common applications, the total number of unique applications that require this additional analysis is frequently significantly lower than the total number of applications in this category.

Phase Two Goals:

  • Leave in place criteria
  • Buy versus build criteria
  • Evaluate existing deployed software
  • Evaluate e-mail system
  • Evaluate Directory
  • Business function and functionality reviews
  • This phase relies on the information collected in Phases One and Two to identify appropriate target solutions for each unique application, which may include products already implemented in the environment, off-the-shelf solutions, Microsoft Collaboration Platform products, or leaving the application in place on Lotus Domino.

Phase Three Goals:

  • Apply the criteria to the applications
  • Begin storage mapping process (map the current Lotus Domino functionality to new technology)
  • Create Directory migration plan
  • Create messaging migration plan
  • Create collaboration architecture
  • Create messaging architecture
  • Create directory architecture

In this phase, the proof-of-concept environment is designed and implemented. Data and users are migrated to the proof-of-concept environment for testing and further planning.

Phase Four Goals:

  • Create migration and capabilities timeline
  • Create application migration plan
  • Create high level future architecture plan
  • Implement proof-of-concept environment
  • Migrate users and applications to proof-of-concept environment
  • Test migration methodology and application functionality in proof-of-concept environment
 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.