From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: 11cae8,b87849933931bc93 X-Google-Attributes: gid11cae8,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public From: Roger Vossler Subject: Re: What is wrong with OO ? Date: 1996/12/06 Message-ID: <32A885CF.5530@csn.net>#1/1 X-Deja-AN: 202742114 references: <32A4659D.347A@shef.ac.uk> <32a5ceba.81462731@news.nstn.ca> content-type: text/plain; charset=us-ascii organization: Vivien Group mime-version: 1.0 reply-to: vossler@csn.net newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.lnag.java,comp.object,comp.software-eng x-mailer: Mozilla 3.0 (Macintosh; I; PPC) Date: 1996-12-06T00:00:00+00:00 List-Id: Tom Bushell wrote: > It is my growing opinion that this is a fundamental problem with all > "formal" design methods, not just OO design. The effort involved in > doing the design is as great or greater than doing the construction > I'm starting to believe that design and code don't make sense as > separate entities - the design should _become_ the code - the design > documents for an implemented system are used as the foundation of the > code, and then regenerated from the code. Major benefits would be > If anyone has knows of tools that would facilitate this approach, I'd > certainly be interested. I've done some very simple prototypes, and > hope to work on the idea in future (when I have more time - Hah!). IMHO, this is more of problem with large CASE tools or design systems than it is with design per say. As I understand it from the OO wizards, start with a small number of use-cases in order to understand the problem, and if you go OO subsequently, then do some CRC card modeling. Thus, all you need for a start is a stack of 3x5 index cards, pencil, paper, and a couple of good books. Peter Coad has a lot of good things to say about this. Then, when you understand what you are doing, commmit to the CASE swamp of your choice. The problem is that people first buy a killer tool chest and spend large numbers of hour understanding how to use the beast and even more hours stuffing a data base only to discover thay they have created a big mess. Cheers, Roger Vossler (vossler@csn.net)