So true.

Just add a little bit, sort of coming in sideways. During last half year, I ran into the same issue several times. The issues are with the requirements. According to the procedure we have, once the requirements is documented, we don't go back to it until the user acceptance testing. When we do unit testing, we test against program spec, not the requirements; when we do system testing, we test against the design, not the requirements. There were several times, we got bad requirements, then there come the "good" design based on the "bad" requirements, as well as the "good" program spec based on the "good" design (that is based on the bad requirements). Then you do coding and unit testing, which go well, as everything meets the spec. System testing is also fine, as everything meets the design.

All those effort are wasted... when it comes to user testing, user don't really test against what is documented, they test against their interpretation of the requirements (or to be more precise: the document didn't really express the true user requirements. When the IT side and the user side agreed upon the document, they thought that they understood the words in the same way, but they didn't.)

Human communication... the single problem that we can never get rid of...

In reply to Re: Dealing with the QA guy ... (no, really) by pg
in thread Dealing with the QA guy ... (no, really) by Tanktalus

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.