Building on the thread of:
What is Service Oriented Architecture
what does it do/what is it for
we should also look at who will benefit from a defined SOA (& will these audiences have such different perspectives that they could be talking about the same thing and not know it)
In setting goals and boundaries for SOA I believe we need to consider question #2 below as part of the definition process. That is first decide what issue/problem that SOA is solving and then create a definition for that solution. The other questions break the first question into more granular pieces.
2. Why have SOA
what are the benefits of SOA (recognize reality; utilize existing efforts)
what are the requirements (to separate a 'true' SOA from a 'pretender'; or what gets branded a SOA
3. What are the ingredients/components of SOA
4. How to describe/define SOA
use of patterns
semantics (that encompase existing efforts & speak to multiple audiences)
Tomorrow can we spend some time on question #2, what do we expect SOA to do (or solve)?
Sally