How to model Application components in CSDM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
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:
- 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.
- 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
