Understanding methods in a ‘system of usability practice’ Dominic Furniss PhD Supervisors: Ann Blandford & Paul Curzon.

Slides:



Advertisements
Similar presentations
Intelligence Step 5 - Capacity Analysis Capacity Analysis Without capacity, the most innovative and brilliant interventions will not be implemented, wont.
Advertisements

Achieve Benefit from IT Projects. Aim This presentation is prepared to support and give a general overview of the ‘How to Achieve Benefits from IT Projects’
Information-Rich Engineering Design (I-RED)
CS305: HCI in SW Development Evaluation (Return to…)
Social Accounting and Audit (SAA) and the Social Audit Network An introduction…
Accident/Incident Investigation
Reflective Practice Leadership Development Tool. Context recognised that a key differentiator between places where people wanted to work and places where.
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
SWE Introduction to Software Engineering
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Internal Control Concepts Knowledge. Best Practices for IT Governance IT Governance Structure of Relationship Audit Role in IT Governance.
The Australian/New Zealand Standard on Risk Management
Requirements Engineering Processes
Overview of Software Requirements
HFSD Methods Nov HFSD Methods Objectives –To consider types of systems –To characterise methods for HF input into SD –To identify HF contributions.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
© Tefko Saracevic, Rutgers University1 digital libraries and human information behavior Tefko Saracevic, Ph.D. School of Communication, Information and.
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
Planning. SDLC Planning Analysis Design Implementation.
1 Performance Auditing  In IT Environment  Evidence Gathering & Analysis Techniques  Computer Assisted Techniques  Use of IDEA.
CS 4310: Software Engineering
Information Literacy in the workplace: implications for trainers By Dr. Mark Hepworth Department of Information Science Loughborough University.
Margaret J. Cox King’s College London
Information Systems Security Computer System Life Cycle Security.
Perspectives of student engagement Learning and Teaching Conference Faculty of Science and Engineering 30th March 2015 Mark Langan (School of Science.
Introduction to Human Factors Chap 1. Three episodes : ► An assembly-line worker ► Medicine bottle’ s print ► Voice response system.
CCLVET Cross Cultural Learning and Teaching in Vocational Education and Training Overview LEONARDO DA VINCI Transfer of Innovation AGREEMENT NUMBER – LLP-LDV-TOI-08-AT-0021.
Long-term twinning seconding and young talents’ involvement for the improvement of land administration development projects Fredrik Zetterquist Managing.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
360 Degree Feedback & Performance Appraisal. What is 360 Degree Feedback ?? 360-degree feedback is defined as “The systematic collection and feedback.
The Drivers of Audit Quality Culture within firm Skills and qualities of partners and staff Audit Quality External factors Reliability and usefulness of.
Software Requirements Engineering CSE 305 Lecture-2.
Angela Hammond University of Hertfordshire Putting internationalisation into practice: how to inform and develop your teaching. SEDA Spring Conference.
Chapter 11: Qualitative and Mixed-Method Research Design
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Consult like a PRO Management Consulting Skills and Problem-Solving Process.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Project monitoring and Control
Lecture 7: Requirements Engineering
INTRODUCTION TO USER DOCUMENTATION Function and purpose Production specifications Evaluate the effectiveness.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
‘Sujala’ Karnataka Watershed Development Programme Developing the Training Strategy Introduction for the “Brainstorming Workshop 1st of October 2003.
Safety Management System Implementation Michael Niels Thorsen Moscow 15 September 2005.
CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright.
How can remote operations become more resilient? Siri Andersen - DNV Energy Stig Ole Johnsen - SINTEF.
Placing Information Security within an Organization
1 Integrating Human Factors into Designing User Interface for Digital Libraries Sung Been Moon
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
IAEA International Atomic Energy Agency Methodology and Responsibilities for Periodic Safety Review for Research Reactors William Kennedy Research Reactor.
The Risk Management Process
Exam 2 Review Software Engineering CS 561. Outline Requirements Development UML Class Diagrams Design Patterns Users, Usability, and User Interfaces Software.
HCI Theory. Classical » Modern » Contemporary All cognition happens inside a user’s brain.
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
Digital Presentation Created by: Chris De Santiago June 8, 2015 Social Media for Professional Learning: AET/562.
Practical Implications of the Essentially Two-faced Nature of Design Research and Design Practice Dr Terence Love Dept of Design Curtin University
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
1 Module 1 Introduction: The Role of Gender in Monitoring and Evaluation.
Customer vs Customer Focus Value from a RoadTek perspectivefrom a customer perspective.
1. 2 Issues in the Design and Testing of Business Survey Questionnaires: Diane K. Willimack U.S. Census Bureau Economic Census The International.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
A new tool for measuring client experience
The Semiotic Engineering of Human-Computer Interaction Section I Foundation Chapter 1 Introduction.
London Funders: Theory of change
Concepts used for Analysis and Design
Safety Management System Implementation
Leadership for Safety Through the Case Method
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Presentation transcript:

Understanding methods in a ‘system of usability practice’ Dominic Furniss PhD Supervisors: Ann Blandford & Paul Curzon

2 Contents The problem Overview of the research process Introduction to accident models and RE Details of a ‘system of usability practice’ Validation Conclusion and the bigger picture

3 Why I chose the problem and why it’s interesting We don’t know enough about usability methods in practice… 1. Many methods do not transfer from research to practice …we need to know more about our users (practitioners), tasks and their contexts to do better applied research… 2. Literature on methods is criticised as being irrelevant to practitioners …we need to know more grounded in practitioner perspectives… 3. Research is moving out from the technical capability of methods, to their use, to their use in practice, to wider factors that impact on the performance of practice. …we need to know how methods integrate with the wider system.

4 Overview of the Research Process 1.Literature review: composition of usability practice knowledge. PITC. 2.Grounded theory: exploratory, engages with practitioner perspectives. Bottom-up mode 3.Website domain analysis (9 interviews) 4.Safety domain analysis (13 interviews) Top-down mode 5.Distributed Cognition perspective 6.Resilience Engineering perspective

5 Accident models and RE Sequential Epidemiological The alarm for reactor signals Operator turns off alarm The reactor overheats ‘Human error’ Design – too many alarms Training – poor Procedures – not followed Management – weak Safety culture – weak Latent conditions

6 Accident models and RE Systemic Non-sequential Events Come together by Bad luck -Murphy’s Law “This cannot be happening to me”

7 Accident models and RE Playing the devil’s advocate: 3 reasons why practitioners don’t use methods (Senior HCI lecturer, 2005, personal communication)

8 Accident models and RE Transferring HCI Modelling Techniques and Design Techniques to Practitioners (Buckingham Shum & Hammond, 1994) Prerequisite gulf Cost gulf Payback gulf Consultancy gulf Organisational factors

9 Resilience Engineering account. Highlights: 1.Methods are coupled with project structures and processes 2.Methods should provide leverage for understanding the project/domain issues 3.Methods should support rapport, be persuasive, and lead to the development of the practitioner’s reputation 4.Methods are coupled with staff development and management 5.The development of tools, methods, and communication practices affect practice 6.Methods should support documentation where appropriate

10 FRAM: Overall system

11 FRAM 1: Project process

12 FRAM 2: HF/usability practitioner understanding

13 FRAM 3: Persuasion, rapport and reputation

14 FRAM 4: Staff development and management

15 FRAM 5: Tools, methods and reporting practices

16 FRAM 6: Auditing and documentation

17 FRAM: Overall system

18 Validation Constant comparative method as part of GT Internal member checking of quotations Internal (10) and external (8) member checking of the model Model vs instantiations Scoping model in terms of detail and complexity Some parts are not unique to HF/usability Differences in tone: facilitating and helping vs persuading and selling Triangulation People, projects and domains Literature; e.g.: DC, RE, and Fitzgerald (1996) in IS development Corroborating and shaping usability practice research

19 Key Contribution to Knowledge A systems-thinking perspective Methods should be understood within a theory of system performance i.e. how they affect, and are affected by, wider aspects of HF/usability practice. In practice methods are simultaneously coupled to the… … technical substance of project … communication of results, issues and reporting … client resources, budgets, and structure … capabilities of the practitioners involved … tools – to enhance and extend capability … rapport, relationships and reputations … creation of documentation where appropriate In practice methods … should not be thought of as tools merely to find problems … should not be thought of in terms of solely how they are prescribed A’ A

20 The Bigger Picture CommunityMessage HCI researchers developing methodsMethods should take advantage of couplings Methods should be reported ‘adaptably’ HF/usability practitionersFRAM network can be used as a reflective tool for fine tuning and diagnosing issues in practice. Gives the ‘bigger picture’. HCI educators and MSc studentsMethods should not be limited to their common prescriptions but understood within a system of practice, e.g. via the functional network. Students should more easily see themselves as a resource for effective usability practice.

21 FRAM: Overall system

22 Thank-you