Application Service and Business Service Offering

[HMJ]

Currently the UI for Application Service Creation and Maintenance enforces a dependency/relationship to a Business Service Offering by making this mapping a required field. As we have "internal" tools that are purely used for administration of IT resources, I can't see a need to model these as Business Services (and offerings) as they support technical services that we require to offer business services to customers. I'm missing an explanation, why the business service offering is required, but not the link to the technical service. In my view, one dependency should be required (technical OR business), but it should not only be the business one. Any explanations or ideas?

[Barry Kant]

hi HMJ,

can you check :
<INSTANCE>/application_service_settings.do

Is the Business Service Offering set as a required relationship?

BR,

Barry

[HMJ]

Yes this is the case, but my question is going further, whether there is a conceptual reason why this is set as required, which I would "destroy" when I set this relationship as optional.

[Barry Kant]

I am not sure I wouldn't set it required. You can change that by these settings. In my instance it is not required. If I phase out a solution I probably break the relations and/or clean up.

[Adi Schmid]

In the CSDM Whitepaper 4.0 you will find a paragraph "How to follow CSDM standard". There it is recommended to work with the business services from the "Run" phase on. We followed this model and had no disadvantages with introducing the business services later.