Web 20 Design Patterns Models and Analysis 1194273339280295 3

Web 2.
0 Design
Patterns, Models, and
Analysis
Duane Nickull
Senior Technical Evangelist
1
2005 Adobe Systems Incorporated. All Rights Reserved.
Speaker bio - Duane Nickull
Current
Chair - OASIS SOA Reference Model Technical Committee (OASIS Standard as of 2006)
Community Member (Planning Committee) - Ontolog Forum
Contributor - OASIS SOA Reference Architecture Technical Committee
Contributor - OASIS Service Component Architecture Technical Committee
Past:
Contributor/architect - W3C Web Services Architecture
Chief Architect/Chair - United Nations CEFACT Technical Architecture (SOA)
Chair - OASIS eBusiness SOA Technical Committee
Chief Architect - ebXML Technical Architecture (first major SOA)
Co-inventor - GoXML Contextual XML Search (51 unique patent points)
Co-Inventor - XML Commerce Pro (1997) first fully XML commerce engine
Author (books, white papers, technical articles)
Speaker (Conferences, Universities …)
My Band http://www.myspace.com/22ndcentury
2
And most recently….
Part of a research project to

capture knowledge in this book
using normative architectural
artifacts on Web 2.0.
3
So what is Web 2.0?
Something that people are struggling to understand

No common architecture
Multiple definitions
Contentious
So how can we capture the knowledge?
4
What architects use to capture knowledge
5
Web 2.0 - Where Does it Begin / End?
6
The Growth of Mobility: Web 2.0 Goes Beyond Wires
7
Definition: What Does Tim O’Reilly Say?
Web 1.0 Web 2.0

DoubleClick Google AdSense
Ofoto Flickr
Akamai BitTorrent
mp3.com Napster
Britannica online Wikipedia
personal websites Blogging
evite upcoming.org and EVDB
domain name speculation search engine optimization
page views cost per click
screen scraping web services
publishing participation
content management systems wikis
directories (taxonomy) tagging (“folksonomy”)
stickiness syndication
8
Methodology Used to Capture Web 2.0 Knowledge *
based on
Abstract
Design Patterns
Models
Guide Reference
Architectures
Refine
Domain specific Account for Specialized

requirements Architectures Concrete
Enable
Solution Patterns
9
Patterns
10
Patterns
Repeatable solution to a commonly occurring

problem.
Patterns can be repurposed across multiple
domains and used to solve recurring problems
there within.
Example: Collaborative Tagging (aka Folksonomy).
Can be used for audio files, video files, text files, binaries, people…
11
Common Web 2.0 Patterns
Collaborative Tagging (folksonomy) Participation/Collaboration

Synchronized Web (harnessing collective intelligence)
SOA Adaptive Software
SaaS, DaaS (variations of SOA) Microformats (a.k.a. fine grained

content accessibility)
Persistent Rights Management
Declarative Living / Tag Gardening
Mashup
Incremental Update (a.k.a. “Atomic
Rich User Experience (a.k.a. RIA, Particle Update”)
knowing something about your
users) … (more)
12
Models
The model for engaging using the

internet as a platform to span all
connected devices, humans and
applications.
13
Models
Definition: Abstract lexicon capturing a generalized set of

concepts and noting their purposes and relationships to
each other.
Primary Audience: Entrepreneurs, Software or Enterprise
Architects
Why:
Models guide all domains, whether explicit or implicit. They facilitate a
common, shared understanding or conceptualization of a domain.
Famous Models: OSI 7 layer stack, OASIS Reference

Model for SOA.
14
Model for the Old Web -> Client Server
Client
Server
15
Abstract Model for Web 2.0
Abstract Model for connecting and integrating capabilities and users
Users
Client Applications/Runtimes
Patterns
Connectivity/Reachability of interaction
SOA Services
Capabilities
“Don't treat software as an artifact, but as a process of engagement with your

users. “
- Tim O’Reilly
16
Reference
Architecture
17
Reference Architecture
A technology component view of a generalized architecture.

NB!: Abstract of all technologies (HTTP, TCP/IP java etc)
and abstract of all applications or vendor products.
Agnostic to patterns of usage.
Primary Audience: Software or enterprise Architects,
developers
Why: There is a great value in being able to communicate
ideas and functionality abstract of specific technologies
protocols or products. These become artifacts that can be
applied by architects in multiple domains.
18
Web 2.0 Reference Architecture
Controller
Client
Data/State Security Virtual Rendering
Application
Management Container/Model Machine & Media
Tier
Communication Services
Design,
Standard Technologies • Consistent object & event models
Development • Consistent architectural models
& Protocols
& Governance
Tools
Service Invocation Layer
Registry- Business Rules/ Service

Service Container Core Services
Repository Workflow Tier
Service Provider Interface
ECM Message Legacy

Resource Tier EIS Databases Directories
Repository Queues Systems
19
Service Oriented Computing
Re-purposing core functionality as service to be consumed.

But wait! What about the clients?
Do they have to be different?
Service Oriented Clients (SOC’s)?
Service Oriented Clients are, in most cases, Web 2.0

applications!
20
Service Oriented Clients - Web 2.0 Application Architecture
Mashing up multiple formats

Using services to deliver rich user experiences
Rendering/Media engines let users control the way they use your
applications.
Are no longer standalone - use knowledge of other users applications.
21
Enterprise Focus
on Web 2.0
22
Enterprises Want the Patterns of Web 2.0, too!
Distributors Customers Suppliers &

& Agencies & Citizens Contractors
Microformats Folksonomy SOA

Trust your users Mashups The long tail…
Semantics ENGAGEMENT PROCESSES Loose coupling
New account opening, Broker productivity, Grant
Identity 2.0
administration...
Engaging your RIA
Rich user experience
users
Internal Processes
ERP / ECM / CRM / BPM / Accounting
23
The Engagement Gap

Frustrating delays, lost revenue, information loss, non-compliance...
Internal Processes
24
Using the Web 2.0 Model to Close the Engagement Gap

Users
Web 2.0! Client Applications/Runtimes
Connectivity/Reachability
Enterprise Services
2.0!
Capabilities
Internal Processes
25
Amgen Tour Tracker (mash-up excellence)
26
So what is possible?
TV, Internet convergence (now)

Custom loyalty is gone (now)
Web 2.0 Design Patterns are top enterprise focus
(now)
Democracy, peace, ideas all flowing (now)
Spin offs galore ( ******* 2.0)
You are going to leave here and build the future (in
a few minutes)
27
Thank you!
Q&A
Yes - this is the

same pantone!
28
Revolutionizing
how the world engages
with ideas and information
29

Web 20 Design Patterns Models and Analysis 1194273339280295 3

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Web 20 Design Patterns Models and Analysis 1194273339280295 3

Uploaded by

Copyright:

Available Formats

Web 2.

Part of a research project to

Something that people are struggling to understand

So how can we capture the knowledge?

Web 1.0 Web 2.0

Domain specific Account for Specialized

Repeatable solution to a commonly occurring

Collaborative Tagging (folksonomy) Participation/Collaboration

SOA Adaptive Software

SaaS, DaaS (variations of SOA) Microformats (a.k.a. fine grained

The model for engaging using the

Definition: Abstract lexicon capturing a generalized set of

Famous Models: OSI 7 layer stack, OASIS Reference

Abstract Model for connecting and integrating capabilities and users

“Don't treat software as an artifact, but as a process of engagement with your

A technology component view of a generalized architecture.

Service Invocation Layer

Registry- Business Rules/ Service

Service Provider Interface

ECM Message Legacy

Re-purposing core functionality as service to be consumed.

Service Oriented Clients are, in most cases, Web 2.0

Mashing up multiple formats

Distributors Customers Suppliers &

Microformats Folksonomy SOA

Distributors Customers Suppliers &

Frustrating delays, lost revenue, information loss, non-compliance...

Distributors Customers Suppliers &

Web 2.0! Client Applications/Runtimes

TV, Internet convergence (now)

Yes - this is the

You might also like