Usability Engineering - Quality Approach ( ISO 13407)

 
 

Introduction

Usability Engineering - is the buzz-word of the new millennium. The new customer is well aware of his requirements, unwilling to compromise. He demands value for his hard earned money. Whether, he purchases a mobile phone, microwave or a washing machine - he would want focus on the USER INTERFACE. How user friendly is the interface which he is handling. Along with the aesthetics of an equipment like mobile phone, the features including, how many key strokes can lead him to perform his regular task. Size, shape, location of the keys, would matter equally to make a selection. Hence the focus of the new customer is USABILITY. Usability Engineering is a science, which studies how to understand and systematically address the Usability demand of a customer. In short, Usability Engineering deals with design of Websites, Computer portals, computer key-board design, car-dash-board design etc.

Usability principles

Usability is defined in ISO 9241 part 11 (a standard giving guidance on usability on requirements for office work with visual display terminals) as the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use. Essentially this means that usability is an attribute of the way in which a particular person and system interact. The important features are:

Effectiveness - How well the user achieves the goals they set out to achieve using the system.
Efficiency - The resources consumed in order to achieve their goals.
Satisfaction - How the user feels about their use of system

Quality of use evaluation when carried out at the end of the development process is of limited use unless the developers have the intention of creating an update soon. Evaluation with typical users of the intended product, or user-based validation should be built in to all the stages of the design process, from the first prototypes till the pre-release stage. The forthcoming ISO 13 407 standards provide a framework for user centered development activities that can be adapted to numerous development environments: from a straight waterfall type of development process to an iterative type of environment.

The model comprises of five stages, four of which are implicitly joined in a loop. Although the process outlined above looks iterative, it need certainly not be so: it may be converted to a waterfall life-cycle model if required by simply going through once only (in this case, there is simply more focus on user needs and user evaluation than one would normally expect to find in a conventional system development) or a V-type lifecycle development (in which the evaluation phase is seen as signing off the specification phase). However, the true benefit of this model emerges when it is used to guide an iterative development process

It is important to stress the transition from each stage to the next is a very crucial step in the successful implementation of the process and it is important not to progress to the next step until satisfied all aspects and information have been covered.

The Schaffer Method™

Over more then 20 years the technical staff at Human Factors International, Inc. has developed the best practice for optimizing user experience and performance. Led by Dr. Eric Schaffer they created a method that is efficient, systematic, scientific, and wholly practical.

The Schaffer Method™is the foundation of efforts to institutionalize usability assurance.
The Schaffer Methodology is a process standard. It is like a theme in jazz. Great jazz results from skilled musicians working within the theme. Great applications happen when a skilled development team works well within the Schaffer Method.

  1. Plan Project.
    Identify main activities and adequate staff and time. Establish the extent of usability work required.
  2. Evaluate Current Applications.
    Identify potential improvements.
  3. Know What the Organization Wants.
    Identify business rules and directions before actual design.
  4. Know What the Users Want.
    Understand different users and their needs to help build a solid foundation.
  5. Design the Structure.
    Ensure that users can understand what is offered, find things quickly, and navigate efficiently.
  6. Check Standards.
    Use standards to save time, improve design quality, provide consistency and help concentrate creativity.
  7. Design Screens.
    Create screen designs once the navigation and standard templates are in place.
  8. Support Implementation.
    Hand over the functional specification to the implementation team.
  9. Evaluate Usability.
    Complete a full simulation test. Maintain an ongoing process of monitoring site performance.
  10. Localize the Application.
    Create localized versions of the design to accommodate additional cultural contexts if required.

Schaffer–Weinschenk Method™ Chart

Acknowledgements
1. ISO 133407 Standards
2. Human Factors International for reference to the Schaffer Method

Prepared by: Anjoo Navalkar

 
 

Close Window