A Goal-Based Organizational Perspective on Multi-Agent Architectures Manuel Kolp † Paolo Giorgini ‡ John Mylopoulos † † Department of Computer Science.

Slides:



Advertisements
Similar presentations
©2003, Karl Aberer, EPFL, School of Computer and Communication Sciences Some Requirements for Semantic Web Serivce from CROSSFLOW and OPELIX Karl Aberer.
Advertisements

An Approach to Wrap Legacy Applications into Web Services Wesal Al Belushi, Youcef Baghdadi Department of Computer Science, Sultan Qaboos University, Sultanate.
Database System Concepts and Architecture
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Social Structures in Tropos Manuel KolpPaolo GiorginiJohn Mylopoulos U Louvain U Trento U Toronto U Louvain U Trento U Toronto First Tropos Workshop, Trento,
Systems Analysis and Design, 7e Kendall & Kendall
Chapter 1 Foundations of Information Systems in Business.
0 General information Rate of acceptance 37% Papers from 15 Countries and 5 Geographical Areas –North America 5 –South America 2 –Europe 20 –Asia 2 –Australia.
Chapter 21 Successfully Implementing The Information System
Reseach in DistriNet (department of computer science, K.U.Leuven) General overview and focus on embedded systems task-force.
Application architectures
Quality is about testing early and testing often Joe Apuzzo, Ngozi Nwana, Sweety Varghese Student/Faculty Research Day CSIS Pace University May 6th, 2005.
Chapter 9: Moving to Design
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Overview of Database Languages and Architectures.
Course Instructor: Aisha Azeem
Database Administration Chapter 16. Need for Databases  Data is used by different people, in different departments, for different reasons  Interpretation.
Application architectures
A Goal-Based Organizational Perspective on Multi-Agent Architectures Manuel Kolp Department of.
A Requirement-Driven Development Methodology Jaelson Castro † Manuel Kolp ‡ John Mylopoulos ‡ ‡ Department of Computer Science University of Toronto University.
Organization-Driven System Development Building Agent Software for E-Business Manuel Kolp
Chapter 6 – Architectural Design Lecture 2 1Chapter 6 Architectural design.
Chapter 2 E-Marketplaces: Structures, Mechanisms, Economics, and Impacts.
Chapter 10 Architectural Design
Chapter 9 Elements of Systems Design
* SRA Division CoopIS- September Extending Multi-Agent Cooperation by Overhearing Floriano Zini SRA Division - ITC-irst, Povo (Trento) - Italy Joint.
1 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
SecureTropos ST-Tool A CASE tool for security-aware software requirements analysis Departement of Information and Communication Technology – University.
Copyright © 2004 by South-Western, a division of Thomson Learning, Inc. All rights reserved. Developed by Cool Pictures and MultiMedia Presentations.
 DATABASE DATABASE  DATABASE ENVIRONMENT DATABASE ENVIRONMENT  WHY STUDY DATABASE WHY STUDY DATABASE  DBMS & ITS FUNCTIONS DBMS & ITS FUNCTIONS 
Chapter 1 Lecture 2 By :Jigar M Pandya WCMP 1. Architecture of Mobile Computing The three tier architecture contains the user interface or the presentation.
Implicit An Agent-Based Recommendation System for Web Search Presented by Shaun McQuaker Presentation based on paper Implicit:
Evaluation of a Publish/Subscribe System for Collaboration and Mobile Working Collaborative Advertising over Internet with Agents Independent Study: Wireless.
CHAPTER 8 Marketing for E-commerce
TROPOS Derived from the Greek tropé, which means easily changeable, also easily adaptable. Presented By: Varun Rao Bhamidimarri.
Negotiation Protocol for Agile Collaboration in e-Science Zeqian Meng, John M. Brooke School of Computer Science, University of Manchester October 29th,
4 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved. Computer Software Chapter 4.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Design Concepts By Deepika Chaudhary.
A Social Organization Perspective on Software Architecture Manuel KolpJaelson CastroJohn Mylopoulos Department of Computer Science University of Toronto.
ATAL - Seattle, August 1 st, A Knowledge Level Software Engineering Methodology for Agent Oriented Programming The Tropos framework Fausto Giunchiglia.
ATAL - Seattle, August 1 st, A Knowledge Level Software Engineering Methodology for Agent Oriented Programming The Tropos framework Fausto Giunchiglia.
MANAGING DATA RESOURCES ~ pertemuan 7 ~ Oleh: Ir. Abdul Hayat, MTI.
E-Commerce Prof. Ir. Kudang B. Seminar, MSc, PhD Direktur Komunikasi & Sistem Informasi IPB Bogor, 12 Nopember 2008.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
Concepts in Enterprise Resource Planning Fourth Edition
Framework of a Simulation Based Shop Floor Controller Using HLA Pramod Vijayakumar Systems and Industrial Engineering University of Arizona.
Intelligent Agents. 2 What is an Agent? The main point about agents is they are autonomous: capable of acting independently, exhibiting control over their.
Introspecting Agent-Oriented Design Patterns Manuel Kolp, T. Tung Do, Stéphane Faulkner and T. T. Hang Hoang Presented by Rachel Bock, Sam Shaw, Nicholas.
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
 2001 John Mylopoulos STRAW’ Software Architectures as Social Structures John Mylopoulos University of Toronto First ICSE Workshop titled “From.
Distributed Database Management Systems. Reading Textbook: Ch. 1, Ch. 3 Textbook: Ch. 1, Ch. 3 For next class: Ch. 4 For next class: Ch. 4 FarkasCSCE.
Chapter 13 설계 개념 Architectural Design 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim for the book “Software Engineering: A Practitioner’s.
Foundations of Information Systems in Business
System A system is a set of elements and relationships which are different from relationships of the set or its elements to other elements or sets.
Database Environment Chapter 2. The Three-Level ANSI-SPARC Architecture External Level Conceptual Level Internal Level Physical Data.
Electronic Business: Concept and Applications Department of Electrical Engineering Gadjah Mada University.
SECURE TROPOS Michalis Pavlidis 8 May Seminar Agenda  Secure Tropos  History and Foundation  Tropos  Basics  Secure Tropos  Concepts / Modelling.
9 Systems Analysis and Design in a Changing World, Fifth Edition.
Managing Data Resources File Organization and databases for business information systems.
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
Patterns -- Manuel Kolp Dept of Information Engineering and Computer Science 11b. Reference Models and Organizational Patterns Reference Models.
CompSci 280 S Introduction to Software Development
Distributed Database Management Systems
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
MANAGING DATA RESOURCES
Design Model Like a Pyramid Component Level Design i n t e r f a c d s
Software models - Software Architecture Design Patterns
Chapter 9 Architectural Design.
Agent-oriented Software Engineering Methodologies
Adaptibility Patterns of Multi-Agent Organizations
Presentation transcript:

A Goal-Based Organizational Perspective on Multi-Agent Architectures Manuel Kolp † Paolo Giorgini ‡ John Mylopoulos † † Department of Computer Science University of Toronto University of Toronto Toronto M5S 3G4, Canada Toronto M5S 3G4, Canada ATAL’01 - August , Seattle, USA ‡ Department of Mathematics University of Trento University of Trento Trento I-38100, Italy Trento I-38100, Italy

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 2 Motivation Multi-agent system: organization of individuals to achieve particular, possible common goals. Multi-agent system: organization of individuals to achieve particular, possible common goals. Using same concepts for requirements and architectures –Multi-Agents architecture as organization and intentional structures –Coordinated autonomous components with goals to fulfil and social inter-dependencies ( i* ) –Concepts from organization theory and modeling Ontology: 3 levels (Macro, micro, atomic) Part of TROPOS ( –Requirements-Driven Development Methodology for Agent- Oriented Software

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 3 i*: an Organizational Modeling Framework Goal Task Resource Softgoal Media Shop

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 4 Multi-Agent Architectures as Social Structures Global architecture in terms of interconnected social components. 3 levels Organizational –1 Macrolevel : Organizational Styles (Organization Theory) Vertical Integration, Pyramid, Joint Venture, Structure in 5, Bidding, Hierarchical Contracting, Co-optation, Takeover Agent, COOPIS –2 Micro level : Social Patterns (Agent, COOPIS Community) Broker, Matchmaker, Contract-Net, Mediator, Monitor, Embassy, Wrapper, Master-Slave,... i* –3 Atomic : Social and intentional concepts – i*

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 5 Organization Theory Mintzberg, Scott, Galbraith, … Studies alternatives and models for (business) organizations Used to model the coordination of business stakeholders -- individuals, physical or social systems -- to achieve common (business) goals. Structure in 5, Pyramid, Takeover, Joint Venture, Cooptation, Hierarchical Contracting, Vertical Integration, Bidding, Merger, Equity Agreement, Virtual Organization, …

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 6 Structure in 5 Strategic and logistic components found in organizations. Operational core Operational core : basic operations -- the input, processing, output associated with running the organization. Strategic apex Strategic apex : executive, strategic decisions. Support Support : Assists the operation core for non-operational services outside the basic flow of operational procedures. Technostructure Technostructure : standardizes the behavior of other components, help the system adapt to its environment. Middle line Middle line : Actors who join the apex to the core.

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 7 Structure in 5 in i* and Telos TELL CLASS StructureIn5MetaClass IN Class WITH /*Class is a MetaMetaClass*/ attribute name: String part, exclusivePart, dependentPart ApexMetaClass: Class CoordinationMetaClass: Class MiddleAgencyMetaClass: Class SupportMetaClass: Class OperationalCoreMetaClass: Class END StructureIn5MetaClass In i* In Telos

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 8 Vertical Integration & Joint Venture Vertical Integration & Joint Venture

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 9 Problems A mobile robot layered architecture Information exchange not always straight-forward Often need to establish direct communication Data and control hierarchies not separated Prevent the dynamic manipulation of components Non Organizational (Classical) Architecture Styles From [Software Architecture: Perspective on an Emerging Discipline, Shaw, Garland, 96]

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 10 Mobile Robot Architecture: Structure-in-5 More distributed architecture

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 11 Software Quality Attributes Predictability, Security, Adaptability, Cooperativity, Competitivity, Availability, Integrity, Modularity, Aggregability

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 12 Example: A User 2 On-line Buying System Media taxonomy Media taxonomy –on-line catalog –DBMS E-Shopping Cart E-Shopping Cart –Check In –Buying –Check Out Search Engine Search Engine –catalog browser –Keywords –full-text Billing Processor Billing Processor –$ transactions –orders Multimedia Multimedia –description –samples Security, Availability, Adaptability, …

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 13 Goal Analysis: Selecting System Architecture

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 14 A Joint-Venture E-commerce Architecture E-business styles: on web, protocols, technologies Not on business processes, NFRs No organization of the architecture, conceptual high- level perspective From Security, Availability, Adaptability

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 15 Social Patterns Matchmaker Monitor

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 16 AgentCapabilities Customer Build a request to query the matchmaker Handle a services ontology Query the matchmaker for a service  Find alternative matchmakers  Request a service to a provider  Manage possible provider failures  Monitor the provider’s ongoing processes Ask the provider to stop the requested service Provider Handle a services ontology Advertise a service to the matchmaker Withdraw the advertisement Use an agenda for managing the requests Inform the customer of the acceptance of the request service Inform the customer of a service failure Inform the customer of success of a service Matchmaker Update the local database Handle a services ontology  Use an agenda for managing the customer requests  Search the name of an agent for a service  Inform the customer of the unavailability of agents for a service

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 17 Assigning Agent Roles to Actors

Manuel Kolp, University of Toronto, Department of Computer Science © A Goal-Based Organizational Perspective on Multi-Agent Architectures 18 Conclusion social and intentional structures Multi-Agents architectures described with concepts from requirements and organization modeling as social and intentional structures -> Narrows the gap requirements / architecture organization information systems Best suited to open, dynamic and distributed applications and organization information systems Ontology on 3 levels: –Macro: Organizational Styles, Micro:Social Patterns, Atomic:i* notions In progress –Formalizing the styles, patterns, Instantiation of a style, pattern ?? –Decision Algorithms, –From Actors to Agents