21st Banking

1
(No Transcript)
2
(No Transcript)
3
Making the move to Java

• The pressures on IT caused by the changing
  banking market
• How Java can help banks address current market
  pressures
• Embracing Thin Client addressing technology
  and skills
• What can be achieved by the Java evolution?

4
IT in banking today

• A diverse mixture of
• Computer languages
• Hardware
• Interfaces
• Home grown and bought applications
• Multiple data bases
• Operating systems and release levels

The result is a complex, inflexible bag of bits
architecture
5
Market pressures

• Cost competitiveness
• Standards
• Regulations and Government laws e.g. Patriot
  Act
• Drive to improved information sharing
• Compliance
• Risk measurability
• Fair market value

6
How to meet new market conditions

• Create economies of scale
• Have fungibility of resources
• Operate in a single IT environment
• Reuse expertise
• Be responsive to market changes

7
Demands facing IT in banking

• Traditional languages mix of hardware no
  integration
• Change rapidly
• Aim for a single environment
• Reduce complexity
• Increase flexibility and responsiveness

8
Evolve or die

• Evolution means replacing bag of bits
  technology by
• Reusing working business processes
• Building ongoing re-usable features
• Discerning between dynamic and static and wrap
  the static look to re-build the dynamic

9
The Web is the driver the choice is Thin Client

• 1980s Life was simple UI, processes and
  data on one platform
• 1990s Demand for a richer client led to
  complexity
• 2000s Web services provides an evolution
  toward simplicity and greater flexibility

Allows greater business focus and less time on
tough technical issues
10
A snapshot of IT today
Application Server
Browser
Server
Database
Desktop
MTS (.Net server 2003)
Microsoft
Internet Explorer
Windows .Net
Windows .Net
SQL Server
Linux UNIX OS/400 S/390
J2EE
Sun IBM Oracle
Netscape/ Mozilla
Linux HTML JavaScript
Oracle DB/2
11
The battleground is focused on the client

• Thin Client or Thinner client Microsoft .Net
• .Net commits you to a Microsoft proprietary
  environment on the desktop
• Linux questions this - reduces desktop costs

12
Can Thin Client be rich enough?
Thick Client development
Grey band indicates the richness required for
Banking systems
Scripting
Where are we heading
Richness of interface
Where are we today
Initial expectations
Development effort
13
Thin Client is rich enough
14
Making the move to Java technology
considerations

• Investing the effort
• Getting the timing right
• Convincing yourself you can evolve a legacy
  environment
• Ensuring the future environment will be robust
  and scalable

15
Architecture Key points

• Separation of Presentation, Business Database
  Logic
• Reuse of Legacy Code
• Open Architecture Variety of Clients
• Open Architecture Variety of Servers
• Easy Internationalisation
• Easy Customisation

16
High Level J2EE Design
Application Container
Web Container
SOAP rpcrouter (Apache)
SOAP Handler
ANSI SQL
Action
SOAP
System Controller
Browser
Control Servlet
Web Handler
DB2
HTTP
Enquiry
Table
JSP
Business Rule
SQL Server
User Session
HTML
JDBC
Custom Tags
Reference
Data Services
Workflow Rule
Key
Oracle
Servlet
Stateful Session EJB
JSP
XML Files
Stateless Session EJB
Plug in class
17
Making the move to Java addressing the people
impact

• The change from Traditional to Java has
  massive impact on your people
• Training and mentoring is key
• The Midas experience
• A third of people love it
• A third of people will go with persuasion
• A third of people will leave

18
An example of the front-end today
Bag of bits architecture
Home grown applications
Hardware
Creating a complex, inefficient and unproductive
user interface
Bought applications
Interfaces
Operating systems
Release levels
Multiple databases
19
The changes Java evolution can bring
20
Benefits to the bank

• Reduced complexity
• More responsiveness
• Increased consistency
• Information available to everyone
• Less costly
• Web enabled

21
The future
Winners are banks that can adopt new web enabled
technology quickly and enable high levels of reuse

• Getting it right means
• Economies of scale
• Open systems
• Reusable components
• and control over your own destiny

22
(No Transcript)