SSADM and DSDM are two methodologies that are for the most part polaric opposites.
SSADM (Structured Systems Analysis and Design Methodology) is based on the traditional Structured Programming techniques. It uses a formal design process that is a direct descendant of the "waterfall" methodologies. This process tends to be relatively slow, but because the process tends to be exhaustive in both finding and debating every reasonable need, the results tend to be large and cumbersome, but thorough.
DSDM (Dynamic Systems Development Method) is based on RAD. Most of the DSDM implementations I've seen approach the "data cowboy" attitude of consultants who are brought in to do one application, who are secure in the knowledge that they'll never have to maintain it. DSDM usually produces results fairly quickly that closely mirror the immediate desires of the user, but sometimes the resulting applications don't fare well over time.
While it might be possible to use both methodologies in a single project, I can't imagine how it might be done. This is something that I'd love to watch, but only from a safe distance!
For More Information
- Dozens more answers to tough database design questions from Pat Phelan
- The Best Database Design Web Links: tips, tutorials, scripts, and more
- Have an Oracle or SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your database design questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
This was first published in December 2002