Activity theory is a way of describing and characterizing the structure of human - tivity of all kinds. First introduced by Russian psychologists Rubinshtein, Leontiev, and Vigotsky in the early part of the last century, activity theory has more recently gained increasing attention among interaction designers and others in the hum- computer interaction and usability communities (see, for example, Gay and H- brooke, 2004). Interest was given a signi?cant boost when Donald Norman suggested activity-theory and activity-centered design as antidotes to some of the putative ills of ahuman-centered designa (Norman, 2005). Norman, who has been credited with coining the phrase auser-centered design, a suggested that too much attention focused on human users may be harmful, that to design better tools designers need to focus not so much on users as on the activities in which users are engaged and the tasks they seek to perform within those activities. Although many researchers and practitioners claim to have used or been in?uenced by activity theory in their work (see, for example, Nardi, 1996), it is often dif?cult to trace precisely where or how the results have actually been shaped by activity theory. Inmanycases, evendetailedcasestudiesreportresultsthatseemonlydistantlyrelated, if at all, to the use of activity theory. Contributing to the lack of precise and traceable impact is that activity theory, - spite its name, is not truly a formal and proper theory.Unified Process, 10a12, 14, 16, 17, 23, 24 UP, see Unified Process Usability use cases, 11 evaluation, 313 Usability evaluation, 257 automated, 336 through reverse engineering, 335 Usability traces analysis, 257 Usage-Centered Design, anbsp;...
|Title||:||Human-Centered Software Engineering|
|Author||:||Ahmed Seffah, Jean Vanderdonckt, Michel C. Desmarais|
|Publisher||:||Springer Science & Business Media - 2009-06-19|