Consider all sorts of usage patterns and create a test plan that reflects them. Care must be taken to ensure that your SOA and external “mashable” components can play well together, and that the enabling technology and standards are working up to expectations. The test plan should be linked with design, governance, and security. In essence, you’re testing a development platform with all of its supporting components.
Where to from here?
Mashups and SOA are part of the same continuum. By linking the new components of Web 2.0 with our own sets of information and services, mashups provide a quick and easy way to solve many of today’s simple business problems — and should scale nicely to solve more complex and far-reaching problems in the future. They make the value of an SOA much more visible over a much shorter term.
As with any new concept, each enterprise must localize the concept for its own needs. One size does not fit all. But the beauty of both an SOA and a mashup is that, with the right foundation, they can be configured to meet almost any set of business requirements — and can be reshuffled quickly when those requirements change.