Context of Use (Based on Ch2 of Usability-Centered Development) Jim Carter USERLab University of Saskatchewan © Jim A Carter Jr 2012.

Slides:



Advertisements
Similar presentations
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Advertisements

ISO 9001:2000 Documentation Requirements
User Interfaces 4 BTECH: IT WIKI PAGE:
ANSI/ASQ E Overview Gary L. Johnson U.S. EPA
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
Chapter 4 Design Approaches and Methods
Solutions to Review Questions. 4.1 Define object, class and instance. The UML Glossary gives these definitions: Object: an instance of a class. Class:
Sept-Dec w1d21 Third-Generation Information Architecture CMPT 455/826 - Week 1, Day 2 (based on R. Evernden & E. Evernden)
Snejina Lazarova Senior QA Engineer, Team Lead CRMTeam Dimo Mitev Senior QA Engineer, Team Lead SystemIntegrationTeam Telerik QA Academy Telerik QA Academy.
Jan Gulliksen, Januari 2001 CIDs insatser inom ISOs standardisering för ökad tillgänglighet “Gulan” Jan Gulliksen, CID och Uppsala.
Study Period Report: Metamodel for On Demand Model Selection (ODMS) Wang Jian, He Keqing, He Yangfan, Wang Chong State Key Lab of Software Engineering,
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Define usability testing Usability is all about how easy a product, service or system is to use. The extent to which a product can be used by specified.
1 Defining Usability Laura Leventhal and Julie Barnes Computer Science Dept.
Inspection Methods. Inspection methods Heuristic evaluation Guidelines review Consistency inspections Standards inspections Features inspection Cognitive.
Fundamentals of Information Systems, Second Edition
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Cloud Usability Framework
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
Opportunities & Implications for Turkish Organisations & Projects
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.
1 Standards Australia and accessibility standards Irene Hagstrom Standards Australia.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Sept - Dec w1d11 Beyond Accuracy: What Data Quality Means to Data Consumers CMPT 455/826 - Week 1, Day 1 (based on R.Y. Wang & D.M. Strong)
E-Accessibility Workshop 10/11 May 2012 Micah Rachuonyo – KEBS
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Lecture 15 Page 1 CS 236 Online Evaluating System Security CS 236 On-Line MS Program Networks and Systems Security Peter Reiher.
1 Usability and accessibility of educational web sites Nigel Bevan University of York UK eTEN Tenuta support action.
Usability Engineering Processes and Open Source Development Hartti Suomela.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
What is Usability? Usability Is a measure of how easy it is to use something: –How easy will the use of the software be for a typical user to understand,
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.
Heuristic evaluation Functionality: Visual Design: Efficiency:
1 Unit 1 Information for management. 2 Introduction Decision-making is the primary role of the management function. The manager’s decision will depend.
Icons to Hardware: The evolving range of ISO & ISO/IEC International Accessibility Standards Jim Carter USERLab University of Saskatchewan BSI/JISC CETIS.
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
Screen design Week - 7. Emphasis in Human-Computer Interaction Usability in Software Engineering Usability in Software Engineering User Interface User.
ISO GENERAL REQUIREMENTS. ISO Environmental Management Systems 2 Lesson Learning Goals At the end of this lesson you should be able to: 
Lecture 7: Requirements Engineering
INTRO TO USABILITY Lecture 12. What is Usability?  Usability addresses the relationship between tools and their users. In order for a tool to be effective,
Usability and Accessibility Usability of Accessibility Features Janey Barnes, PhD User-View, Inc. 1.
CS2003 Usability Engineering Human-Centred Design Dr Steve Love.
EHR Usability Standards, Tools and Frameworks Muhammad F Walji, PhD University of Texas Health Science Center Houston, TX.
Accessibility Principles Jim Carter USERLab University of Saskatchewan © Jim A Carter Jr 2012.
Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All ICT Accessibility Standardization Dr. Jim Carter, ISACC Document No: GSC16-PLEN-57r2 Source: ISACC.
Systems Analysis and Design in a Changing World, Fourth Edition
Fundamentals of Information Systems, Second Edition 1 Systems Development.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
AT Approach AT Definitions AT Assessment AT Accessibility AT Adaptability and Personalization.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Smart Home Technologies
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Useability testing Software Development Unit 4 Outcome 1.
IT Project Management, Third Edition Chapter 8 1 Chapter 5: Project Quality Management.
Organizations of all types and sizes face a range of risks that can affect the achievement of their objectives. Organization's activities Strategic initiatives.
Crew-centered Design and Operations of ships and ship systems CyClaDes Workshop ( )
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
HCC 831 User Interface Design and Evaluation. What is Usability?
Software Quality Control and Quality Assurance: Introduction
System Design, Implementation and Review
User Interface Design and Usability Course Introduction
INCOSE – North Texas Chapter
CLINICAL INFORMATION SYSTEM
Usability Techniques Lecture 13.
Human Computer Interaction
Presentation transcript:

Context of Use (Based on Ch2 of Usability-Centered Development) Jim Carter USERLab University of Saskatchewan © Jim A Carter Jr 2012

Usability Usability 1 is the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use 1. ISO :1998 Guidance on usability CMPT 480/840Context of use 2

Accessibility ISO and ISO define accessibility as: usability of a product, service, environment or facility by people within the widest range of capabilities 1. ISO TS 16071:2002 Ergonomics of Human-System Interactions – Guidance on accessibility for human- computer interfaces 2. ISO :2008 Ergonomics of Human-System Interactions – Accessibility guidelines for information/communication technology (ICT) equipment and services 3. ISO :2008 Ergonomics of Human-System Interactions – Guidance on software accessibility CMPT 480/840Context of use 3

Accessibility ISO/IEC JTC1 Information Technology /SC35 User Interfaces in 2011 resolved “ISO/IEC JTC 1/SC 35 strongly supports the existing definition of accessibility, as specified in ISO :2007 and ISO :2007 “But., if (for whatever reason) a definition of accessibility is required that is not based upon usability, it should read as follows: extent to which products, systems, services, environments and facilities can be used by people from populations with the widest range of user needs for the widest range of goals in the widest range of contexts of use NOTE 1: Contexts of use include direct use or use supported by assistive technologies. NOTE 2: While it is valid to claim compliance with accessibility standards, it is not appropriate to claim that something is accessible without specifying the user needs, goals, and contexts of use for which it is accessible. CMPT 480/840Context of use 4

The Universal Access Reference Model (UARM) CMPT 480/840Context of use 5

UARM & Overlapping Contexts CMPT 480/840Context of use 6

in a specified context of use ISO defines context of use (CoU) as users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used Like any shopping list, additions have been suggested: Goals (in ISO/IEC ) Content (by ISO TC159/SC4/WG9) Organizational environments / contexts (by both of the above) We can reword “in a specified context of use” to be: in a specified (set of) users, goals, tasks, equipment (hardware, software and materials), content and the physical, organizational and social environments in which the product is used 1. ISO/IEC DIS 25063:2011 Systems and software engineering - Software product Quality Requirements and Evaluation (SQuaRE) - Common Industry Format (CIF) for usability: Context of use description CMPT 480/840Context of use 7

in a specified (set of) users, goals, tasks, equipment (hardware, software and materials), content and the physical, organizational and social environments in which the product is used Even if we are not evaluating usability for these specified users they still exist in the CoU and the other specified users might interact with them so we need to consider how their existence might effect usability This provides further reason to consider stakeholders, as well as “users” Stakeholders are included in the ISO/IEC discussion of context of use Usability does not exist in a vacuum. Usability tests in a sterile lab generally miss at least some elements of the CoU 1. ISO/IEC TR 25060:2010 Systems and software engineering - Software product Quality Requirements and Evaluation (SQuaRE) - Common Industry Format (CIF) for usability: General Framework for Usability- related Information CMPT 480/840Context of use 8

in a specified (set of) users, goals, tasks, equipment (hardware, software and materials), content and the physical, organizational and social environments in which the product is used The ISO definition of CoU focuses on tasks rather than on goals ISO/IEC and consider both goals and tasks as parts of the CoU Remember, ISO defines Goal as intended outcome Task as activities required to achieve a goal The CoU needs to tie these two together. CMPT 480/840Context of use 9

in a specified (set of) users, goals, tasks, equipment (hardware, software and materials), content and the physical, organizational and social environments in which the product is used ISO seems to be considering this the “systems” context of the “product” for which usability is being evaluated NOTE: this clumsy wording is an artifact of the time in which this definition was developed. ISO/IEC refers to this as the “technical environment” So we can further reword this clause to be: in a specified (set of) users, goals, tasks, content and the technical, physical, organizational and social environments in which the product is used CMPT 480/840Context of use 10

Context of use in a specified (set of) users, goals, tasks, content and the technical, physical, organizational and social environments in which the product is used Neither ISO nor ISO/IEC consider content as part of the CoU However, the operations and usability of many IT systems can be highly dependent on differences in information content. Whenever differences in content leads to different contexts that further lead to different levels of usability then it is important to consider this within the CoU by treating separately each set of content that might produce different levels of usability CMPT 480/840Context of use 11

Context of use in a specified (set of) users, goals, tasks, content and the technical, physical, organizational and social environments in which the product is used This recognizes the many possible effects of various environmental factors on usability Wherever differences in environments lead to different levels of usability then it is important to consider this within the CoU by treating separately each set of environments that produce different levels of usability NOTE: There is a difference between mobile (so called ubiquitous) environments and office and/or home environments. The term ubiquitous should not be used as an excuse to ignore specific environments that produce different levels of usability. CMPT 480/840Context of use 12

Context of use in a specified (set of) users, goals, tasks, content and the technical, physical, organizational and social environments in which the product is used The overall CoU consists of all of the users, goals, tasks, content and the technical, physical, organizational and social environments in which the product is used This might actually represent many specific CoU which contain unique combinations of some of the users, goals, tasks, content and the technical, physical, organizational and social environments in which the product is used CMPT 480/840Context of use 13

Context of use in a specified (set of) users, goals, tasks, content and the technical, physical, organizational and social environments in which the product is used There are a variety of different CoU to consider: There might be different specific CoU within the overall CoU that should be considered separately, because they have different levels of usability The current CoU is the only one we can be certain of (but it will change) Changes (to any components of the CoU) will result in a future CoU We can treat the future CoU in various ways, including: Pretending that it won’t change from the current CoU (not a good idea) Predicting an anticipated CoU that might result from changes to the system, users, environments, and/or goals and tasks (a better idea) Intentionally planning a designed CoU as part of our development efforts (the best idea) And each will have its own set of usability measures (usability profile) CMPT 480/840Context of use 14

Usability Profiles By considering the many different CoU that could result in different usability we see that there are very many usability measures that could, and perhaps should, be considered ISO does not require us to evaluate and apply all of these possible measures but it does alert us to the complexity of the problem It states, “The choice of measures and the level of detail of each measure, is dependent on the objectives of the parties involved in the measurement “The relative importance of each measure to the goals should be considered” CMPT 480/840Context of use 15