Document Controls

  • View a Print Friendly version of this document

    Print
  • Toggle highlighting of search terms in this document

  • Text Size: 

    • A (normal)
    • A (larger)
    • A (largest)

For Application Development & Delivery Professionals

Primary Analyst Photo Document Information Rate this Document

December 14, 2006

Your Strategy For Web Services Specifications

by Randy Heffner

with Gene Leganza, Jacqueline Stone

This is an excerpt

Executive Summary

SOA and Web services adoption continues, but it is taking a long time for the industry to work out all of the specifications and standards. Core standards like SOAP and WSDL are widely adopted, and others like WS-Security are ready for broad adoption. But to build Web services that operate with high quality of service, the industry needs many other specifications like those for management, transactions, and advanced security. These are under development but as yet are mature enough only for aggressive technology adopters. To determine how aggressive they should make their firm's strategy for adopting advanced Web services specifications, architects and developers must balance the potential for business value from use of a given spec against their firm's ability to manage adoption risk through research and prototyping prior to early use of a spec.

TABLE OF CONTENTS

  • The Context For Your Web Services Adoption Strategy
  • The Elements Of Maturity For Web Services
  • Crafting Your Web Services Adoption Strategy

RECOMMENDATIONS

  • Business Value And R&D Capacity Should Drive Your Strategy
  • Supplemental Material
  • Related Research Documents

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.

Add to cart

Save and Share

Document Tools

Spread the word: