hi @MitchMcln ,
I use some tweaked models to make this easier to explain/understand:
There is a split in:
Plan/Build - This is the Conceptual layer --> these are not real solutions (yet) and therefore these objects do not play a role in eg ITSM transactional data.
Deliver/Run - This is about real solutions. This data is what is managed and offered for consumption.
I made a split here in the orange domain as in:
the Run is a realization of a conceptual Business Application were the Application is the deployment on a Business Application. All of the below is needed to make it a solution.
The Managed section is how we manage/support the part in the Run section. (Internal and External)
The Consumed section is how we offer the Run section for consumption. (Internal and External)
If you offer an application solution to the internal audience (eg a traditional on-prem application) the the consumers know this by eg App ABC. The solution might depend on :
Application support running via webserver (apache?) a DB (oracle) on a host (linux?). Meaning on the managed section you have :
- Application service
- Apache service
- Oracle service
- Linux service
If the Application is eg a SAAS solution then it is a more flat model of the solution (might be only Application support).
If it is a modern solution then it also might be more flat as the managed service supports the vertical stack.
Still the concept of the lower part of the model is the same:
I have Solutions that I offer for consumption and that needs to be managed/supported.
Note:
were sometimes this is discussed on the standard output I tweaked it for this reason ( so these are my versions of the model to make it 'easy' )
Hope this helps.
Barry
@Barry Kant , very good drill down drawing, to explain simplicity, on the orange layer I have also expanded the drawing to better understand the technical stack and services.
In the Conceptual / Plan section, I think it would by good also to extend this to show Information Object -> Data Domains layer.
