Gould ( 1988) considers continuous evaluation and modification within the software development process as one prerequisite to design usable systems. IsoMetrics supports this approach by getting quantitative and qualitative informations about deficiencies of the system from the users point of view and thereby permits its improvement.
IsoMetrics has been applied in several software development projects in which the inventory has proven its practicability. Given ten evaluators IsoMetricsL evokes about one hundred remarks (the validity of this outcomes has been reported elsewhere, Willumeit et al., 1996). They are prioritized due to their rated importance and their frequency ( Gediga et al., in press; Willumeit et al, 1996). The content analysis of the remarks results in weak points of the evaluated software providing the input to a usability review. In such a review users, software-engineers and human factors specialists develop remedies for the systems weak points and discuss its (re)design. The acceptance of this procedure could be proved on either side by the developers as well as the users.
A version of IsoMetrics which is applicable in group settings is discussed in Hamborg et al. ( 1999).
Gediga, G., Hamborg K.-C. & Dtintsch, I. (in print). "The IsoMetrics Usability Inventory: An operationalisation of ISO 9241-10". Behaviour and Information Technology.
Gould, J. D. ( 1998). "How to Design Usable Systems". In M. Helander (ed.): Handbook of Human-Computer-Interaction. Amsterdam: Elsevier Science Publishers, pp. 757-789.
Hamborg, K.-C., Gediga, G., Döhl, M., Janssen, P. & Ollermann, F. ( 1999) "Softwareevaluation in Gruppen oder Einzelevaluation: Sehen zwei Augen mehr als vier"? In U. Arend & K. Pitschke (Hrsg.): Software-Ergonomie '99. Design von Informationswelten. Stuttgart: Teubner, pp. 97-109.
Willumeit, H., Gediga, G. & Hamborg, K.-C. ( 1996). "IsoMetricsL: Ein Verfahren zur formativen Evaluation von Software nach ISO9241/10". Ergonomie und Informatik, 27, pp. 5-12.