SDLC Components and Business Application Versioning

[CMDB Whisperer]

In CSDM 4.0 the Business Application is broken down into individual SDLC Components.  However, component breakdown of a business application is by nature version-specific, whereas business applications themselves are version-agnostic.  Is there a method of indicating the business application versions that apply to a specific component, so that you can determine whether a component should exist in a particular instance based on what version of the business application that instance is using?

[Shannon Lake]

Paul, my understanding is that is the purpose of the Model.  Every CI is supposed to be tied to a product model going forward.

[CMDB Whisperer]

Makes total sense.  Thanks Shannon.

[Mark Bodman · Accepted solution]

Yes, you will see a more systemic and complete use of Product Models going forward, eventually flipping to lead with Product / Product models from idea through end of life.  We use Product Models today mostly in just a Software and Hardware context. But the vision is that Product Model is where we capture the version detail, agnostic of deployment and related to classic CI's

The goal is to have CI's represent the instantiation of Product Models, their use and specific configuration.  Historically Business Application was created to be version agnostic pseudonym of Product in an IT plan & build context, while Business and Technical Services were the consumption pseudonym in Run and Delivery.  We want to be able to capture Application Service (or System) and Offering as versioned components.

It's best to think of the SDLC components as versioned ingredients used by build teams to construct App Service in CSDM V4.  They are the assembly of instances of other products such as hardware, commercial and internally built software, config files, API's and other piece-parts used in the construction of Application Services that are managed and consumed.