1 / 6

Specifying Agent Types

Specifying Agent Types. Agent types are formed by combining functionalities. One proposed grouping of functionalities is better than another if it gives lower coupling and higher cohesion Coupling is the extent to which functionality groups depend on each other

vevay
Download Presentation

Specifying Agent Types

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Specifying Agent Types • Agent types are formed by combining functionalities. • One proposed grouping of functionalities is better than another if it gives lower coupling and higher cohesion • Coupling is the extent to which functionality groups depend on each other • Cohesion is the extent to which parts of a functionality group are related to each other

  2. Deciding on Agent Types • Formulate functionality groupings considering alternative groupings • Criteria: when “it makes sense,” there is a cardinality match (e.g., middle of page 57), and they require the same information. Also, security/privacy and modifiability • Review coupling and decide on preferred grouping • Review the degree of cohesion of each preferred grouping • Develop agent descriptors

  3. Data Coupling Diagram Consists of the functionalities and all identified data. Directed arrows between functionalities and data. • When head arrow points to data indicates that data is written or produced by functionality. • When head arrow points to functionality indicates that data is used by the functionality • Double-headed arrow indicates that the functionality both uses and produces the data Example on pages 59 and 60

  4. Revisions due to Cardinality and Cohesion • Cardinality • Grouping should include same number of instances of functionality (one or many). See example on page 61. • Cohesion • Investigate whether some functionality can become part of an existing group • Name of grouping should be representative of all the functionalities in the group – e.g., top of page 63

  5. Acquaintance Diagram Used to review coupling among prospective functionality groupings. Interaction among functionalities is extracted from the functionality descriptors (see bottom of page 64). Review: • Density (ratio: links from over max links) of the links within diagram • -Problem: Star design with each group connecting to a central one only (low coupling but bottleneck if central goes down). To decide on extent of problem, consider actual situations (refer to middle of page 64) • Diagram useful in determining whether all links are necessary

  6. Develop Agent Descriptors Consists of: • Name and brief description • List of functionalities it comprises (i.e., group) • Number of instances (e.g., one Sales Assistant agent per customer) • Llifetime (when and how agent is created/destroyed) • Initialization-what needs to be done • Demise-what clean up needs to be done • Goals • Percepts it responds to • Actions it will take • Data it uses or produces Sample descriptor on page 66, and Appendix A

More Related