Example outcome of a worldwide IBM Notes Domino application analysis, including usage scan. Customers willing to decide on strategic options regarding the future of IBM Notes and Domino may want to take a look at our offerings: http://www.insight-notes.com

1. Migration of Domino Application Landscapes
… using cedros Software Analysis & Measurement methodology – c.-SAMM™

2. 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

3. What would you say?
We should talk if you can‘t answer these questions
Do you know the
Complexity of your applications?
What is the Value of your Lotus-Notes
Application Landscape?
What is the dimension of
Migration Costs?
Who are the End-Users of business
applications?

4. Overview: Migration of Notes Infrastructures
Cedros divides the strategic consultation of Lotus Notes Domino into two separate
disciplines. Both fields can basically be directed independently from each other.
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

5. 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.
5
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
3
4
5
8
2
1
20
11
6
3
1
3
8
Technical Analysis Consulting

6. Funneling down large app infrastructures
The application landscape of Zeta-Corp has been analyzed regarding Domino
migration packages. A Migration project was planned in detail based on the results.
App App
App
App
App
App
App
Scan of 74 Domino Servers with a total of 24.817 files
Filtering based on rules
• System/Other: 13.557
• 3rd Party: 1.562
• Replica/Template/Instance: 7.209
• Content Libs: 269
Reduced to 2.220 customapplications
• Missing: 4662
Analyzed by c.-AppScale: 1.754 o/w
• Duplicates: 682
• Unused: 296
Resulting in 776 unique applications with usage
Total 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

7. 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.

8. 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.
32
38
23
# Complex
# Medium
# Small
869
171
3,048
Effort Complex
Effort Medium
Effort Small
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).

9. Cost/Gain Analysis
Customer specific application clustering are derived from the analysis results and
presented well-arranged.

10. Top 10 Rankings
Using the results of the modules „Measurement“ and „Analysis“ cedros compiles
different 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)

11. 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.

12. 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 Agents
Replication Formulas
External Code
Role Usage *
Messaging
Multiple Element
Agents
Encrypted Fields
Signed Elements
Embedded Views
View Formulas
Read-Only
Author/Reader-Fields Non-Role Hide-When
Microsoft Sharepoint
Target Platform Evaluation
Focus items

13. 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

14. Keep
Notes
Core System
Content Transfer
Web
Enablement
Custom
Development
Examples for Target Platforms
Archiv
no development efforts
efforts for data migration
no development efforts
only suitable for obsolescent data bases
no direct decommissioning
no development efforts
low costs
external hosting possible
not suitable for critical data bases
medium effort
greatest effort
no client-side license necessary
server-side implementation efforts

15. Examples of Applications – 1:1 Migration
Function Points based computation of migration efforts enable early project
budgeting and show alternatives.
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/Ffp
Median Delivery Rate for C# 15,1h/Ffp
Median Delivery Rate for XPages Basic 2,0 h/Ffp
Median Delivery Rate for XPages Advanced 5,9 h/Ffp

16. Create Migration Plan
• Business Rules
• Roadmap
• Overall Efforts
Status quo and next steps
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
Technical
Analysis
Planing

17. Questions?
Benefit from our experience of analyzing more than 250.000 Notes applications –
for further information see http://www.insight-notes.com
Philipp Königs
Business Unit Executive
Member of the Board
Cedros Gesellschaft für Datenverarbeitung mbH
Siegburger Straße 35
53757 Sankt Augustin
Deutschland
Fon: +49 (0)2241 8834-16
Fax: +49 (0)2241 8834-11

18. Individual strategic decision based on cost/usage
Input:
Global c.-SAMM™ App Catalog
Tools
1. Business Rules
2. Questionnaires
3. Interviews
Output:
Target System/
Action per App