The Word template can be bought through a template package. Case studies and reports are freely available in the table below.
The following roles use the user-interface prototype:
You can make three basic kinds of prototypes:
In most projects, you should use all three prototypes, in the order listed above.
The user-interface prototype is built early, during Inception or in the beginning of the Elaboration phase, and before the whole system (including its "real" user interface) is analyzed, designed, and implemented.
Note that the main purpose of creating a user-interface prototype is to be able to expose and test both the functionality and the usability of the system before the real design and development starts. This way, you can ensure that you are building the right system, before you spend too much time and resources on development.
In order to achieve this, early testing follows that the prototype must be significantly cheaper to develop than the real system, while having enough capabilities to be able to support a meaningful use test.
A user-interface designer is responsible for the integrity of the user-interface prototype, ensuring that the prototype contributes to a usable user interface according to the requirements from use-case storyboards and boundary objects.
Decide whether a prototype is suitable for your project. Decide whether the prototype includes drawings, bitmaps, and/or an interactive executable. Decide on how much of the user interface to prototype, and the depth and realism of any interactivity. Decide whether the prototype is purely throwaway, or whether some aspects are intended to evolve into the end product.