--- In [email protected], "htshozawa" <htshoz...@...> wrote: > > Should IT not think about SOA at this stage because it's too late? > I would > say no.
The double negative is throwing me off--are you saying that IT should think about SO? I think you're say that they should. Correct me if my brain is misfiring. If IT is tasked with architecting and designing a solution, following SO principles would seem to be okay. There would seem to be some increased risk that the segmentation of services might be off but maybe not. > Now, this brings us back to the question that's been repeated here - > should SOA be initiated by a business or IT. If IT is part of the business, is there a distinction? :-) I'd offer that this isn't a question of which organizational unit drives an architecture effort. Should business or enterprise architecture, in whatever style, be driven by business or technology concerns? These forums have explored this in many ways and I think there is at least some consensus that while business concerns should dominate (especially in a BA), technology needs to be part of the picture as well (perhaps even in a BA). The decision to follow SO principles is one to be made by the architect (or architecture team), at whatever level the architect is working at. I agree with the several folks here that probably the best level at which to start is the business architecture level. Where some may disagree is if it starts at a lower level (presumably less business focused and more technology focused), that's okay too. A big part of the role of the architect is consensus building. Balancing the constraints and sometimes competing interests of the groups involved. This isn't "selling" per se but it does involve the ability to persuade when necessary. > IMHO, it doesn't matter too much as long as both parties become > involved as time goes along. If IT is part of the business, isn't there just one party? :-) > IMHO, SOA is a concept which has some best practices suitable for > many organizations but no one fixed implementation guideline > that's suitable all organizations (as is the same for most > concepts involving human factor). Agreed. And that's a big source of contention and frustration. Some want that fixed, guaranteeed to work guideline. Some say that without it, SO is useless. -Rob
