Ø Used to reduce requirements risk
Ø The prototype is developed from an initial specification, delivered for
experiment then discarded
Ø The throw-away prototype should not be considered as a final system
o Some system characteristics may have been left out
o There is no specification for long-term maintenance
o The system will be poorly structured and difficult to maintain
o Existing management processes assume a waterfall model of development
o Specialist skills are required which may not be available in all
development teams
Ø Maintenance problems
o Continual change tends to corrupt system structure so long-term
maintenance is expensive
Contractual
problems
Ø Developers may be pressured to deliver a throw-away prototype as a final
system
Ø This is not recommended
o It may be impossible to tune the prototype to meet non-functional
requirements
o The prototype is inevitably undocumented
o The system structure will be degraded through changes made during
development
o Normal organisational quality standards may not have been applied
No comments:
Post a Comment