Composite Applications For Users

1,431 views

Published on

At Corizon we believe that without the use of Enterprise Mashup SOA implementations will run into the same problems they are trying to address. The following slidepack, which I created for and presented at the 1st SOA Symposium, explains why this is, and more importantly, what to do about it

Published in: Technology, Business
1 Comment
1 Like
Statistics
Notes
  • It stinks that you cannot see the entirety of this presentation via the web. Take for example slide 16. It just doesn't work well in this format.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,431
On SlideShare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
0
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide
  • Subtitle : How Enterprise Mashups are critical to a successful SOA approach
  • Composite Applications For Users

    1. 1. Composite Applications for Users Edwin van der Sanden, CTO, Corizon
    2. 2. Agenda copyright 2008. all rights reserved The Not-So-Agile Enterprise Breaking Down the Monolithic Application State of the Software Industry Q&A
    3. 3. Agenda copyright 2008. all rights reserved The Not-So-Agile Enterprise Breaking Down the Monolithic Application State of the Software Industry Q&A
    4. 4. The Not-So-Agile Enterprise copyright 2008. all rights reserved 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 organization should support this requirement for agility The notion of changing business needs has to be supported by the IT infrastructure But, does it?
    5. 5. The Not-So-Agile Enterprise <ul><li>Example </li></ul>copyright 2008. all rights reserved Business Telco Business Process Ticket to Resolve Roles Back office, accounts, front office and customer Domains Diagnostics, Billing, CRM
    6. 6. The Not-So-Agile Enterprise <ul><li>Traditional Silo’ed Architecture </li></ul>copyright 2008. all rights reserved Back Office Accounts Front Office Diagnostics Billing CRM
    7. 7. The Not-So-Agile Enterprise <ul><li>Traditional Silo’ed Architecture </li></ul>copyright 2008. all rights reserved 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. 8. The Not-So-Agile Enterprise <ul><li>SOA Enabled Architecture </li></ul>copyright 2008. all rights reserved Back Office Accounts Front Office Diagnostics Billing CRM Business Services & Processes
    9. 9. The Not-So-Agile Enterprise <ul><li>SOA Enabled Architecture </li></ul>copyright 2008. all rights reserved 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. 10. The Not-So-Agile Enterprise <ul><li>SOA Enabled Architecture </li></ul>copyright 2008. all rights reserved User Interface functions are rebuilt for each user group expensive for the service provider <ul><ul><li>expensive for the service consumer </li></ul></ul><ul><ul><li>Increased dependency on service provider </li></ul></ul>Business Process execution and optimization is bottlenecked by continuous demand on human domain expertise. Increased SOA adoption leads to decreased business agility <ul><ul><li>Every Business Change requires re-implementation of several UIs </li></ul></ul><ul><ul><li>SOA success becomes its downfall </li></ul></ul>
    11. 11. Agenda copyright 2008. all rights reserved The Not-So-Agile Enterprise Breaking Down the Monolithic Application State of the Software Industry Q&A
    12. 12. Breaking Down the Monolithic Application copyright 2008. all rights reserved 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 infrastructure THEN Enable the different user communities to recombine, or mashup, these atomic UI functions into User Processes oriented solutions. Back office
    13. 13. Breaking Down the Monolithic Application <ul><li>Mashup Architecture </li></ul>copyright 2008. all rights reserved Back Office Accounts Front Office Diagnostics Billing CRM User Interface Services Business Services & Processes Self Service
    14. 14. Breaking Down the Monolithic Application <ul><li>Mashup Architecture can deliver </li></ul>copyright 2008. all rights reserved 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. 15. Agenda copyright 2008. all rights reserved The Not-So-Agile Enterprise Breaking Down the Monolithic Application State of the Software Industry Q&A
    16. 16. State of the Software Industry <ul><li>Application development tools </li></ul>copyright 2008. all rights reserved e.g. J2EE, C# .NET - component based UI reuse - no provisioning for UI Service - custom framework development required Traditional e.g. Oracle/BEA, IBM Web Portal + service based UI + allows for live UI aggregation - consumer has very little control over portlet L&F or behaviour - burden on provider to supply multiple, customizable, views Portal e.g. Adobe AIR, Silverlight - a specialist type of &quot;traditional&quot; tools - component based UI reuse o some support for portlet embedding ( WSRP ) Rich Client e.g. Corizon Platform, JackBe o very diverse class of tools o customer grade to enterprise grade + can be combined with traditional development tools + live aggregation and customization of UI is possible Mashup
    17. 17. State of the Software Industry <ul><li>Conclusions </li></ul>copyright 2008. all rights reserved Enterprise Mashups a natural fit for SOA Runtime UI aggregation ideal for SOA 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
    18. 18. State of the Software Industry <ul><li>Recommendations </li></ul>copyright 2008. all rights reserved Adopt Make Enterprise Mashups part of your SOA blueprint in a way that makes sense for your business 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
    19. 19. Agenda copyright 2008. all rights reserved The Not-So-Agile Enterprise Breaking Down the Monolithic Application State of the Software Industry Q&A

    ×