Top-Down Incremental Development of Agents' Architecture for Emergency Management Systems: Management Systems: TOGA methodology HID, CAMO Seminars Series.

Slides:



Advertisements
Similar presentations
Computer Supported Cooperative Work by an Agent Oriented Software Engineering Approach: CSCW by AOSE Darlinton Carvalho
Advertisements

Andrea Maurino Web Service Design Methodology Batini, De Paoli, Maurino, Grega, Comerio WP2-WP3 Roma 24/11/2005.
2 Introduction A central issue in supporting interoperability is achieving type compatibility. Type compatibility allows (a) entities developed by various.
A-MAZE NEST-IDEA Seminar "Interdisciplinarity in Research" 22nd, June 2004 Applied Mathematics Ability Zone Adam Maria Gadomski (ENEAs contribution ) Towards.
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Improving System Safety through Agent-Supported User/System Interfaces: Effects of Operator Behavior Model Charles SANTONI & Jean-Marc MERCANTINI (LSIS)
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Modeling of Socio-cognitive Vulnerability of Human Organizations Modeling of Socio-cognitive Vulnerability of Human Organizations TOGA Meta-theory Approach.
OASIS Reference Model for Service Oriented Architecture 1.0
Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal.
Chapter 6: Design of Expert Systems
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
April 15, 2005Department of Computer Science, BYU Agent-Oriented Software Engineering Muhammed Al-Muhammed Brigham Young University Supported in part by.
SOFTWARE CRISIS SOLUTIONS? © University of LiverpoolCOMP 319slide 1.
Course Instructor: Aisha Azeem
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
On Roles of Models in Information Systems (Arne Sølvberg) Gustavo Carvalho 26 de Agosto de 2010.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 The Traditional Approach to Requirements
Chapter 2: Approaches to System Development
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 2 The process Process, Methods, and Tools
Software Engineering CS B Prof. George Heineman.
Requirements Analysis
CSE 303 – Software Design and Architecture
Knowledge representation
Cognitive Reasoning to Respond Affectively to the Student Patrícia A. Jaques Magda Bercht Rosa M. Vicari UNIVERSIDADE FEDERAL DO RIO GRANDE DO SUL BRASIL.
Universal Top SYNTEX Functional Architecture Building Working Document Adam Maria Gadomski, Vittorio Rosato ENEA    A Contribution to the SYNTEX Development.
EIDA Project ( Proposal ) Research and Technical Background Emergency Intelligent Decision Assistant: Emergency Intelligent Decision Assistant: Toolkit.
Managerial Intelligent Node for Decisional Emergency Support Energy Department Strategic Project Balducelli Claudio Bologna Sandro Gadomski Adam M. More.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 5-1 Chapter 5 Business Intelligence: Data.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
SOFTWARE DESIGN.
11 CORE Architecture Mauro Bruno, Monica Scannapieco, Carlo Vaccari, Giulia Vaste Antonino Virgillito, Diego Zardetto (Istat)
Content The system development life cycle
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
One or More Topologies ? One or More Topologies ? A methodological reflection IRRIIS Project, WP2.1 “Topology Analysis” Rome Meeting, 6,7 April 2006 IST.
Sub-Project III 4: CRESCO-SOC-COG Second Progress Report (15 February June 2007)
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Volgograd State Technical University Applied Computational Linguistic Society Undergraduate and post-graduate scientific researches under the direction.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Florian A. Twaroch Institute for Geoinformation and Cartography, TU Vienna Naive Semantic Interoperability Florian A. Twaroch.
RE-ENGINEERING AND DOMAIN ANALYSIS BY- NISHANTH TIRUVAIPATI.
College of Computer Science, SCU Computer English Lecture 1 Computer Science Yang Ning 1/46.
Software Quality Assurance and Testing Fazal Rehman Shamil.
RULES Patty Nordstrom Hien Nguyen. "Cognitive Skills are Realized by Production Rules"
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Knowledge Support for Modeling and Simulation Michal Ševčenko Czech Technical University in Prague.
From NARS to a Thinking Machine Pei Wang Temple University.
Primary Decision Support Technologies Management Support Systems (MSS)
Artificial Intelligence
Ontology From Wikipedia, the free encyclopedia
Chapter 6: Design of Expert Systems
Overview of System Engineering
Model-Driven Analysis Frameworks for Embedded Systems
Systems development life cycle (SDLC)
Top-Down Incremental Development of Agents' Architecture for Emergency
Managerial Intelligent Node for Decisional Emergency Support
PASSI (Process for Agent Societies Specification and Implementation)
Presentation transcript:

Top-Down Incremental Development of Agents' Architecture for Emergency Management Systems: Management Systems: TOGA methodology HID, CAMO Seminars Series This activity is realized in cooperation between La Sapienza University and ENEA: F.Delli Priscoli (Univ. La Sapienza, Rome), A.M.Gadomski (CAMO, ENEA), A.Caputo - thesis (Univ. La Sapienza - Engineering Dep., ENEA scholarship 2002/0362) Andrea Caputo, Adam Maria Gadomski, Franco Delli Priscoli May 2005 University of Rome La SapienzaItalian National Research Agency ENEA

Top-Down Incremental Development of Intelligent Agents' Architecture Intelligent Agents' Architecture: Problem Specification Intelligent Agents' Architecture: Problem Specification Existing Design & Programming styles (short soa) Existing Design & Programming styles (short soa) TOGA Theoretical Tool TOGA Theoretical Tool Method: Top-Down incremental development Method: Top-Down incremental development Emergency Management Test-Case Emergency Management Test-Case Conclusions Conclusions Prototype demonstration Prototype demonstration Presentation outline

Contents of the Caputos Thesis General request overiview General request overiview Contest of the simulation: Socio-Cognitive Engineering Contest of the simulation: Socio-Cognitive Engineering A TOGA proposal A TOGA proposal IPK monad IPK monad Universal Management Paradigms Universal Management Paradigms Example showed at SCEF 2003 Example showed at SCEF 2003 Intelligent Decision Support System Intelligent Decision Support System Modelling Disaster Domain Modelling Disaster Domain Disaster Propagation Disaster Propagation GEA GEA

NaturalSciences SoftwareTechnology ArtificialIntelligence Socio-CognitiveEngineering Contest of the Simulation From the Socio-cognitive contest we will arrive at a ripetitive, incremental, ricorsive, distribuite INTELLIGENT ENTITY [ 1 ]

IPK Informations( I ) Informations( I ) Preferences( P ) Preferences( P ) Knowledges( K ) Knowledges( K ) I = K x I I, I DD K x K K x = P s (K, I) UMP Universal Management Paradigm (UMP) is a functional architecture of organizational High-Intelligence for every natural and artificial High- Intelligent agents organization. It is characterized by: Complete Complete Relative Relative Recursive Recursive Incremental Incremental IPK paradigm and UMP describe essential functional properties of abstract highly intelligent entities, natural and artificial. A TOGA PROPOSAL [ 2 ] I KP SOCIO-COGNITIVE ENGINEERING PARADIGMS

structural assumptions: structural assumptions: -- Recursivity -- Recursivity -- Iterativness -- Iterativness -- Repetitivity -- Repetitivity -- Modularity -- Modularity They intend to minimize total axiomatic information employed by the theory. They intend to minimize total axiomatic information employed by the theory. methodological assumptions, which require completeness and congruence methodological assumptions, which require completeness and congruence of the problem conceptualization on every abstraction level. of the problem conceptualization on every abstraction level. terminological assumption, to reduce the number of terms as is possible. terminological assumption, to reduce the number of terms as is possible. The key TOGA paradigms (top assumptions/axioms) are divided on [ 3 ] : Conceptualization, Ontological, and Methodological TOGA Normative Meta-Assumptions

Three components: TAO : Basic conceptualization frame independent on represented domain of interest. independent on represented domain of interest. KNOCS : Axioms system for the real-world problem representation MRUS : Methodological RUles Systems Non ordered observations, knowledge, values TAO Conceptualizations KNOCS Conceptualization Goal-oriented Problem Model MRUS: Methodological Rules System They refers to an Abstract Intelligent Agent (AIA), his/her/its Domain-of-Activity and to the relations between them. Summarizing, what is it ? Complex-Knowledge Ordering Methodology (Meta-theory) Complex-Knowledge Ordering Methodology (Meta-theory) Problem Specification & Decision-Making Modelling Approach. (It has algebra property) Problem Specification & Decision-Making Modelling Approach. (It has algebra property) TOGA Meta-Modeling Framework

Personois: IPK Abstract Agent Model Axioms Model Axioms Repetivety Repetivety Modularity Modularity Recursivity Recursivity … I P K PK PK I LEVEL I I II META-LEVEL

Universal Management Paradigm COOPERATINGMANAGERMANAGERADVISOR SUPERVISOR EXECUTORINFORMER INFORMATION TASKS EXPERTISESCOOPERATION TASKSINFORMATION DISASTER DOMAIN Based Structure: Subjective, Incremental, Recursive Ref. [ 4 ]

Disaster Manager: simple model example InInInIn KP I1I1I1I1 KP I2I2I2I2 KP I3I3I3I3 KP Infrastructure Network Real Emergency Domain I KP Agent Manager Agent 1 Agent 2 Agent 3 Agent n I : Information P : Preferences K : Knowledge

Objectives of experiment: why? Practical vefification of the methodology by the designing a series of agents with incremental complexity and functionality. The prototypes have been developed in Object oriented C++ language. As a test case, we assumed an emergency situation caused by An explosion in a chemical plant where its consequences cause An intoxication of the water in a neighboring city.

On the base of the TOGA paradigms, we built an evolution line of the incremental design of Intelligent Agents aimed at the development of the model of an Intelligent Entity The representation of the abstract world of the Agent is: WORLDANIMATOR ABSOLUTEOBSERVER PERSONOIDANIMATORWORLDSIMULATORPROTO-PERSONOID In this image is showed the relations between the world of the Agent and the Human Utent. There are distinghished three different human roles, evidenced in the lighter boxes Definition of the Experiment Architecture

K Decomposition of different fields of the Agent Constrain Environment BodyDomain World Animator Personoid Animator Absolute Observer IP To describe the World Simulator and the Proto-Personoid and the interaction between them, will be used the following symbolization The IPK structure is seen from the social prespective according to the UMP paradigm. Infact in the Domain we can see the other different components of the UMP paradigm. DOMAIN SUPERVISOR ADVISORCOOPERATINGMANAGER INFORMEREXECUTOR EXPERIMENT: Architecture incrementing

IDSS: Intelligent Decision Support Systems IDSS: Software program that integrates human intellectual and computer capacities to improve decision making quality, in semi-structured problems situations [Keen, Scott-Morton, 1996] to improve decision making quality, in semi-structured problems situations [Keen, Scott-Morton, 1996] Provides active, partially autonomous Decisional Aid which involve human-like computational intelligence. Provides passive Informational Aid and Toolkits IDSS DSS When IDSS is important? amount of information necessary for the management is so large, or its time density is so high, that the probability of human errors under time constrains is not negligible. amount of information necessary for the management is so large, or its time density is so high, that the probability of human errors under time constrains is not negligible. coping with unexpected situation requires remembering, mental elaboration and immediate application of complex professional knowledge, which if not properly used, causes fault decisions. coping with unexpected situation requires remembering, mental elaboration and immediate application of complex professional knowledge, which if not properly used, causes fault decisions.

Modelling Disaster Domain: Disaster Prop. Map

Experiment Realization We created a general agent, which follows a simple set of rules. It represents a first interaction of the proto-personoid with the external world. Then, from this generic starting point, we decompose the various aspects of the agent, analysing the IPK monad which represent the core of the agent. The monad, as we said, is composed of three different parts (Information, Preferences and Knowledge), and in every new step of our decomposition, we increase the complexity of one of these parts. To focus this aspect of the analysis we introduce a scale of colours which represent the grade of the complexity of the analysed part of the system.

The main important results of the experiment are: modular and reproducible decomposition of the Personoid has been realized. modular and reproducible decomposition of the Personoid has been realized. its possible to obtain incrementally new specializations of the Personoid focalized on a more detailed problems its possible to obtain incrementally new specializations of the Personoid focalized on a more detailed problems The complexity of the problem ( functionality and architecture) can growth infinitely. The complexity of the problem ( functionality and architecture) can growth infinitely. Proto-Personoids produced in the design experiment RESULT S OF THE EXPERIMENT

Test Case: Disaster Domain Application of Emergency/Disaster Propagation Framework Events: Explosion and fire in chemical factory, Fire in the forest Emision of toxical substances by tubes to the river Water in City Aqueduct is toxic Water users are in danger. EMERGENCY MANAGER: Identification of intervention/vulnerable objects, goal of intervention and possible actions

Test Case: Disaster Propagation Map (DPM)

TEST Case: Time Diagram without intervention PROPAGATION OF EMERGENCY WITHOUT INTERVENTION

Evolution of the DPM without intervention Combined together the DPM with the Time Diagram without intervention, this evolution in time will be obtained Factory Forest Factory tubes River City Aqueduct Citizens Chicken Farm Others

GEA: IPK Cognitive Agent

Synthesis of the results of the work Documentation and validation of the TOGA Theory Documentation and validation of the TOGA Theory 25 Agents prototype realized 25 Agents prototype realized code lines written code lines written GEA prototype GEA prototype User friendly interface User friendly interface

Click hereClick here for demonstration Click here GEA: Demo

References TOGA Meta-theory Web page: toga.htm 4.