Apparently this did not make it out, please ignore if you did see it already.
Gregg Wonderly
--- Begin Message ---
Anne Thomas Manes wrote:
While I agree with your recommendation to focus on "why", I recommend
focusing on "what" way before you start thinking about "how".
I'm using "how" in the sense of "how do your business processes work" not "how
will you create an SOA". "what" is where I put "how will you create an SOA".
> And
you've totally lost me when you talk about moving end-to-end services
"into the SOA". That terminology makes it sound like a SOA is a piece
of infrastructure. (e.g., an ESB).
When you look at the business processes and see, end to end, what bits and
pieces are used, you may find that you already have an SOA that might just
benefit from some tweaking/improvements.
If there is not an SOA already in place, then you will need to decide if you
1) almost have and SOA
2) nothing like an SOA.
If you think that you can do some simple things related to the
technologies/practices you already have in place to finish out and SOA, then you
can move things towards an SOA by making those changes. In this case, I don't
see that there would be a big technology change or anything which would create a
participation barrier for the pieces and practices of your end to end business.
On the other hand, if you have nothing close to an SOA, then you will have to
move your technologies and practices in that direction. It may be that you use
new technologies or new practices which would create integration barriers.
Then, you might feel like you are pulling them "into the SOA".
It's this last case, that is the most extreme and presents an "inside the SOA"
vs "outside the SOA" from my perspective.
Maybe you have a different view point on these two situations?
Gregg Wonderly
--- End Message ---
