Benefits of user interface prototyping early in the cycle
Filed Under User, Interface, Benefits, Prototyping | Posted on February 16, 2008
It is recommended that user interface prototyping not be left to latter stages of the project (say when the code has already been written). Prototyping can be considered as a risk reduction activity. What are some of the benefits available due to prototyping?
* Elucidate requirements. A prototype can “translate” the domain vocabulary of users into concrete aspects of a system. For example, a prototype can convert a general set of workflow or task descriptions into a sequence of GUI screens and controls displaying well-defined data.
* Misunderstandings between software developers and users may be identified as the system functions are demonstrated.
* Once the prototype is developed, it can be installed at the client site, and left for them to continually validate and verify that the proposed system will meet their changing requirements.
* Missing user services may be detected. Though customers can’t always tell you exactly what they want, when shown a prototype, they’re very reliable in telling you when you get it wrong.
* Difficult-to-use or confusing user services may be identified and refined.
* Software development staff may find incomplete and/or inconsistent requirements as the prototype is developed.
* A working, albeit limited, system is available quickly to demonstrate the feasibility and usefulness of the application to management. Further, a prototype can answer specific questions about high-risk aspects of the system design that impact everything else.
* Impact on usability: Improved usability of the final product, due to early feedback on design and presentation from users
* The prototype serves as a basis for writing the specification for a production quality system.
* Fine-tuning schedule: Developing the prototype allows the software engineer some insight into the accuracy of initial project estimates and whether the deadlines and milestones proposed can be successfully met.
* Improved and increased user involvement: Prototyping requires user involvement and allows them to see and interact with a prototype allowing them to provide better and more complete feedback and specifications.
* User training: The developed prototype can support user training
* System testing: Prototypes give good pointers to the team preparing test plans and cases, both in terms of new ideas and validation
* Development of the prototype leads to improved morale of the whole team, and a feeling of partnership between client and development team
* Reduced feature creep since features can be more easily validated through the prototype
Leave a Reply
