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: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public From: alt@rumba.iinet.net.au (Harry Protoolis) Subject: Re: What is wrong with OO ? Date: 1996/12/13 Message-ID: #1/1 X-Deja-AN: 203842272 references: <58l3d4$12r@news3.digex.net> organization: alt.computer pty ltd reply-to: harry@alt.net.au newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.object,comp.software-eng Date: 1996-12-13T00:00:00+00:00 List-Id: On 11 Dec 1996 01:39:48 GMT, Ell wrote: >Harry Protoolis (harry@matilda.alt.net.au) wrote: >: Robert C. Martin wrote: >: > >: >However, I also prefer to >: >begin producing the architecture well before all the analysis is complete. >: >And I prefer producing code that is conformant to the architecture - and the >: >analysis - long before the architecture is complete. >: >... >: >It's just that I don't wait for *all* the analysis to be completed before >: >I begin on designing the architecture. And I don't wait for the complete >: >architecture before I begin on the code. > >: Sure, but I tend to do a overall sketch to give me a big picture before >: diving in to the detail at any point. I find this helps to size the >: problem up. > >I think the word "overall" is key here vs. what is said immediately above >it. Overall meaning, as I see it, at least covering all points percieved >to be major. In my and others experience, no "new" application production >coding should go on before having done overall application analysis and >architecture. This helps to avoid unnecessary re-work among other >benefits. Sure, as long as you don't get too bogged down in it. There is a very real danger that if you spend too long doing 'overall' architecture you wind up with pipe dreams. My rule-of-thumb is that overall architecure should consist of a small (say < 10) number of fairly simple diagrams. You should be able to get it across to the project team in a single ~ 1 hour presentation. Harry