Paul Scerri and Nancy Reed

Slides:



Advertisements
Similar presentations
Inference without the Engine!. What is EZ-Xpert 3.0? EZ-Xpert is a Rapid Application Development (RAD) environment for creating fast and accurate rule-based.
Advertisements

E-Science Data Information and Knowledge Transformation Thoughts on Education and Training for E-Science Based on edikt project experience Dr. Denise Ecklund.
Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface UI Evaluating Design Proposals for Complex Systems.
© Devon M.Simmonds, 2007 CSC 550 Graduate Course in Software Engineering ______________________ Devon M. Simmonds Computer Science Department University.
Jenkins — Modular Perception and Control Brown Computer — ROUGH DRAFT ( ) 1 Workshop Introduction: Modular Perception.
Software Construction
© Franz Kurfess Project Topics 1 Topics for Master’s Projects and Theses -- Winter Franz J. Kurfess Computer Science Department Cal Poly.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Introduction to Software Architecture. What is Software Architecture?  It is the body of methods and techniques that help us to manage the complexities.
Reasons to study concepts of PL
PDDL: A Language with a Purpose? Lee McCluskey Department of Computing and Mathematical Sciences, The University of Huddersfield.
Chapter 2 Making interactive systems feel natural for users
Introduction to Software Testing
Acquiring Information Systems and Applications
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Lecture 1 What is Modeling? What is Modeling? Creating a simplified version of reality Working with this version to understand or control some.
CSE 303 – Software Design and Architecture
11 C H A P T E R Artificial Intelligence and Expert Systems.
Artificial Intelligence: Prospects for the 21 st Century Henry Kautz Department of Computer Science University of Rochester.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Lecture on Computer Science as a Discipline. 2 Computer “Science” some people argue that computer science is not a science in the same sense that biology.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Artificial intelligence systems form a broad and diverse set of.
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
Introduction to Software Engineering. Why SE? Software crisis manifested itself in several ways [1]: ◦ Project running over-time. ◦ Project running over-budget.
1. Where to use Multimedia ? 2  Business  Government  Education  Broadcasting & Entertainment  Research & Development  Health.
What is Software Engineering? The discipline of designing, creating, and maintaining software by applying technologies and practices from computer science,
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Computing For Embedded System IEEE Instrumentation and Measurement Technology Conference Budapest, Hungary, May 21-23, Author : Edward A. Lee UC.
Introduction The design, development and maintenance of concurrent software are difficult tasks. Truly effective support methodologies have yet to be developed.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
4+1 View Model of Software Architecture
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Learning Procedural Knowledge through Observation -Michael van Lent, John E. Laird – 인터넷 기술 전공 022ITI02 성유진.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Chapter 7: Designing solutions to problems OCR Computing for A Level © Hodder Education 2009.
HCC 831 User Interface Design and Evaluation. What is Usability?
 Programming methodology: ◦ is a process of developing programs that involves strategically dividing important tasks into functions to be utilized by.
Introduction to Software Engineering
Advanced Software Engineering Dr. Cheng
Air Force Institute of Technology
Software Development Life Cycle Waterfall Model
INTRODUCTION The economies of ALL developed nations are dependent on software. More and more systems are software controlled Software engineering is concerned.
Intelligent Systems Development
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
User-centred system design process
IS301 – Software Engineering Dept of Computer Information Systems
Design and Manufacturing in a Distributed Computer Environment
Data Science Diversity from the Perspective of a National Laboratory
ECE 551: Digital System Design & Synthesis
Presenter: Guan-Yu Chen
Overview of System Engineering
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Chapter 1: Object-Oriented Thinking
Model-Driven Analysis Frameworks for Embedded Systems
A BRIEF INTRODUCTION TO UNIX OPERATING SYSTEM
Analysis and Understanding
Introduction to Software Testing
TGn Simulation Methodology Validation Proposal
Chapter 0 : Introduction to Object Oriented Design
CS 8532: Advanced Software Engineering
User Interface Design and Evaluation
Software Processes Process should be
Extreme Programming.
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Adapting an Agent to a.
From Use Cases to Implementation
Architecture Issue in the New Disciple System
Presentation transcript:

Requirements for a General Agent Architecture for Agent-Based Simulation Environments Paul Scerri and Nancy Reed Department of Computer and Information Science Linköpings Universitet, S-581 83, Linköping, Sweden pausc,nanre@ida.liu.se

Outline Domain of interest is simulation environments We argue that agent architectures need to be evaluated by a range of engineering criteria Discuss some suggested criteria

Simulation Environments Highly complex, real-time training and testing simulation environments Agents used in place of humans Examples Air-combat simulation Disaster management RoboCup simulated soccer

Agent Architectures Define an agent architecture as a framework for developing agents e.g. PRS, Subsumption, Soar Wide range of fundamentally different architectures used in the domain Agents built using many different architectures capable performing most of the tasks required of agents in the domain

Criticism of Current Architecture Descriptions Literature focuses evaluation on capabilities of agents From the perspective of someone wanting to use agents rather than just build them it is equally important to know how difficult it was to build the agents Evaluation needs to be done as to how difficult it is to build agents with the required behavior

Engineering Considerations for Architecture Selection Accessibility Conciseness Reuse Generality Software Engineering Hardware Usage Learning

Accessibility How easy is it for non-agent experts to create agents with the architecture? How much does a designer need to understand about the architecture in order to create useful agents? Agent “gurus” only Any Tom, Dick or Mary

Conciseness How much programming is required to create agents capable of performing different tasks? Verbose Succinct

Reuse How easy is it to reuse parts of one specification in another specification All similar behavior None

Generality For what range of applications is the architecture useful? One specific application only General intelligence

Software Engineering Does the architecture support a software engineering methodology? How modular is the agent specification? Built in development methodology Ad hoc hacking

Debugging How difficult is it to trace from inappropriate agent behavior to incorrect specification elements? Is there any system support for debugging? Errors simple to locate and fix Impossible to locate errors

Hardware Usage What are the computational requirements for the agents? Requires Mainframe 1000s of agents on a PC

Learning Does the architecture provide support for machine learning? Abstract unsupervised learning Does not learn

Summary Most capabilities required of agents can be achieved Little emphasis is placed on how difficult it is for a programmer, or user, to develop agents to perform certain tasks We have proposed criteria by which we believe agent architectures should be evaluated in order for non-agent experts to find the architecture they need