1. Theoretical perspectives in Human Computer Interaction Tessy Cerratto & Henrik Artman IPLab, KTH Tessy@nada.kth.seTessy@nada.kth.se; Artman@nada.kth.se Artman@nada.kth.se

2. Outline for today Introduction Mindmap of groupmembers Perspectives on system development Perspectives on interaction Summary Table for analysing perspectives

3. Basic themes Active Activity Cognition Passive System Media Socialconstructionism Konstruktivism Kognitivism

4. Riddles for the information Age Cooper, A. (1999) The inmates are running the asylum Presentation of accidents and ”misunderstandings” between users and computer systems Analysis of user-computer dialogue –Errors –Feedback –Context of use –Type of user Critique of the development process of software-based products

5. Looking at the dialogue/interaction between the pilot and the computer The navigation aid was valid but not for the landing procedure at Cali Communication was precise and exact even though it was completely wrong The navigation aid did not tell the pilot that the radio station chosen was wrong

6. Looking at the navigation aid ”Software-based products are not inherently hard to use, they are that way because we use the wrong process for creating them” How to change this process ? How to do in order software-based products become friendly, powerful and desirable ?

7. Programmers and users have different goals The programmer wants the construction process to be smooth and easy The user wants the interaction with the program to be smooth and easy Can programmers create interaction?

8. Introduce interaction design in the development process Programmers Software user Interaction designers

9. Usability - Nomos Perspective: Task-oriented Motive: User needs, Internet demands easiness System: Computer system, user-measurement Solution: Standards, tailored system, one- functionality system, lab-testing

10. Designer Perspective: Experience oriented, estetics Motive: Success, love of an artifact System: Product + marketstrategy (branding) Solution: Target group identification, individuality, create brands

11. Different perspectives on user - information systems System theoretical Socio-technical Humanistic No perspective alone is sufficient Need of multi-perspective competence

12. System theoretical perspective Emphasis on technical formal aspects Knowledge is objectivistic User, if any s/he is rational and mechanicist Tasks are performed by machine Communication with a machine System development is a lifecycle

13. Socio-technical perspective Emphasis on interaction between human and computer Knowledge is instrumental Active users of Information system Communication with a friendly-user machine System development is participative

14. Humanistic perspective Emphasis on individuals Knowledge is situated The user is a human actor of both job and IS Tasks are performed by human actors using tools Communication is between users System development is evolutionary

15. About ” The science of design” A Note on Herbet Simon’s program The program for a Rationalistic Science of Design, design of artificial –Design is a process of problem-solving by individuals making decisions among sets of possibilities Alternatives ? –The systems approach as a seriuos humanistic alternative (cf. Churchman, Ackoff,Checkland) –Computers and understanding as philosophical and practical different tradition (cf. Winograd, Dreyfus) –Floyd’s work in the area of software engineering from product-oriented view to process-oriented view

16. Perspectives on interaction Preunderstanding and background (H) User interface /I-O devices (C) Functionality (C) Operative cognitions (H) Media structure/presentation (C) Domain representation (C) Change Stable

17. System Human Computer

18. System General perspective for all components Information transfer between components System goal Technology focused Information objective Constrained to technology? Meaning?

19. Dialogue

20. Dialogue-partner Mimic human behaviour Structural aspects of interaction Interface Not focused on background knowledge System self contained Mainly linguistic interaction?

21. Actor-tool

22. Tool Action-focused The user is an expert Tools are for accomplishing tasks Domain specific Learning is part of being expert New design based on tacit-knowledge Readiness-at-hand, present-at-hand

23. Media

24. Communication between people Technology is a medium Each medium needs a structure to encode Change operative cognitions, by media structure Domain representation is relevant for the sender Conduit-metafor of communication?

25. Aim for user studies Productivity Efficiency Change (development) Social identification, trend Learning

26. Method for design – relation to theory Standards –Detached –Conserving Intermediator –Costumer oriented – Expert designer Emacipatory –Involvment –Workoriented –Politically oriented

27. Unit of analysis Automated task Individual use Group – target group Organization -

28. Basic theoretical concepts ActivePassive InterpretiveMechanistic ObjectiveSubjective UniversalContextual IndividualCollective LogicalExperiental ActionMental GlobalLocal AwarenessTacit LearningRole

29. User assumptions ActivePassive InterpretiveMechanistic ObjectiveSubjective UniversalContextual IndividualCollective LogicalExperiental ActionMental GlobalLocal AwarenessTacit LearningRole

30. Design orientation InstrumentalEmpathic Design-for-allParticularity ActivitydesignTaskdesign Design for Closure Design for openness AccessibilityUsability SuccessUnderstanding LearningEasiness IdentificationFunctional ChangeConservation, automatation ExpertNovice