UML is a near-deprecated aspect of what was once called Computer-Aided Software Engineering (CASE). UML became the canonic iconic notation that replaced the mul

UML is a near-deprecated aspect of what was once called Computer-Aided Software Engineering (CASE). UML became the canonic iconic notation that replaced the multitude of -cough- guru-inspired systems and software notations that preceded it. As is documented in the rest of this thread, UML belongs to the age of mainframe and mini-computer programming projects with ubiquitous RDBMS backends. While the notations it consolidated were much lighter-weight and easier to use [AND more intuitive!], UML drowned in formalizing the corporate complexity of all of them. And as if that weren't a complex enough ambition, UML attempted to do rules-based and heuristic enforcement of Object-Oriented programming just to ensure its rejection by pedestrian programming staffs. Today, its a convoluted mess that virtually no one tries to untangle in a professional setting. Intelligent IDEs and the left-shift of Dev-Ops utilities have co-opted the CASE tools lunch. For sketching, Google's Draw.IO is superior by leaps and bounds to the heavyweight, commercial drawing products. While that explains the UML-narcolepsy effect, the broader issue has always been the lack of systems and program design education. It still is important to convey system and programming information beyond the cohort of programmers. I can tell you from experience that many accountable company business actors have NO IDEA what these systems actually look like in all the important ways. What's missing is Computer-Aided Business Engineering tools.