Network-Centric Analysis and Representation Requirements for Successful Effects Based Operations Resilient Cognitive Solutions James Gualtieri, William.

Slides:



Advertisements
Similar presentations
Object-Oriented Application Frameworks Much of the cost and effort stems from the continuous re- discovery and re-invention of core concepts and components.
Advertisements

J. David Tàbara Institute of Environmental Science and Technology Autonomous University of Barcelona Integrated Climate Governance.
Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface UI Evaluating Design Proposals for Complex Systems.
Chapter 12 Health Care Information Systems: A Practical Approach for Health Care Management 2nd Edition Wager ~ Lee ~ Glaser.
Software Architecture in Practice (3 rd Ed) Understanding Quality Attributes Understanding the following: How to express the qualities we want our architecture.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Knowledge Acquisition and Modelling Concept Mapping.
Modeling Human Reasoning About Meta-Information Presented By: Scott Langevin Jingsong Wang.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
The Executive’s Guide to Strategic C H A N G E Leadership.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Dissemination pathways Science and policy
Requirement Engineering – A Roadmap
Mink Spaans What are the problems that need to be solved What is hard.
Feb. 23, 2004CS WPI1 CS 509 Design of Software Systems Lecture #5 Monday, Feb. 23, 2004.
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
Concept Mapping. What is Concept Mapping ? Concept mapping is a technique for representing knowledge in graphs. This technique was developed by Professor.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Course Instructor: Aisha Azeem
Risk and Resilience: A Canadian Perspective on Climate Change Adaptation Donald S. Lemmen, PhD Climate Change Impacts and Adaptation Directorate Natural.
Computational Thinking Related Efforts. CS Principles – Big Ideas  Computing is a creative human activity that engenders innovation and promotes exploration.
Professional Growth= Teacher Growth
Firat Batmaz, Chris Hinde Computer Science Loughborough University A Diagram Drawing Tool For Semi–Automatic Assessment Of Conceptual Database Diagrams.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Annual SERC Research Review - Student Presentation, October 5-6, Extending Model Based System Engineering to Utilize 3D Virtual Environments Peter.
STRATEGIES FOR ONLINE LEARNING IN A GLOBAL NETWORK UNIVERSITY INTED 2013 Annette Smith, Kristopher Moore, Erica Osher Reifer New York University.
Streamlining Business Operations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Computational Models of Emotion and Cognition Computational Models of Emotion and cognition Christopher L. Dancy, Frank E. Ritter, Keith Berry Jerry Lin,
Evidence based research in education Cathy Gunn University of Auckland.
GENERAL CONCEPTS OF OOPS INTRODUCTION With rapidly changing world and highly competitive and versatile nature of industry, the operations are becoming.
CPIS 357 Software Quality & Testing
Business Analysis and Essential Competencies
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Framework for Assessment: Technology-Assisted Learning and Collaboration Overview by Anne H. Moore.
3rd Country Training, K.Subieta: System Engineering and Databases. Lecture 3, Slide 1 February 20, 2004 Lecture 3: Introduction to Software Analysis and.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
Basic Concepts Software Architecture. What is Software Architecture? Definition: – A software architecture is the set of principal design decisions about.
 3:30 Simulation and curriculum integration Learning and competency assessment of students (Margaret Hindman)  4:15 Debriefing & simulation scenario.
Ventures, Inc. 1 Effects-based Coalition Operations Maris “Buster” McCrabb KSCO Symposium 23 April 2002.
Measuring the Quality of Decisionmaking and Planning Framed in the Context of IBC Experimentation February 9, 2007 Evidence Based Research, Inc.
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
1 Introduction to Software Engineering Lecture 1.
The Evolution of ICT-Based Learning Environments: Which Perspectives for School of the Future? Reporter: Lee Chun-Yi Advisor: Chen Ming-Puu Bottino, R.
The Next Generation Science Standards: 4. Science and Engineering Practices Professor Michael Wysession Department of Earth and Planetary Sciences Washington.
McGraw-Hill/Irwin ©2008 The McGraw-Hill Companies, All Rights Reserved CHAPTER 9 DECISION MAKING.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Chapter 8 Management, Leadership, and Internal Organization Learning Goals Define management and the skills necessary for managerial success. Explain the.
(c) Adaptive Processes Consulting Be with the Best!
McGraw-Hill/Irwin © The McGraw-Hill Companies, All Rights Reserved CHAPTER 9 Enabling the Organization—Decision Making.
February 19, February 19, 2016February 19, 2016February 19, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific.
1 S ystems Analysis Laboratory Helsinki University of Technology Effects-Based Operations as a Multi-Criteria Decision Analysis Problem Jouni Pousi, Kai.
Software Engineering Lecture 10: System Engineering.
System A system is a set of elements and relationships which are different from relationships of the set or its elements to other elements or sets.
Planning Instruction A Review of the Cognitive Domain and Performance Objectives.
UCI Large-Scale Collection of Application Usage Data to Inform Software Development David M. Hilbert David F. Redmiles Information and Computer Science.
March, 2004 Into the LAN: An Integrated LAN/WAN End User Study © 2004 Frost & Sullivan. All rights reserved. This document contains highly confidential.
Chapter 3: Strategy and Tactics of Integrative Negotiation
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
PLANNING, COMMUNICATION AND EVALUATION MODELS Oyinda Osibanjo H 671.
Working Together With Families : Outcomes and Evaluation
Chapter 13: Setting a Direction for Information Resources
Complexity Time: 2 Hours.
Chapter 9 Architectural Design.
Visual Modeling Using Rational Rose
Leadership for Safety Through the Case Method
Enabling the Organization – Decision Making
Presentation transcript:

Network-Centric Analysis and Representation Requirements for Successful Effects Based Operations Resilient Cognitive Solutions James Gualtieri, William Elm, & Jay Peffer

Hurdle to Success Functional Relationships in adversary systems are at the heart of Effects Based Operations (EBO) – This abstract functional thinking is difficult – Military planning community struggles to do it Applied Cognitive Systems Engineering (ACSE) seeks to understand these same Functional Relationships for systems design – Developers tend to drift to focusing on the Physical rather than the Functional – Concrete Physical thinking is easier 1 EBO and ACSE are the both natural extensions of the same science

2 The Real Challenge is identifying Effects and their relationship to Objectives Effects-Based Operations Objective Effect Action MOEs Effects Based Operations “is a methodology for planning, executing and assessing operations to attain the effects required to achieve desired national security objectives.“ AFDD 1 The focus tends to be on assessing what physical actions produce the desired behavioral effects

Mapping Physical to Functional 3 Functional substitutes impact the effectiveness of combat actions Function is a property of a physical object – its goal or purpose Identifying the relationship between the physical and functional world is critical for EBO The same Function can often be accomplished by different Physical objects

Focus on the Physical Alone Insufficient 4 Tools must reflect true complexity of domain not just surface features (Isolate the Battlefield) (Deny Access) Effects-Based Plan Representation Objective Indicator Effect Desired direct effect indirect effect complex effect cumulative effect Task/Activity (Name) Traditional EBO Representations Do Not Accurately Portray the Relationship Between Physical Components and Functional Effects Mechanism Strategy Development Tool

How does Missing Information Impact Decision Making? 5 Complexity of cognitive work not reflected in tool Representation impacts thinking – User likely to become target fixated – Functional concepts, like transportation, missing – What other Functions are “riding” on Bridge 1? – Side effects invisible – user can’t remember all functions – Trade-offs not obvious

6 Many-to-Many relationships are a property of all complex systems Many-to-Many Complex relationships exist between Physical entities and Functional properties – Relationships look simple from the perspective of any one physical entity – Impact of a single event can have a multitude of effects From a physical perspective, EBO decision-makers are unable to see and understand these cascading effects

7 Functional model of domain must be integrated into support environment Support Tools Critical for EBO Managing physical to functional mappings and many-to- many relationships is very difficult To be effective, EBO decision makers need tools that promote abstract thinking – Make functions and relationships explicit – Support runtime execution not just planning

8 Capturing abstract functional concepts improves support tool development A New Approach to Tool Development Applied Cognitive Systems Engineering (ACSE) is based on understanding functional concepts within a domain

Systems must respect how humans think and domain constraints Visualization Requirements Build Correspondence Between the Domain and Representation 9 – Provide frames of reference that capture meaningful relationships in domain – Put information into context – Highlight changes and events – Highlight departures from a referent

ACSE-based tools enable warfighters to rapidly assess information Visualizations of functional abstractions dramatically improves decision-making under stress ACSE Based Visualizations Representing effects as a functional abstraction network improves effectiveness 10

Conclusion Functional relationships must be considered for EBO to be effective – It requires more than just an inventory of physical components Functional concepts and relationships are at the heart of ACSE – It provides a framework for developing tools to support effective EBO Decision-makers must succeed at thinking functionally – There is a tactical advantage – Provide ability to invent new tools