The advantages of the rapid prototyping approach are as follows:
1) The method can achieve very quickly know the user feedback information to facilitate the user and the developer of the exchange, so as to dynamically improve the needs of analysis and system design, with the prototype to inspire, reveal and clear the needs of users.
2) Although the method can very quickly know the user feedback information, but more emphasis on user participation, the prototype can activate the user and the developer’s thinking in order to quickly test new ideas, new technology, is conducive to evaluation, improve the development program, effective To use resources.
3) This approach not only reduces the risk of software development, but also helps improve software quality and software productivity.
4) if the product gradually development, maintenance, expansion, then you think which is convenient? Of course, choose a rapid prototype development method.
Rapid prototyping methods mainly have the following problems:
1) prototype development is difficult to manage, can not prepare all the information, resulting in the existence of quality risks.
2) it is difficult to determine the prototype, the prototype target deviation from too much, it will lead to system failure.
3) more strenuous is to put all the subsystems of the form of integration into the entire information system.
4) due to repeated times, resulting in the user lost the patience of the beginning, in the impatient circumstances to choose a defective prototype as the final system.
It is worth noting that archetypal and waterfall methods are complementary to the design of the design process, but the prototype and waterfall methods are not mutually exclusive, in the process of developing prototypes and improving prototypes Do not exclude the phased implementation of demand analysis, system design, coding testing. In addition, taking into account the quality problems that may arise from prototyping, the prototype method is applied only to the demand phase of waterfall development. Once the requirements are defined, the prototype is discarded and the system is developed according to the waterfall development method, , But the waterfall development needs of the problem is not complete to solve. This method is often used in systems with high quality requirements.