What is the best approach for Enterprise Architecture Business Applications lifecycle Management ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday - last edited Wednesday
We are implementing enterprise architecture and we need to implement the process for lifecycle of a business applications.
As is process is very complex and we need to replicate the same to the ServiceNow as per customer.
There are around 8-10 personas in current process who will be performing this lifecycle and compliance management for an application.
For example -
There are specific users who has to approve before marking business application as operational.
There are specific set of users who has to update specific set of compliance attributes in specific application lifecycle stage.
Certain set of validations and information has to be updated before marking an application as retired.
What is the best robust and scalable way to approach this requirement ?
I have below in my mind.
Approach 1. Implement a catalog item / record producer which will manage these lifecycle. We will write code or run different type of validations on catalog item and at an access level of business application they will have read access on architecture workspace where they can see all the information but updates are controlled through catalog item / record producer.
Rather than writing code and ACLs on the Enterprise architecture workspace UI its better to write on catalog item is my view.
Implement ACL where real security is needed such as cost information etc if required.
Approach 2. Implement all validations , access controls or ACLs (wherever really necessary) , scripts , business rules etc on Enterprise architecture workspace UI.
I am personally against it and trying to avoid.
My approach is keeping workspace UI clean and users can read information from workspace UI only but going forward all updates should happen from catalog item or record producers.
Enterprise architects or only few set of users can update workspace UI directly.
One forward risk I see is that relate list features , allowing read only access at EA workspace levle might not allow users to access related list features. However that is okay as few personas will still have access to these features for any analysis. For ex - Enterprise Architects.
What is your view ?
Do we have any document where ServiceNow recommendation is listed ?
