|
ABSTRACT:
The foundation of SOA testing includes selecting the right tool for the job, having a well thought out plan, and sparing no expense in testing cycles or else risk that your SOA will fail out of the gate and thus have no creditability.
Organizations are beginning to roll out their first instances of SOA, typically as smaller projects. While many work just fine, some are not living up to expectations due to quality issues that could have been prevented with adequate testing. You need to take these lessons, hard learned by others, and make sure that testing is high on your priority list when you dive into SOA.
|
| |
 |
| |
AUTHORS:
David S. Linthicum
Managing Partner, ZapThink, LLC
David S. Linthicum is a Managing Partner at ZapThink, LLC. He joined the firm through the acquisition of Linthicum Group, LLC, a consulting organization dedicated to excellence in SOA product development, SOA implementation, corporate SOA strategy, and leveraging the next generation Web (Web 2.0).
Jim Murphy
Vice President of Product Management, Mindreef
Jim Murphy is Vice President of Product Management at Mindreef, with more than 10 years experience designing, implementing, testing and debugging distributed soft-ware architectures using Java, .NET, C++ and XML. Prior to Mindreef, he was an independent consultant, working with companies building distributed systems focused on DCOM and high-performance XML based messaging. He also served as a director, software architect and senior software engineer at several product and consulting organizations including Aspen Technology, Foliage Software Systems, TransactionWorks, and WWWhoosh, the Excelergy Corporation. Jim holds a BASc in Engineering from the University of Waterloo.
|
My Research History
Free Newsletters