Simpler applications in CSDM

[mark_oldroyd]

Could anyone give me any guidance on slightly simpler less behemoth type applications\application services in CSDM.

1) A basic application is represented in CSDM? Something like Notepad++, that is just a local install and not part of a bigger stack. I'm not sure whether you create an App Service for these, or the best approach is just to link the Application CIs straight to the related Service Offering (e.g End User Apps)

2) Something like Adobe Creative Cloud (I'm thinking CC is an Application Service and the individual parts are Application CIs). I realise we could make each part e.g. Fireworks, Photoshop etc. an app service. I suppose here I am struggling with what question\s to ask whom to determine the granularity needed.

Thanks in advance for any tips.

[Sanjay Arora]

Agree with the comments in the thread, but how does one "operationalize" Desktop Software CIs such as Excel , Powerpoint, Jabber etc that can be exposed on the Incident form?  SAMP actually will help create a list of software models that can be leveraged on a service catalog, but one would think that the same list of software models may require support and therefore need to be accessed on an Incident form? 

One can define app services like MS office services, Cisco Collaboration Services etc. to handle the above examples, but surprised there is no consistent guidance about how to handle this in the CSDM

[Mary Vanatta]

You would expose the "Service Offering" field on the incident form.  The Service Offering would be "Excel", "PowerPoint", "Jabber"  the CI would be the laptop or desktop that is the entry point to access those softwares.