| Title: |
The SOA Maturity Model – Part II |
| Author: |
David Sprott |
| Publication Date: |
22 March 2006 |
| Report Type: |
|
| Abstract: |
In December’s report I updated the basic Maturity Model and Roadmap framework. Actually there were few changes to the basic framework in terms of levels or streams, mostly fine tuning. The major change was rather emphasis and level of detail on the concepts of capability and dependency.
If SOA is a set of principles and policies that define better structure, looser coupling, reuse of standard components and so on, then to adopt SOA an organization or ecosystem needs to acquire various capabilities that enable these characteristics. And the Maturity Model allows us to assess what capabilities we have currently and the new or improved capabilities needed to support certain classes of activity.
But December’s report concentrated on the basic framework. It didn’t explore how we might use the approach to make decisions on what to do and when. In this report we will look at how the framework supports a methodological or engineered approach to SOA introduction.
|
| Backgrounder: |
This report follows on from a major update to the CBDI Maturity Model and methodology published in December 2005. The first report updated the framework and showed how capabilities form a practical foundation for SOA planning. This second part illustrates how the maturity model provides a framework for deciding and communicating many aspects of IT strategy. |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home