Business Application -> Application Model -> Application Model Lifecycle

[Justin Docken]

When adding a Business Application [cmdb_ci_business_app] its "Model ID" gets populated with the Business Application Name and an Application Model [cmdb_application_product_model] record gets created where its Name = the Business Application Name. The Business Rule – "Populate Application Model" is responsible for this.

This configuration ensures every new Business Application has an associated Model, which supports the Application Model Lifecycle [cmdb_application_model_lifecycle]. This creates a 1:1 relationship between Business Application [cmdb_ci_business_app] and Application Model [cmdb_application_product_model]. Why the redundancy?

Here are my Questions:

1.) The Application Model [cmdb_application_product_model] table is also used by Enhancements, Stories, Demands, Incidents, and Projects with the "Product" field. Doesn't this redundancy create potential confusion considering these other work items also reference the Application Model table for Products? Which table should we be managing our overall Products within? Is this really the right table? If we change it, we'd have to change OOB functionality with all these other work items referencing this table for Product.

2.) Is there any documentation on how and when exactly we should be creating and managing Application Model Lifecycle [cmdb_application_model_lifecycle] records? How many per Application Model/Business App? What do the dates pertain to on the Application Model Lifecycle [cmdb_application_model_lifecycle] form? Are these contract based for General Availability? There is a Phase Start Date and a Phase End Date with the following Lifecycle phase choices:

a.) General Availability

b.) End of Sale

c.) End of Support

d.) End of Extended Support

e.) End of Life

I haven't found any articles or training documentation pertaining to Application Model Lifecycle [cmdb_application_model_lifecycle]. Please share if you're aware. Thank-you!

[Mathew Hillyard]

Hi @Justin Docken 

1) Application Model is perhaps not the best name for this field. I believe there were plans to migrate Business Applications to Digital Products but I see that has not made it into CSDM v5.0. A Business Application is really a Digital Product (although a Digital Product is a wider scope than just the Business App), so maybe consider the Application Model field to really be synonymous with Digital product, then you have consistency with other Products in you Agile Development App. Most key elements of CSDM/CMDB are related to a corresponding Model record - the CSDM whitepaper describes why in detail. The reason for a Model record for Business Applications is largely that it is a type of product and that the product model is version-agnostic, whereas the Business Application may not be.

2) CSDM v5.0 contains a lengthy discussion on Life Cycle Stages and Stage Statuses, including Application Model, from pages 16 - Product Life Cycle Definitions are on Page 21.

I hope this helps!
Mat