The objective of evolutionary prototyping is
to deliver a working system to end-users
The development starts with those
requirements which are best understood.
The objective of throw-away prototyping is
to validate or derive the system
The prototyping process starts with those
requirements which are poorly understood
Outline of the prototyping process
1. Identify basic requirements
Determine basic requirements including the input and
output information desired. Details, such as security, can
typically be ignored.
2. Develop Initial Prototype
The initial prototype is developed that includes only user
The customers, including end-users, examine the
prototype and provide feedback on additions or changes.
4. Revise and Enhance the Prototype
Using the feedback both the specifications and the
prototype can be improved. Negotiation about what is
within the scope of the contract/product may be
If changes are introduced then a repeat of steps #3 and
#4 may be needed.
Reduces development time.
Reduces development costs.
Requires user involvement.
Developers receive quantifiable user feedback.
Facilitates system implementation since users know
what to expect.
Results in higher user satisfaction.
Exposes developers to potential future system
This method can be used to avoid documenting the
requirements of the system.
Management is required
Long term maintenance can be expensive
Uncertain design idea’s
Information can be lost through so many improvement