Using SSADM for Relational Design
I worked for a British computer company in the 1990s, and it was company policy to use SSADM (Structured Systems Analysis and Design Method) for any new projects. At the time, we were working on a part of the London Underground (also called the Tube) automation. I went to my manager with the time estimate for a new module that I was designing. The estimate was high, and he asked, “What are all these tasks for gathering requirement specifications and technical system options?” I said those were SSADM-based tasks. He replied: “We can do the documentation later. Right now, get on with the database design and front-end development.” A lot of years later, that attitude has not gone away.