Software
by toks02 Accepted solution
by tony hopkinson Accepted solution
A prototype is meant to help investigate an aspect of a design. Aside from the extremely trivial, there are no devlopments that wouldn't benefit from an investigation of the unknowns.
The biggest danger with going down this route is the prototype becomes the application, and what you found out from doing it is never applied.
Never make a fully functional one.
When engineers want to look at the the aerodynamics of a body shape they build it out of wood, when they prototype an engine they stick it on a bench.
Only in software do we blow most of the budget making a prototype and then end up selling it so we can delay doing the job properly.
The difficulty is all in the design infrastructure. How much front end work do you need to test a prototype backend for instance.
Slap your tutor round the head, for giving you a crap question.
This discussion is closed to new replies.
Sort by Trending