Tuesday, December 5, 2006

Measuring the Maturity of Enterprise Service Definitions

I've been researching on the necessary criteria for determing quality enterprise service definitions. One of the points that I'm running into, is how well you can measure the level of compliance with certain criteria when you are only in the analysis & design phase of creating a service. For example, most everyone agrees that services should be: manageable, secure, traceable, and conform to certain performance standards (as described in a SLA). An SLA can be (and should be) agreed upon and put in writing during the design of an enterprise service. This might include such things as: availability and reliability of the service, and what actions are taken if the desired level of performance is not achieved. So this part is clear - when desiging a service you can measure whether an SLA has been defined, with certain elements. But to actually measure the performance, this can't be done until the service is already implemented. The same is true for manageability, traceability and security - these elements are all monitored typically by application tools that would be installed at the middleware level and span across the entire SOA design.

So my question then is still - is it possible to measure the maturity of these criteria when designing an individual service, or can this only be done by monitoring software that is an umbrella over all of the services after they have been implemented? I suspect the latter is the case, and as a result these elements shouldn't even be criteria for creating quality service definitions.

Anyone have any thoughts?