Planning from the start involves having a good spec. Demanding this is a case of making life easy for the developer at the cost of making it impossible for the customer. Thereby giving both sides plenty to complain about.

People typically are unable to envision the consequences of the spec they hand you without the feedback of seeing how it would work. With a rigid product cycle this leads to the classic conflict where the developers complain that the spec is incomplete and changing, and the clients complain that the developers do not understand what they want and are unresponsive to their needs. And they are both right. The spec is changing and that is a real problem for the developers. But human and fallible clients are unable to give you a decent spec 18 months out, things change!

Various incremental design techniques exist that try to get a rapid feedback cycle. A little more is specified, a little more is developed. Clients try it out and can figure out what they want added. Developers aim to have a design that can be readjusted and refactored.

This strategy is emphatically not a question of not taking time out to plan the project. Rather it is a question of intentionally using design strategies that have evolved to avoid the classic problems that come with more rigid strategies.

And yes, I have seen this kind of thinking applied (OK applied slightly hapazardly) to reasonably complex CGI projects that were based on a backend that deliberately had a lot of OO in it. (Well it didn't up front, but after a few iterations it did. :-)

In reply to Re (tilly) 3: UML for PERL? by tilly
in thread UML for PERL? by gregor42

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.