Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!pasteur!ames!ll-xn!mit-eddie!uw-beaver!cornell!rochester!kodak!mcgrath
From: mcgrath@kodak.UUCP (bill mcgrath)
Newsgroups: comp.software-eng
Subject: Re: Anybody know about SADT?
Message-ID: <1265@kodak.UUCP>
Date: 16 May 88 14:30:43 GMT
References: <660@vsi.UUCP>
Reply-To: mcgrath@kodak.UUCP (bill mcgrath)
Distribution: comp
Organization: Eastman Kodak Co, Rochester, NY
Lines: 24

In article <660@vsi.UUCP> friedl@vsi.UUCP (Stephen J. Friedl) writes:
>Hi net.{guys,gals},
>
>     A number of months ago I became exposed to the Yourdon
>Structured Analysis methodology (DeMarco's book) and was very
>impressed with it.  I had previously done systems (20k-50k lines)
>with no more than good programming skills, and the *design* skills that
>I learned were really helpful


ADT is a methodology with rules and procedures to analyze and present
high level, abstract definition of enterprises which are supported by
systems.  It is used by DOD in its Integrated Computer Aided Manufacturing
(ICAM) process to represent system development capabilities of vendors
and configuration control and management abilities. Yourdon is a systems
development methodology with diferent and more rigororous rules with the
goal of building a system.  The goal of SADT is to gain an understanding
of an enterprise and document it.  It will break down in doing detail design.
All of this is arguable.  Most system design methods are extensions of Yourdon
not SADT.  Yourdon rules and procedures constrain thinking around high level
definition of an enterprise.  Read 'Diagramming Techniques for Analysts and
Programmers' by Martin and McClure, Prentice-Hall. There are others.

Bill McGrath