From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=0.0 required=3.0 tests=BAYES_20,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.5-pre1 Date: 13 Nov 92 16:03:08 GMT From: cis.ohio-state.edu!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!qt.cs. utexas.edu!news.Brown.EDU!noc.near.net!inmet!ryer@ucbvax.Berkeley.EDU (Mike Ry er) Subject: Re: SA/SD Documentation of an OBD Design Message-ID: <1992Nov13.160308.9974@inmet.camb.inmet.com> List-Id: 943 at Northrup asks: How do you document an OOD design using SA/SD? Here are some suggestions: 1. Once you've got it fully coded, use an automatic flowcharting tool to generate a few hundred pounds of paper. I'll testify that it looks like SA/SD to me. 2. Take the SA/SD documentation from your last (not necessarily related) project, and attach the OOD documentation for this project as an appendix. Put in a colored separator page. No one will know the difference. 3. Buy an expensive CASE tool with re-engineering capability, and assign some people (not your friends) to convert the design. After a few years, report to managment that you need another million dollars (or they can settle for the OOD stuff instead). 4. Write an introduction that says you analyzed and decomposed the design into one component, using SA/SD, and then provide a copy of the OOD as added-value backup information about the fine-grained detail of that component. Hope that helps. Mike "speaking only for myself" Ryer