Path: utzoo!attcan!uunet!wuarchive!mit-eddie!uw-beaver!sumax!halcyon!happym!nwnexus!kelpie
From: kelpie@nwnexus.WA.COM (Anthony C. Garland)
Newsgroups: comp.object
Subject: Re: Mixing Structured Design and OOD
Message-ID: <402@nwnexus.WA.COM>
Date: 15 Oct 90 03:21:50 GMT
References: <CIMSHOP!DAVIDM.90Oct11105657@uunet.UU.NET>
Distribution: comp
Organization: Northwest Nexus Inc.; Seattle, WA
Lines: 25

cimshop!davidm@uunet.UU.NET (David S. Masterson) writes:

>Does anyone have a good methodology for using a CASE tool that's oriented
>toward structured design in the process of developing object-oriented programs
>(for instance, in C++)? 

    Although I have yet to take this approach myself, after having pondered the
    same question, I had considered taking the following tack:

	o  Use a Entity-Relationship Diagram (ERD) editor to describe
	   attributes of each class.
	o  Use a State Transition Diagram (STD) editor to describe the
	   states that each object moves through.
	o  Use a Dataflow Diagram editor (DFD) to describe/design the methods
	   which operate upon an object/class.

    With this approach, each class is described by a triad of diagrams based
    upon structured design techniques.  Probably not optimum, but seems like a
    reasonable approach.

o-----------------------------------------------------------------------------o
| Anthony C. Garland, P.E.                                 Garland Consulting |
| 1373 S. Bonanza Alley,                                       (206) 387-6390 |
| Camano Island, WA 98292                               kelpie@nwnexus.WA.COM |
o-----------------------------------------------------------------------------o