A good start, Shivambi,
I was also looking for starting points as the whole model could be somehow abstractive and floating. I was trying to look at it indeed a) from a business perspective (what the business wants to achieve (business capability) and how (business application), b) who the owners are (services, infra, foundation data), c) who the consumers are (customers, internal users) and what they consume (technical or business services via service offerings) and how (technical or service catalog). Surely, the application services are the enable of the whole with the underlying infra and here I'd also put "enablers" like SSO (meaning, no user comes to consume SSO but something that is behind the SSO, i.e. buy a product on a portal after authenticated via SSO).
In general, those 'enabler' entities like SSO, a Service Aggregator, even a Platform (portal) makes it a bit difficult to place on the map but application service seems to be the right place.
Another complexity is being added by localizations and domain separation, like in example if we take again the amazon example - you have the portal but you can choose the country/ language, then you may have normal or premium access until you reach the final product catalog. It adds many layers to the taxonomy and if you want to map the entire thing, how would structure it hierarchically?
@Everyone, please feel free to share your thoughts or add another examples. What would be your approach in adapting the CSDM v.4 model to a specific business case?
