Professional Documents
Culture Documents
September 9, 2008
1:00 p.m. Eastern/10:00 a.m. Pacific
60 Minutes
© 2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
®
®
THING ONE THING TWO
The Internet
THING THREE
®
THING ONE THING TWO
XML
THING THREE
®
THING ONE THING TWO
Web Services
THING THREE
®
THING ONE THING TWO
SOA
THING THREE
®
THING ONE THING TWO
ESB
THING THREE
®
THING ONE THING TWO
HTTP/REST
THING THREE
®
®
Starbucks?
®
®
Reference:
A Reference Model
acts as a point of
reference for a
domain.
Durability:
By not tying it directly
to existing technologies
it can be reused over
a maximum set of
environments.
®
Web Services
live here.
®
®
®
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
Note: These comparisons are several years old many companies have innovated since.
®
based on
Abstract
Design Patterns
Models
Guide Reference
Architectures
Refine
Domain specific Account for Specialized
requirements Architectures Concrete
Enable
Solution Patterns
®
®
Monolithic Structured
Client - Server
spaghetti beasts Monoliths
BPM
Mashups
Things that SaaS
Components Services RIA’s
use Services SCA
Composite Apps
®
®
®
DEMO
®
Impact of Web 2.0 on Testing and Quality Management
Jeffrey A. Meyers
Senior Product Manager
© 2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
How does Web 2.0 Affect You?
• In front of every mash-up / RIA is some fancy
Web 2.0 technology
− Flex, AJAX, etc.
• Behind every mash-up is some sort of service
based architecture
− XML / HTTP, SOAP, etc.
• People are both building software and
manufacturing composite apps
• Your testing and QM practices need to be able to
deal with these issues
A look at Duane’s example
A look at Duane’s example
An application
Bringing it all together
Racing Info
Chat Feed Over Racing Info
Mapping Service
A tale of two perspectives
• Your web 2.0 app
• The service
Yahoo Mapping
Services
x.com
y.com
Service X
LOB1.com
Service Y
A slight twist
“Enterprise” Web 2.0 is slightly different than “public” Web 2.0
Service X
LOB1.com
Service Y
Enterprise Boundary
Multiple mash-ups and services exist within the same zone of control
Impact on testing & QM
LOB1.com
LOB3.com
Service
Enterprise Boundary Y
Identify /
manage
requirements
Establish risk
based test
plan
Manage
execute and
• The process is inherently
report
still the same Go
/
• Web 2.0 impacts activities
No-
and workflows
go
• Your role (consumer vs.
provider) greatly influences
your activities
Quality Management
The technology stack is layered
Composite Applications
Performance
Functionality Security
.. . Quality .. .
HPSW Tools
• Quality Center with Service Test Management:
− Proper test planning for the services
− Understanding the impact of services on apps
• Service Test: validation at the service layer and below
• QuickTest Professional: validation of the flex based application
• Performance Center (or LoadRunner):
− Performance validation for the app
− Performance validation for the services
• Application Security Center:
− Security validation for the app
− Security validation for the services
• Systinet:
− Governance over the relationships between providers and consumers
Tools overlaid on the problem
Quality Center with Service Test Management
LOB1.com
LOB3.com
Service
Enterprise Boundary Y
Systinet
Tools overlaid on the problem
Service Test,
Performance Center / LoadRunner (SOA)
LOB1.com
LOB3.com
Service
Enterprise Boundary Y
QuickTest Professional,
Performance Center / LoadRunner
(Web)
Attendee Services