paradigm is also problematic for the following reasons in the model of prototyping: paradigm is also problematic for the following reasons:

 1 The customer gets what appears to be a working version of the software, aware of the fact that the prototype took place, and "the wire Rubber and bales, "not knowing the race to make it work does not consider the overall quality of the software and the long-term sustainability. Once you know that the product should be rebuilt to a high standard of service quality, customer cry poor and say that "some corrections" applied to a product prototype. Too often, grants management software development. 2. The developer often makes implementation compromises to develop a prototype to quickly find a job. The right operating system or programming language can only be used in what is available and known to be an inefficient algorithm can be implemented to demonstrate the ability. After a while ', the developer can get used to the elections and forget why they would have to be adjusted. The less than ideal solution, is now an important part of the system. Although problems may occur, may be an effective prototyping software development paradigm. The key is to change the rules of the game to begin with, it is the customer and developer must both agree that the prototype is based on a mechanism for defining requirements. then discarded (at least in part), and the actual software and is designed just for the quality and sustainability ..