A software prototype is partially implemented by the proposed new product. There are three main purposes using prototypes: • Clear and improve the demand prototype as a demand tool, which is initially implemented part of the system. User's evaluation of prototypes can point out many of the needs in need, and can solve these problems before you develop real products. • Exploring the design selection prototype as a design tool, uses it to explore different user interface technologies to achieve best availability, and evaluate possible technical solutions. • Developed as a final product prototype as a construction tool, is the complete functional implementation of the product initial subset, through a series of small-scale development cycles, you can complete the development of the entire product. The main reason for establishing prototype is to solve the problem of uncertainty in the early stage of product development. Use these uncertainties to determine which part of the system needs to create prototypes and want to get anything from the user to the prototype. The prototype is also a good method for discovering and resolving the demand. Erons and inconspreas make developers confused the developed products, establishing a prototype helps to explain and correct these uncertainty. User, manager and other non-technical project risk bearers have found that the prototype can make their imagination more specific when determining and developing products. Prototype is more readily understood than developers commonly used techniques.
