*Prototype model:
| Characteristic | Strengths | Weaknesses | Applicability |
| * A prototype (early estimation of final software product) is built for user to test by trying them out, as oppose from user just interpreting the design based from description. *The prototype will be rebuilt again for improvement based on user feedback. *This process will be done several times until an acceptable prototype is achieved to produce complete software product. | * Can ensure that the developer, user and customer have a common understanding of what is needed and what is proposed. * Can be used by users to describe and proved requirements that developers have not considered. * Prevents misunderstanding between developer, user and customer that might occur particularly in the requirement analysis phase. | *The focus on a limited prototype can distract developers from properly analyzing the complete project. * Developers have the tendency to build complicated prototype (that in the end they have to throw it away) and thus results in lengthy development time. *Using prototype model is very costly because developers need to build many prototypes before right prototype is attained. | * When the requirements are unclear. *Most beneficial to system that will have many interaction with users. * Especially good for designing human-computer interfaces. |
No comments:
Post a Comment