Prototype Testing:
Developers build a prototype during the requirements phase
Prototype is evaluated by end users
Users give corrective feedback
Developers further refine the prototype
When the user is satisfied, the prototype code is brought up to the standards needed for a final Product.
Prototype Steps:
A preliminary project plan is developed
An partial high-level paper model is created
The model is source for a partial requirements specification
A prototype is built with basic and critical attributes
The designer builds the database,User Interface,algorithmic functions
The designer demonstrates the prototype, the user evaluates for problems and suggests improvements.
This loop continues until the user is satisfied
Prototyping Weaknesses:
Tendency to abandon structured program development for “code-and-fix” development
Bad reputation for “quick-and-dirty” methods
Overall maintainability may be overlooked
The customer may want the prototype delivered.
Process may continue forever (scope creep)
When to use Prototype Model:
Requirements are unstable or have to be clarified
As the requirements clarification stage of a Waterfall model
Develop user interfaces
Short-lived demonstrations
New, original development
With the analysis and design portions of object- oriented development.
No comments:
Post a Comment