Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!pacbell.com!pacbell!att!dptg!mtunq!psrc
From: psrc@mtunq.ATT.COM (Paul S. R. Chisholm)
Newsgroups: comp.software-eng
Subject: Re: Amount of Design Documentation
Summary: *form* of design documentation? prose???
Message-ID: <1207@mtunq.ATT.COM>
Date: 5 Aug 90 15:42:42 GMT
References: <Eail8ur0BwwAEiGEo8@transarc.com>
Organization: AT&T Bell Laboratories
Lines: 11

There's an implicit assumption here:  that design documentation is done
in English (or Japanese, or whatever) prose.  To what extent have
people had good luck with other forms, e.g., data flow diagrams, data
dictionaries, structure charts, as documentation?  (By "success", I
mean both "success in creating or generating such documentation", and
"doing anything with such documentation when maintenance time comes
along, and keeping such documentation up-to-date".)

Paul S. R. Chisholm, AT&T Bell Laboratories
att!mtunq!psrc, psrc@mtunq.att.com, AT&T Mail !psrchisholm
I'm not speaking for the company, I'm just speaking my mind.