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.9 required=3.0 tests=BAYES_00,FROM_ADDR_WS autolearn=no autolearn_force=no version=3.4.5-pre1 Date: 15 Nov 92 22:20:40 GMT From: agate!linus!linus.mitre.org!linus!sdl@ames.arc.nasa.gov (Steven D. Litvi ntchouk) Subject: Re: SA/SD Documentation of an OBD Design Message-ID: List-Id: In article <943@ast.dsd.northrop.com> dvorak@ast.dsd.northrop.com (dvorak josep h l.) writes: > Now management has decided that we must document the object > based design using SA/SD. Why? > They want to se dataflows and possibly > structure charts. I would suggest finding out exactly what *problem* management is trying to solve with this "solution". Perhaps there is a way to meet their concerns and solve their problem with some part of your (existing) OBD or OOD approach? Remind them: "Before you propose a solution, be sure you understand what the *problem* is you are trying to solve." Steven Litvintchouk MITRE Corporation 202 Burlington Road Bedford, MA 01730 Fone: (617)271-7753 ARPA: sdl@mitre.org UUCP: linus!sdl "Where does he get those wonderful toys?" -- Steven Litvintchouk MITRE Corporation 202 Burlington Road Bedford, MA 01730 Fone: (617)271-7753 ARPA: sdl@mitre.org UUCP: linus!sdl "Where does he get those wonderful toys?"