You're not ready for SOA - and that's ok. If you're SW development isn't mature - go mature it. Building SOA on top of a poor foundation will lead to failure.
My recommendation is to improve the basics: - architecture as a dicipline (application, integration & enterprise) - SDLC, methods, process activities - best practices within activities (config mgmt, build mgmt, deploy mgmt, etc.) Go back to your group and present what your organization needs to do to "get ready for SOA". Jeff --- In [email protected], Fakhar Imran <fakharimra...@...> 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 >
