: Bringing Web2'0 to IT Systems

1
Bringing Web2.0 to IT Systems
2
Why are we interested in Web2.0 in the IT Systems
world?

• The IT Systems complexity impacts on time to
  market and customer and user satisfaction
• Classic Software engineering methodologies and
  architectural approaches like EAI, BPM and (of
  course) SOA and don't seem to be valid to solve
  real IT Systems issues
• Although those steps have taken us in the right
  direction. The promise of reusability,
  adaptability, scalability, productivity and loose
  coupling still arent a reality
• In these solutions Users havent been taken into
  consideration as an integral part of systems
  architecture. It is necessary to explore a
  user-centric approach
• People are the most important part of the System.
  People have the knowledge that the systems must
  use

3
The reality of SOA

• Today, a real Service Oriented Architecture is
  the main goal of most Enterprise Systems.
• However most used SOA implementations (WSDL/SOAP
  for example) don't seem to provide the promised
  solution...
• System integration is not as easy as they told
  us...
• Beware with the WS Stack
• In fact we have YARPC (Yet Another RPC)
• CORBA, RMI, COM...
• But services are more than RPC calls.
• They must be something Useful
• Final users have been forgotten
• Try to give a WSDL to your mother

4
Looking for the new SOA

• We need services that
• Involve and empower users
• The only way to get their satisfaction
• Adapted to real user requirements
• ... and their needs
• Usable, touchable and accessible
• Making it empirical and real
• Make easy system integration
• The best solution involve several Systems
• Bring to reality SaaS (beyond ASP solutions)?
• Really configurable Software as a Service
• Interact in a marketplace
• Market rules to services evolution
• Anyway not all is lost. Real Services already
  exist!!
• At least... in the Internet.

5
Put a face on SOA A new Approach

• Gadgets Application components integration
  based on EzWeb Mashup and Wiring
• Application components creation through Data
  Sources Application Resources composition
  Piping
• Semantic searching, discovery and sharing of Data
  Sources Application Resources
• Users and Systems Knowledge acquisition and
  representation tagging, tracking, evolving...
• Business Resources generation upon systems and
  services

6
EzWeb High Level Architecture
7
Capturing the long tail
8
Gadget Mashup. The SOA enabler
9
What's an EzWeb-Gadget?

• Gadgets are supposed to be SMALL, REUSABLE and
  USER-CENTRIC web applications
• Welcome to the Post-IT Generation!!
• Generic gadgets are desirable but ad-hoc
  solutions are allowed too... only if they are
  quickcheap enough
• Sometimes all you need is a Kleenex!!
• Gadgets should be adapted to real problems
• Gadget Evolution versus Application Creationism
• The idea is to Develop USEFUL / Develop FAST

2008 Odyssey My God, It's full of... Gadgets!
10
How to develop a Gadget?

• Get Inspired
• Searching, Browsing, Reusing, Importing,
  Wrapping, Adapting... COPYING
• We are the dwarfs standing on shoulders of
  giants
• Catch the idea
• One idea, One gadget... Two ideas, Two gadgets...
• We need simple solutions with a well defined
  behaviour
• Think about Gadget data flows
• Gadgets want to be SOCIAL, not only with other
  Gadgets but also with People and environment
• No more lonely apps

11
How to develop a Gadget?(II)?

• Design your interface (pen to paper)
• One screen is better than two
• Desktop belongs to user. Don't waste pixels!
• Remember Gadgets prefer to live in the front end
  layer (View)
• But you'll need the support of a back-end (Model
  / Controller)
• Sometimes EzWeb could be your Model and
  Controller
• Choose the best technology
• Gadgets are agnostic XHTML / FLASH / APPLETS /
  XUL / SVG... anything your browser can eat!
• However Javascript is a must, if you want to use
  advanced platform functionality

12
That's all?... we need a template

• Why do we need a Template?
• Template allows gadgets to share information with
  the world in an standard, declarative and
  semantic way.
• The same gadget implementation could have several
  different templates. Depending on how we want
  them to be exposed or used.
• Of course you can use a default Template, but you
  will lose some platform interesting capabilities
• Template has two main sections
• Integration Variables Binding Flows to Aspects
• Description with all kind of context information

That's all Folks!
13
Resource Description

• ltCatalog.ResourceDescriptiongt
• ltVendorgtMorfeolt/Vendorgt
• ltNamegtDevice_Data_Viewerlt/Namegt
• ltVersiongt1.0lt/Versiongt
• ltAuthorgtlmayllonlt/Authorgt
• ltMailgtlmayllon_at_tid.eslt/Mailgt
• ltDescriptiongtThis is the Gadget
  Description lt/Descriptiongt
• ltImageURIgthttp//myimages/devices/samples.
  jpglt/ImageURIgt
• ltWikiURIgthttp//mywiki/Device_Data_Viewerlt
  /WikiURIgt
• lt/Catalog.ResourceDescriptiongt

14
Integration Variables?

• Properties
• They allow free persistence
• Preferences
• They permit configuration User Forms
• Context
• The easy way to access the delivery context
• Event
• Talk to other gadgets
• Slots
• Receive notifications from other gadgets
• .. and so on...

One concept to rule them all!
15
So... why EzWeb?

• Build and compose your own Applications
• Personalise your apps. Not only contents
• Develop Small Beautiful
• Anyone can develop the best gadget ever
• Back-end Support
• Preferences, context, notify events,
  persistence...
• EzWeb is an open source platform
• www.morfeo-project.org
• Front-end system integration
• Integrate systems and functionalities at user
  level
• Marketplace infrastructure
• Helps you to make business

16
For more information

• BLOG
• http//ezweb.morfeo-project.com/
• WIKI
• http//forge.morfeo-project.org/wiki/index.php/Pla
  taforma_EzWeb
• TRAC
• http//trac.morfeo-project.org/trac/ezwebplatform
• MAILING LIST
• morfeo-ezweb_at_lists.morfeo-project.org