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.
--Jim
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
