Governance and Wrapup
Unit 5a-3
© 2007 IBM Corporation
3
IBM Americas Advanced Technical Support
Washington Systems Center, Gaithersburg, MD
Going Back to Our Original “Problem Statement”
Starting out …
Do you recall the really inflexible application interconnection chart we showed
earlier? That serves as the backdrop for this discussion:
How do you approach this?
How do you make sure it’s
approached in a sensible,
controlled fashion?
How do you make sure it
works as you hoped?
This is more than just a “use product X” issue. Here we get into the issue of
planning for and executing on a plan in a defined, controlled and disciplined manner.
Way back in the first unit we presented picture that represented the typical “spaghetti code”
application design. We mentioned back then that many companies -- IBM included, by the way --
have pictures that look like that. It just something that happened over time. As we contemplate
what we’ve learned so far, and look at this picture, we’re faced with some basic questions about
approaching this and applying SOA to it. The purpose of this unit is to give you a sense of the
issues and thinking in this space.
Before we do that, it should be clear that what we’re about to talk about is not just a product usage
issue. What we’re about to talk about is really more of a high-level control and discipline approach,
aided by technology implemented in particular products. Much of this is really related to human
behavior -- tools are only as good as our willingness to use them properly.
评论1
最新资源