Path: utzoo!attcan!uunet!bu.edu!snorkelwacker!apple!bionet!hayes.ims.alaska.edu!acad3.fai.alaska.edu!ftdkl
From: ftdkl@acad3.fai.alaska.edu (LaSota Daniel K)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Diagramming Technique for HyperCard?
Message-ID: <1990Oct15.175207.13847@hayes.ims.alaska.edu>
Date: 15 Oct 90 17:52:07 GMT
References: <6430@bgsuvax.UUCP>
Sender: usenet@hayes.ims.alaska.edu (J Random USENET)
Reply-To: ftdkl@acad3.fai.alaska.edu
Organization: University of Alaska Fairbanks
Lines: 16
News-Software: VAX/VMS VNEWS 1.3-4
Nntp-Posting-Host: acad3.fai.alaska.edu

In article <6430@bgsuvax.UUCP>, maner@bgsuvax.UUCP (Walter Maner) writes...
>Of all the various diagramming techniques available to software developers,
>which is most appropriate for use in HyperCard stack design?  Flow charts?
>Structure charts?  Object-oriented structure charts?
> 
>WALT
Walt,
Check out the
"Stack Design Guidelines" from Apple published through Addison Wesley.
It was put out with 1.x.x in mind but it very much good and general enough so
that it will still be good for 2.0.  (There will probably be a new release any
way).  It talks about how to design a stack from forming a theme all the way
through to distributing your stack. 

Dan LaSota
ftdkl@acad3.fai.alaska.edu