Fipa abstract Architecture Specification
Transport Message relationships
Download 250.15 Kb.
|
- Navigate this page:
- 4.3Directory-entry relationships
- 4.4 FIPA-message Elements
- 4.5Message-transport elements
- 4.6FIPA-entity relationships
- 5Architectural elements
4.2Transport Message relationshipsTransport-message is the object conveyed from agent to agent. It contains the transport-description for the sender and receiver or receivers, together with a payload containing the FIPA-message. 
Figure 16 – UML: Transport Message relationships 4.3Directory-entry relationshipsThe directory-entry contains the FIPA-entity-name, locator and FIPA-entity-attributes. The locator provides ways to address messages to an agent. It is also used in modifying transport requests. 
Figure 17 – UML: Directory-entry and locator relationships 4.4 FIPA-message ElementsThis diagram shows the elements in a FIPA-message. A FIPA-message is contained in a transport-message when messages are sent. 
Figure 18 – UML: FIPA-message elements 4.5Message-transport elementsThe message-transport-service is an option service that can send transport-messages between agents. These elements may participate in other relationships as well.
Figure 19 - UML: Message Transport Entities 4.6FIPA-entity relationshipsThe following UML diagram describes the FIPA-entity relationships. A FIPA-entity is an addressable software component that delivers some of functionality of the abstract architecture. 
Figure 20 - UML: FIPA Entity relationships 5Architectural elementsThe architectural elements are defined here. For each element, the semantics are described informally. Then the relationships between the element and other elements are defined. 5.1Classification of elementsThe word element is used here to indicate an item or entity that is part of the architecture, and participates in relationships with other elements of the architecture. The architectural elements are classified in three ways. Firstly, they are classified as mandatory or optional. Mandatory elements must appear in all instantiations of the FIPA abstract architecture. They describe the fundamental services, such as agent registration and communications. These elements are the core aspects of the architecture. Optional elements are not mandatory; they represent architecturally useful features that may be shared by some, but not all, concrete instantiations. The abstract architecture only defines those optional elements which are highly likely to occur in multiple instantiations of the architecture. The second classification is whether elements are actual or explanatory. Actual elements must be created as a software that meets the required functionality. They may be either mandatory or optional. Explanatory elements exist simply as useful constructs in the system, such as gathering together similar elements. For example, there is an explanatory entity, FIPA-service, which contains attributes that all FIPA-services should have. However, there is no independent entity, FIPA-service. Instead, there are various services, such as message-transport-service and directory-service, that inherit characteristics from that element. The third classification is whether the element must be implemented as a single software entity, or if the functionality can be spread across multiple entities. Note that a single software entity may be in turn composed of several components, but functionality there is a mechanism that makes that entity addressable (for example, it can accept messages, has an API, or something similar). These are said to be single or functional elements Categorization of elements
Illegal combination: Mandatory/Explanatory Download 250.15 Kb. Share with your friends:
|