For a project of that size and complexity, I'd strongly recommend that you write a throwaway prototype before you do any detailed, intense design work. By all means write an overview before your prototype... but keep in mind that you probably don't know enough about the problem to do a detailed requirements plan or interface specification until you've tried it at least once, in real code. (If you, or other people on your team, have written data warehouse/data mining systems before, all bets are off.)

I'm a big fan of learning by doing: write little throwaway prototypes for each feature as you go. They don't have to be complete, or easy to use, or fast... their purpose is to give you some idea of what a solution looks like, so that you can refine it for your finished product. If you keep the parts separate and the interfaces between them clean, you can refine incrementally as you go with minimal pain, and you'll probably end up keeping some prototype code, but "plan to throw one away; you will, anyhow".

It just so happens that Perl makes an excellent prototyping language.

--
F o x t r o t U n i f o r m
Found a typo in this node? /msg me
The hell with paco, vote for Erudil!

In reply to Re: Design Documents? by FoxtrotUniform
in thread Design Documents? by Anonymous Monk

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.