I've done one major project where I used the Yourdon Methodology progressing through all six models and then writing code. I used Excelerator as the design tool for this. My one major piece of advice is not to design to a level of detail below that assigned to one person for coding. The design should go to a level where each process in the design can be assigned to one person to code with all the necessary data entering or leaving the process completely defined. Object design may be taking the place of the now traditional design methodologies, but I suspect that for a lot of purposes both aught to be used.
Decision and state tables don't seem to be used much. I don't understand this as I have found both to be very useful tools. Complex logic can usually be rigorously and unambiguously modeled with these tools. Also, both provide ways to test the design for errors and to simplify the logic. I've also used boolean algebra along with Decision Tables to simplify complex logic.
The tools I've used for system design and documentation are Excelerator for data flow, process flow, and state modeling, Erwin/ERX for database modeling, and other tools such as MS Excel, Lotus Notes, etc. used on an ad hoc basis.
| © Copyright 2000-2001 Stephen Daniel McLeod |