Indicator suggestions Circles of Sustainability 1. The Application2. Agent-oriented and GORITE3. Agent architecture 4. Dummy Project5. Demonstration.

Slides:



Advertisements
Similar presentations
Software Requirements
Advertisements

K. Ingram1November 2000 Object Orientated Analysis and Design - Contents When to use OO? What is OO? Unified Modelling Language OO Methodologies: –Object.
Peer-to-peer and agent-based computing Agent-Based Computing: tools, languages and case studies (Cont’d)
1 Update on Learning By Observation Learning from Positive Examples Only Tolga Konik University of Michigan.
COMP4710 Senior Design Process Documentation and Deliverables.
Science & The Environment
Chapter 7 – Object-Oriented Design
Yiannis Demiris and Anthony Dearden By James Gilbert.
Informatics 43 – May 7, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases  No.
Water Conservation and Consumption…a different story! Sara Syswerda Feb. 24, 2010.
SWE Introduction to Software Engineering
Software Requirements
Prometheus Design Tool (CAFnE Extension) v0.1: WeatherApplication.pd PDT/CAFnE Workspace is organized into four main panes Component Descriptor pane contains.
1 Software Testing and Quality Assurance Lecture 14 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
1 Measuring Performance of Resource Management Responses Rich Juricich (DWR) David Groves (RAND)
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
INTRODUCTION TO ARTIFICIAL INTELLIGENCE Massimo Poesio Intelligent agents.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Introduction to Jadex programming Reza Saeedi
ARTIFICIAL INTELLIGENCE [INTELLIGENT AGENTS PARADIGM]
Lesson 7 Guide for Software Design Description (SDD)
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements.
Lecture nu 9 Presented by: Dr. Zainab O.Saeed The way in which an individual perceives the environment; the process of evaluating and storing information.
Spoken dialog for e-learning supported by domain ontologies Dario Bianchi, Monica Mordonini and Agostino Poggi Dipartimento di Ingegneria dell’Informazione.
Software Requirements Presented By Dr. Shazzad Hosain.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Requirements Documentation CSCI 5801: Software Engineering.
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
NAVEEN AGENT BASED SOFTWARE DEVELOPMENT. WHAT IS AN AGENT? A computer system capable of flexible, autonomous (problem-solving) action, situated in dynamic,
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 6 Slide 1 Software Requirements.
The Prometheus-ROADMAP Methodology Lin Padgham in collaboration with Leon Sterling and Michael Winikoff School of Computer Science and IT, RMIT University,
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
WATER SCARCITY. Water stress and Water scarcity occur when the demand for water exceeds the available amount during a certain period or when poor quality.
Intelligent Agents RMIT Prof. Lin Padgham (leader) Ass. Prof. Michael Winikoff Ass. Prof James Harland Dr Lawrence Cavedon Dr Sebastian Sardina.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Design Reuse Earlier we have covered the re-usable Architectural Styles as design patterns for High-Level Design. At mid-level and low-level, design patterns.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Earth's Oceans: The World's Next Major Water Resource By Allison Lambert.
M1G Introduction to Programming 2 3. Creating Classes: Room and Item.
Rational Agency CSMC Introduction to Artificial Intelligence January 8, 2004.
 An Information System (IS) is a collection of interrelated components that collect, process, store, and provide as output the information needed to.
Explainable Adaptive Assistants Deborah L. McGuinness, Tetherless World Constellation, RPI Alyssa Glass, Stanford University Michael Wolverton, SRI International.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
® IBM Software Group © 2007 IBM Corporation Module 3: Creating UML Diagrams Essentials of Modeling with IBM Rational Software Architect, V7.5.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Software Engineering, COMP201 Slide 1 Software Requirements BY M D ACHARYA Dept of Computer Science.
Supporting the design of interactive systems a perspective on supporting people’s work Hans de Graaff 27 april 2000.
Intelligent Agents Chapter 2. How do you design an intelligent agent? Definition: An intelligent agent perceives its environment via sensors and acts.
AlburyCity’s Sustainability Comms for Coordination & Cooperation.
Social Simulation of Rescue Teams' Dynamic Planning João Ulisses, Rosaldo J. F. Rossetti, João E. Almeida, Brígida Mónica Faria, presented by: Luis Paulo.
1 Software Requirements Descriptions and specifications of a system.
WATER SCARCITY. Water stress and Water scarcity occur when the demand for water exceeds the available amount during a certain period or when poor quality.
Case Study -- Weather system
Chapter 5 – Design and Implementation
Technology And The Environment
Chapter 4 – Requirements Engineering
Chapter 9 Requirements Modeling: Scenario-Based Methods
Software Requirements
Design and Implementation
Analysis models and design models
Ecological Footprints
Object-Oriented Software Engineering
Applying Use Cases (Chapters 25,26)
Applying Use Cases (Chapters 25,26)
UML Design for an Automated Registration System
Presentation transcript:

Indicator suggestions Circles of Sustainability 1. The Application2. Agent-oriented and GORITE3. Agent architecture 4. Dummy Project5. Demonstration

2 The Application Circles of Sustainability – Indicator suggestions General Diagram of the application architecture

Reminder : Use Case 3 3 The Application Circles of Sustainability – Indicator suggestions Use Case 3: Selection of Indicators 1.What existing proto-indicators are already captured that relate to the critical issues. 2. Browse knowledge-base of all indicators for indicators that relate to the critical issues. 3. Identify any required new indicators that relate to critical issues and add indicator to knowledge-base. 4. For each critical issue choose indicators from candidates (includes selecting parameters, weighting importance/relevance, targets). 5. Check/test/warn that all domains and all critical issues are covered by at least one indicator. From the project Wiki

Agent-Oriented & GORITE Agent System 4  Agent System  Percept / Action  GORITE  Goals / Plans  Beliefsets Circles of Sustainability – Indicator suggestions  Group of agents, group of reasoning entities interacting with their environment.  Opposite: external environment.  1 thread, multiple processes  1 Agent System per project

Agent-Oriented & GORITE Percepts / Actions 5  Agent System  Percept / Action  GORITE  Goals / Plans  Beliefsets Circles of Sustainability – Indicator suggestions  Percept: the elements external to the Agent System, which it is able to perceive. Representation of a percept in PDT  Action: the elements that the Agent System perform on its external environment. Representation of an action in PDT

Agent-Oriented & GORITE GORITE 6  Agent System  Percept / Action  GORITE  Goals / Plans  Beliefsets Circles of Sustainability – Indicator suggestions  GORITE, or Goal Oriented Teams: library written in Java language.  Created in RMIT.  Framework supporting Agent-Oriented development.  Includes a graphical design tool generating code structure.

Agent-Oriented & GORITE Goals / Plans 7  Agent System  Percept / Action  GORITE  Goals / Plans  Beliefsets Circles of Sustainability – Indicator suggestions  Goal: an intention that an Agent has.  Plan: predefined sequence of actions performed by an Agent to achieve a goal. In GORITE:  BDI Goal: generates new intentions, triggering others goals.  Sequence Goal: succeed if all its sub-goals succeed.  Condition Goal: succeed if any of its sub-goals succeed.  Task Goal: equivalent of a plan. Actual sequence of actions. Representation of a plan in PDT

Agent-Oriented & GORITE Beliefsets 8  Agent System  Percept / Action  GORITE  Goals / Plans  Beliefsets Circles of Sustainability – Indicator suggestions  Internal data maintained by an Agent about what it believes.  Beliefsets are used to reason. Representation of a belief in PDT

9 Agent Architecture Circles of Sustainability – Indicator suggestions Agent Interface

10 Agent Architecture Circles of Sustainability – Indicator suggestions Agent Interface

11 Agent Architecture Circles of Sustainability – Indicator suggestions PDT Design Agent System Percepts Actions Agent

12 Agent Architecture Circles of Sustainability – Indicator suggestions PDT Design “Details Specifications” Agent Use Case 2 Use Case 4 Use Case 3

13 Agent Architecture Circles of Sustainability – Indicator suggestions PDT Design “Select Candidates indicators” Capability

“Provide Indicator Suggestions” Capability 14 Agent Architecture Circles of Sustainability – Indicator suggestions PDT Design 1 2 3

15 Dummy Project Circles of Sustainability – Indicator suggestions Water Crisis: Description: Water crisis is a term used to refer to the world’s water resources relative to human demand. The term has been applied to the worldwide water situation by the United Nations and other world organizations. General Issue: Overall scarcity of usable water and water pollution. Normative Goal: Have enough water for everybody and reduce water pollution. Critical Issues:  Inadequate access to drinking water  Inadequate access to water for sanitation  Groundwater over-drafting  Overuse and pollution of Water: o Water Overuse o Water Pollution o Harming biodiversity  Conflict for water Source: Wikipedia – article “Water Crisis”

16 Dummy Knowledge Base Circles of Sustainability – Indicator suggestions  Rain Amount: Average amount of rain (in mm) this year. Ecology > Earth, Water and Air  Bushfires: Number of important bushfires (more than 1000ha burnt) this year. Ecology > Other Target: 1  Water supply: The total water supply of the territory (in m3). Ecology > Earth, Water and Air  Water Consumption / Person: The water consumption this year (in m3). Economy > Consumption and Leisure  Number of Dams: The number of dams in the region. Ecology > Building and Infrastructure  Number of crimes: The number of crimes recorded by police last year. Politic > Conflict and Insecurity

Demonstration 17Circles of Sustainability – Indicator suggestions