1. This Presentation Courtesy of the
International SOA Symposium
October 7-8, 2008 Amsterdam Arena
www.soasymposium.com
info@soasymposium.com
Founding Sponsors
Platinum Sponsors
Gold Sponsors Silver Sponsors
Composite Applications for Users
Edwin van der Sanden, CTO, Corizon
1
2. Agenda
Breaking Down State of the
The Not-So-
the Monolithic Software Q&A
Agile Enterprise
Application Industry
3 copyright 2008. all rights reserved
Agenda
Breaking Down State of the
The Not-So-
the Monolithic Software Q&A
Agile Enterprise
Application Industry
4 copyright 2008. all rights reserved
2
3. The Not-So-Agile Enterprise
Business Agility is a key differentiator for the business
Faster response to changes in market conditions, legal requirements, opportunities,
suppliers, etc. == more profit
The IT infrastructure should support this requirement for agility
The notion of changing business needs has to be supported by the IT infrastructure
But, does it?
5 copyright 2008. all rights reserved
The Not-So-Agile Enterprise
Example
Business
Telco
Business Process
Ticket to Resolve
Roles
Back office, accounts, front office and customer
Domains
Diagnostics, Billing, CRM
6 copyright 2008. all rights reserved
3
4. The Not-So-Agile Enterprise
Traditional Silo’ed Architecture
Back Office Accounts Front Office
Diagnostics Billing CRM
7 copyright 2008. all rights reserved
The Not-So-Agile Enterprise
Traditional Silo’ed Architecture
Business Processes rely heavily on human interaction, which is expensive
and error prone
Business changes are slow to implement and expensive due to retraining
and adjusting of staff
IT adds to this with rigid Point-to-Point integrations
8 copyright 2008. all rights reserved
4
5. The Not-So-Agile Enterprise
SOA Enabled Architecture
Back Office Accounts Front Office
Business Services & Processes
Diagnostics Billing CRM
9 copyright 2008. all rights reserved
The Not-So-Agile Enterprise
SOA Enabled Architecture
SOA introduces a common way to share business services and processes
across business units:
Expose
Control
Discover
Access
BUT only for Business Services and Business Processes, not the user interface
10 copyright 2008. all rights reserved
5
6. The Not-So-Agile Enterprise
SOA Enabled Architecture
User Interface functions are rebuilt for each user group
expensive for the service provider
expensive for the service consumer
Business Process execution and optimization is bottlenecked by continuous
demand on human domain expertise.
Increased dependency on service provider
SOA success becomes its downfall
Every Business Change requires re-implementation of several UIs
Increased SOA adoption leads to decreased business agility
11 copyright 2008. all rights reserved
Agenda
Breaking Down State of the
The Not-So-
the Monolithic Software Q&A
Agile Enterprise
Application Industry
12 copyright 2008. all rights reserved
6
7. Breaking Down the Monolithic Application
Let service producers, i.e. the domain experts, build fit for purpose atomic UI
functions or UI Services
Run diagnostics
Plan Engineer
Take payment Order Run
Infrastruc- Diagnos-
Order infrastructure ture tics
Back Take Plan
office Payment Engineer
THEN Enable the different user communities to recombine, or mashup, these
atomic UI functions into User Processes oriented solutions.
13 copyright 2008. all rights reserved
Breaking Down the Monolithic Application
Mashup Architecture
Back Office Accounts Front Office Self Service
User Interface Services
Business Services & Processes
Diagnostics Billing CRM
14 copyright 2008. all rights reserved
7
8. Breaking Down the Monolithic Application
Mashup Architecture can deliver
Traceability
Who is using what, when and how much both Design time as well as Runtime
Scalability
Avoiding direct dependency on domain experts by service consumers means
more solutions can be built cheaper and faster
Agility
End users, analysts and developers to use flexible UI Services to mashup user
process oriented applications
Dynamic UI aggregation enable UI updates to be reflected immediately
15 copyright 2008. all rights reserved
Agenda
Breaking Down State of the
The Not-So-
the Monolithic Software Q&A
Agile Enterprise
Application Industry
17 copyright 2008. all rights reserved
8
9. State of the Software Industry
Application development tools
Traditional
Portal J2EE, C# .NET
e.g.
- component based UI reuse
Rich Client
e.g. Oracle/BEA, IBM Web Portal
- no provisioning for UI Service
+ service based UI
Mashup framework development required
e.g. Adobe AIR, Silverlight
- custom
+ allows for live UI aggregation
- a specialist type of "traditional" tools
-e.g. Corizon Platform, JackBe
- component based UI reuse
consumer has very little control over portlet L&F or behaviour
-osome diverse class of tools multiple, WSRP )
very support for portlet embedding ( customizable, views
o burden on provider to supply
o customer grade to enterprise grade
+ can be combined with traditional development tools
+ live aggregation and customization of UI is possible
18 copyright 2008. all rights reserved
State of the Software Industry
Conclusions
UI approach critical to SOA success
Not addressing the last mile of SOA will keep heavy reliance on human interaction
in place
Traditional UI development does not deliver
Application development stuck in traditional component based reuse
Proliferation of UI detrimental to agility
Enterprise Mashups a natural fit for SOA
Runtime UI aggregation ideal for SOA
19 copyright 2008. all rights reserved
9
10. State of the Software Industry
Recommendations
Analyse
Take a look at your SOA effort and see how UI development is hurting it
Experiment & Learn
Select tactical areas to start showing how mashup tools can relieve this pain
Different tools will suit different situations
Adopt
Make Enterprise Mashups part of your SOA blueprint in a way that makes sense for
your business
20 copyright 2008. all rights reserved
Agenda
Breaking Down State of the
The Not-So-
the Monolithic Software Q&A
Agile Enterprise
Application Industry
21 copyright 2008. all rights reserved
10