Where is the best place to begin when building a testing system for SOA?
Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.
Hannah Smalltree, Editorial Director
First, you need to establish a quality policy as part of the overall SOA governance strategy. That policy needs to enumerate the various factors that directly influence the quality of a SOA system. For example, how are the back end systems validated? What kind of tests need to be in place for the back ends and the services? What measures and thresholds are going to be in place? Second, an enforcement mechanism needs to be put in place for the quality policy. For example, how are the collaboration workflows going to be automated and tracked? How are the tests executed, and how are the results gathered and metrics monitored to ensure compliance? Once that is in place, you start by implementing the testing system in accordance with the defined policy on a single pilot group that works on one or more applications with a few services, then expand from there. The pilot group will help revise the policy as necessary before expanding, and the gradual approach helps ensure success as opposed to a "big bang" approach.
This was first published in September 2008
