Representing Agent Interaction Protocols in UML. Agent UML A Formalism for Specifying Multiagent Software Systems

Transcription

1 Representing Interaction Protocols in UML UML A Formalism for Specifying Multiagent Software Systems James J. Odell H. Van Dyke Parunak Bernhard Bauer Interaction Protocols in UML Page 1 Bernhard Bauer Jörg P. Müller James Odell Intelligent Autonomous s Siemens AG Interaction Protocols in UML Page 2

2 AN AGENT CONVERSATION WINOGRAD-FLORES VERSION OF AN AGENT INTERACTION PROTOCOL (AIP) 10. C A REFUSE: I m abandoning my COMMIT D A SHIP: Here are your widgets. Please pay me A D ASSERT + REQUEST: You re five short. Please send the difference D A SHIP: Here are five more widgets. Please pay me. 14. A D PA Y Seq Sndr Rcvr Utterance Rspnds to Replies to Resolves 1. A B,C,D REQUEST: Please send me 50 widgets at your catalog price by net Thursday. 2. B C QUESTION: Are you bidding on A s RFQ? 1 3. C B INFORM: Yes, I am B A REFUSE C A PROPOSE (INFORM + REQUEST): How about widgets at catalog price by net Friday? 6. A C REQUEST: Please send me 40 widgets at catalog price by net Friday. 7. C A COMMIT: I plan to send you 40 widgets at catalog price by net Friday. 8. D A COMMIT: I plan to send you 50 widgets at catalog price by net Thursday. 9. A C ASSERT: I ve found a better supplier, and am 7,8 7 not relying on your COMMIT. Completes A: REQUEST 1 2 A: REFUSE B: PROPOSE B: REFUSE A: ASSERT Out B: COMMIT A: ASSERT Out A: ASSERT Bad B: REFUSE B: SHIP A: PAY A: ASSERT Out After Smith and Cohen 1995 Interaction Protocols in UML Page 3 Interaction Protocols in UML Page 4

3 STANDARDIZATION MOF/OADF/BOF ARCHITECTURE Analysis and Design Task Force (ADTF) of Object Management Group (OMG) Overall goal: vendor-neutral common semantics, metamodel, and abstract synta for A&D methodologies Specific Mfg Fin Med High Mission To enable developers to better understand how to develop applications using OT thereby growing the market. To recommend technology that interoperates across the lifecycle of A&D tools designs/work products. To recommend technology that enables reuse of designs and work products developed using A&D tools To recommend technology that has common semantics, meta-model, and abstract synta for A&D methodologies. To leverage eisting OMG specifications. OA&D TF RFP-1 - approved and released June 1996 Submissions due: 17 Jan 1997; Revisions due: 1 September 1997 Selection: 25 September 1997; Adoption: November 1997 Object Management Group (508) MetaModel Specialization Generic Common Business Objects Business Object Facility OA&D (UML) Facility Meta-Object Facility CORBA 3.0 M1 M2 M2 M3 Low Interaction Protocols in UML Page 5 Interaction Protocols in UML Page 6

4 UML DIAGRAMS Static Diagrams AGENTS STANDARDIZATION AND AGENT UML (AUML) Class diagrams Packages Component diagrams Dynamic Diagrams Statechart Collaboration diagrams Sequence diagrams Activity diagrams Deployment diagrams OMG s Working Group recommends standards for agent technology where appropriate particularly the OMG's Object Management Architecture (OMA). ( FIPA (Federated Intelligent Physical s) has been working to develop and promote standardization in the area of agent interoperability since It has an ongoing work program, meeting around the globe on a quarterly basis, with ecess of 50 member organizations. ( Use Case diagrams So, which will be useful for representing agent interaction protocols? Interaction Protocols in UML Page 7 Interaction Protocols in UML Page 8

5 A COMMON AIP REPRESENTATION UML Sequence Diagrams INTERACTION PROTOCOLS CAN BE SPECIFIED IN MORE DETAIL Initiator Participant Role-1 Role-2 call-for-proposal CA-1 CA-2 deadline not-understood propose accept-proposal y g z Role-2 CA-3 CA-4 Role-3 reject-proposal inform cancel FIPA Contract Net Protocol Interaction Protocols in UML Page 9 Interaction Protocols in UML Page 10

6 A LAYERED APPROACH TO AIPs USING PACKAGES TO EXPRESS NESTED PROTOCOL Level 1: Representing the overall protocol Purchasing Supplying Level 2: Representing interaction among agents Broker Retailer Wholesaler call-for-proposal Level 3: Representing internal agent processing propose inform Interaction Protocols in UML Page 11 Interaction Protocols in UML Page 12

7 LEVEL 1 Generic AIP epressed as a template package BINDING THE PARAMENTERS OF THE FIPA CONTRACT NET PROTOCOL PACKAGE TEMPLATE contract initiation FIPA Contract Net Protocol Initiator Participant Initiator, Participant Deadline call-for-proposal, *, not-understood*, propose, reject-proposal*, accept-proposal*, cancel*, inform* FIPA Contract Net Protocol Buyer, Seller call-for-proposal 8/8/99 at 12:00 deadline seller-rfp, -1, -2, not-understood, propose, reject-proposal, accept-proposal, cancel, inform not-understood propose accept-proposal reject-proposal inform cancel Interaction Protocols in UML Page 13 Interaction Protocols in UML Page 14

8 APPLYING A TEMPLATE TO A PARTICULAR SCENARIO LEVEL 2: Basic format of Sequence Diagrams for agent communication Buyer Seller seller-rfp -1/Role:Class -2/Role:Class -1-2 not-understood deadline: 8/8/99 at 12:00 hours CA-1 propose CA-2 accept-proposal reject-proposal inform cancel Interaction Protocols in UML Page 15 Interaction Protocols in UML Page 16

9 CONCURRENT COMMUNICATION WITH AN AGENT PLAYING DIFFERENT ROLES SEQUENCE DIAGRAM Eample A / Customer A / Negotiator B / Contractor B / Competitor Analyzer C / Contractor1 C / Contractor2 C / Competitor D / Contractor D / Debtor CA-1 CA-2 CA-3 [role-1] or or CA-1 [role-1] CA-2 CA-3 CA-1 CA-1 CA-2 CA-2 CA-3 CA-3 <<role change>> reques t <<role change>> <<role change>> propose commit commit assert question inform CA-1 CA-1 ship assert + CA-2 CA-3 or CA-2 CA-3 ship pay Interaction Protocols in UML Page 17 Interaction Protocols in UML Page 18

10 DETECTING ROLES AS TIME INTERVALS IN A SEQUENCE DIAGRAM ROLES AS PARALLEL BRANCHES IN A SEQUENCE DIAGRAM (only A s roles labeled) A : B : C : D : A : B : C : D : customer>> negotiator>> customer>> negotiator>> question inform propose commit commit assert propose commit commit assert question inform customer>> ship assert + ship pay ship assert + ship pay customer>> negotiator>> contractor>> competitor analyzer>> contractor>> contractor>> competitor>> contractor>> debtor>> Interaction Protocols in UML Page 19 Interaction Protocols in UML Page 20

11 ROLES AS TYPES COLLABORATION DIAGRAM WITHOUT INDIVIDUAL AGENTS An alternative representation Customer Negotiator <<role change>> Contractor propose commit Competitor Analyzer <<role change>> <<role change>> question inform * Contractor Debtor 12: assert + 14: 1.1: B / Contractor A Customer 4: <<role change>> <<role change>> 1.2: 1.3: B / Competitor Analyzer <<role change>> C / Contractor1 6: 2: question 3: 5: propose 7: commit C / Competitor A / Negotiator 9: assert 10: C / Contractor2 commit assert D / Debtor 13: ship 8: commit 11: ship D / Contractor ship assert + ship pay Interaction Protocols in UML Page 21 Interaction Protocols in UML Page 22

12 ROLES ON MESSAGES IN A COLLABORATION DIAGRAM ACTIVITY DIAGRAMS Another alternative representation (only roles for A shown) B : 2: question 3: inform C : Place Process Accept Accept Create 1.1: customer>> A : 4: 5: propose 7: commit 10: 1.2: customer>> 6: negotiator>> 9: assert negotiator>> Match and 1.3: customer>> 12: assert + customer>> 14: pay customer>> 8: commit 11: ship 13: ship Settle Close Update D : Interaction Protocols in UML Page 23 Interaction Protocols in UML Page 24

13 ORDER PROCESSING: ACTIVITY DIAGRAMS WITH SWIMLANES Customer Broker ECN Market Maker ORDER PROCESSING: ACTIVITY DIAGRAMS WITH SWIMLANES AND OBJECT FLOW Customer Broker ECN Market Maker Place Process Accept Accept Create Place [ed] Process [unfilled] Accept Accept Create [unfilled] Match and [filled] [accepted] Match and [accepted] [filled] Settle Close Update [closed] Settle Close Update [updated] Interaction Protocols in UML Page 25 Interaction Protocols in UML Page 26

14 LEVEL 3 Generic AIP epressed as a template package STATECHART NOTATION Even another alternative Customer Processor Invoice Sender Payment Receiver Place order Completed Invoice Received payment A: REQUEST Open B: COMMIT A: ASSERT Bad A: PAY Closed Proposed Requested Committed Shipped Paid B: SHIP placed Accepted accepted Assembled assembled Ship shipped Close completed B: PROPOSE A: ASSERT Out A: ASSERT Out Aborted Prepare /send Invoice (Invoice) Process Payment (Payment) Payment accepted B: REFUSE B: REFUSE A: ASSERT Out B. RENEGE Reneged Rejected A state-based speech-act version of the Winograd-Flores protocol in UML statechart notation Interaction Protocols in UML Page 27 Interaction Protocols in UML Page 28

15 REPRESENTING AGENT INTERACTION PROTOCOLS IN UML OTHER UML EXTENSION Package specifying agents instead of operations as interface points. Level 1: Representing the overall protocol Level 2: Representing interaction among agents Level 3: Representing internal agent processing Common Function s telescoping agent packages Manufacturing Cell Common Function s an aggregate interface agent Negotiator Process Planning Dispatch Resource 1..* 0..* Resource Capacity Manager 1.. Account Manager 0.. Interaction Protocols in UML Page 29 Interaction Protocols in UML Page 30

16 OTHER UML EXTENSION Adding mobility to deployment diagrams. OTHER UML EXTENSION Representing cloning, mitosis, and reproduction using sequence and activity diagrams Salesperson's laptop Shopper <<at-home>> Internet <<mobile>> Dr_Frankenstein: Scientist get specs <<clone>> Dolly: Sheep Sequence Diagram Dolly2: Sheep Dolly: Sheep <<prototype>> <<clone>> Dolly2: Sheep Class Diagram SalesWeb Internet server Sales Shopper Corporate Novell Network/SQL A: Amoeba <<mitosis>> Mitosis A1: Amoeba A2: Amoeba Biseual John: Starfish Janet: Starfish <<reproduction>> Junior: Starfish Accounting mainframe Inventory mainframe Sequence Diagram Collaboration Diagram Interaction Protocols in UML Page 31 Interaction Protocols in UML Page 32

17 OTHER UML EXTENSION Representing parasitic, symbiotic, and emergence relationship using class diagrams Representing Interaction Protocols (and then some) in UML Dog 0..* <<host/parasite>> 0..* Flea Tree 1 <<symbiosis>> 0..* Epiphyte UML A Formalism for Specifying Multiagent Software Systems James J. Odell H. Van Dyke Parunak Bernhard Bauer Bernhard Bauer Jörg P. Müller James Odell 0..* Market 0..* Consumer <<emergence>> Interaction Protocols in UML Page 33 Interaction Protocols in UML Page 34