Prototyping: Role of the end user

-End user is continually involved throughout

-The user is involved right from the start of the project

- ...in helping the systems analyst define some preliminary requirements

-The user tests each version of the prototype

-...and provides feedback to the analyst

-Based on the feedback the analyst will make changes to the prototype, give it back to the user who will then evaluate the changes.

The process will continue as refinements are made to the prototype. The result of these refinements may result into a fully working system (evolutionary prototyping) or produce a set of user requirements (throw-away prototyping).The system is then fully developed using an alternative approach such as Waterfall method. A prototype which is usually a practical implication of the systme is produced to help discover requirements.  

Purpose: to ensure the new system meets its objectives/requirements and to identify any errors/faults/bugs. It is important part of systems development. This is to ensure the system is of a high quality. Quality indicators are used during the testing stage:

Remember SUE!

Suitablity: It meets all of the objectives, fit for purpose, provides required functionality, compatible with existing technology/hardware/software/data and is free of errors.

Usability: user can learn to use the user interface quickly, intuitive interface, ICT competence level of user matches the interface, the user can transfer previous skills, training may or may not be required.

Effectiveness: The system performs tasks efficiently and has been designed to facilitate maintenance.