Prototypes: Difference between revisions
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
There is almost always a gap between what the client wants and what the designer THINKS the client wants. Prototypes help narrow the gap effeciently. | There is almost always a gap between what the client wants and what the designer THINKS the client wants. Prototypes help narrow the gap effeciently. | ||
Revision as of 07:19, 8 January 2023
System Fundamentals[1]
A prototype is an early model of a product built to test a concept or process or to act as a thing to be replicated or learned from.
Prototypes are simplified versions of a system that are used to test and refine the requirements. They can be used to demonstrate the proposed system to the client in order to get feedback on the design and functionality of the system.
There are several benefits to using prototypes to demonstrate the proposed system to the client:
- Prototypes allow the client to see and interact with a rough version of the system, which can help them better understand how the system will work.
- Prototypes allow the client to provide feedback on the design and functionality of the system, which can help the development team make necessary changes before the final version of the system is built.
- Prototypes can help the client visualize the final product and understand how it will fit into their business or organization.
- Prototypes can help reduce risk by allowing the client to identify and address any issues or concerns before the final version of the system is built.
Real-world practical advice[edit]
There is almost always a gap between what the client wants and what the designer THINKS the client wants. Prototypes help narrow the gap effeciently.
Standards[edit]
- Describe the purpose of prototypes to demonstrate the proposed system to the client.