Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface UI Evaluating Design Proposals for Complex Systems.

Slides:



Advertisements
Similar presentations
CONCEPTUAL WEB-BASED FRAMEWORK IN AN INTERACTIVE VIRTUAL ENVIRONMENT FOR DISTANCE LEARNING Amal Oraifige, Graham Oakes, Anthony Felton, David Heesom, Kevin.
Advertisements

When Students Can’t Read…
Qualifications Update: National 5 Music Qualifications Update: National 5 Music.
System Development Life Cycle (SDLC)
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Chapter 12 User Interface Design
Chapter 2 Analyzing the Business Case.
Lecture # 2 : Process Models
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
1/10 POSDATA Team EVR:MAKING USE Hou, Kyu Cho, Eun Young Jeung, Min Ho Jung,Hee Joon.
Bologna Process in terms of EU aims and objectives
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Systems Engineering in a System of Systems Context
Systems Analysis and Design 9th Edition
Chapter 2.
COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.
Slide 1 FAA’s Special Technical Audit of Boeing and the Audit Resolution Plan.
Analysis Concepts and Principles
Fundamentals of Information Systems, Second Edition
Analyzing the Business Case
Meaningful Learning in an Information Age
System Planning Analyzing the Business Case
User Centered Design Lecture # 5 Gabriel Spitz.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Object-Oriented Analysis and Design
SYSTEM ANALYSIS AND DESIGN
Critical Characteristics of Situated Learning: Implications for the Instructional Design of Multimedia Herrington, J., & Oliver, R. (1995). Critical Characteristics.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Requirements Analysis
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
Multimedia Specification Design and Production 2013 / Semester 1 / week 9 Lecturer: Dr. Nikos Gazepidis
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.
Systems Engineering In Aerospace Theodora Saunders February AUTOMATION IN MANUFACTURING Leading-Edge Technologies and Application Fairfield University.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Lecture 7: Requirements Engineering
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
1 of 27 How to invest in Information for Development An Introduction Introduction This question is the focus of our examination of the information management.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 8 Management, Leadership, and Internal Organization Learning Goals Define management and the skills necessary for managerial success. Explain the.
OO Design Roshan Chitrakar. Analysis to Design Do the RIGHT thing Do the RIGHT thing Requirement Analysis Requirement Analysis Domain Modeling with addition.
Victorian Curriculum: Introduction and overview
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
The Nature of Organisation Chapter 2, page 55. Structure of Part 1: The Nature of Organisations The concept and role of organisations Elements of an organisation.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
N ational Q ualifications F ramework N Q F Quality Center National Accreditation Committee.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
User Interface Evaluation Introduction Lecture #15.
Software Engineering Lecture 10: System Engineering.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
1 Systems Analysis & Design 7 th Edition Chapter 2.
OBJECT-ORIENTED TESTING. TESTING OOA AND OOD MODELS Analysis and design models cannot be tested in the conventional sense. However, formal technical reviews.
INTRODUCTION TO THE WIDA FRAMEWORK Presenter Affiliation Date.
Systems Architectures System Integration & Architecture.
Ecological Interface Design Overview Park Young Ho Dept. of Nuclear & Quantum Engineering Korea Advanced Institute of Science and Technology May
Systems Analysis & Design 7 th Edition Chapter 2.
EIAScreening6(Gajaseni, 2007)1 II. Scoping. EIAScreening6(Gajaseni, 2007)2 Scoping Definition: is a process of interaction between the interested public,
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
SQA project process standards IEEE software engineering standards
SQA project process standards IEEE software engineering standards
The Systems Engineering Context
Introduction to Project Management
TSMO Program Plan Development
HCI – DESIGN RATIONALE 20 November 2018.
Measuring Data Quality and Compilation of Metadata
Presentation transcript:

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface UI Evaluating Design Proposals for Complex Systems with Work Domain Analysis Neelm Naikar Defence Science and Technology Organization, Melbourne, Austrailia Penelope M. Snderson Swinburne University of Techonology, Melbourne, Austrailia 1

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface Division of Information Management Engineering User Interface Laboratory #11 Contents INTRODUCTION Evaluating Designs for Complex Systems Standard Technique for Evaluating Designs A Work Domain Analysis-Based Approach for Evaluating Designs EVALUATING DESIGNS FOR AIRBORNE EARLY WARNIN G AND CONTROL AEW&C Work Domain Analysis Using Work Domain Analysis to Evaluate AEW&C Designs Benefits and Challenges of Using Work Domain Analysis to Evaluate AEW&C Designs CONCLUSION 1

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface Cognitive work analysis has most commonly been used for the design and evaluation of interfaces for complex systems Focus in this paper is to show how work domain analysis, the first phase of cognitive analysis, can be used to evaluate design proposals for complex systems, such as military aircraft Traditionally, the role of human factors professionals in test and evaluation of designs has involved assessing the human performance implications of alternative design solutions To encourage human factors advice to be taken seriously, new steps are necessary for promoting the role of human factors practitioners in system design and development work domain analysis offers a means for fulfilling this goal In this paper, present work domain analysis as a framework for evaluating designs in the context of military acquisition INTRODUCTION 2

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface Evaluating Designs for Complex Systems Complex systems have special characteristics that place unique requirements on the evaluation of designs Complex systems consist of an interdependent set of human and machine components that must interact to achieve the work requirements of the system The work requirements of complex systems can no longer be described by a stable set of task sequences or procedures INTRODUCTION 3

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface Standard Technique for Evaluating Designs Describe standard techniques for evaluating designs and show that these techniques only partially fulfill the requirements for evaluating designs for complex systems Technical and operational evaluation techniques: derived from systems engineering and are commonly used for military acquisition throughout the world The technical evaluation involves examining the physical devices of a proposed design against a set of prespecified technical performance criteria by using this technique, evaluators develop a detailed understanding of the technical solution of a proposed design The operational evaluation involves examining how the technical solution of a proposed design will perform in specific mission scenarios has little to offer in determining how designs will perform in a broad range of situations, including changing or unanticipated conditions INTRODUCTION 4

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface A Work Domain Analysis-Based Approach for Evaluating Designs Work domain analysis explicitly recognizes that complex systems are subject to a great many events that cannot be specified or enumerated in detail WDA focuses on the fundamental functional boundaries on system performance and safety An abstraction hierarchy typically described a.The functional purposes or high level objectives of a work domain b.The priorities and values c.The purpose-related functions or general functions d.The physical functions e.The physical form INTRODUCTION 5

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface A Work Domain Analysis-Based Approach for Evaluating Designs The links between the layers of an abstraction hierarchy express means-ends or ho w-why relations By using an abstraction hierarchy for evaluation, the physical-device solutions of a pr oposed design can be evaluated in terms of how well they fulfill the higher-level functi ons and objectives of a work domain The abstraction hierarchy can also be used to evaluate interactions among physical-d evice solutions In summary, WDA focuses evaluation on whether an interdependent set of physical-d evice solutions will interact effectively to fulfill the work requirement of a proposed sys tem Thus, WDA promotes an understanding of how designs will perform in a wide variety of situations, including changing or unpredictable contingencies INTRODUCTION 6

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface Having outlined the theoretical motivations for a work domain analysis-based approach to evaluation AEW&C (Airborne Early Warning and Control) –Highlights the benefits and challenges of using WDA to evaluate designs, and compares it with standard evaluation techniques that were also used on this project –Complex airborne system that is currently being manufactured by Boeing for the Australian Defense Force –The AEW&C Project Office was going to use only standard techniques to evaluate AEW&C designs –Realized that the technical evaluation would result in a series of disparate reports about each if the many physical devices of AEW&C –All of the physical devices of AEW&C were being designed into a single system to support a common set of functions, priorities and values, and purposes. WDA could be used to carry out an integrated evaluation of all of the physical devices of AEW&C EVALUATING DESIGNS FOR AIRBORNE EARLY WARNING AND CONTROL 7

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface AEW&C Work Domain Analysis First step on the AEW&C project was to develop an abstraction hierarchy for AEW&C In reviewing the documents and interviewing subject-matter experts, used labels and descriptions of each layer of the abstraction hierarchy The means-ends links illustrates that evaluators can use the AEW&C work domain analysis to judge the impact of physical device solutions on the higher-level functions of the work domain EVALUATING DESIGNS FOR AIRBORNE EARLY WARNING AND CONTROL 8

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface The process for using the AEW&C work domain analysis to evaluate designs took advantage of the structure of the evaluation team that had been set up for the technical evaluation The team was divided into subgroups that were responsible for evaluating the designs of particular physical devices of the AEW&C aircraft (1) After the subgroups had completed their reports, the head of the evaluation team, assisted by the subgroups, summarized the overall impact on the purpose-related functions of AEW&C (2) The next step was to compare the three AEW&C designs in terms of how well they supported the purpose-related functions, priorities and values, and functional purposes of AEW&C (3) EVALUATING DESIGNS FOR AIRBORNE EARLY WARNING AND CONTROL Using Work Domain Analysis to Evaluate AEW&C Designs 9

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface Benefits and Challenges of Using Work Domain Analysis to Evaluate AEW&C Designs Several reasons WDA was considered to be a useful approach 1.The AEW&C WDA provided a set of functional criteria for integrating the results of the technical evaluation across all of the physical devices of AEW&C 2.The AEW&C WDA shifted the focus of evaluation from technical properties to the purpose-related functions, priorities and values, and functional purposes of AEW&C 3.Whereas the operational evaluation was restricted to six mission scenarios, the AEW&C WDA focused evaluation on a set of functional properties that were independent of particular events Some challenges in using WDA 1.Conveying to the evaluation team that the AEW&C abstraction hierarchy represented the functional properties of the AEW&C work domain rather that the activity that occurs in the work domain 2.Standard framework for evaluation involves educating the defense acquisition community in the approach EVALUATING DESIGNS FOR AIRBORNE EARLY WARNING AND CONTROL 10

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface Work domain analysis provides a useful and feasible approach for evaluating designs for complex systems. WDA therefore complements standard systems engineering approaches to evaluation in accommodating the special characteristics of complex systems Using WDA for evaluating designs is useful much earlier in the system life cycle for defining functional requirements and specifications Hence, although WDA is initially resource intensive, it can be used repeatedly, in many powerful ways, throughout the life of a system CONCLUSION 11