Abstract

Uptake of HCI and usability engineering by software development organisations can be terminally impeded by lack of appreciation of the benefits of HCI activities. However, descriptions of HCI offerings in terms of activities (e.g. task analysis, user mapping, allocation of function, interaction design) and methods (e.g. user profiling, prototyping, GOMS modelling) do not convey to product managers a readily comprehensible conception of the value of such offerings. Similarly, descriptions of HCI activities and methods give little indication of how these are to be associated and managed with reference to stages and deliverables in a software development life cycle. This lack of clear association between usability engineering and software engineering contributes to the marginalisation of usability related activities. Even when investment is made in usability resources its eventual pay off can be minimal, with resulting disillusionment on both sides. Specification of usability deliverables can provide a solid basis for a manageable usability perspective on the development of software products. The article identifies usability deliverables and describes their content and relation to deliverables in a software design and development process. More general implications for an approach to the specification of quality processes for the creation of interactive software products are discussed.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call