Phase Two: Analyze Data


Topic Last Modified: 2006-09-14

The goal of the second phase of analysis is to perform in-depth reviews and analysis of the unique applications identified in Phase One.

Whenever this document refers to unique applications, this means that when a number of applications share a common design, they will be considered one unique application that requires analysis and recommendations. Likewise, if multiple replica copies of an application exist, as long as the design is replicating, they will be considered one unique application that requires analysis and recommendations.

Any application that was based on a default Lotus Domino template (quadrants one and two) does not require any additional analysis because these templates are well known. Custom applications (quadrants three and four) require additional analysis before recommending a target solution.

To provide recommendations for custom applications, it is critical that a comprehensive analysis of all features and functionality be performed. To fully understand and document a custom Lotus Notes application, we recommend that you focus on the logical components of the application.

Data/Content Elementsinclude text, numbers, time/date, and file attachments and data interaction within an application such as reply records and back-end connectivity to external systems such as SAP, SQL, and DB2.

Business Logic/Processes consist of the actions and events that are triggered within an application. Business workflow functionality is included in this component category.

Presentation Layer/Functionalitydescribes items such as off-line access, role-based security, reporting, and forms-based data input.

Usage Patterns provide information about the users who access the application, their level of security access, and the amount of reads/writes/edits performed on the data in the last 365 days.

By using this comprehensive approach to research a Lotus Notes/Domino application, it is possible to obtain a strong understanding of the application's features and business functionality.

Application users and owners can provide information that cannot be determined from a technical design analysis. This information may include the usage model and application background, which may prove useful in determining an appropriate target solution.