Skip to Content

SOA requires a strategy to manage change

The pervasive adoption of SOA changes the very definition of “an Application”. With SOA an application becomes an assembly and orchestration of business services, service composition, process engines and user interface modules. The concept in IT of ‘who owns what’ then changes, impacting funding, change control, operations, portfolio management – the list goes on. There are more components to manage – making common statements like “the application is up” (or “the application is down”) meaningless.   Business solutions will become composed of services that might be shared across business units, or sourced from partners in a business process.  But none of this will work unless there is an agreed-upon governance model, with standards, policies, funding and associated infrastructure for hosting, monitoring and testing services. And Enterprise Architecture is the logical leader to champion the need for governance and relate governance and investment in SOA to the strategic objectives of the firm and the firm’s IT.
Be the first to leave a comment
You must be Logged on to comment or reply to a post.