This section provides a summary of the six SOA readiness profiles used within Oracle's SOA Maturity Model. The profiles provide a view into the different stages companies typically move through, and how they need to transform, in order to achieve additional capabilities and leverage from their shared services IT strategy. Companies may exhibitcharacteristics of more than one Profile depending on where they are in their evolution to SOA.
|PROFILE 1 |PROFILE 2 |PROFILE 3 |PROFILE 4 |PROFILE 5 |PROFILE 6 | | |No Adoption of SOA |Ad Hoc Adoption of SOA |SOA Approach Defined |Division-Level Adoption of SOA |Enterprise-Wide Adoption of SOA |Optimized for SOA | |Business Process & Strategy |Monolithic applications drive business processes;data and systems in separate silos; sub-optimal user experience. True IT costs or business return is hard to measure. |SOA strategy is under investigation. True IT costs or business return is hard to measure. |SOA vision and strategy defined. Roadmap developed. Enterprise business process model under development. Basic cost metrics defined for building the first shared services application.|Multi-year enterprise-wide SOA strategy plan defined and documented.
Cost metrics and funding model defined for cross-division services. |Multi-year enterprise-wide SOA strategy implementation is underway.
Costs and benefits metrics defined at the enterprise level. |Ongoing analysis of business opportunities enabled by services development approach. Direct linkage of SOA services performance to keybusiness measures. Costs and benefits metrics defined at the enterprise level. | |Architecture |No SOA concepts incorporated. |Enterprise reference architecture is under investigation. Services deployed in Ad Hoc manner. |First reference architecture designed, tested. Several industry best practices are adopted into the reference architecture. |Reference Architecture education and adoptionthroughout the division.
Reference Architecture reviewed by Architecture Board or knowledgeable experts. |Components of reference architecture moving into production as part of multi-year build plan. Reference Architecture embraced by multiple divisions. |Reference architecture completed and in production, with ongoing refinement. | |Infrastructure |Heterogeneous infrastructure, No domain model; disparatedata stores. |Some areas of component-based and service-oriented development are underway. |Necessary frameworks and infrastructure services have been defined but are
not widely used. Shared services are reused within single division but not across divisions. |Common frameworks and infrastructure services are widely used. Service enablement infrastructure available division wide. |All servicedependencies are tracked and impact analysis is starting to be used. Usage of the service enablement infrastructure is measured and enforced. |Enterprise-wide usage of service enablement infrastructure for both legacy and new. | |Information |No existing Data Reference Model. Different applications have duplicated
access logic to the same data. |The need for a Data Reference Model to effectivelyshare data has been identified, but the model has not been built. |Initial, incomplete Data Reference Model has been defined. Further refinement necessary. |Data Reference Model has been reviewed and accepted by affected groups.
Multiple projects within a division are utilizing the Data Reference Model. |Adherence to the Data Reference Model is mandated and enforced. Data
Reference Model beingutilized by projects across multiple divisions. |Enterprise-wide usage of the Data Reference Model for integration and data translation / transformation. The model is subject to reviews for
continuous improvement and a strategy is in place to raise legacy information providers to the same standards. | |Projects, Portfolios and Services |Monolithic Applications, silos. |Identified potential...