> Ok, but what is the point ? The use of low fidelity prototypes is a
> very valuable tool in the requirements phase, but the point is
> precisely to get rid of any software tools and use mainly pencil and
> paper, so that several prototypes can be build at no cost in iterative
> evaluation cycles. I do not see any benefit in using such a software
> tool (presumably with a gui builder) in this phase.
While I agree that index cards and board markers are maybe best in
design, I can follow the logic of that LnF author. There is more to
shipping working software than what you can find in research papers and
academic discussions.
If you have to hand out half-finished software, e.g. if you do a series
of early deliveries to QA, alpha and beta testers and the gold owners,
and if you want to indicate that the GUI implementation (not the design)
and/or the application logic isn't finished, then this LnF is a clear
statement.
I have been in the situation myself a few times, were people thought the
application was done at the very moment the main window popped up the
first time. I wouldn't have used this LnF, because the statement is IMHO
a little bit to strong, but I thing his idea is good.
/Thomas