In the 80s I learnt SSADM and it was great for making sure business logic and architecture were understood and viable before a line of code was run. Which was v

In the 80s I learnt SSADM and it was great for making sure business logic and architecture were understood and viable before a line of code was run. Which was very important on old mainframes with several hour turnarounds on compiles. For last few decades I have only used diagrams to design and to explain. Have found too hard to keep diagrams up to date when iterating on compiles multiple times per hour. What I feel is needed is ways to keep code, infra and spec in sync throughout the lifecycle.