SOA Kongress 2006, Mainz

1. CONFIDENTIAL
SOA Kongress 2006, Mainz
Interface Management System
Concepts and Implementation
Date: 22.11.2006
Produced by: Tarmo Ploom
Produced by: Name Surname
Date: 03.11.2005 Slide 1

2. Agenda
Introduction Credit Suisse
Interface taxonomy
SOA@Credit Suisse
Interface repositories, history
Framework for analysing interface repositories
First generation interface repository
Second generation interface repository
Third generation interface repository
Fourth generation interface repository
Interface repository, future
Summary
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 2

3. Credit Suisse in brief
Credit Suisse is a leading global bank headquartered in Zurich.
It is focused on serving its clients in three business lines:
investment banking, private banking and asset management.
Credit Suisse is renowned for providing expert advice, holistic
solutions and innovative products to a wide range of corporate and
institutional clients and high-net-worth individuals globally, as well
as retail clients in Switzerland.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 3

4. Assets under Management
of selected financial services companies
As per March 31, 2006 (CHF billion)
UBS* 2,652
State Street 2,012
Barclays* 1,997
Allianz Group* 1,991
Fidelity Investments 1,960
AXA* 1,683
Credit Suisse Group 1,554
Deutsche Bank* 1,371
Vanguard Group** 1,255
JP Morgan Chase 1,141
Mellon Financial Corp. 1,056
ING Group* 866
Northern Trust 853
Morgan Stanley** 827
Merrill Lynch 759
Citigroup 758
*as per December 31, 2005
Goldman Sachs** 746
**as per February 28, 2006
Aviva* 719
695
CHF/USD 1.3068
Prudential Financial*
CHF/EUR 1.5814
BNP Paribas* 680
CHF/GBP 2.2668
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 4

5. Interface taxonomie
CS language:
Event: fire and forget style asynchronous communication.
Service: request and response style synchron communication.
Bulk: Bulk data transfer (>100 MB).
Interface: abstraction of communication (not grouping).
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 5

6. SOA@Credit Suisse
Services:
ca 900 public services.
47% reuse.
12 million transaction per day.
Events:
ca 38 000 queues.
15 – 20 million transactions per day.
Bulk:
25 000 files.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 6

7. Implementation, history
1991 – 1999, Client/Server Banking System:
Two tier approach.
Paper based interface management.
First interface repository (1997 – 2001):
First generation interface repository for service (CORBA) interfaces only.
PHP/MySQL based.
Second interface repository (2002 – 2006):
First generation interface repository for service (CORBA) interfaces only.
MOF 1.3 based, JAP platform.
Paper based SOA governance processes.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 7

8. Implementation, problems from past
How to manage SOA landscape consisting of thousands of interfaces?
Who are active consumers of interfaces?
What interfaces are deployed and used in production?
Decomissioning of interfaces?
How to make SOA governance less bureaucratic?
Integration of interface repositories with other repositories.
Integration of interface development with interface repository.
How to bridge gap between interface design and implementation?
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 8

9. Framework for analysing interface repositories
Fourth generation
interface repository Model
Driven SOA
Third generation SOA IDE
interface repository (Integrated Development
Environment)
Second generation
SOA Governance
interface repository
(engineering, decomissioning, etc.)
First generation
Management of interface metadata
interface repository
(classical interface repository)
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 9

10. First generation interface repository
Fourth generation
interface repository Model
Driven SOA
Third generation SOA IDE
interface repository (Integrated Development
Environment)
Second generation
SOA Governance
interface repository
(engineering, decomissioning, etc.)
First generation
Management of interface metadata
interface repository
(classical interface repository)
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 10

11. First Generation Interface Repository
Passive management of interface metadata.
Interface catalog
paper based,
Excel,
commercial repositories, etc.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 11

12. First Generation Interface Repository, Meta-Model
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 12

13. First Generation Interface Repository, Architecture
Two main components:
Interface Dictionary
Reporting
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 13

14. First Generation Interface Repository, Problems
Problems
What if there are more than 1000 or more interfaces?
Who are active consumers of an interface?
What interfaces are deployed and used in production?
SOA standards enforcement?
SOA long term direction?
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 14

15. Second generation interface repository
Fourth generation
interface repository Model
Driven SOA
Third generation SOA IDE
interface repository (Integrated Development
Environment)
Second generation
SOA Governance
interface repository
(engineering, decomissioning, etc.)
First generation
Management of interface metadata
interface repository
(classical interface repository)
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 15

16. Second Generation Interface Repository
Elements:
Management of interface metadata.
Active semi-automated SOA governance processes.
Interface portfolio management.
SOA governance processes:
Interface engineering.
Interface decomissioning.
Interface migration.
Interface usage.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 16

17. Second Generation Interface Repository,
Interface Life Cycle
Main states in the life of an interface.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 17

18. Second Generation Interface Repository, Meta-Model
Management not only of providers but also of consumers.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 18

19. Second Generation Interface Repository,
Common Architecture
Additional components:
Process engine.
Quality assurance.
Portfolio management.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 19

20. Second Generation Interface Repository, Problems
Problems:
SOA bureaucracy.
Resistance to SOA bureaucracy.
Integration with other repositories.
Gap between design and implementation of services.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 20

21. Third Generation Interface Repository
Fourth generation
interface repository Model
Driven SOA
Third generation SOA IDE
interface repository (Integrated Development
Environment)
Second generation
SOA Governance
interface repository
(engineering, decomissioning, etc.)
First generation
Management of interface metadata
interface repository
(classical interface repository)
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 21

22. Third Generation Interface Repository
Elements:
Management of interface metadata.
Active semi-automated SOA governance processes and
Integrated development environment.
Integration:
Graphical design environment.
Design repository.
Application portfolio.
Log manager.
Infotype reuse:
Interface infotype dictionary.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 22

23. Third Generation Interface Repository, Meta-Model
New concepts:
Traceability of design artefacts (Business Object Model, Process Model, etc).
Infotype (infotype dictionary).
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 23

24. Third Generation Interface Repository,
Common Architecture
Substantial complexity increase compared to the second generation
interface repositories.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 24

25. Third Generation Interface Repository, Problems
Problems:
Integration.
Gap between interface design and implementation.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 25

26. Fourth Generation Interface Repository
Fourth generation
interface repository Model
Driven SOA
Third generation SOA IDE
interface repository (Integrated Development
Environment)
Second generation
SOA Governance
interface repository
(engineering, decomissioning, etc.)
First generation
Management of interface metadata
interface repository
(classical interface repository)
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 26

27. Fourth Generation Interface Repository,
Model Driven SOA Repository
Elements:
Management of interface metadata.
Active semi-automated SOA governance processes.
Integrated development environment.
Generation of interface stubs, skeletons and code.
Linking design to implementation:
Software configuration management.
IDL/WSDL/XSD/PL1/Java generator.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 27

28. Fourth Generation Interface Repository,
Common Architecture
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 28

29. Interface Management System, Plan
Fourth generation
interface repository Model
Driven SOA
Third generation SOA IDE
interface repository (Integrated Development
Environment)
Second generation
SOA Governance
interface repository
(engineering, decomissioning, etc.)
First generation
Management of interface metadata
interface repository
(classical interface repository)
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 29

30. Interface Management System, Current Status
Third Version (2007 – future)
Interface Management System as a mean to:
Control public interfaces of components.
Reduce complexity of component interactions.
Reduce costs by increasing reuse.
Increase flexibility of Credit Suisse banking platform.
Interface Management System with:
Interface metadata.
Semi automated SOA governance processes.
Integrated SOA development environment.
Model Driven SOA.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 30

31. Interface Management System, Summary
An Interface Management System becomes brain of the SOA strategy.
An Interface Management System is the core instrument for:
SOA asset management.
SOA standards enforcement.
SOA planning.
SOA strategy performance measurement.
Reducing resistance against SOA.
Reducing entrophy of a very large software system.
Increasing flexibility and reducing costs of a very large software system.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 31

32. Questions?
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 32

33. Backup
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 33

34. Key facts and figures on Credit Suisse Group
Credit Suisse Group’s registered shares (CSGN) are listed in Switzerland (SWX)
and as American Depositary Shares (CSR) in New York (NYSE).
For the first quarter of 2006, the Group reported net income of CHF 2,604
million.
As of March 31, 2006, the Group reported assets under management of CHF
1,553.6 billion.
Total number of staff: around 63,000
As of March 31, 2006, BIS tier 1 ratio stood at 10.8% .
The Group’s long term ratings are:
Moody’s Aa3, Standard & Poor’s A, Fitch Ratings AA-
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 34

35. Second Generation Interface Repository
Interface Portfolio Management
high reuse
low reuse
high change rate low change rate
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 35

36. Second Generation Interface Repository,
Interface Engieering Process
Process
Software engineering process
for interfaces.
Control of changes and new
interfaces
Several quality gates.
Waterfall with limited agility.
Objective
SOA standards enforcement.
Design of reusable interfaces.
Design of stable interfaces.
Design of long living interfaces.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 36

37. Second Generation Interface Repository,
Interface Decomissioning Process
Process
Simple process with clear rules of game.
Cleanup in operation and development.
Objective
Reduce number of interfaces.
Reduce number of interface versions.
Reduce interface consumer adaption.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 37

38. Second Generation Interface Repository,
Interface Migration
Transforming of existing non-managed interfaces to managed interfaces.
Enforcing of SOA standards on existing non-managed interfaces.
non-managed interfaces managed interfaces
(not in interface repository) (in interface repository)
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 38

39. Second Generation Interface Repository,
Interface Usage
Identification of interface consumers and regstraton of consumers.
Sources for service interface usage:
Log manager or code parsing.
Sources for events interface usage:
Configuration files.
Source for bulk interface usage:
Configuration files or code parsing.
Identification of interfaces for reuse.
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 39

40. Fourth Generation Interface Repository, Meta-Model
Separation between:
Platform Independent Model (PIM)
Platform Specific Model (PSM)
Platform Independent Model Platform Specific Model
Produced by: Tarmo Ploom
Date: 22.11.2006 Slide 40