You absolutely right Rob. Not every project will be end up using SO techniques, but there are some which will. Instead of a "SOA project", a better phrase might have been a project which I think will benefit from using SOA. Finally, I think it's better not to include "SOA" in the title of a proposal unless the customer specifically asks for it. :)
H.Ozawa --- In [email protected], "Rob Eamon" <[EMAIL PROTECTED]> wrote: > > IMO, trying to get budget to startup an SOA project is a misplaced > idea. SOA isn't the end goal. > > Being business driven means there is a business issue of some sort to > address. Or many. There should be a business driven desire to > revise/define the business architecture. Then, one can consider whether > or not SO principles (among others) would be a good fit for what one is > trying to accomplish. > > If the business architecture seems fine as is, perhaps there is a need > at another architectural level. Even here, one identifies a business- > driven need first. > > One shouldn't try to convince the business team (which includes IT) > that "we need to do an SOA project." That's backwards. The more > appropriate discussion, IMO, is one about the fit of SO principles to > an already recognized architectural definition need. e.g. "We know we > want to change/update/revise/define the architecture, are SO principles > (and others) a good way to meet the business goals that the > architecture must fulfill?" > > -Rob >
