Starting and applying SOA are different things. I think that SOA has to be started in one 'place' - business - (while it may be initiated in IT) and applied anywhere needed.
I say that "IT is a part of the business, not a disconnected, disinterested 3rd party that is merely to be given marching orders" - must be but, in too many cases, it is not, yet. This is why we hear that 'SOA failing', I believe. - Michael ________________________________ From: Rob Eamon <[email protected]> To: [email protected] Sent: Monday, January 5, 2009 2:35:48 AM Subject: [service-orientated-architecture] Re: How to start SOA in Organization I disagree. SOA as an architectural style can be applied to any sort of architecture. Thus, SOA can start anywhere. SO applied to business architecture starts at the business level. SO applied to application architecture would seem to start in IT. Is the biggest bang for the buck to be gained by starting at BA level? Probably. But that's not the only place where SO can be applied. I'll forego my usual "IT is a part of the business, not a disconnected, disinterested 3rd party that is merely to be given marching orders" spiel. :-) -Rob --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <m3pou...@.. .> wrote: > > SOA starts from Business, not from IT. > > - Michael > > > > ____________ _________ _________ __ > From: A W <ashra...@.. .> > To: service-orientated- architecture@ yahoogroups. com > Sent: Saturday, January 3, 2009 2:54:10 AM > Subject: Re: [service-orientated -architecture] How to start SOA in Organization > > > Web services are clearly the most promising technology for distributed computing and systems integration. > But, there are many reasons that go beyond technology. > You have to build a framework for thinking about web services adoption in your organization that can bring some of the benefits of the technology without exposing you to unnecessary risk and expense. > I think you need a help from external consultant. Don't try to step down the SOA road without such help. Specially, in your industry since in Teleco , the major problem is that business is the technology and the technology is the business. > > It is time to adopt web services in the organizations now but do not invest in technology in the beginning. Technology is not the problem. > You don't need to have an organization wide SOA rollout, and you don't have to re engineer legacy systems that work well. > However, you need to build the web services skill set in your company, because the technologies hold great promise for solving some of the tough(not all of course) problems facing IT. > The technologies that are available in the market, either vendor or open source products, have achieved capabilities, scalability, ..etc., and ready to be used. > I think a lot of projects in the teleco industry can benefit from application of web services, specially the network convergence. > > I think you will find customer data found in wirline, wireless and cabel. Try to build a unified view of your customer. You will learn too much. > > All the best > > Ashraf Galal > > > > > On Fri, Jan 2, 2009 at 3:03 AM, Fakhar Imran <fakharimran77@ yahoo.com> wrote: > > Dear all, > > This is Fakhar from Pakistan, I am working for local Telecom company. > > I've been assigned to work on the in-house Application Development for > our business requirements and I was thinking about presenting SOA for > design and implementation for new Software Development. > > Right now our SW development is not very mature and my fellows are not > aware of benifits of SOA (that also includes me :-)). I was wondering how > to convince for this grand shift as we are right now using .NET and > client-server model . > > Thanks, > > Fakhar Imran >
