How to specify user interfaces systematically


Cologne, 12 January 2004



There are only very few interactive products which can be used intuitively. This is true for software applications as well as for hardware products, i.e. video tape recorders, cellular phones, or even washing machines. This can be rather upsetting, but will in most cases not stimulate the private user to return the product; though in the case of custom software developed for a specific business context, poor usability leads to extra large cost and frustration for those who have to work with the product on a daily basis.During the development phase of a custom software project, endless discussions are typically being held about the requirements of the involved departments, but nevertheless, massive complaints of the users will pop up after the roll out of the product. These are then only "band-aided" (if at all) since the project budget has already been spent.

ProContext has developed the "Context-Scenario-Method" based upon many years of experience from numerous industry projects. This methodology identifies the requirements for the user interface accurately and economically and leads to the specification of a user interface which is appropriate for the supported tasks and thus highly intuitive, efficient and satisfying to users.

The following diagram shows the core outputs of the Context-Scenario-Method during the construction of a user interface for an interactive product, including software, webware or interactive hardware products.



The Context-Scenario-Method assumes that a defined set of user interface specifications needs to be developed as part of the overall product development. It is important to follow an iterative process in order to improve and validate the specifications step by step based on the knowledge available within the project team at certain points of time. Therefore, the illustration just shows dependencies between the specifications, it is not meant to picture a linear process.

First, target user groups are identified which differ by their work context and real usage conditions are identified as part of the analysis of the context of use with future users of the product. Hidden user requirements are identified and specified by requirements engineers based upon the identified context scenarios.

The specification of the interaction then describes how the user interface efficiently supports the user tasks and is based on the identified user requirements. During the next step, the user interface specification is specified to determine the required user interface elements, their properties and the user actions necessary to be performed on the user interface elements. 

The user interface specification forms the basis for a prototype, which should be designed by an experienced usability engineer in order to assure that all common design rules of ISO standards and user interface style guides are applied.

Following such a systematic path leads to a user interface that is not an accidental product anymore (as happens quite often) but is consequently built on validated user requirements and gives a stable basis for the implementation of the product.

Do you also want to profit from our methodology or use it as part of your development projects/cycle and safeguard the success of your projects? We will explain and demonstrate our systematic approach to you and your colleagues, happily.

Just get into contact with us and arrange your personal presentation date.

ProContext GmbH
Deutzer Freiheit 77-79
50679 Köln
Germany
Telefon:  0221 759 92 595
Fax:0221 759 92 597
E-Mail:info@procontext.com