home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.object:4221 comp.lang.ada:3268 comp.software-eng:4268
- Path: sparky!uunet!usc!rpi!newsserver.pixel.kodak.com!laidbak!tellab5!mcdchg!ast!ast.dsd.northrop.com!dvorak
- From: dvorak@ast.dsd.northrop.com (dvorak joseph l.)
- Newsgroups: comp.object,comp.lang.ada,comp.software-eng
- Subject: SA/SD Documentation of an OBD Design
- Message-ID: <943@ast.dsd.northrop.com>
- Date: 12 Nov 92 14:20:05 GMT
- Sender: dvorak@ast.dsd.northrop.com
- Distribution: usa
- Organization: Northrop Corp - ESD, Rolling Meadows, IL
- Lines: 24
-
-
- We are completing an object based *redesign* of an existing medium
- sized application (~300K LOC).
-
- We have been using a modified Booch approach in the redesign
- and have employed abstraction and encapsulation (but not
- inheritance or dynamic binding since we are using Ada).
- All of the people involved in the object based redesign believe
- that this is a much better design than the SA/SA design that exists.
-
- Now management has decided that we must document the object
- based design using SA/SD. They want to se dataflows and possibly
- structure charts. We are unsure about how to do this since
- the design truly reflects the object model. In addition,
- this is the first time we have faced this situation since all
- of our past OBD and OOD projects were documented in an OOD
- form.
-
- We are looking for suggestions and opinions on the wisdom of
- this approach. Any help would be appreciated. Thanks in
- advance.
-
- Joe Dvorak
- dvorak@sunfs1.dsd.northrop.com
-