Participation Components for Holding Roles in MultiAgent Systems Protocols Christophe Sibertin-Blanc, IRIT Toulouse Nabil Hameurlain, LUPPIA Pau.

Slides:



Advertisements
Similar presentations
Knowledge Based Scripting. Effective communication requires not only that people share knowledge but also that they know they share knowledge." 2.
Advertisements

Logistics & Channel Management
Identifying, Modifying, Creating, and Removing Monitor Rules for SOC Ricardo Contreras Andrea Zisman
15 th International Conference on Design Theory and Methodology 2-6 September 2003, Chicago, Illinois Intelligent Agents in Design Zbigniew Skolicki Tomasz.
Software Architecture in Practice (3 rd Ed) Understanding Quality Attributes Understanding the following: How to express the qualities we want our architecture.
Control and Entrepreneurial Activity. E  Organizations need control systems Policies, procedures, and rules are needed to ensure order, achieve coordination,
Database Software Creation Process Arvin Meyer, MCP, MVP
What is Strategic HRM? Strategic human resource management: The pattern of planned human resource deployments and activities intended to enable an organization.
1.
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
Effective Coordination of Multiple Intelligent Agents for Command and Control The Robotics Institute Carnegie Mellon University PI: Katia Sycara
Variability Oriented Programming – A programming abstraction for adaptive service orientation Prof. Umesh Bellur Dept. of Computer Science & Engg, IIT.
Software Connectors. Attach adapter to A Maintain multiple versions of A or B Make B multilingual Role and Challenge of Software Connectors Change A’s.
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Software Connectors Software Architecture Lecture 7.
Agent-Based Acceptability-Oriented Computing International Symposium on Software Reliability Engineering Fast Abstract by Shana Hyvat.
SOCIAL MARKETING GÜLŞAH KILIÇKAYA EMRE AYDINLIOĞLU DİBA TAŞDEMİR OYA MURATOĞLU 1.
1 Computer Systems & Architecture Lesson 1 1. The Architecture Business Cycle.
© 2006, Cognizant Technology Solutions. All Rights Reserved. The information contained herein is subject to change without notice. Automation – How to.
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Software Connectors Software Architecture Lecture 7.
Software Architecture in Practice (3rd Ed) Introduction
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
TDT4252/DT8802 Exam 2013 Guidelines to answers
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
Architecture Business Cycle
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
Inspire Personal Skills Interpersonal & Organisational Awareness Developing People Deliver Creative Thinking & Problem Solving Decision Making, Prioritising,
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
International marketing strategy segmentation. Factors influencing IMS Corporate strategy Goals, objectives for the particular market Customer segmentation.
Software Architecture and Design Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 23 rd, 2003.
Lecture 7: Requirements Engineering
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Identity Management: A Technical Perspective Richard Cissée DAI-Labor; Technische Universität Berlin
Military Family Services Program Participant Survey Briefing Notes.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
What’s MPEG-21 ? (a short summary of available papers by OCCAMM)
Theories of Learning: Cognitive Theories Dr. K. A. Korb University of Jos 15 May 2009.
Queen’s Management & Leadership Framework
1 Object Oriented Logic Programming as an Agent Building Infrastructure Oct 12, 2002 Copyright © 2002, Paul Tarau Paul Tarau University of North Texas.
Distributed Models for Decision Support Jose Cuena & Sascha Ossowski Pesented by: Gal Moshitch & Rica Gonen.
Working in Partnership
CSE 303 – Software Design and Architecture
Chap-2(hrm), MCA HRM system, international model of HRM, concept and framework for strategic HRM, line management responsibility for HRM, HRM and organizational.
Software Connectors Acknowledgement: slides mostly from Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic,
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Software Connectors in Practice Software Architecture.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.
Cognitive Architectures and General Intelligent Systems Pay Langley 2006 Presentation : Suwang Jang.
Introduction to: Tycoon A Market Based Resource Allocation System by Alejandro García López.
LECTURE 4 WORKING WITH OTHERS. Definition Working with others : is the ability to effectively interact, cooperate, collaborate and manage conflicts with.
The Four Enablers of Strategy 24 February The Four Enablers of Strategy Systems Structure Capability CultureStrategy.
Topics on Web Services COMP6017 Dr Nicholas Gibbins –
Intelligent Agents: Technology and Applications Unit Five: Collaboration and Task Allocation IST 597B Spring 2003 John Yen.
Computing Price Trajectories in Combinatorial Auctions with Proxy Bidding Jie Zhong Gangshu Cai Peter R. Wurman North Carolina State University.
Data Grids, Digital Libraries and Persistent Archives: An Integrated Approach to Publishing, Sharing and Archiving Data. Written By: R. Moore, A. Rajasekar,
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
Chapter 5 ASX Guidelines for Listed Companies
Software Engineering Development of procedures and systematic applications that are used on electronic machines. Software engineering incorporates various.
Organization and Knowledge Management
Chapter 11: Usability © Len Bass, Paul Clements, Rick Kazman, distributed under Creative Commons Attribution License.
STRATEGIC MANAGEMENT AND BUSINESS POLICY THIRD EDITION AZHAR KAZMI Chapter 1 Introduction to strategic management and business policy.
Database System Architecture
Outline What is governance and what does it comprise?
Software Architecture Lecture 7
Software Architecture Lecture 7
Dept. of Computation, UMIST
Software Architecture Lecture 7
Ponder policy toolkit Jovana Balkoski, Rashid Mijumbi
UML Design for an Automated Registration System
Software Architecture Lecture 6
Information system analysis and design
Presentation transcript:

Participation Components for Holding Roles in MultiAgent Systems Protocols Christophe Sibertin-Blanc, IRIT Toulouse Nabil Hameurlain, LUPPIA Pau

21 oct. 2004, ESAW'04 2 Organisation-centred vs Individu-centred view on a MultiAgent vs System Accounting for engineering issues: Reusability, maintainability, interoperability, scalability … The system view: to ensure –Objectives –Rules –Tasks allocation –Resources sharing –Operation: security, performance, … The agent view: to allow – Desire, intention – Autonomy – Skills – Abilities – Openess, negociation, intensive interactions, …

21 oct. 2004, ESAW'04 3 Organisation-centred vs Individu-centred view on a MultiAgent vs System To conciliate the three perspectives, Separate the Concerns: the organisational features are treated as first-class entities at the specification, design and runtime levels => the organisational constraints are enforced => agents focus on their own functional concerns The interaction pattern: Protocols

21 oct. 2004, ESAW'04 4 Plan 1.The system view: Moderator Approach 2.The agent view: Participation Component 3.Example 4.Conclusion

21 oct. 2004, ESAW'04 5 The Moderator Approach: Protocols Items in the definition of a protocol: –Roles agents may hold –Types of interventions agents may perform –Initial state and final state –Casting constraints on the holding of roles –Behavior constraints on the performance of interventions A Conversation = a process following the rules of a protocol

21 oct. 2004, ESAW'04 6 The Moderator Approach: Architecture Moderator Functional Agent Library of Protocols Server of Conversations Functional agent direct contributor to the system’s goals, has the needed skill and abilities Moderator agent that monitor 1 conversation Grant roles to agents Manages the state of the conversation Receives and process the agents’ interventions Server of Conversation database on the available conversations and protocols Library of protocols Stores the definitions of protocols

21 oct. 2004, ESAW'04 7 Library of Protocols Server of Conversations (1) (3) (2) (3) (4) (5) (4) (5) The Moderator Approach: Operation (1) Asks for the creation of a new conversation (2) Looks for the protocol’s agent type (3) Instanciates a new moderator (4) Gives the moderator’s identity (5) Takes part in the conversation End : the Moderator terminates (5)

21 oct. 2004, ESAW'04 8 The Moderator Approach: properties System’s point of view: –The rules are respected Agents’ point of view: –They are relieved of watching over others –The interaction space is sure and well-defined –The interaction space is large

21 oct. 2004, ESAW'04 9 The Moderator Approach: what about the Agents’ autonomy? Agents autonomy consists in deciding: –Which conversation to initiate, and in which conversation to enter? –While taking part in a conversation, Which intervention and When? The effective use of this autonomy requires a deep knowledge of each protocol –Hard-coded into agent? NO –Declarative? –Delegated?

21 oct. 2004, ESAW'04 10 Plan 1.The system view: Moderator Approach 2.The agent view: Participation Component 3.Example 4.Conclusion

21 oct. 2004, ESAW'04 11 Participation Components: Principle To distinguish the strategic from the tactic knowledge Strategic knowledge: –has a large applicability, not bulky –must be kept by the agent, close to its own objectives Tactic knowledge: –specific to each role of each protocol, voluminous –delegated to a specific component: a Participation

21 oct. 2004, ESAW'04 12 Participation Components: architecture Library of Protocols Conversation Server (1) (4) (2) (3) (1) Asks for a role (2) Grants the role and creates a new participation (3) Strategic interactions (4) Tactic interactions End : the moderator terminates Participation Has the tactic knowledge to intervene in the conversation on the behalf of the functional agent

21 oct. 2004, ESAW'04 13 Participation Components: structure of a participation Strategic variables Tactic engine Role’s behavior AGENTMODERATOR The variables of the strategic kit The protocol’s behaviour constraints The strategy‘s operational semantics

21 oct. 2004, ESAW'04 14 Plan 1.The system view: Moderator Approach 2.The agent view: Participation Component 3.Example 4.Conclusion

21 oct. 2004, ESAW'04 15 Example: strategies of the bidder role in an auction Strategic choices: –to enter in an auction, if the good on sale matches the good wanted –the upper bound of bidding for that good firmly decidedbored basket -- thriftyhesitating wanted / proposed good adequation accepted financial effort

21 oct. 2004, ESAW'04 16 Example: strategic kit for the bidder role wanted: Goods;/object seeked adequacy_rate: Percentage /wanted--proposed matching (matching(wanted, o: Goods) > adequacy_rate): Boolean /enter in the auction for o? financing_rate: Percentage;/financing effort available_amount: Currency;/financial resources value(o: Goods): Currency; /evaluates of the price of o max_price: Currency; /the amount it is ready to pay

21 oct. 2004, ESAW'04 17 Example: The participation component /Agent type of the participation for the bidder role in a fish-market auction R_Agent Bidder_Fishmarket; object: Goods; max_price, p: Currency; RBTS R_to_bid ("OK") // to_pay (p) [p<=max_price] / to_bid() [p>max_price]/ newprice() R_new_price ("End") / object := Nul / p:= Current_price() R_to_pay (f)/ object := f R_newprice (p) / 0 12 for the bidder role in a fish-market auction R_to_bid(p) /

21 oct. 2004, ESAW'04 18 Conclusion The protocols' rules are strictly respected and agents have the means to exercise their autonomy within the remaining indeterminism Agents have access to a number of protocols, because strategic K has a large applicability and is not bulky Agents can have several concurent participations in conversations A methodology to design Protocols usable as resources Engineering issues: reusability, clear design, integrity, …