CREDIT SUISSE's Java Application Platform - JUG · CREDIT SUISSE's Java Application Platform JUGS Presentation March, 27th 2008 Robert Bennek KIRO 6 ... JAP Facts & Figures Documentation

CREDIT SUISSE TIS KIRO 6

CREDIT SUISSE's Java Application Platform

JUGS Presentation March, 27th 2008Robert Bennek KIRO [email protected]

CREDIT SUISSE TIS KIRO 6Produced by: Robert Bennek KIRO 6

Date: 27.03.2008 Slide 2

Text

Text

Text

Text

Text

Text

Managed, high-quality Technical Components

Automated, integratedTool-chain

Hosting on Shared HWResources

Architecture, Guidelines &

Documentation

Agenda

5

1 JAP facts and figures

Application Platform

Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 3

Text

Text

Text

Text

Text

Text





Documentation

Agenda

5



Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 4

Text

Text

Text

Text

Text

Text





Documentation

JAP Facts & Figures

JAP

Hub Zurich

400 servers (120 prod, 1:7 consolidation)190 applications169'000 users (intranet & internet)14 MLines of effective code360 mio requests per month43 FTEs for Hub Zurich for190 apps and 30+ concurrent projects

Hub Singapore

12 servers (4 prod.)4 PB applications 6 FTEs for Hub SG

Hub New York (Q2/08)

5 servers (2 prod.)1 PB pilot application + prospect applications from PB and IB

71

5.5 2.79.3 11.5

PB IB AM TIS CoS

% of apps. on JAP

Productive Application Statistics

0

20

40

60

80

100

120

140

160

180

Jan

05

Mrz

05

Mai

05

Jul 0

5

Sep

05

Nov

05

Jan

06

Mrz

06

Mai

06

Jul 0

6

Sep

06

Nov

06

Jan

07

Mrz

07

Mai

07

Jul 0

7

Sep

07

# A

pplic

atio

ns

Tower 4/5

Tower 1/2

JAP: Java APMF: MainframeSE: Special Eng.

AverageMinMax

-50%

Days/UCP of projects and platform (time-to-market)

UCP: Use Case Point


Date: 27.03.2008 Slide 5

Text

Text

Text

Text

Text

Text





Documentation

Agenda

5



Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 6

Text

Text

Text

Text

Text

Text





Documentation

JAP HistorySTARTING SITUATION (1999 – 2002)

Hand crafted heterogeneous serversMultiple variants => expensive testingNumerous application servers with different versionsEach application needed to organize component providersApplying component patches systematically to all servers was a major challengeAudit and regulatory compliancy was at risk.Developer support in production


Date: 27.03.2008 Slide 7

Text

Text

Text

Text

Text

Text





Documentation

STARTED WITH SIMPLE SERVLET APPLICATIONS (1999-2002)JAP History

Started with servlet and mainframe integration (Corba)Added additional middleware and integration topics (DB, MQ, Mail, ...)Scalability via HW Load Balancer and multiple WLS instancesTwo active sides/data centers for Disaster Recovery (BCP)First technical stack including all necessary basic componentsRelease concept provides rules and guidelines for updates


Date: 27.03.2008 Slide 8

Text

Text

Text

Text

Text

Text





Documentation

JAP HistoryDISTRIBUTED EJB APPLICATIONS CHALLENGED THE PROCESS (2002/3)

Due to additional needs from Internet applications separation ofpresentation and business logic and additional non mainframe logic was required EJBStarted with Session, Message and finally a limited number of Entity BeansClear technical structure and architectural blue prints, as well as fully adherence to J2EE standardsNew functionality increased configuration complexity significantly


Date: 27.03.2008 Slide 9

Text

Text

Text

Text

Text

Text





Documentation

JAP HistoryAUTOMATE AND SUPPORT THE PROCESS (2004, ongoing)

Development Tool-Chain for compilation and packagingAutomated generation of AppServer configuration reduced theerror rate drastically.Application configuration DB contains setup of all JAP applications. Rebuild (for additional deployments or upgrades) of identicallyconfigured WLS instances on a click.End2End consultant supports IT-PL with all processes.


Date: 27.03.2008 Slide 10

Text

Text

Text

Text

Text

Text





Documentation

Agenda

5

1 Credit Suisse facts and figures


Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 11

Text

Text

Text

Text

Text

Text





Documentation

Managed Stack, no Dependency Explosion, increased Stability,

less maintenance costs, less support, capacity mgt (CHP)Explosion of dependencies and support and maintenance

costs, un-coordinated lifecycles in technical stack

Hardware

Core OS

Applications

InfrastructureSWcomponents

Server Model 1 Server Model 2 Server Model 3 Server model ...

OS Core Version 1

Component a

Version ...

Component a

Version 2

Component a

Version 1Component a

Version ...

Component a

Version 2

Component b


Version ...

Component a

Version 2

Component c

Version 1Component ...

Version ...

Component ...

Version 2

Component ...

Version 1

OS Core Version 2 OS Core Version 3 OS Core Version ...

Component a

Release ...

Component a

Release 2

Application a

Release 1Component a

Release ...

Component a

Release 2

Application b


Release ...

Component a

Release 2

Application c


Release ...

Component ...

Release 2

Application ...

Version 1

Hardware

Core OS

Applications


Server Model 1 Server Model 2 Server Model 3 Server model ...

OS Core Version 1

Component a

Version ...

Component a

Version 2

Component a


Version ...

Component a

Version 2

Component a


Version ...

Component a

Version 2

Component b


Version ...

Component a

Version 2

Component b


Version ...

Component a

Version 2

Component c


Version ...

Component a

Version 2

Component c


Version ...

Component ...

Version 2

Component ...


Version ...

Component ...

Version 2

Component ...

Version 1

OS Core Version 2 OS Core Version 3 OS Core Version ...

Component a

Release ...

Component a

Release 2

Application a


Release ...

Component a

Release 2

Application a


Release ...

Component a

Release 2

Application b


Release ...

Component a

Release 2

Application b


Release ...

Component a

Release 2

Application c


Release ...

Component a

Release 2

Application c


Release ...

Component ...

Release 2

Application ...


Release ...

Component ...

Release 2

Application ...

Version 1

Hardware

Core OS

Applications


Server Model 1

Server Model 2

OS Core Version 1

Component a

Version 1Component b

Version 1Component c

Version 1

Component a

Release ...

Component a

Release 2

Application a


Release ...

Component a

Release 2

Application b


Release ...

Component a

Release 2

Application c


Release ...

Component ...

Release 2

Application ...

Version 1

RuntimePlatformRelease

RTP Release 1 RTP Release 2 RTP Release 3

Server Model 2

Server Model 3

OS Core Version 2

Component a



Version 2

Server Model 3

Server Model ...

OS Core Version 3

Component a



Version 1

Virtualization VM Layer Version 1 VM Layer Version 1 VM Layer Version 1

Hardware

Core OS

Applications


Server Model 1

Server Model 2

OS Core Version 1

Component a



Version 1

Component a

Release ...

Component a

Release 2

Application a


Release ...

Component a

Release 2

Application a


Release ...

Component a

Release 2

Application b


Release ...

Component a

Release 2

Application b


Release ...

Component a

Release 2

Application c


Release ...

Component a

Release 2

Application c


Release ...

Component ...

Release 2

Application ...


Release ...

Component ...

Release 2

Application ...

Version 1

RuntimePlatformRelease

RTP Release 1 RTP Release 2 RTP Release 3

Server Model 2

Server Model 3

OS Core Version 2

Component a



Version 2

Server Model 3

Server Model ...

OS Core Version 3

Component a



Version 1

Virtualization VM Layer Version 1 VM Layer Version 1 VM Layer Version 1

WHY WE INVEST IN PLATFORMS?

Platform

Release Mgt


Key Benefits of Platform Lifecycle Mgmt

Applications (and platforms) stay in technology lifecycle and mainstream (no "rotten" components)Technical upgrades due to lifecycle mgmt of platform are combined with update on business functionality Constant decommissioning of out-dated platform releases identifies no longer used applicationsNew releases of platforms (with new features) have no impact on productive applications (no need to migrate; no stability impactdue to changes)

Key Benefits of Platform Lifecycle Mgmt

Applications (and platforms) stay in technology lifecycle and mainstream (no "rotten" components)Technical upgrades due to lifecycle mgmt of platform are combined with update on business functionality Constant decommissioning of out-dated platform releases identifies no longer used applicationsNew releases of platforms (with new features) have no impact on productive applications (no need to migrate; no stability impactdue to changes)

year year+1 year+2 year+3 year+4

AR i-2

AR i-1

AR i

requirements &project setup

release engineeringpilot applications

phase-outapplication migration

standard releasenew applications

EOL


Date: 27.03.2008 Slide 12

Text

Text

Text

Text

Text

Text





Documentation

TECHNICAL DRIVERS

Pricedesign/build/test once, operate and automate centrally, amortize across many applications

Qualityshared tested components, common monitoring &

stability measures (including bug fixes/patches)

Riskpre-defined infra security, IT-DR, accountability established and enforced for platform

Capability

defined operational characteristics, performance and capacity

Pricedesign/build/test once, operate and automate centrally, amortize across many applications

Qualityshared tested components, common monitoring &

stability measures (including bug fixes/patches)

Riskpre-defined infra security, IT-DR, accountability established and enforced for platform

Capability

defined operational characteristics, performance and capacity

From custom building → platform:

Integrated and tested components in runtime stackFixed component versions per platform releaseDefined and largely automated processes for ordering, provisioning, configuration management, software distribution, change management, performance & capacity management, monitoring, IT DR, auditing, etc.Platform management for platform as a whole: requirements management, release management, life cycle management, technology strategy & architecture, end to end service, pricing, business case, KPIs, etc.

Application Specific WorkGraphical User Interface (GUI)Business LogicDatabase SchemasConfiguration

Infrastructure Design / ImplementationRuntime StackHW, OS, Middleware, NetworkSystems Management/Operation, Security, Development Tools, etc.



Date: 27.03.2008 Slide 13

Text

Text

Text

Text

Text

Text





Documentation

WHAT IS A PLATFROM?

Platform Types

•Runtime Platform (RTP)

generic

•Hosting Platform (HP)

added services like capacity mgt (virtualization) for OS build, DB build, etc.

•Application Platform (AP)

added services specialized for areas of similar applications

Text

Text

Text

Text

Text

Text





Documentation

A set of integrated technical components and processes for the development and operation of applications



Date: 27.03.2008 Slide 14

Text

Text

Text

Text

Text

Text





Documentation

Application PlatformHIGH-LEVEL MODEL

Services provided by an Application Platform– Platform Product Mgmt & Governance: drives product

development and release & lifecycle management adhering to a well-defined governance model

– Platform Operations: operates applications cost-efficiently with standardized processes according to OLA

– Application Development Support: guides projects through entire development process and shields projects from low-level infrastructure issues

Infrastructure needed to provide these services– Technical Components: providers supply high-quality and

well-managed technical components that are tested and integrated into readily deployable packages (so-called TIP)

– Hosting: applications are hosted on shared hardware resources according to production guidelines; applications may also run ondedicated servers if required

– Tool-chain: automates key processes of solution delivery such as configuration management and deployment in a reliable, repeatable manner

– Architecture, Guidelines & Documentation: defined, standardized architecture based on open standards for various needs, and information to implement applications for the platform

Text

Text

Text

Text

Text

Text





Documentation


Date: 27.03.2008 Slide 15

Text

Text

Text

Text

Text

Text





Documentation

TOOL-CHAIN OVERVIEW

Tool-chain supports typical create-edit/configure-build-deploy-run-debug functionalityTool-chain automates key processes of solution delivery such as configuration mgmt and deploymentJAP enables repeatable deployment of applications to any system at any time (in accordance to CMMI/SOX)

Main elements are:– TIPD (technical infrastructure package for development)

create application & components structures

collaboration / configuration mgmt of source code

build-deploy-run-debug on local machine– Configuration Mgmt (required by CMMI / SOX) for source code,

components, deployment units, and documentation – Build Server: automatically compile code and package deployment units– WLS Instance Creation: create configuration of runtime environment

(instance) of WebLogic Server– Debugging, Testing: start/stop instance, inspect log-files, perform load

tests, monitor application behavior– Software Deployment: configuration of profiles of target machines,

package repository and installation of packages

Developer Machine

IDE TIPD Browser

Tool-chain

ConfigurationManagement

BuildServer

WLS InstanceCreation

SoftwareDeployment

DebuggingTesting

Hosting environment

(Shared) Test Servers (Shared) Production Servers

SCM



Date: 27.03.2008 Slide 16

Text

Text

Text

Text

Text

Text





DocumentationApplication Platform Toolchain


Date: 27.03.2008 Slide 17

Text

Text

Text

Text

Text

Text





Documentation

OVERVIEW TECHNICAL COMPONENTS

Layer 1 (Hardware, Disk, Network, OS Build, Core Systems Mgmt / Security / Integration)

Monitoring

JMX TAP 1

Tr@Log

Oracle TAP 1

Notify Core

WLS TAP 1

Performance(Introscope)

J2EE MonitoringProbe

Enterprise Perf. Agent

Security

Web Entry Integration

Public Key Infra. & API

PKI Certificates

Integration

Java Corba Bridge

Corba Infra.

Java Mail API

JMS Wrapper

Middleware

Batch Framework

Batch Libraries

Oracle DB Client

Runtime

BEA WebLogic Server (WLS)

Java Developer Kit (JDK)

Java Runtime Env.(JRE )

Java Core Framework (JCF)

JCF Extension

CS Application Interface (Tivoli Adapter)

JAP defines the runtime stack in three layers– Layer 1 subsumes infrastructure elements provided by a

Runtime Platform (OS Build & Services)– Layer 2 contains application server and APIs to access

infrastructure (security, integration, systems mgmt)– Layer 3 subsumes configuration, code, and resources of

applications (some libraries are standardized)

Applications only access interfaces provided by Layer 2→ JAP may exchange Layer 1 components without affecting

applications (e.g., cheaper hardware)

JAP owns no components but reuses already existing components from various providers; components are engineered once for the platformJAP provides a bundle of layer 2 components as TIP (Technical Infrastructure Package) that runs on a well defined layer 1

Layer 3

Layer 2: Technical Infrastructure Package (TIP)

Applications(Code, Configuration)

Standard Libraries


1TAP = Tralog Application Probe


Date: 27.03.2008 Slide 18

Text

Text

Text

Text

Text

Text





DocumentationApplication PlatformARCHITECTURE, GUIDELINES & DOCUMENTATION

JAP supports Java applications that are built according to the CS Tower architectureJAP provides the necessary information to facilitate the application development for and operation on JAP– Architectural & Process Guidelines– Manuals & Training Material– .....The information are centrally available through the JAP HomepageJAP ensures the configuration management of the relevant documents

Architectural Guidelines

Platform Documentation

Operations Manual

Training Material

Support Material

JAP Customers

JAP Organization

ComponentProviders

Java Support

(Platform)Architects


Date: 27.03.2008 Slide 19

Text

Text

Text

Text

Text

Text





DocumentationApplication PlatformHOSTING ON SHARED HW RESOURCES

Typical J2EE application requires up to 20 servers with traditional hosting including test stages and BCPJAP provides the necessary infrastructure; applications share server but are still isolated at the system levelEach platform release may require its own resources→ but only 3 releases in parallelQuantitative Benefits: – JAP hosts 190 applications on 400 servers.

Traditional hosting would require more than 2800 servers

– More efficient operations support

→ critical mass of applications requiredQualitative Benefits: – Standardized OLA, multi-rail, BCP solution,

fail-over– Standardized processes for operations


Date: 27.03.2008 Slide 20

Text

Text

Text

Text

Text

Text





Documentation

Complex ApplicationsJAP DEPLOYMENTS

Example shows a "logical Deployment" and two "physical Deployments"


Date: 27.03.2008 Slide 21

Text

Text

Text

Text

Text

Text





Documentation

Agenda

5



Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 22

Text

Text

Text

Text

Text

Text





DocumentationBusiness Case APPLICATION COST MODEL (CUSTOM DEVELOPMENT)

Business EngineeringAnalysis & Design

ImplementationTesting

ConfigurationProject Mgmt

Stack Engineering Integration into

Surrounding SystemsDeployment

BF

DII

D

Application MaintenanceApplication Monitoring3rd Level Support (App)

70%(A1)

30%

60%(A4)

Infra. MaintenanceInfra. Monitoring

3rd Level Support (Infra)

1st and 2nd Level Support

1&

2IL

AL

30%(A6)

10%

Recurring Costs (Run the Bank)– Maintenance Costs at Application Level (AL), i.e.

Application Maintenance, Monitoring, Support (3rd)– Maintenance Costs at Infrastructure Level (IL) i.e.

Infrastructure Maintenance, Monitoring, Support (3rd)– 1st and 2nd Level Support (1&2LS), i.e., only

infrastructure support excluding business support– Assumptions:

A4: 60% of all RTB costs at application levelA6: 30% of all RTB costs at infrastructure level

One time Costs (Change the Bank)– Business Functionality Development (BFD) incl.

Business Engineering, Analysis & Design, Implementation, Testing, Configuration, Project Mgmt

– Infrastructure Integration & Deployment (IID)

Stack Engineering (Systems Engineering, Infrastructure Testing, Configuration)Integration into Surrounding Systems (Security, Systems Mgmt, SOA, Legal & Compliance)Deployment

– Assumptions:

A1: 70% of project costs are spent for BFD


Date: 27.03.2008 Slide 23

Text

Text

Text

Text

Text

Text





DocumentationBusiness Case SAVINGS FOR DEVELOPMENT ON JAP

custom on JAP

IID

70%(A1)

30%

100%

BFD

IID

10%(A2)

80%(A3)

63%

6%

69%

AL60%(A4)

30%(A6) IL

1&2LS10%

100%

AL

IL

55%

10%65%custom

8%(A5)

66%(A7)

100%(A8)

Savings on Recurring Costs (RTB)– Maintenance Costs at Application Level (AL)

Savings: High quality reduces problems in prod.;periodic review & decommissioning of applicationsResidual Costs: 3rd level support & maintenance

– Maintenance Costs at Infrastructure Level (IL)Savings: Infrastructure lifecycle mgmt does not involve applications (e.g., DST handling)

– 1st and 2nd Level Support (1&2LS)Savings: JAP provides full 1st and 2nd level support

– Assumptions:A5: 8% savings for maintenance on ALA7: 66% savings for maintenance on ILA8: 100% savings for 1st and 2nd level support

Savings on One time Costs (CTB)– Business Functionality Development (BFD)

Savings: Reuse of common framework and components (Facades, JSF, ...) provided by JAPResidual Costs: development of business func.

– Infrastructure Integration & Deployment (IID)

Savings: complete stack from JAP; integration into infrastructure done; servers up and runningResidual Costs: extensions of infrastructure; infrastructure configuration; JAP E2E consultant

– Assumptions:

A2: 10% savings for BFD in solution deliveryA3: 80% savings for II&S in solution delivery

BFD

on JAP


Date: 27.03.2008 Slide 24

Text

Text

Text

Text

Text

Text





Documentation

BENEFITS OF A JAVA APBusiness Case

Provision of significant quality attributes (e.g. security, failover, operability, auditability,…) is ensured.Lifecycle is in place. Release 1 and 2 of the platform are already phased out, currently 3 & 4.Shared servers improve utilization.Unit prize constantly reduzed (-15% per year)Increased efficiency of application products.Standardization improves QoS.Toolchain makes upgrade or extension of applications much moreefficient.Documentation of processes and organisation enables a steeplearning curve for new IT-PLs. KPIs provide important management information.


Date: 27.03.2008 Slide 25

Text

Text

Text

Text

Text

Text





Documentation

Agenda

5



Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 26

Text

Text

Text

Text

Text

Text





Documentation

Lessons learned

Processes

organizational change from silos to value chains

new discipline Platform Management

establish adequate governance system

introduce key metrics

Services

Competence Center & Support

Platform Consultancy

Automation and tool support

Communication & Information

Product Management

Sustainable value creation requires a product-oriented approach

Flexibility must be part of the architectural product line design

Culture and organizational readiness

Stakeholder Management

Management Attention

Politics

It is much more than Technology, prepare for heavy investments in Processes and Value Chain coordination

Complexity increases, platform consultancy for application development is required (processes and services)

Tool Chain Automation reduces error rate and prevents manual interventions

Decouple infrastructure standardization from application-driven approach otherwise a sustainable cost efficiency may be corrupted

Standardization is important, but controlled flexibility as well

More transparency makes you vulnerable, be prepared for heavy fights

Agree on Platform Development Strategy in advance and tailor approach to your specific environment, organization and culture

Prepare your stress hormones for unbelievable huge numbers of organizational interfaces. There is always lot's of politics...


Date: 27.03.2008 Slide 27

Text

Text

Text

Text

Text

Text





Documentation

Lessons learned









Processes





Services





Product Management






Politics

It is much more than Technology, prepare for investments in Processes and Value Chain coordination

It is much more than Technology, prepare for investments in Processes and Value Chain coordination


Date: 27.03.2008 Slide 28

Text

Text

Text

Text

Text

Text





Documentation

Lessons learned









Processes





Services





Product Management






Politics




Date: 27.03.2008 Slide 29

Text

Text

Text

Text

Text

Text





Documentation

Lessons learned









Processes





Services





Product Management






Politics

Standardization is important,

but controlled flexibility as well

Standardization is important,

but controlled flexibility as well


Date: 27.03.2008 Slide 30

Text

Text

Text

Text

Text

Text





Documentation

Agenda

5



Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 31

Text

Text

Text

Text

Text

Text





Documentation

RoadmapWRITE AN APPLICATION ONCE, RUN IT EVERYWHERE

First international hub established in Singapore.Hub New York is currently rolled out.

Global JAP Governance Centralized Platform Product Management provides JAPJAP 3rd level support for other JAP locationsSame location as a JAP HubJA

P G

loba

l Pla

tform

M

gmt

JAP

Hub

Support JAP application development and runningOne per regionFirst contact for satellite locations in the region


Date: 27.03.2008 Slide 32

Text

Text

Text

Text

Text

Text





Documentation

PORTAL FUNCTIONALITY IN JAP 5 Roadmap

Weblogic Portal enables a new class of applications.Integration driven portals allow decoupling of complex applicationsPortal functionality is focused on application integration– Decouple portlet applications from portals– Allow reuse of portlet providers in different portals– Update of single portlet apps at runtime

Support campaign management

Challenges include:– provide registry and repository– development, packaging und distribution support– ensure operability and maintainability– manage new dependencies between applications– versioning and lifecycle


Date: 27.03.2008 Slide 33

Text

Text

Text

Text

Text

Text





Documentation

FIRST STEP FOR ENTERPRISE READY TRANSACTION SUPPORT Roadmap

A new dimension for the Java platform: get ready to host applications and data with massive transaction requirementsChallenges include:– development, packaging und distribution support– guidelines needed for data modelling, DB engineering, programming, migration, testing,….– ensure operability and maintainability– interaction with existing systems– ….

JAP 5 is the first step towards a Java transaction platform– delivers basic architectural & engineering principles– PoC by building a prototype for applications with massive transaction requirements– establish technical and application confidence for future developments– Benchmark measurements


Date: 27.03.2008 Slide 34

Text

Text

Text

Text

Text

Text





Documentation

Agenda

5



Business Case4

3

2

6

JAP history

Lessons learned

Roadmap

7 Summary and Q&A


Date: 27.03.2008 Slide 35

Text

Text

Text

Text

Text

Text





Documentation

Summary

StandardsStandards

Release ManagementRelease Management

End2End SupportEnd2End Support

GovernanceGovernance

Architecture & GuidelinesFew Hardware TypesJ2EE/Java EEOne Application Server ProductOne DB ProductOne ToolchainSynchronous Bus (Corba/JAX WS)Asynchronous Bus (JMS/MQ)Bulk Transfer

Architecture & GuidelinesFew Hardware TypesJ2EE/Java EEOne Application Server ProductOne DB ProductOne ToolchainSynchronous Bus (Corba/JAX WS)Asynchronous Bus (JMS/MQ)Bulk Transfer

Business CaseBusiness Case


Date: 27.03.2008 Slide 36

Text

Text

Text

Text

Text

Text





Documentation

Summary

StandardsStandards





3 parallel releasesdefined phase outplanned migration managed lifecyclecoordinated with providers

3 parallel releasesdefined phase outplanned migration managed lifecyclecoordinated with providers

year year+1 year+2 year+3 year+4

AR i-2

AR i-1

AR i

requirements &project setup

release engineeringpilot applications

phase-outapplication migration

standard releasenew applications

EOL


Date: 27.03.2008 Slide 37

Text

Text

Text

Text

Text

Text





Documentation

Summary

StandardsStandards




Complexity requires E2E supportHub model allows cloningSingle point of contactCompliancy checkGuided processTrainingEnd-2-End Process

Complexity requires E2E supportHub model allows cloningSingle point of contactCompliancy checkGuided processTrainingEnd-2-End Process



Date: 27.03.2008 Slide 38

Text

Text

Text

Text

Text

Text





Documentation

Summary

StandardsStandards




Stakeholder ManagementSteering CommitteeProvider BoardLifecycle BoardArchitects OfficeLong-term StrategyGlobal RolloutHub model

Stakeholder ManagementSteering CommitteeProvider BoardLifecycle BoardArchitects OfficeLong-term StrategyGlobal RolloutHub model



Date: 27.03.2008 Slide 39

Text

Text

Text

Text

Text

Text





Documentation

Summary

StandardsStandards





JAP reduces costs by ~30%JAP decrease billing prices ~38%Server utilization 1:7 ratioEnvironmental aspects

JAP reduces costs by ~30%JAP decrease billing prices ~38%Server utilization 1:7 ratioEnvironmental aspects

LELE

LE LE

2005 2006 2007 2008

LE(preliminary

figure)

-15%-28% -32%

-38%


Date: 27.03.2008 Slide 40

Text

Text

Text

Text

Text

Text





Documentation

Summary

Text

Text

Text

Text

Text

Text





Documentation

Business CaseBusiness Case Release ManagementRelease Management

End2End SupportEnd2End Support StandardsStandards GovernanceGovernance


Date: 27.03.2008 Slide 41

Text

Text

Text

Text

Text

Text





Documentation

Time To Market? I need the latest lib of ....?

...but I want framework X?.Net?

Sounds interesting, but ....?Flexibility?

Maven?

QUESTIONS? Speed?

Business wants ...?Agility?

Application Server X?

Web 2?MDA?

Documents

CREDIT SUISSE's Java Application Platform - JUG · CREDIT SUISSE's Java Application Platform JUGS Presentation March, 27th 2008 Robert Bennek KIRO 6 ... JAP Facts & Figures Documentation