Datasheet

c01_1 07/08/2008 22
this scenario, or will end up with a very limited bottom-up SOA imple-
mentation with limited business value.
&
SOA Acceleration and Assimilation. The acceleration and assimila-
tion phase of SOA adoption is where the organization leverages the
reference implementation to add new SOA capabilities, add new proc-
esses, expand the consumption and development of new services, and
accelerate the adoption of SOA by its IT and business consumers. The
SOA acceleration and assimilation phase is where SOA becomes inter-
nalized by the organization as the primary means by which business
capabilities will be enabled by the IT organization, and the primary
means by which the IT organization will operate. This phase involves
rapid iterations around the SOA reference implementation core, ex-
pansion of SOA governance, and achievement of a repeatable SOA
realization model.
&
SOA Programmatic Execution. In the SOA programmatic execution
phase, SOA has become a standardized and repeatable model for the
delivery of business capabilities and solutions via services. This phase
represents the point at which the SOA strategy is being executed crisply
and steadily as a formalized program. SOA governance is robust and
guides all SOA activities from strategic planning through sunsetting
and retirement of services. This phase represents when an organization
should be delivering SOA value through rapid delivery of service-
enabled capabilities, where reuse of services is accelerating, and where
desired organizational benefits can be measured and demonstrated.
&
SOA Steady State. By the time an organization reaches the SOA steady
state adoption phase, the phrase ‘‘Service-Oriented Architecture’’ and
the ‘‘SOA’’ acronym will probably not be in use anymore. SOA will
have become the fundamental model by which IT services are delivered.
These will be no other model except for services. This phase of SOA
adoption is a long way off, but it represents some point at which SOA
is the clear and assumed model for business and IT. It will have become
so ingrained in the organizational culture that services are just a natural
way of architecting and delivering business solutions. At SOA steady
state, SOA governance will be natural and infused throughout the or-
ganization. The SOA strategy will become just another aspect of both
the business and IT strategies, and will not necessarily be documented
separately anymore. At SOA steady state, the next big IT trend will
probably be well on the way, and we’ll be exploiting the opportunities
that the SOA wave created for us.
As you might surmise, the activities, processes, capabilities, and SOA
governance requirements are all different for the various SOA adoption
22 THE SOA GOVERNANCE IMPERATIVE