------art_15284_33522464.1206859374772
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

>
> Yes ... as you state below, if a project is defined by requirements,
> performance requirements should be specified. They fall under the
> general heading of usability, and there are (and have been for decades)
> rather well known rules of thumb.
>

Are you saying that there are projects that have no requirements? :) I'm
sure that you don't mean that, so please elaborate.


>
> > but if you're making a digital calculator
> > that will run on a quad core server with at most 10 people using it at
> one
> > time, I'd hardly recommend performance as a major concern, and would
> rather
> > just fulfill the requirements as fast and economically possible.
>
> This seldom happens in the real world. Nobody can create a significant
> software project in total absence of any feedback from users or the
> market.
>

Agreed, but please take the example in the context it was presented, and
that was that performance is nothing more than just "A" requirement. There
are times, when it pays to consider it, other times, you just waste your
time and money after something that won't even be apparent. Hence no value
for time spent.

------art_15284_33522464.1206859374772--