Still use subset of UML often: class diagrams, state diagrams and sequence diagram. Exactly the things that were used before uml and that uml 1.0 standardized.

Still use subset of UML often: class diagrams, state diagrams and sequence diagram. Exactly the things that were used before uml and that uml 1.0 standardized. Note: I’m using a subset non strict “uml”. Just to discuss software architectures or document designs. However sometimes simple boxes and arrows are enough but at least uml prevents some ambiguity. Note that UML 2 and MDE (model driven engineering) indeed failed. However some of the theoretic aspects still hold true today. Such as DSL languages written in a GPL language (react / Kotlin dsls / etc) And off course SQL is explainable in MDE terms (sql is a dsl for querying) Cool think is that these days new programming languages that are more functional oriented and cross platform solve the problem UML and MDE wanted to solve. These languages support dsls for example Kotlin.