The services extension is intended to allow more sophisticated modeling of the service portfolio by creating a concept of IS services in addition to the core concept of business services. IS services are directly supported by applications and creating the layer of abstraction relaxes the constraints on business services whilst simultaneously allowing technical stakeholders to put more formality into an IS service catalog. The scope of this extension is as follows: I Creation of IS services as an extension of business service This extension should be used in the following situations: I When the business has a preset definition of its services that does not align well to technical and architectural needs I When business and IT use different language to describe similar capabilities I Where IT service is misaligned with business need, particularly around the areas of quality of service, visibility of performance, and management granularity I Where IT is taking initial steps to engage business in discussions about IT architecture The benefits of using this extension are as follows: I Business services can be defined outside of the constraints that exist in the core metamodel. This allows for a more natural engagement with business stakeholders. I IS services can be defined according to a model that maps closely to implementation, providing a more realistic solution abstraction to support IT decision-making. I Business and IS service relationships show where the business view aligns with the IS view and where there are misalignments. |
|