I noticed that there were very few mentions and little
elaboration on output/reports. Is this not a consideration
with this project? Almost all of the larger projects I've
worked on have core requirements in this area (whether in
written or electronic form).
In the few instances where I've made design mistakes, they
usually stemmed from the fact that I failed to examine the
required output/reports closely enough or made wrong
assumptions (though usually valid) based on experience.
Recently I was given an example (publication) to work from
and found out later in development that they had changed
their example substantially without telling me. Thus the
need for constant design/programmer/customer feedback
throughout the life cycle of the project.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||