Gregg, Yes, good design strategy will ease the problems caused by what is designed. I will not see the earth (software world) as flat, oo vs. soa, or soa vs. bpm. They are not parallel so no comparisons. They are related in the same way as organic molecules relates to cells; cells relates to organs, and organs relates to organisms. All these different levels of unities at packaged into 0's and 1's like the way we see light. We only see different colors with a lense.
We have a pleasant light because all colors are present behind the scene. If some colors are lacking, then the light we experience may not be as pleasant as it should be. Jerry --- Gregg Wonderly <[EMAIL PROTECTED]> wrote: > Jerry Zhu wrote: > > OO business concept for OO is not as important as > SOA > > business concept for SOA. In other words, as we > move > > up in abstraction, business model becomes > increasing > > important, hence increasing business and IT > aliance. > > Jerry, it's not about OO vs SOA. It's about the > right people thinking of the > right concepts, the right transports and the right > packages. Everything else is > a feature or problem of the associated > implementation. The implementation might > be base on SOA, it might not... > > A software design strategy is not the problem. It's > what you are designing that > can create the problems. > > Gregg Wonderly >
