CSDM 5.0

[Erick18]

When will CSDM 5.0 be released? 

Thanks,

Erick

[Community Alums · Accepted solution]

I was in the K24 and fortunate to take a picture on CSDM 5 Draft at the CSDM booth on the expo floor. Interesting to see the Gen AI + Domain-LLM in the BUILD domain. @Mark Bodman, I missed both of your sessions at K24 but would be grateful if you can share some content about CSDM 5.0.

[Bobby Campbell]

If my notes from the K24 session are accurate, 5.0 draft in Xanadu, final in Yokohama.

[Fred Jonkhart]

Looking at IT4IT I would opt for the following 
- portfolio/design: Digital Product

- build: Digital Product Release ( a particular version, a sub-class of Product Model?)

- ops: Digital Product Instance

The IT4IT model mentions System as the object that represent the technical internals of a digital product. So an alternative could be.

- portfolio/design: System

- build: System Release ( a particular version, a sub-class of Product Model?)

- ops: System Instance

My point is that there should be a natural flow from portfolio to build to operations and not using 3 different terms in each area.

[richardlemesle]

"Service Portfolio" disappeared as a main concept wich is a good thing (portfolios are useful for more than only services and I don't consider it as a "first class" entity).

I would call the "service instance" simply "Digital Product CI Group" since its aimed to represent one instance of an SDLC component or one instance of a digital product which may be composed of other "Digital Product CI Group" representing instances of the SDLC Components of the Digital Product.

This would be coherent with "Dynamic CI Group" terminology to group CI.

I would rename "Technical Management Offering" by "Digital Product Offering" since its an offering centered on a Digital Product. No need for "Technical Management Service" which can be represented by the "Digital Product" (just need to add a link between a Digital Product and its offerings in the service delivery domain).

I would create two subtypes for "Digital Product" :
- one is "Business Application" representing the current "Business Application",
- and the other is "Technical Service" (in the Design domain) which represent a plateform or infrastructure which need to be seen as a product from the Design to the Run.

And I would keep an "Infrastructure Service" in the "service delivery" with "Infrastructure Service Offering" refering CIs using the "Dynamic CI Group" to manage every basic CI.

[swarner]

Well,  I understand an Application Service to be a stack or group of associated CI's, and possibly the environment they are in (dev/test/prod etc.).  I wish they would just leave it alone and not fuss around with terminology. But if they HAVE to change it my vote would for Service Stack, since that's what it is IMHO.

[Miklos Palfi]

Here is an earlier (Apr. 2024) discussion about the CSDM 5, with some interesting background considerations. There are newer versions of the same slide, but this shows still valuable insights.

IT4IT & CSDM: Through the Looking Glass
https://youtu.be/N6ZpcMSA7M4?feature=shared