Chapter 19 Case study on requirements, design, and evaluation: NATS

Slides:

Advertisements

Similar presentations

Chapter 5 Development and Evolution of User Interface

Advertisements

Chapter 1 Introducing User Interface Design. UIDE Chapter 1 Why the User Interface Matters Why the User Interface Matters Computers Are Ubiquitous Computers.

Geographical investigation

Overview of the Interaction Design Process. Objectives By the end of today’s class you will be able to… –Describe the major steps in the interaction design.

ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.

Saul Greenberg User Centered Design Why User Centered Design is important Approaches to User Centered Design.

Part 2d: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding.

UI Standards & Tools Khushroo Shaikh.

©N. Hari Narayanan Computer Science & Software Engineering Auburn University 1 COMP 7620 Evaluation Chapter 9.

James Tam User Centered Design Why User Centered Design is important Approaches to User Centered Design.

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.

Identifying needs and establishing requirements Chapter 7a.

Identifying needs and establishing requirements Chapter 7b.

Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.

John Kelleher (IT Sligo) Cognitive Walkthrough. 1 Background Authors – Lewis & Polson (1991) Based on theory L&P CE+ Theory of Exploratory Learning Assesses.

Human Computer Interaction & Usability Prototyping Design & Prototyping HCI Prototyping.

Predictive Evaluation

Introduction to SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2009.

HCI Prototyping Chapter 6 Prototyping. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “prototyping” –Explain the.

S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.

Part 1-Intro; Part 2- Req; Part 3- Design  Chapter 20 Why evaluate the usability of user interface designs?  Chapter 21 Deciding on what you need to.

2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.

Requirements Engineering Requirements Elicitation Process Lecture-8.

Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.

What about Chapter 7?. What is the usability process? Tyldesley’s 22 possible Measurement Criteria Let’s focus on usability–A usability initiative needs.

SEG3120 User Interfaces Design and Implementation

Chapter 13. Reviewing, Evaluating, and Testing © 2010 by Bedford/St. Martin's1 Usability relates to five factors of use: ease of learning efficiency of.

Usability Assessment Methods beyond Testing Chapter 7 Evaluating without users.

CS2003 Usability Engineering Human-Centred Design Dr Steve Love.

Chapter 7 Interactive Design and Prototyping Human Performance Engineering Robert W. Bailey, Ph.D. Third Edition.

1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Information Gathering Prototypes Structured Walkthrough.

Chapter 15: Analytical evaluation. Inspections Heuristic evaluation Walkthroughs.

Software Engineering User Interface Design Slide 1 User Interface Design.

Chapter 15: Analytical evaluation Q1, 2. Inspections Heuristic evaluation Walkthroughs Start Q3 Reviewers tend to use guidelines, heuristics and checklists.

1 Human Computer Interaction Week 7 Prototyping. 2 Introduction Prototyping is a design technique where users can be involved in testing design ideas.

Chapter 3 Managing Design Processes. 3.1 Introduction Design should be based on: –User observation Analysis of task frequency and sequences –Prototypes,

Identifying needs and establishing requirements Data gathering for requirements.

Cognitive Walkthrough More evaluating with experts.

Chapter 15: Analytical evaluation. Aims: Describe inspection methods. Show how heuristic evaluation can be adapted to evaluate different products. Explain.

Chapter 23 Deciding how to collect data. UIDE Chapter 23 Introduction: Preparing to Collect Evaluation Data Timing and Logging Actions –Automatic Logging.

고려대학교 산업경영공학과 IMEN 315 인간공학 3. DESIGN AND EVALUATION METHODS.

Oct 211 The next two weeks Oct 21 & 23: Lectures on user interface evaluation Oct 28: Lecture by Dr. Maurice Masliah No office hours (out of town) Oct.

Interface Types and Models Dr. Dania Bilal IS 588 Spring 2008.

Part 4: Evaluation Days 25, 27, 29, 31 Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what,

5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.

User-centred system design process

Chapter 16: User Interface Design

Fundamentals of Information Systems, Sixth Edition

CIS 376 Bruce R. Maxim UM-Dearborn

Topic for Presentaion-2

Usability Evaluation, part 2

Software Requirements analysis & specifications

Chapter 20 Why evaluate the usability of user interface designs?

Evaluation technique Heuristic Evaluation.

A software engineering perspective

Usability Techniques Lecture 13.

Case Study on requirements, design, and evaluation: NATS

Chapter 23 Deciding how to collect data

Chapter 7 Case study on requirements: Tokairo, part 1

User Interface Design and Evaluation

Chapter 26 Inspections of the user interface

Chapter 22 Planning who, what, when, and where

Prototyping Sriram Mohan.

Immersion Team Research Plans

Introduction to Web Authoring

1. INTRODUCTION.

Evaluation Plan Group interview Post-session questionnaire

Interface Design and Usability

COMP444 Human Computer Interaction Prototyping

Presentation transcript:

Chapter 19 Case study on requirements, design, and evaluation: NATS

The Final Approach Spacing Tool (FAST) National Air Traffic Services Air Traffic Management Systems Airspace corridors Lower airspace, Upper airspace Final Approach Control The FAST User Interface UIDE Chapter 19

UIDE Chapter 19

UIDE Chapter 19

UIDE Chapter 19

Completed FAST Interface Landing Sequence Countdown to turning UIDE Chapter 19

UIDE Chapter 19

How the Team Developed FAST NATS Research and Development Improving and developing air traffic management systems The Human Factors Unit Analyzes the work of the controllers and works to help project teams design air traffic management systems. The FAST Project Team 5 members Project manager Requirements engineer Software developer Algorithm developer Human Factors practitioner Others as needed UIDE Chapter 19

Requirements Gathering The Domain, Users, Environment, and Usability Requirements The Air Traffic Controllers and LATCC The Tasks Carried Out by Air Traffic Controllers Using FAST The Air Traffic Control Room Usability Requirements UIDE Chapter 19

Requirements Gathering How the Project Team Gathered the User Requirements Visited the facility Observed controllers performing their tasks Interviewed controllers Informal discussions UIDE Chapter 19

The Design and Evaluation of the User Interface Design by Prototyping Low-Fidelity Prototyping Paper prototypes -> emulation with PowerPoint High-Fidelity Prototyping Iterative C++ development UIDE Chapter 19

Preparing to Evaluate Writing the Evaluation Plan Choosing the Users Stages of evaluation Objectives of each evaluation How to conduct the evaluations Choosing the Users Representative controllers Creating the Correct Physical Environment Current system’s Operations Room Planning the Evaluation Sessions Different times during the work periods UIDE Chapter 19

UIDE Chapter 19

Observing the Controllers Debriefing Sessions Problems, likes, dislikes, changes needed Questionnaires Complement the debriefings Workload Assessment Tool Individual self-assessment tool (ISA) Some Changes Resulting from Having Observed the Controllers UIDE Chapter 19

UIDE Chapter 19

Inspecting the User Interface Predicting the Likelihood of Errors Predictive evaluation, inspection (walk-through) Is the correct answer evident to the user? Can connect description to correct action? Will user know if they made the correct/incorrect choice? Guideline Review – Style Guidelines reviewed A Change Resulting from Having Inspected the User Interface UIDE Chapter 19

Analyzing and Interpreting the Evaluation Data To help understand the weaknesses of the design and how to overcome them Communicating the Findings to the Customer Involve all stakeholders in the evaluation process Keep stakeholders informed of all evaluations UIDE Chapter 19