InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Article: SOA Contract Maturity Model

Posted by Abel Avram on Jan 22, 2009

Sections
Architecture & Design,
Enterprise Architecture,
Operations & Infrastructure
Topics
SOA ,
Governance ,
Versioning
Tags
Maturity Models

In this article, Kjell-Sverre Jerijærvi presents with enough detail Microsoft’s SOA Maturity Model (SOAMM) which can be used to evaluate the maturity of a SOA implementation.

Read: SOA Contract Maturity Model

SOAMM has four levels of increasing maturity:

  1. Basic
  2. Standardized
  3. Advanced
  4. Dynamic

Each level is evaluated considering the following 3 perspectives:

Service Implementation

This model perspective describes capabilities of an enterprise to implement efficient best practices, patterns in building and providing services. Achieving this capability strengthens and optimizes the design and development of enterprise business and system services.

Service Consumption

This model perspective describes capabilities of an enterprise to effectively adopt and promote use of services. This capability provides foundation for support and enhancement the consumption of enterprise services by others.

Service Administration

This model perspective describes capabilities of an enterprise to support the cross-organization governance and operational aspects of services.

Kjell-Sverre explains each maturity level, how one qualifies for it and what are the benefits. While most companies, 82% to be more precise, are at Basic level, there is no need to jump from start to the highest level in order to achieve results with SOA. One can start with the Basic level and gradually advance to the Dynamic one which provides the best results for a SOA investment.

  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.