EIDA Project ( Proposal ) Research and Technical Background Emergency Intelligent Decision Assistant: Emergency Intelligent Decision Assistant: Toolkit.

Slides:



Advertisements
Similar presentations
Pat Langley Computational Learning Laboratory Center for the Study of Language and Information Stanford University, Stanford, California
Advertisements

Modelling with expert systems. Expert systems Modelling with expert systems Coaching modelling with expert systems Advantages and limitations of modelling.
Top-Down Incremental Development of Agents' Architecture for Emergency Management Systems: Management Systems: TOGA methodology HID, CAMO Seminars Series.
Improving System Safety through Agent-Supported User/System Interfaces: Effects of Operator Behavior Model Charles SANTONI & Jean-Marc MERCANTINI (LSIS)
S Y S T E M S E N G I N E E R I N G.
Main issues: • Why is reuse so difficult • How to realize reuse
Lecture # 2 : Process Models
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
ENEA’s Virtual e-Seminar FPN- RADCASS Unit New Research Ideas 2008 Super-Safety Constrains for Nuclear On-Line Monitoring Strategy Adam Maria Gadomski,
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
4.1 Blended approaches: Information Engineering IMS Information Systems Development Practices.
University of Minho School of Engineering Algoritmi Center Uma Escola a Reinventar o Futuro – Semana da Escola de Engenharia - 24 a 27 de Outubro de 2011.
Chapter 6: Design of Expert Systems
Knowledge Acquisition CIS 479/579 Bruce R. Maxim UM-Dearborn.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
An Environmental Multiagent Architecture for Health Management Francesco Amigoni Nicola Gatti.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
[ §4 : 1 ] 4. Requirements Processes II Overview 4.1Fundamentals 4.2Elicitation 4.3Specification 4.4Verification 4.5Validation Software Requirements Specification.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
Architecture Business Cycle
1 Computer Group Engineering Department University of Science and Culture S. H. Davarpanah
Universal Top SYNTEX Functional Architecture Building Working Document Adam Maria Gadomski, Vittorio Rosato ENEA    A Contribution to the SYNTEX Development.
SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2007.
C2-SENSE T.3.5 & WP4 Organizational Interoperability Ankara.
Managerial Intelligent Node for Decisional Emergency Support Energy Department Strategic Project Balducelli Claudio Bologna Sandro Gadomski Adam M. More.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
SOFTWARE DESIGN.
RELATIONAL FAULT TOLERANT INTERFACE TO HETEROGENEOUS DISTRIBUTED DATABASES Prof. Osama Abulnaja Afraa Khalifah
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
Measuring the Quality of Decisionmaking and Planning Framed in the Context of IBC Experimentation February 9, 2007 Evidence Based Research, Inc.
Project Life Cycles.
1 INTEROP WP1: Knowledge Map Michaël Petit (U. of Namur) January 19 th 2004 Updated description of tasks after INTEROP Kickoff Meeting, Bordeaux.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
1 Introduction to Software Engineering Lecture 1.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Creating a European entity Management Architecture for eGovernment CUB - corvinus.hu Id Réka Vas
GREGORY SILVER KUSHEL RIA BELLPADY JOHN MILLER KRYS KOCHUT WILLIAM YORK Supporting Interoperability Using the Discrete-event Modeling Ontology (DeMO)
One or More Topologies ? One or More Topologies ? A methodological reflection IRRIIS Project, WP2.1 “Topology Analysis” Rome Meeting, 6,7 April 2006 IST.
APPLY FUNCTIONAL MODELING TO CONSEQUENCE ANALYSIS IN SUPERVISION SYSTEMS Present by Xinxin Zhang 1 Morten Lind 1, Giulio Gola 2,
Chapter 4 Decision Support System & Artificial Intelligence.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Model Integrated Computing and Autonomous Negotiating Teams for Autonomic Logistics G.Karsai (ISIS) J. Doyle (MIT) G. Bloor (Boeing)
Thomas L. Gilchrist Testing Basics Set 3: Testing Strategies By Tom Gilchrist Jan 2009.
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Rule Engine for executing and deploying the SAGE-based Guidelines Jeong Ah Kim', Sun Tae Kim 2 ' Computer Education Department, Kwandong University, KOREA.
1 Sobah Abbas Petersen Adjunct Associate Professor, NTNU Researcher, Sintef TDT4252 Modelling of Information Systems Advanced Course TDT4252,
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
SECURE TROPOS Michalis Pavlidis 8 May Seminar Agenda  Secure Tropos  History and Foundation  Tropos  Basics  Secure Tropos  Concepts / Modelling.
Pedro Emanuel Botelho Espadinha da Cruz
Intelligent Systems Development
SDLC: System Development Life Cycle
Chapter 6: Design of Expert Systems
UNIFIED PROCESS.
Software Design Methodology
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Technical Management Processes
Assoc. Prof. Dr. Syed Abdul-Rahman Al-Haddad
Top-Down Incremental Development of Agents' Architecture for Emergency
Gio.net First Proposal to discuss during Barcelona Meeting
Managerial Intelligent Node for Decisional Emergency Support
Presentation transcript:

EIDA Project ( Proposal ) Research and Technical Background Emergency Intelligent Decision Assistant: Emergency Intelligent Decision Assistant: Toolkit for Coordinated Emergency Management Toolkit for Coordinated Emergency Management by Claudio Balducelli Sandro Bologna, Adam Maria Gadomski ENEA, July 1995

EIDA - Project (proposal) Summary Project Goals Project Methodologies and Tools Project Realization amg

EIDA Project Toolkit : 1) Domain problem conceptualization tools 2) Modeling tools 3) Methodology, methods and techniques 4) Software design tools 5) Software modules Project Goals : Development of a domain-oriented toolkit and its validation for a class of Emergency Management active Decision Support Systems. amg

active Decision Support Systems Goal-driven decisional support which is based on: user role-model domain model M-M cooperation model EIDA Project

Project Methodology and Tools - TOGA Top-down Object-based Goal-oriented Approach Top-down Object-based Goal-oriented Approach Basic conceptual couple: Basic paradigmes: Environment Intelligent Agent interaction

Top-down and Object-based : EIDA Project Object-based Top-down Structural decomposition of concepts Representation of concepts in term of objects and relations

EIDA Project Goal-oriented (example): E-M goal (losses, risk, intervention,..), Domain( losses generation events, risk objects,..) search Maps (...) search Toxic substances risk model support of

EIDA Project Project main phases 1 - User Requirement specification 2 - Modeling 3 - Tools prototyping and verification 4- Demos (user oriented applications) validation

EIDA Project Generic Emergency Management Scenario N-th Decompositon level: Model 1Model 2Model 3Model n Sub-Model 1.. Sub-Model 2.. Sub-Model m Architecture of EIDA kernel Architecture of an ideal emergency manager Verification Validation... modification integration selection Prototype 1 Prototype m Prototype 2... l User oriented demos 4

Formalization of the Applicative Domain Wp1 Summary - Domain of EM Activity - EM Activities and Tasks - EM operators organizational structure

Formalization of the Applicative Domain Wp1 - Domain of EM Activity -> Reusing Muster Model - EM Activities and Tasks -> Use Task Analysis - Agents organizational structure -> ISEM Model Methods and Tools Muster and ISEM are EU projects.

Summary - Definition of a Common Terminology - Single Agent Model - Decisional Model Based on Agents Cooperation Definition of Models and System Requirements Wp2

Methods and Tools Single Agent Model ( TOGA Th.): Physical Domain of Activity Actions Data acquisition New Information Decisions Goals AD P K P K Abstract - Domain; a representation of Physical Domain of Activity Agent Preference System Agent Knowledge System

Definition of Models and System Requirements Wp2 Methods and Tools -> GEMS top-activities loop Detecting/ monitoring Diagnostics Previsions Decision- Making Domain modelsEmergency org. models What-if simul. Role-preferences Information acquisition: with/without request Cause searching Consequence searching Action / task choice Comunication Agent Diagnostic Agent Evaluator Agent Action Selector Agent

Methods and Tools Diagnostic agent structure: Domain representation -> focused on the Causal Trees of the Emergency Events and Risk Objects Preference System -> the agent goal is to send to the evaluator agent more and more precise informations about event causes and event characterization Knowledge System -> has the task to execute Cause Searching Process. It could be based on Case Based Reasoning approach Definition of Models and System Requirements Wp2

Methods and Tools Evaluator agent structure: Domain representation -> focused on Causal Trees of the Emergency Events and Risk Objects Preference System -> the agent goal is to refine evaluations performing a Consequence Searching Process Knowledge System -> is supported by Numerical Simulators and/or executes a qualitative Case Based Reasoning Definition of Models and System Requirements Wp2

Emergency propagation map primary event registrated event cause searching model consequence searching model Domain model Domain model - risk Definition of Models and System Requirements Wp2 A.M.Gadomski, 1995

Methods and Tools Action selector agent structure: Domain representation -> focused on organizational emergency structure, management resources and physical layout; Preference System -> the agent goal is to choice the best recovery actions and procedures on the basis of evaluation results; Knowledge System -> is composed by an action selector and an action executor. The action selector could be supported by a a Rule Based processing. Definition of Models and System Requirements Wp2

Specification of EIDA ToolKit Kernel Wp3 Wp3 Methods and Tools - Choose of adeguate final software environment. - Software functional Specification and Testing (for the different agents) using a Case Tool - Design a Protocol for Data exchange between the agents - Design the Users Interface architecture

Implementation and Validation of EIDA ToolKit Kernel Wp4 -Wp5 Wp4 -Wp5 Methods and Tools - Incremental implementation of the EIDA software Agents - Verification and Validation of the produced Kernel modules respect at least two different Users oriented prototypes. - Generalization of the produced ToolKit to support its utilization in other application of the same class

EIDA proposal Toolkit for Coordinated Emergency Management Set of decision-support tools (agents) Intelligent interface (agent) EIDA System Emergency manager Coordinator