How to model Application components in CSDM

[Shilpa29]

Hi Team,

We are currently progressing our CSDM implementation and would appreciate some guidance on how to model Application Components within the CSDM framework.

An Application Component is "a separately deployable component of an application that provides services to the application." Example: Capture Claim Center Listener is a document service that receives notifications when the document capture process is complete and subsequently notifies ClaimCenter. It is one of several web-based subsystems that form part of Capture Services (Document Services) and runs on server infrastructure. The corresponding Business Application is Capture Services (Document Services), which already has an associated Application Service.

Mu questions are:

1. Would it be appropriate to model Capture Claim Center Listener as an Application Service and relate it directly to the Capture Services (Document Services) Business Application? or  is there any better way to represent it in CSDM. We use this component for Incident/Problem/Change requests. 
2. Is it mandatory to have an Application Service to Business Application relationship in CSDM?

Any guidance or best-practice recommendations would be greatly appreciated.

Thanks

[Mathew Hillyard]

Hi @Shilpa29 

1) Yes, think of Application Services as instances of a Business Application by environment or geography. However the convention is normally to append the environment to the Business Application to get the Application Service name. A Business App and an App Service should not have different product names. I would recommend Capture Claim Listener as the Business App and then Capture Claim Listener Production for the production app service, Capture Claim Listener Dev for the Development instance and so on (if this app has multiple environments, like ServiceNow, as another example).

2) Yes. An App Service must be linked to a single Business App, and a Business App should normally be linked to all installed environments of that app, except in two edge cases: a) you want to record a Business Application that you are considering using (think of a portfolio pipeline use case) but have not yet implemented, and b) when you are retiring a Business App and have retired and maybe even deleted the App Services, but have not yet retired the Business App. 

I hope this helps!

Mat

[Shilpa29]

Thanks Mark for your response!!

The main issue with creating a Business Application is that Enterprise Architects do not want to create this application component as a separate Business Application. In this example, the architecture governance would be performed at the main application level, which is ClaimCenter. Hence, the confusion. Is there any alternative solution.