Find out which specific "views" for ops, devs, and architects are necessary

[bonndan]

Currently machines are not included in the graph, which is an issue for ops. Developers may be interested in certain details, too, which are not relevant for other groups. Architects may only want to see abstractions, but perhaps wider/more landscapes.

https://modus.medium.com/what-makes-a-map-good-4db0de3b2cec

• define ops needs
• define dev
• define architect needs (but not sophisticated togaf or EAM stuff)
• views for stakeholders

[bonndan]

Index everything, but render an appropriate abstraction level.

On the highest level, render only groups and dataflows. Enhance dataflow relations to contain a "business object"

See also https://c4model.com/

[deka]

Hi,
In my case, I need in addition to the IT view, a business view (product manager, business process manager ...)
To get the correct views, I think the nomenclature needs to be configurable.
Currently there is only 'group' and 'item'
ex for information system urbanization : Area contains Quarter, contains Application bloc contains services
Regards

[bonndan]

Hi @deka , thanks for the feedback. Would you mind describing the urbanization approach a little more? What do you need it for and how does it differ from https://c4model.com/ ?

[deka]

The C4 model is a good starting point for an application and technical vision.
In a medium/large information system, the higher level of the model c4 'System Context' is not sufficient to have a functional and business vision.

Example of urbanization we have:
We use the four standard areas: 'BI', 'Business', 'Reference (Master Data)', 'Support'

• The 'Business' area contains, among other things, the quarters (districts ?): 'Production', 'Logistics'.
  The 'Production' district contains the 'Production scheduling', 'Raw materials supply' ... applications block and each application block contains technical elements (containers, database, scripts, etc.)
  The 'Logistique' district contains the 'WMS' and the 'TMS
  ...

The common urbanization layers

To have flexibility, i think

• Technical and applicative layers items can be fixed and inspired by C4 model.
• Fonctionnal and bussiness flow layers need to be fully configurable.

[bonndan]

Hi @deka,

so far I have never heard of the urbaniztion concept but that does not have to mean anything. It sounds much easier to grasp than TOGAF etc. What I can find are some scientic sources from French speaking countries (e.g. https://www.researchgate.net/publication/269518809_Urbanized_Information_Systems_based_on_Business_Services). It might fit our needs, since we want to provide a quick and easy approach to EA on a beginner level.

• Is the concept of French origin?
• Is it actually used in practise and how widespread is it?
• Is it hands-on or ivory tower?
• Do you have first-hand experience?
• Could you explain the difference between business/metier and functional level? It is really necessary to distinguish the two?

[deka]

Hi @bonndan,

Is the concept of French origin?
I don't know, but it's actually used in some big French companies.
Is it actually used in practise and how widespread is it?
Yes, in France, in large groups (Industry, banks, public service).
An urban planner is more or less an architect, with a vision that is more functional than technical
Is it hands-on or ivory tower?
Perhaps ivory tower. The goal is to streamline IT processes. It's not a framework like TOGAF, but some concepts to streamline and manage the applications lifecycles
Do you have first-hand experience?
Any small experience in a medium-sized company (3500 employees) to set up processes to map and redesign the IS
Could you explain the difference between business/metier and functional level? It is really necessary to distinguish the two?
I’m not sure I understand, in my case, i need multiple monitoring views :

• Technical views (for dev, ops, architects ...)
• Global business views (for product owner, business managers ...)
• Business processes views (for operators, workers, business owners ...)

Regards

[bonndan]

Cool feedback @deka, thanks.