VELTI Evaluation Methodology

Slides:



Advertisements
Similar presentations
Chapter 12 User Interface Design
Advertisements

Characteristics of on-line formation courses. Criteria for their pedagogical evaluation Catalina Martínez Mediano, Department of Research Methods and Diagnosis.
UI Standards & Tools Khushroo Shaikh.
Algorithms and Problem Solving-1 Algorithms and Problem Solving.
Mgt 240 Lecture MS Excel: Decision Support Systems September 16, 2004.
Evaluation of usability tests. Why evaluate? 1. choose the most suitable data- collection techniques 2. identify methodological strength and weaknesses.
Part 4: Evaluation Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what, where, and when Chapter.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Software Process and Product Metrics
Web 2.0 Testing and Marketing E-engagement capacity enhancement for NGOs HKU ExCEL3.
User Interface Design Chapter 11. Objectives  Understand several fundamental user interface (UI) design principles.  Understand the process of UI design.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Evaluation of digital Libraries: Criteria and problems from users’ perspectives Article by Hong (Iris) Xie Discussion by Pam Pagels.
Paper Prototyping Source:
Website evaluation models and acceptability factors K.Vipartienė, E. Valavičius.
S/W Project Management
Instructional Design Eyad Hakami. Instructional Design Instructional design is a systematic process by which educational materials are created, developed,
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
Where Innovation Is Tradition SYST699 – Spec Innovations Innoslate™ System Engineering Management Software Tool Test & Analysis.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Chapter 6 : Software Metrics
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Patterns, effective design patterns Describing patterns Types of patterns – Architecture, data, component, interface design, and webapp patterns – Creational,
1 Usability and accessibility of educational web sites Nigel Bevan University of York UK eTEN Tenuta support action.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa REQUIREMENT SPECIFICATION Today: Requirements Specification.
Preliminary Evaluation Results: A Discussion with the Advisory Committee on Citizen-Friendly Reporting August 30, 2005 Human Services Research Institute.
Heuristic evaluation Functionality: Visual Design: Efficiency:
Introduction of Geoprocessing Topic 7a 4/10/2007.
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Recuperação de Informação B Cap. 10: User Interfaces and Visualization , , 10.9 November 29, 1999.
Project Overview Vangelis Karkaletsis NCSR “Demokritos” Frascati, July 17, 2002 (IST )
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
Newspaper in Education Web Site (NEWS) Usability Evaluation Conducted by Terry Vaughn School of Information The University of Texas at Austin November.
Introduction of Geoprocessing Lecture 9. Geoprocessing  Geoprocessing is any GIS operation used to manipulate data. A typical geoprocessing operation.
Internet Literacy Evaluating Web Sites. Objective The Student will be able to evaluate internet web sites for accuracy and reliability The Student will.
1 Usability evaluation and testing User interfaces Jaana Holvikivi Metropolia.
Be.wi-ol.de User-friendly ontology design Nikolai Dahlem Universität Oldenburg.
TRAINING PACKAGE The User Action Framework Reliability Study July 1999.
Introduction of Geoprocessing Lecture 9 3/24/2008.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
Shuang Wu REU-DIMACS, 2010 Mentor: James Abello. Project description Our research project Input: time data recorded from the ‘Name That Cluster’ web page.
Software Engineering Developing Requirements. © Lethbridge/Laganière 2001 Chapter 4: Developing requirements2 4.1 Domain Analysis The process by which.
© NCSR, Frascati, July 18-19, 2002 CROSSMARC big picture Domain-specific Web sites Domain-specific Spidering Domain Ontology XHTML pages WEB Focused Crawling.
LB160 (Professional Communication Skills For Business Studies)
Advanced Higher Computing Science
Algorithms and Problem Solving
Web-based structures, links and testing
Requirements Validation – II
The Development Process of Web Applications
Object-Oriented Analysis and Design
Software testing
Unified Modeling Language
CHAPTER 18 Food Marketing Individual Series Event
Software Engineering: A Practitioner’s Approach, 6/e Chapter 12 User Interface Design copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Usability Testing T/TAC Online Project Design Team
Software Requirements analysis & specifications
Introduction to Software Engineering
Quality Management Systems – Requirements
Social Knowledge Mining
Chapter 20 Why evaluate the usability of user interface designs?
Lecture 12: Data Wrangling
Introduction To System Analysis and Design PART 2
Internet Literacy Evaluating Web Sites.
User interface design.
Introduction to Engineering Design II (IE 202)
DATABASES WHAT IS A DATABASE?
Accessible / Universal Design
Programming Languages, Preliminaries, History & Evolution
Presentation transcript:

VELTI Evaluation Methodology Paris 4th Meeting 5-6 Dec, 2002 Created by VeltiNet

Table of Contents Prototype Evaluation at SCIE02 event Evaluation Methodology of Web Spidering, Information Extraction and User Interface

SCIE02 General On a total population of 10 evaluators participating Web Spidering On a total of 9 answers IE Tool On a total of 8 answers Responsiveness: 62.50% Accuracy: 87.50%, 75.00% User Interface On a total of 7 answers Simplicity: 57.14% (I1) Responsiveness: 57.14% (I2) Comprehensibility: 71.3% (I3) Consistency: 57.14% (I4), 42.86% (I5), 42.86% (I6) Workflow: 57.14% (I7), 71.3% (I8), 57.14% (I9) Forgetfulness: 57.14% (I10), 42.86% (I11) Localisation: 57.14% (I12) Help: 71.3% (I13), 57.14% (I14)

Evaluation Methodology Scope Behavioral Tests Test Cases Acceptance Criteria

Scope Address the quality of the artifacts produced Address product quality by the attributes outlined in ISO 9126 model Functionality, Efficiency, Reliability, and Usability Database consisted of 10 web pages

Behavioral Tests Simplicity. Were some parts unnecessarily complex? Responsiveness. Did the user perceive the system as responsive? If some operation takes long, was the user given a visual indication that the system is progressing, albeit slowly, in its response? Comprehensibility. Was the user at any time in doubt as to the meaning of some part of the interface? Consistency. Did the same action lead to the same results everywhere? Workflow. Did the sequence of the actions the user was forced to go through correspond to the user’s intuitive idea of performing the task? Did each action offer a clear feedback? Was the next action to do evident enough? Was the user’s task performed with the minimum number of steps? Forgetfulness. If the user happened to do something wrong, was the way to fix it easy? How much time did it took to return to the user’s intended path? Was it possible to restore the system to its past state? Localisation. Did the interface conform to customary conventions for the user’s language? Help. Was it easy to obtain help?

Test Cases Web Spidering Information Extraction User Interface

Web Spidering Scenario 1: Description: Use the Web Spidering Tool and select one of the existing URLs. While the Web Spidering Tool is processing the selected URL, open the URL with a browser and search it manually in order to find 2 pages presenting laptop offers Scenario 2: Description: Use the Web Spidering Tool and select a new URL of your choice. While the Web Spidering Tool is processing the selected URL, open the URL with a browser and search it manually in order to find 2 pages presenting laptop offers

Information Extraction Scenario 1: Description: Ask the system to extract information from two pages you choose from the ones provided by the system, according to the language you prefer. The pages provided belong to two types: List A contains single product description pages List B contains multiple product descriptions pages Scenario 2: Description: Ask the system to extract information from one of the pages collected by the Web Spidering Tool, according to the language you prefer

User Interface Scenario 1: Description: Search for laptops suitable for graphic designers. The user is supposed to discover unaided the proper preferences for this search Scenario 2: Description: The user is given some vague requirements, not necessarily expressed in the same language used in the interface. This will test how well the interface adapts to the domain Scenario 3: Description: The user is to find the most powerful laptop, as he/she understands it, regardless of price Scenario 4: Description: The user is to find the absolutely cheapest laptop, regardless of features

Acceptance Criteria Not a single formal method or technique The standardization process is ongoing by the ISO project 'Evaluation and Metrics' The ISO/IEC 9126 proposes four rating levels: Excellent, Good, Fair and Poor. The first three are considered as satisfactory; the last is considered as unsatisfactory Test output indicating above 25% efficiency can be considered as an adequate level of conformance to requirements

Q & A