Human-Automation Interaction Design and Evaluation Tools. Michael Feary, PhD



Similar documents
Federal Aviation Administration. Kathy Abbott and Robert Burke Federal Aviation Administration 4 February 2015

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.

Criteria for Flight Project Critical Milestone Reviews

Malay A. Dalal Madhav Erraguntla Perakath Benjamin. Knowledge Based Systems, Inc. (KBSI) College Station, TX 77840, U.S.A.

Safety Management Challenges for Aviation Cyber Physical Systems

Prokrustes säng. och HMI-design

Structure of Presentation. Stages in Teaching Formal Methods. Motivation (1) Motivation (2) The Scope of Formal Methods (1)

What is a life cycle model?

Software Classification Methodology and Standardisation

WebSphere Business Modeler

Commercial Crew Transportation System Certification Requirements for NASA Low Earth Orbit Missions

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project

Business Analyst Work Plan. Presented by: Billie Johnson, CBAP CSM

Syllabus - Fatigue Risk Management (FRM) Training

Requirements Analysis Concepts & Principles. Instructor: Dr. Jerry Gao

Assurance Cases and Test Design Analysis

Lecture 9: Requirements Modelling

AS9100 B to C Revision

Application of Nuclear and Aerospace Industry Experience to Offshore Barrier Integrity Management

Best Practices for Verification, Validation, and Test in Model- Based Design

Certification Authorities Software Team (CAST) Position Paper CAST-9

Fundamentals of Measurements

Draft Requirements Management Plan

Ministry of Civil Aviation Egyptian Advisory Circular Number 00-3 Egyptian Civil Aviation Authority. EAC No.00_3

SOFTWARE REQUIREMENTS

Aviation Safety Policy. Aviation Safety (AVS) Safety Management System Requirements

The use of statistical problem solving methods for Risk Assessment

Exploration Medical System Demonstration (EMSD) Project

PRESENTATION. Patrick Ky Executive Director EUROPEAN COMMISSION

UniGR Workshop: Big Data «The challenge of visualizing big data»

An Introduction to the ECSS Software Standards

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >

Practice Overview. REQUIREMENTS DEFINITION Issue Date: <mm/dd/yyyy> Revision Date: <mm/dd/yyyy>

Using TechExcel s DevSuite to Achieve FDA Software Validation Compliance For Medical Software Device Development

Certification Authorities Software Team (CAST) Position Paper CAST-13

Software Engineering. Session 3 Main Theme Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti

SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK

Using Measurement to translate Business Vision into Operational Software Strategies

Subject: CREW RESOURCE MANAGEMENT TRAINING PROGRAMME

Manjula Ambur NASA Langley Research Center April 2014

b) Describe the concept of ERROR CHAIN in aviation.

SAFE SOFTWARE FOR SPACE APPLICATIONS: BUILDING ON THE DO-178 EXPERIENCE. Cheryl A. Dorsey Digital Flight / Solutions cadorsey@df-solutions.

System Development and Life-Cycle Management (SDLCM) Methodology. Approval CISSCO Program Director

Scalability of formal methods for validation and verification of software control systems

Automating Code Reviews with Simulink Code Inspector

Mission Assurance Manager (MAM) Life Cycle Risk Management Best Practices David Pinkley Ball Aerospace MA Chief Engineer September 23, 2014

Custom Software Development Approach

Agile Model-Based Systems Engineering (ambse)

The Challenges of Medical Events in Flight

Model Based Software Development for DDG 1000 Advanced Gun System

FAA s Progress and Challenges in Integrating Unmanned Aircraft Systems into the National Airspace System

Development of AUTOSAR Software Components within Model-Based Design

Anatomy of a Decision

Kirsten Sinclair SyntheSys Systems Engineers

Advanced Test Manager E-learning Course Outline

For the purpose of see-and-avoid, visual observers must be utilized at all times

The OMG BPM Standards

Software Verification/Validation Methods and Tools... or Practical Formal Methods

Software Certification and Software Certificate Management Systems

Requirements Definition and Management Processes

Title & Image NATIONAL CIVIL AVIATION ADMINSTRATION. Advisory Circular

VAIL-Plant Asset Integrity Management System. Software Development Process

Software Verification for Space Applications Part 2. Autonomous Systems. G. Brat USRA/RIACS

Business Process Modeling with Structured Scenarios

AGI Software for Space Situational Awareness

Technology WHITE PAPER

An Integrated Operational Risk Management Framework for Power Generation

The Key to a Successful KM Project

Software Quality. Software Quality Assurance and Software Reuse. Three Important Points. Quality Factors

Business Solutions Manager Self and contribution to Team. Information Services

Building the EDM Roadmap An Innovation Platform for New Product Development & Regulatory Compliance. Mark Cowan mark@cowaninc.

BAL2-1 Professional Skills for the Business Analyst

Safety Verification of the Small Aircraft Transportation System Concept of Operations

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction

PMI Agile Certified Practitioner (PMI ACP) Boot Camp Course AG05; 4 Days, Instructor-led

SCADE SUITE SOFTWARE VERIFICATION PLAN FOR DO-178B LEVEL A & B

Software Test Plan (STP) Template

Formal Specification and Verification of Avionics Software

Ten steps to better requirements management.

DITA Adoption Process: Roles, Responsibilities, and Skills

SESAR Air Traffic Management Modernization. Honeywell Aerospace Advanced Technology June 2014

A Design Rationale Capture Tool to Support Design Verification and Re-use

The Role of Design in the Design of EMR Systems

Interactive Guidance for Safety Critical Avionics

RFP Attachment C Classifications

Implementation of ANSI/AAMI/IEC Medical Device Software Lifecycle Processes.

Do you know? "7 Practices" for a Reliable Requirements Management. by Software Process Engineering Inc. translated by Sparx Systems Japan Co., Ltd.

GAO. Year 2000 Computing Crisis: Business Continuity and Contingency Planning

Risk Management Framework

A Characterization Taxonomy for Integrated Management of Modeling and Simulation Tools

SCADE Suite in Space Applications

Partnering for Project Success: Project Manager and Business Analyst Collaboration

Transcription:

Human-Automation Interaction Design and Evaluation Tools Michael Feary, PhD

Outline Human Automation interaction Research Challenges Research Approach Understanding Work domain analysis Visualization Prediction Human Performance Formal Verification 2

Accident Causes

Automation Development Exponential increase in complexity, but reduction controls and dedicated displays Resultant Proliferation of modes, and multiple function controls and displays

Methods and tools usable early in the design process (Moraal and Kragt, 1990)

Validation and Verification 6

DO-178B Software Design Process PDR CDR ATP D0 Develop Task Design D1 Develop Software Requirem ents D2 Design Software D3 Code Software D4 Integrate Modules D5 Integrate HW/SW System Requireme nts Task Design Document Software Requireme nts Document Software Design Module Code Integrated Module Code Total System (Code+HW) V0 Task Design Review V1 Software Requirem ents Review V2 Design Software Review V3/4 Code Review and Module Test V5 Module Integratio n Test V6 System Verification (HW/SW Integration) Test V7 Task Verification Test V8 System Validation/ Acceptanc e Test Module Test Procedures (Drivers) Integrated Module Test Procedures (Drivers) System Verification Test Procedures Task Verification Test Procedures System Validation/ Acceptance Test Procedures Module Test Results Integrated Module Test Results System Verification Results Task Verificatio n Results System Validation Results Traceability Matrix (Sherry, Feary)

HAI and Flight Deck Certification CS 25.1302 Installed Systems and Equipment for Use by the Flight Crew installed equipment must be shown, individually and in combination with other such equipment, to be designed such that qualified flight crewmembers trained in its use can safely perform their tasks associated with the intended function by meeting the following requirements: (b) The flight deck controls and information intended for the flight crew use must: i. Be presented in a clear and unambiguous form, at resolution and precision appropriate to the task, and ii. Be accessible and usable by the flight crew in a manner consistent with the urgency, frequency, and duration of their tasks, and

NASA Human Rating Requirements 2.5.3.2 All human-rated space flight systems shall be designed so that neither two human errors during operation or in-flight maintenance nor a combination of one human error and one failure shall result in permanent disability or loss of life. 2.5.3.3 The program shall consider tailoring requirement 2.5.3.1 if: a. It can demonstrate that two -failure tolerance is either impractical or negatively impacts overall system reliability, and b. Test data, hazard analyses, and comprehensive risk analyses together provide certainty that the system will have a very high reliability without twofailure tolerance. Impractical refers to cost prohibitive. Certainty that a system will have a high reliability refers to demonstration of high confidence. Very high reliability is reliability consistent with the accepted crewed aerospace industry standard at the time of each program s initiation. FAA 25.1302: Demonstrating intended function, task characteristics and integration 9

Methods and Tools for Validation and Verification Work Domain Analysis Visualization Human System Performance Analysis Normative Human Task Behavior Model Erroneous Human Behavior Generation Erroneous Human Task Behavior Model xor Task Model to Formal Model Translator Formal System Model Analyst Human Task Model Model Checker Verification Report Mission Model System Information Human-device Interface Model Device Automation Model 1/5/2011 Environment 10 Model System Specification Visualizer Counterexample Visualization

Major HAI Tool Challenges Need to provide Human Automation Interaction analysis tools which are: Robust The tools need to overcome the illusion of precision. The precision of the results needs to match the confidence in the results Useful The tools that need to be useful in the limited design and evaluation timecycle, by design personnel without extensive expertise (i.e. not cognitive scientists) Scalable Defining a minimum set of information to allow computational tools to provide help Presenting large amounts of data and information that are interpretable Supportive The tools need to be generalizable to help with the new and changing roles in NextGen

Defining the Mission How well can we describe the work? Background: Difficult problem (CTA 15+ year history) Time with domain experts is expensive and limited Accurate task descriptions are critical Current task analysis methods request detailed action sequence information, which is time consuming, and problematic Focus Issues: How can we involve domain experts in the task analysis process most efficiently? How can identify work structures and prioritize important work themes? What level of description detail is necessary? Need performance metrics/utility functions

Work Domain Analysis Minimum Information: Description of tasks/products, and utility functions Product diagrams (Billman, Feary, Schreckenghost, Sherry, ) 13

Task Analysis Tools Medina, Sherry, Feary (2008)

Research Approach Understanding the Problem Domain Characterization and Representing the Work Context Visualization of the problem and solution space Evaluating Human-System Performance Human Performance Analysis Formal Verification of Integrated Human-Automation Systems 15

Visualization See Chuck s talk 16

Human Systems Analysis How well can we evaluate the Human Automation Interaction performance, and predict problems? Work Domain Analysis Challenges: What development work needs to be done to enable human performance modeling optimize a design in the design process timeframe? Construction of Automation Behavior/Interface Can provide metrics and parameters that are directly applicable to design issues? Can we provide methods and tools usable within design process constraints? Can we computationally optimize strategies/action sequences? Need the utility functions Procedure generation can be seen as a reachability (and hence model checking) problem. Prototype Generation Computational Human Performance Modeling

Specification of Automation and Interface Behavior in ADEPT Logic Editor User Interface Editor

Human Performance Analysis Aviation CogtoolExplorer with SemanticAnalysis (Carnegie-MellonUniv.) Combined a tool that allows a designer to quickly build a representation of a procedure, then analyze it with multiple techniques including: Information foraging analysis for pilot attention Latent semantic analysis for pilot cognition, based on anaviation corpus database that simulatestheknowledge of typicalairline pilots 19

END Thank you For more info: Michael.S.Feary@nasa.gov