Use the key users, tasks, and system requirements generated in the previous project phase as support for your prototype design. Remember a prototype is used to illustrated how your system would appear to the customer. You should be creating several (at least 2) low-fidelity prototypes e.g., paper sketches, storyboards, or physical mockups. You should also be thinking about what mental model the system will portray to its customers. These prototypes do not have to be advanced or technically correct but they must represent the application in as complete manner as possible. For example, they should contain the core screens that illustrate how the system will work as a whole, including (perhaps) a sample interaction based upon some of the key tasks.
Use the key users, tasks, and system requirements generated in the previous project phase as support for your prototype design. Remember a prototype is used to illustrated how your system would appear to the customer. You should be creating several (at least 2) low-fidelity prototypes e.g., paper sketches, storyboards, or physical mockups. You should also be thinking about what mental model the system will portray to its customers. These prototypes do not have to be advanced or technically correct but they must represent the application in as complete manner as possible. For example, they should contain the core screens that illustrate how the system will work as a whole, including (perhaps) a sample interaction based upon some of the key tasks.
Step by step
Solved in 2 steps