The only reason UML didn't pan out was because it isn't code, and if it's not code, software engineers don't want to do it because software engineers are lazy w

The only reason UML didn't pan out was because it isn't code, and if it's not code, software engineers don't want to do it because software engineers are lazy when it comes to things that are neither code nor one-step-away-from-code tasks. They will go build a million different things instead of documenting. As a consequence, they lose their engineering title and get called developers. UML works. One can lead a horse to water... just like one can stand up ALL of the top, fully-functional UML tools for a software team at what used to be a performant defense contractor, and have literally ZERO people use it. Same with system engineers and commitment. Requirements work. Model driven time wasting doesn't.