>through psuedocode, descriptions, diagrams et al). Example: SSADM has, as
>as I have seen, only been used on one project, even though we do a lot of
SSADM is used in a lot of government projects, or used to be at any rate.
>can claim credit for Z. I've also never [s]een it outside the classroom.
I seen it in bookstores if that makes you feel better ;-)
>Whilst I suspect there is a place for formal design languages, notations and
We use UML quite extensively at our company and it works well, although it not applied
all that rigorously. It must be said that one of the things that is most appreciated
about it in the clientproject based work that we do is that it gives you something to
show to the client, they seem to like that . . .
On that line, the project I'm working on at the moment has been designed and partially
implemented by Andersen Consulting, and they use structured design a _lot_, and I must
say that many of their documents read like they've just filled in a boilerplate with
the client's details. Again, it's gone down well with management but the implmentation
teams aren't that impressed.
Yours,
Ian.
#ifndef __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | TIBCO Software Inc.
#endif | www.TIBCO.com
************
[EMAIL PROTECTED] http://www.linuxchix.org
