repect logoFunctionality Matrix

Primary Reference Source

Catterall, B (1990) The HUFIT functionality matrix -In D. Diaper, G. Cockton, D. Gilmore, B. Shackel, (Eds) INTERCHI'90, Amsterdam, North-Holland

Summary Description

This is a way of specifying which functions each user type needs. Identifying which tasks are critical allows more time to be paid to these during design and usability testing.

Typical Application Areas

Applicable mainly to systems where tasks are well defined.

Benefits

Enables a realistic consideration of early user and task issues on product functionality specification.

Tailorable to suit varying design processes and in-house styles.

Allows different user types to be considered together in a single process.

Superfluous functions are identified.

Represents a reference in subsequent product lifecycle stages and may be updated in the light of prototyping.

Limitations

Prime focus on functions and features rather than interface appearance. Can be cumbersome for large numbers of functions.

Cost of Use

Resources required fairly small. Requires input from different user types to complete matrix fully.

Costs of acquisition

Compulsory training not specified although the method may require some degree of practice in order to acquire the basic skills.

Suitability for requirements engineering in telematics

Useful for the specification phase of design process.

Detailed Description of Method

 
Structure of Functionality Matrix (example)
Functions
Users and Tasks F1 F2 F3 F4 F5 Key:
User A X - Critical to Task
Task A X O - Occasional Use
Task B O
Task C O
User B
Task A X
Task B O
Task C O

[Go to Methods Table (by Lifecycle)] [Go to Methods Table (by Special Needs)] [top of page]