[dathinab]

I think the problem comes from the difference between "modelling" as in the CS field of modelling and diagram generation for documentation purpose.

They are fundamentally two different use-cases which just seem similar if you ignore all the subtle but important details.

But UML tries to bridge both by having something you roughly could describes of "layers" of details.

But for documentation, especially tutorials, well suited diagrams aren't often just simplified by omitting/grouping details or similar. They are often simplified in ways which makes them subtle wrong in ways anyone getting started with the software can ignore and (hopefully) a foot note about this wrongness.

And most times for most people it's only ever used for less formal diagrams instead of "proper modelling". And more often for on-boarding/tutorial documentation then for deep technical documentation.