1 / 6

Detailed Design

Detailed Design. For each individual agent, we identify the capabilities it needs to have to fulfils its responsibilities as outlined in the functionalities it contains Decompose each functionality and define a corresponding capability stressing the principle of cohesion

milo
Télécharger la présentation

Detailed Design

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. Detailed Design For each individual agent, we identify the capabilities it needs to have to fulfils its responsibilities as outlined in the functionalities it contains • Decompose each functionality and define a corresponding capability stressing the principle of cohesion • Each capability should be a well-defined collection of plans, using particular beliefs or data, which addresses a specific set of goals (or sub-goals) of the agent – see bottom of page 101

  2. Agent Overview Diagram Consists of information as to what goal(s) each capability is to achieve, combined with the information of the protocols the agent engages in (from previous chapter) and the databases it accesses • Begin with the interface to the agent as specified in the System Overview diagram • The capabilities are then added, and each interface element is linked to at least one capability • The protocol descriptions are then used to guide the specification of the messages that need to pass between capabilities see Figure 8.2 on page 103 for Stock Manager AOD

  3. Process Specifications • Variant of UML activity diagram (see Figure 8.3 on page 104) • By looking at goals of agent, scenarios and protocols come up with process diagrams – examples for Stock Manager agent, see Figure 8.4 on page 105 • Diagram of manage customer profile process in the Customer Relations agent, see Figure 8.5 on page 106

  4. Capability Descriptor Consists of • Name • Goals • Processes • Protocols • Outgoing messages • Incoming messages • Internal messages • Percepts • Actions • Included capabilities • Data used • Data produced • Data internal Included plans Ordering capability of Stock Manager agent seen on page 107

  5. Process Descriptor Consists of • Name • Description Activities • Triggers • Messages • Protocols • Notes See bottom half of page 108 for process descriptor for the “Stock maintenance” process, within the Stock Manager agent

More Related