Prototyping - The way to go for software development projects.
Prototyping is an alternative to the traditional method of software development. The project proceeds in a re-iterative cycle until a satisfactory
result is reached. Prototype versions of the system are delivered from time to time. Feedback is obtained. Corrections and changes are made to bring
the system into line with your requirements, and the new version issued.
Here's a comparison for you to consider:
| | Traditional | Prototyping |
|---|
| Cost of requirement definition | 23% of project cost (varies) | 2% of project cost or less |
|
Relationship between developers and your staff | Adversarial | Co-operative |
|
During project | Developers disappear and come back with finished product (set in concrete) | Finished product evolves with your participation |
|
After project | Little option but to accept their terms | Ordinary hourly rate charged |
|
Training | Training course comes complete with high price tag and strident tutor who doesn't really know how you do things | Staff who have been working on the project are available at ordinary hourly rate; no course fee charged. |
|
Typical outcome | Failure (unsatisfactory or unusable system, aborted project) | Success |
|
Cost | Normally much more than you expected | Normally a little more than you expected, because of things you didn't initially consider. |