paradigm is also problematic for the following reasons:
1 The customer gets what appears to be a working version of the software, aware that the prototype took place, and "the gum and baling wire," not knowing the rush to get it working no one considers the overall quality of the software or the long-term sustainability.
Once you know that the product should be rebuilt to a high standard of quality maintenance, customer cry poor and say that "some fixes" applied to a working prototype products. Too often, software development management relents.
2. The developer often makes implementation compromises to develop a prototype quickly find a job. The right operating system or programming language can only be used as it is available and known to an inefficient algorithm can be implemented to demonstrate the ability. After a while, the developer can get accustomed to the elections and forget the reason why they should have been appropriate. The less than ideal solution, is now an important part of the system. Although problems may occur, can 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 built on a mechanism for defining requirements. Subsequently discarded (at least in part), and the actual software is designed for quality and sustainability..
1 The customer gets what appears to be a working version of the software, aware that the prototype took place, and "the gum and baling wire," not knowing the rush to get it working no one considers the overall quality of the software or the long-term sustainability.
Once you know that the product should be rebuilt to a high standard of quality maintenance, customer cry poor and say that "some fixes" applied to a working prototype products. Too often, software development management relents.
2. The developer often makes implementation compromises to develop a prototype quickly find a job. The right operating system or programming language can only be used as it is available and known to an inefficient algorithm can be implemented to demonstrate the ability. After a while, the developer can get accustomed to the elections and forget the reason why they should have been appropriate. The less than ideal solution, is now an important part of the system. Although problems may occur, can 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 built on a mechanism for defining requirements. Subsequently discarded (at least in part), and the actual software is designed for quality and sustainability..
No comments:
Post a Comment