In many industries, in order to express and quickly verify the feasibility of a project, manufacturers often produce different prototypes to determine whether the idea is risky or not.
There are many ways to build prototypes. In addition to code, prototypes can be made on notes, index cards, clay, etc. For example, for the design and development of a new type of car, the car model can be built through cork and cloth tape, or the car prototype can be modeled in a virtual environment.
When do you need a prototype?
Any unproven, experimental, dubious, previously untried feature that is critical to the final system needs a prototype.
Examples: architecture, new features in existing systems, third-party tools or components, performance issues, user interface design, etc. By building prototypes, you can discover the risks of this new thing in time. In fact, prototyping is a learning experience, and the value is not in the code produced, but in the lessons learned.
How to use prototyping?
In short, ignore the details. The following details should be ignored in prototyping:
Accuracy of 1.
The data in the prototype can be replaced with other data, without having to be completely correct and necessary.
2. Integrity
The prototype only needs to satisfy a limited number of functions, and will not be fully functional. For different functions, different prototypes can be made for verification.
3. The robustness
There is no need for rigorous inspection of the prototype. If the logic is right, it doesn’t matter if the prototype is a shoddy project.
4. The format
Although there is a lot of documentation that comes out of prototype validation, there is not much comment and documentation required during prototyping.
Don’t use prototypes for products
Before you start working on a prototype, it’s important to note that a prototype is not complete and will never be complete. Prototypes help identify potential problems early in the project and correct them. But because the prototype is not correct, the prototype can not be applied to real product development.
After all, some people build a prototype of a new car out of cork and duct tape, but not on the road.
In short, prototyping can save a lot of communication costs, time costs, and resources when developing a product, as well as laying the groundwork for subsequent tracer development. To use the prototype well, it needs to be explored step by step in practice.
More wonderful video sharing: www.zentao.net/page/colleg…