1. Do a comprehensive, all-inclusive system design document first.
  2. Implement part of it.
  3. Show the result to the users/client.
  4. Find out what they said they need/want is not what they need/want.
  5. Scratch the comprehensive, all-inclusive system design document.
  6. Do a second comprehensive, all-inclusive system design document.
  7. Implement part of it.
  8. ...

One of the fundamental rules of software development is that the clients never ever know what they want and the more detailed your plan is, the more you'll have to change it.

Jenda
Enoch was right!
Enjoy the last years of Rome.

In reply to Re^2: I want to know the problems in Perl by Jenda
in thread I want to know the problems in Perl by maheshgupta024

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.