Xref: utzoo comp.software-eng:2918 comp.graphics:10068
Path: utzoo!attcan!uunet!husc6!encore!pinocchio.encore.com
From: jkenton@pinocchio.encore.com (Jeff Kenton)
Newsgroups: comp.software-eng,comp.lang.visual,comp.graphics
Subject: Re: visual languages
Message-ID: <11202@encore.Encore.COM>
Date: 22 Feb 90 13:59:07 GMT
References: <98229@linus.UUCP>
Sender: news@Encore.COM
Followup-To: comp.software-eng
Lines: 29

From article <98229@linus.UUCP>, by munck@chance.uucp (Robert Munck):
> 
> SADT is far and away the best visual language for requirements analysis
> and similar forms of modeling.  It is also known as Structured Analysis
> and Design Technique, IDEF-0, and "State, Activity, Data, Transition".
> The best published description is "SADT" by Marca and McGowan,
> McGraw-Hill, 1988.
> 
> The graphic language is a "constraint diagram," basically a
> generalization of data flow, flowchart, state-transition, etc.  It is,
> essentially, a more powerful structuring mechanism for natural language,
> a kind of structured hypertext. . . .  
> 
> SADT is, in my opinion, unique in putting major emphasis on how groups
> of people work together well.

Does anyone else have any experience with this? About 8 years ago I was
part of a startup which had a person who had been at Softech.  He tried
to promote SADT, but wound up creating friction and blocking progress in
many imaginative ways.  He left after 9 months without having written a
single line of code, and a demo scheduled for the board of directors in
two weeks.

Was it him, or us, or SADT?


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      jeff kenton  ---	temporarily at jkenton@pinocchio.encore.com	 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -