I'm really confused about these acronyms. Most of the SOA approaches
I've seen have been driven by the business architecture and business
cases. However, the resulting architecture has been very different
depending on how they have choosen to model the business and how they
have choosen to implement the models.
For instance, the granularity of the resulting services has varied
widely despite that they all started by modeling the business
architecture. One reason is that a business architecture could be
modeled in many different ways i.e. as business components, business
functions, business processes, value chains, business objects, business
capabilities etc, or a combination of these approaches. There isn't one
way to model the business so B-SOA doesn't make sense as a
differentiating factor for the resulting service architecture. You must
be much more specific about the approach.
Dennis Djenfer
Steve Jones wrote:
Reading some things about SOA recently and speaking with clients I'm
getting a consistent feedback that T-SOA is being seen as a failure
and that companies are looking more and more at a B-SOA approach as
being the right way and driving change through structural,
organisational and governance with technology being part of the story.
Now clearly I'm HUGELY biased because its what I've been campaigning
for years, but are others seeing this as well?
Steve
------------------------------------
Yahoo! Groups Links
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.175 / Virus Database: 270.9.3/1788 - Release Date: 2008-11-14 13:36
