Migration of Domino Application Landscapes

… using cedros Software Analysis & Measurement methodology – c.-SAMM™

Cedros Gesellschaft für Datenverarbeitung mbH

Founded in 1991 as GmbH, business volume in 2012: 14,1 mio

73 IT experts and consultants equipped with comprehensive technical-

and domain-know-how

Headquarter in St. Augustin near Bonn

Software-Development und -Consulting (Java, .net/ASP, @Notes,

SharePoint)

Experts for e-Collaboration and implementation of Business

Applications

Own tools and methods to analyze and measure implementation

effort estimations in software projects

Hosting and Maintenance of business critical applications

What would you say?

What is the Value of your Lotus-NotesApplication Landscape?

Do you know the

Complexity of your applications?

Who are the End-Users of business applications?

What is the dimension of

Migration Costs?

We should talk if you can‘t answer these questions

Overview: Migration of Notes Infrastructures

Migration of PIM Components(mail, calendar, contacts, etc.)

less challenging:

Standardized approach Existing and proven tools make migration

more easy Costs depend on number of mailboxes and

amount of data Firm price for a migration can be calculated

directly

Migration of Notes Applications(libraries, workflows, complex apps)

medium to strongly challenging:

Costs depend mainly on number and state of applications

Cedros has a proven method to gain necessary knowledge of the application landscape

Basic information is the measuring of the landscape and the source code relating technical and functional complexity

Cedros divides the strategic consultation of Lotus Notes Domino into two separate disciplines. Both fields can basically be directed independently from each other.

Methodology at a glance

Measurement Analysis Evaluation Planning Migration

Analysis Application: Automated inventory taking of the application landscape

Results

> Application Catalog> Usage Data> Replications> 3rd Party Products> System Files> Design-Exports> etc.

Static code analysis: Measurement of implementation effort, complexity and maintainability

Results

> Efforts> Interface Indications> Notes Specific Features> Duplicate Code> Dead Code> Maintainability> etc.

Customer specific evaluation: Clear presentation of the analysis results

Results

> Overview> Cost/Gain> Top 10 Rankings> Platform Eligibilities> Statistical Raw Data> etc.

Application categorization and customer tailored migration plan

Results

> Consolidated AWL> Migration list> Project effort> Comp. Scale Factor> Situation modifier> etc.

Consolidation and Migration to the defined target platform

Results

> Successfully completed Migration Project based on maximal transparency and planning certainty

a

b

c

d

e

j

i

f

g

h

5

5

10

6

34

5

5

82

1

20

116

3

1

3

8

Technical Analysis Consulting

Funneling down large app infrastructures

App

App

App

App

App

App App

Scan of 74 Domino Servers with a total of 24.817 filesFiltering based on rules• System/Other: 13.557• 3rd Party: 1.562• Replica/Template/Instance: 7.209• Content Libs: 269Reduced to 2.220 custom applications• Missing: 4662

Analyzed by c.-AppScale: 1.754 o/w• Duplicates: 682• Unused: 296Resulting in 776 unique applications with usageTotal consolidated application value: 21.830 PD

Based on Cedros experience, a business unit initiated decommissioning may lead to the following numbers of “left-over” applications:

• 20% reduction in a worst-case scenario: 620 applications• 75% reduction in a best-case scenario: 194 applications• 38% reduction in an average scenario: 481 applications

Analysis

Estimation

The application landscape of Zeta-Corp has been analyzed regarding Domino migration packages. A Migration project was planned in detail based on the results.

Transparency via Code Analysis

Static code analysis provides means to quickly understand an application‘s source code structure and exposes potential tripping hazards when it comes to migration.

Value Estimation using standardized methods

ISBSG‘s industrial standard is used to compute the effort that has been used to build a Notes database– an important indicator for the assessment of an application.

# Small

# Medium

# Complex

38

32

23

Effort Small

Effort Medium

Effort Complex

171

869

3,048

The overal project effort according to the ISBSG-industrial standard for Lotus Notes adds up to 4.088 person days. Thereof 1.758 person days ran into the programming (build effort).

Cost/Gain Analysis

Customer specific application clustering are derived from the analysis results and presented well-arranged.

Using the results of the modules „Measurement“ and „Analysis“ cedros compiles different rankings.

Top 10 Rankings

Value [PD] Usage # Documents # Templates

1. PressServer (542 PT)2. PCLC MailinBox (499 PT)3. Imageupload eGK (454 PT)4. Forms (380 PT)5. SportsEvents (327 PT)6. DoctorsApp (327 PT)7. FeedbackManager (317 PT)8. V&G (204 PT)9. Pro DMSplus (167 PT)10. Memo (149 PT)11. mail (146 PT)12. online Backend (132 PT)13. TeamRoom 0070 10 (117 PT)14. Master-Adressbook (115 PT)15. Request-DB 2.5 (113 PT)

1. AdressBook (2.857) 2. mail (1.278)3. Departments-DB (944)4. Client Configuration (477)5. FeedbackManager (320)6. EmployeesData (303)7. V&G (287)8. Forms (278)9. MAR_BE (249)10. StartPage (173)11. Law-DB (79)12. Request-DB 2.5 (49)13. Memo Bulletin Boards (39)14. RZ Requirements (32)15. Roles 2.1 (25)

1. mail-Forms (571.921)2. eGK Backend v1.0 (543.635)3. V&G (458.562)4. mail Archiv-Index (400.939)5. MAR-BE (293.794)6. EMS MailFilter (151.558)7. mail-Outbound (115.867)8. FeedbackManager (104.821)9. V&G – Archive (97.171)10. Agents (72.146)11. Request-DB 2.5 (71.914)12. mail-SMTP (58.660)13. 2005 online Forum (50.169)

1. StdR7Mail (1.486)2. Pattern ScannerDB (375)3. SY_Content_BDB_DE (147)4. StdR4PublicAdrBook (81)5. StdNotesMailbox (51)

Barriers are exposed within the analysis

Notes specific functionality and interfaces are hard to migrate – our analysis detects these obstacles, they are display and thus enables to plan these challenges.

Appraisal of obstacles per target platform

Comparing the functional size of a target platform with the functionality to be migrated shows the obstacles to expect and focus on.

Periodic AgentsReplication Formulas

External Code

Role Usage *

Messaging

Multiple Element Agents

Non-Role Hide-WhenAuthor/Reader-Fields

Read-Only

View Formulas

Embedded Views

Signed Elements

Encrypted Fields

Focus items

Microsoft SharepointTarget Platform Evaluation

Cost Transparency via FSM

Using function point assessment enables us to present maximal cost transparency – the migration effort can be computed for a given target platform.

Functional Size Measurement

FSM is a methodology used to estimate the effort of software development projects base on functional requirements (non-technical)

The Functional Size of an application has been determined according to ISO 29811 (FISMA) by means of functional requirements or based the design of the application.

Consulting further criteria like delivery rates, individual project parameters and reuse factors enables to establish benchmarks for other platforms.

This is significant information in any migration project.

Effort

Functional Size

Delivery Rate

Project Situation

Re-Use Factor

Keep Notes

Content Transfer

Core System

Web Enablement

Custom Development

Examples for Target Platforms

Archivno development efforts low costsexternal hosting possible not suitable for critical data bases

no development effortsonly suitable for obsolescent data basesno direct decommissioning

efforts for data migrationno development efforts

medium effort

no client-side license necessaryserver-side implementation efforts

greatest effort

Examples of Applications – 1:1 Migration

Application Complexity FP (backfired) XPages SharePoint OOTB

Inventory Approvals L 274 (127/147) 31 – 93 PD 371 PD

Zeta Corp Workflow L 454 (255/199) 63 – 188 PD 589 PD

Material M 21 (8/13) 2 – 6 PD 31 PD

Purchasing S 4 (3/1) 1 – 2 PD 4 PD

This result is based on the following:

Median Delivery Rate for ASP 6,7 h/FfpMedian Delivery Rate for C#15,1h/FfpMedian Delivery Rate for XPages Basic 2,0 h/FfpMedian Delivery Rate for XPages Advanced 5,9 h/Ffp

Function Points based computation of migration efforts enable early project budgeting and show alternatives.

• Business Rules• Roadmap• Overall Efforts

Create Migration Plan

Holistic App Catalogue• Scan with c.-AppScan™• # Server/Applications• Usage Scan

Identify Responsibilities

• Responsibility for Realization• Responsibility for Costs• Departmental Responsibility• Right to Information

Technical Analysis• c.-AppScale™ Detail Analysis• SW-Metrics• Calculations

Aggregation• Quality Assurance• Key Statements• Visualization• Efforts according c.-SAMM™

Define Migration Goals

• Potential Target Systems

Status quo and next steps

Technical Analysis

Planing

Questions?

Philipp KönigsBusiness Unit ExecutiveMember of the Board

Cedros Gesellschaft für Datenverarbeitung mbHSiegburger Straße 3553757 Sankt AugustinDeutschland

Fon: +49 (0)2241 8834-16Fax: +49 (0)2241 8834-11

Benefit from our experience of analyzing more than 250.000 Notes applications – for further information see http://www.insight-notes.com

Individual strategic decision based on cost/usage

Input:Global c.-SAMM™ App Catalog

Tools1. Business Rules2. Questionnaires3. Interviews

Output:Target System/Action per App