Prototype Classification and User Interface Management during the Requirements Analysis Phase of System Acquistion

Abstract

Much has been written about the value of prototyping during the requirements analysis phase of system acquisition. This paper focuses on the classification of prototypes as they impact the user interface. Using a style guide to manage the user interface during the prototyping process is also examined. A distinction between different categories of prototypes, can be drawn in terms of the amount of functionality provided to the user. Consequently, three distinct types of prototypes can be differentiated: conceptual, detailed design and operational prototypes. The conceptual prototype presents the user with the least amount of functionality and is often undertaken to derive functional requirements and to exhibit a proposed solution to a problem. The detailed design prototype exhibits more functionality and is often used by human factors personnel to collect detailed user feedback and performance data to make specific tradeoff decisions and to derive a more detailed design of the user interface. An operational prototype is a complete system that has been fully tested by selected end users, but is not sold as a commercial product. Once the category of prototype is established, a style guide is helpful in managing the development of the user interface. Ensuring consistency within a prototype is the principal role of a user interface style guide. Recent experience in the creation of a style guide for a prototyping effort for the US Air Force has led to a number of suggestions. These suggestions are discussed and future efforts in the development of user interface style guides is indicated.