Re: OOA, OOD, design all first, how to go about it all?

From: Joseph Jolic (jjolic_at_bigpond.net.au)
Date: 04/25/04

  • Next message: Universe: "Re: Aggregation vs composition" 
    Date: Sun, 25 Apr 2004 09:44:44 GMT

    This gells with me as well. there needs to be some sort of design to have
    direction, and then the iteration. Other techniques are probably more
    specialized and not what i really want to start now.

    "AndyW" <foo_@bar_no_email.com> wrote in message
    news:6gkm80lvtj1vgomijp0sq715icdnll8qdk@4ax.com...
    > I believe that the general principle of software development has
    > always been to do some level of analysis and a modicum of design at
    > the higher level. At least enough so that you understand the problem,
    > enough to know what ballpark you are in and to understand what game
    > you are actually playing. You may even chose to do a small amount of
    > development to test that you understand the rules of the game.
    >
    > Once you have achieved the goals of knowing the problem, having a
    > tentative idea of the solution and understanding that your approach
    > will at least work, then you can go down and use any technique you
    > like. Whether it be a big bang software approach or small iterations
    > it really doesnt matter.
    >
    > The main thing is to understand that you do need to reduce risk during
    > the main development phase. Ideal ways to do this are to communicate
    > with all parties often, dont do too much at a time, and prove that
    > what you have is always at a working state.
    >
    > These principles have been around before the age of software
    > development and are nothing new.
    >
    > The agile (or hack methods as I call them) seem to all be targeted at
    > the small $10 projects or at least, try to convert the large scale
    > systems into a collection of $10 projects. While they do often
    > attempt to solve many of the problems during the main software cycle,
    > I have often observed that people are quite often in the wrong ball
    > park in the first place.
    >
    > Getting in the wrong ballpark and/or playing the wrong game is the
    > general problem that has always dogged software development. There is
    > no magical hack method that will ever solve this for you. But I can
    > say that if you really do understand the problem and have a solid idea
    > that your solution will work, then it is highly likely that you will
    > succeed so long as you keep the risk to a minimum.
    >
    > Andy

  • Next message: Universe: "Re: Aggregation vs composition"

    Relevant Pages

    • Re:Urgent requirement for Java developers.
      ... Identifies key business and technology drivers that impact application ... and application design, coding and design standards, best practices, ... application of techniques and standards such as service-oriented ... Expert level on Java J2EEdevelopment knowledge (5+ years on J2EE ...
      (comp.lang.java.beans)
    • Re: XP Requirement Analysis?
      ... IMHO it would be a shame if change request forms were necessary. ... These design sessions occur at the ... start of the iteration and throughout it as well. ... Certainly unit tests are readable by the domain experts. ...
      (comp.object)
    • Sr. Java Architect Needed
      ... Performs design, development and maintenance of highly complex ... Researches problems, discovered by QA or product support, and develops ... Determines what tools and techniques we will utilize to meet the ... -Expert analytical and design skills at ...
      (comp.lang.java)
    • Re: Graphic designers creating with Word
      ... A Word file does not contain the concept of a "page". ... And stop listening to people who say Word can't do page design. ... it's not helpful :-) Neither can inDesign. ... programs, so if you use the techniques from inDesign or Quark, everything ...
      (microsoft.public.mac.office.word)
    • Re: OOA?
      ... I don't think they are design choices. ... "One of the most crucial steps in software engineering is to model the ... The most frequently used diagrammatic techniques are ... diagrams, Entity-Relationship Diagrams, Object Diagrams, and ...
      (comp.object)