Ajouter aux favoris   Ajouter cette page à mon bookmark --- SOCIAL BOOKMARKING --- Digg Furl del.icio.us Netscape

Rich Internet/interactive applications (RIAs) are at the convergence of two competing development cultures: desktop and web browser. One of their most important characteristics is that they work in both a connected and disconnected state without loss of functionality. The challenge is in understanding what this means for software development and creating an architecture on which RIAs can be deployed. The current rush by vendors to jump on the RIA bandwagon has led to competing models and approaches. This report defines a generic RIA architecture and highlights the development and deployment issues that will need to be overcome to make RIA successful.

Table of contents

Key messages

RIA represents an essential evolution in application design and development
An RIA platform
A burning need for good application design and architecture
Don’t underestimate the work required
Cool technology – yes, but don’t lose your head
Standards and common practices will emerge, but in the short term you have to apply your own
It’s all about the business, and the outcome that the business wants
What is a rich interactive application?

Today’s solutions and their challenges
Why RIA fits the bill
RIAs are more than object orientation and clever web services
RIAs and the Web 2.0 phenomenon
Getting there from here – a pragmatic migration strategy and adoption curve
Architecture and design

RIA building blocks
The Ovum RIA architecture
RIA design issues
RIA development

Success is in the planning
Role-based development
Designing interaction
User involvement
Looking outside traditional skills
Methodologies
A new breed of tools
RIA deployment

Competing models
Infrastructure
Testing
Management and metrics
RIA enablement

Key elements of enablement
RIA enablement example
RIA development stages