[EA] Business App Lifecycle - Install Status vs Lifecycle stage/status - question around registering

[Tom Sienkiewicz]

Hey Folks,

we'd like to leverage the OOTB Business App Lifecycle Catalog (Register anew Business App) as the starting point in the process of creating a new app. In the default setup, I noticed that the request will go for EA team approval, and then the Business App record will be created.

However, the BA gets created with "Implementing" install status, which is by default mapped to "Design/Build" Lifecycle stage/status.

Question: Why is the install status not set to Under Evaluation (mapped to Ideation/Under Evaluation)? What is the purpose of the Under Evaluation state in this lifecycle? Are we basically "skipping" it when using the above catalogue item? I understand that technically after EA approval, the app has been evaluated to some degree, just wondering if there's really any usage for the Ideation stage still when leveraging that lifecycle.

Looking forward to comments!

Tom

[mcastoe]

Hi Tom,

the real reasoning is lost somewhere in the mists of time 8-9 years ago.   I guess the original APM product owners felt business apps should be created as they were being built.  Now, it is ideal that the record is created in the ideation/planning phases as result of a Demand.  

[Tom Sienkiewicz]

Thank you Mark,

I'm trying to visualize the e2e process of creating a new Business App. My initial thought was as below, maybe you could give me your thoughts on this:

1. first use the "Register new Business App" catalog item, this adds the BA record to the table after approval of EA team. Ideally, this would be in the Ideation stage...

2. The next step would be to create a Demand - here, the BA record created in step 1 would be leveraged -> this would solve the challenge we have today, that "dummy" new BA records are being used within a Demand. The Demand has its own approval process and as a result, Change or Project would follow. This ideally would be reflected in the BA stage "Design"

3. As the Change gets accepted/completed, the BA stage would change to "Deploy" and then "Operational".

I'm not sure about the overlap/coexistence of those Lifecycle Catalog Items and the Demand/Change process. I would see step 1 as just a tentative review and creation of the app "concept" and then more detailed reviews/approvals, e.g. security team approval, would follow in the Demand/Change phase.

Does the above make sense, or am I overcomplicating things here?

Cheers,

Tom

[mcastoe]

Hi Tom,

yeah, that works and is in line with where we are going in EA.  The BA record serves as a "holder" for designs that are the architecture side of the Business Case/Demand.   Imaging ARB decisions and architectural models as part of the overall business case.  the BA record gives you that place to bring the technical and EA details together.   Attached is a New Bus App process i did up a few years ago.