====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
what_is_an_agent [2008/10/06 17:57] jodel |
what_is_an_agent [2008/10/06 19:34] (current) jodel |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | **What is an Agent** \\ | + | ======What is an Agent?====== |
| In general, agents can be software agents, hardware agents, firmware agents, robotic agents, human agents, and so on. While software developers naturally think of IT systems as being constructed of only software agents, a combination of agent mechanisms might in fact be used from shop-floor manufacturing to warfare systems. \\ | In general, agents can be software agents, hardware agents, firmware agents, robotic agents, human agents, and so on. While software developers naturally think of IT systems as being constructed of only software agents, a combination of agent mechanisms might in fact be used from shop-floor manufacturing to warfare systems. \\ | ||
| Line 27: | Line 27: | ||
| - | //*SoaML effect*// | + | //**SoaML effect**// \\ |
| Agent extends Participant with the ability to be active, participating components of a system. They are specialized because they have their own thread of control or lifecycle. Another way to think of agents is that they are “active participants” in an SOA system. Participants are Components whose capabilities and needs are static. In contrast, Agents are Participants whose needs and capabilities may change over time.\\ | Agent extends Participant with the ability to be active, participating components of a system. They are specialized because they have their own thread of control or lifecycle. Another way to think of agents is that they are “active participants” in an SOA system. Participants are Components whose capabilities and needs are static. In contrast, Agents are Participants whose needs and capabilities may change over time.\\ | ||
| Line 34: | Line 34: | ||
| Agents possess the capability to have services and Requests and can have internal structure and ports. They collaborate and interact with their environment. An Agent's classifierBehavior, if any, is treated as its life-cycle, or what defines its emergent or adaptive behavior.\\ | Agents possess the capability to have services and Requests and can have internal structure and ports. They collaborate and interact with their environment. An Agent's classifierBehavior, if any, is treated as its life-cycle, or what defines its emergent or adaptive behavior.\\ | ||
| - | //Notation// | + | //**Notation**//\\ |
| - | An Agent can be designated using the Component or Class/Classifier notation including the «agent» keyword. Is can also represented by stick “agent” man icon with the name of the agent in the vicinity (usually above or below) the icon. (Figure 17) Note: the stick icon is similar to the notation for UML actors, except that it has a wizard hat shaped as an elongated “A”. | + | An Agent can be designated using the Component or Class/Classifier notation including the «agent» keyword. Is can also represented by stick “agent” man icon with the name of the agent in the vicinity (usually above or below) the icon. Note: the stick icon is similar to the notation for UML actors, except that it has a wizard hat shaped as an elongated “A”. \\ |
| - | + | {{agentnotation.png|}}\\ | |
| - | + | Agent notation. | |
| - | Figure 17: Agent notation. | + | |
| - | Additions to UML 2.X | + | |
| - | Agent is a new stereotype in SOA-Pro extending UML2 Component with new capabilities. | + | |
