in reply to OO Design Reference?

*giggle* The following i actually learned after sifting through the pages of IBM's OO Rexx manual:

Simple design strategy: construct multiple sentences concerning the actions of the program: for example, The customer inserts an item into his shopping cart. In this case, you can variably choose nouns to represent some objects- "customer" and "shopping cart" and "item" (product). Verbs will be the functions- ShoppingCart.insert(Item); Try this a few times to get the hang out it. Why not try sifting through one of the thousands of complete shopping apps and trying to perhaps redo it with OO design for practice.

AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.

Replies are listed 'Best First'.
Re: Re: OO Design Reference?
by PsychoSpunk (Hermit) on Dec 08, 2000 at 00:38 UTC
    I've seen the sentence metaphor used a whole lot in OO introductions. I think it's a pretty good one, but then you have to get into the whole sentence composition rules, such as what's the subject and the object (pardon the pun) of the sentence? Don't forget that if you go creating objects willy-nilly from all of the nouns in the sentence, you'll end up with more objects than you need (unless you're programming in Java or Smalltalk, in which case, you can't do anything but objects).

    ALL HAIL BRAK!!!