AOSE
From CasGroup
| Line 6: | Line 6: | ||
open question. | open question. | ||
| - | + | == Problems and Challenges == | |
=== Basic Problems === | === Basic Problems === | ||
| Line 25: | Line 25: | ||
Each technology for building software has advantages and disadvantages. Agent technology | Each technology for building software has advantages and disadvantages. Agent technology | ||
is not an exception, it has advantages and positive properties, but there are also many | is not an exception, it has advantages and positive properties, but there are also many | ||
| - | pitfalls and drawbacks, see the section | + | pitfalls and drawbacks, see the section "Potentials and Pitfalls" of the [[Agent|agent]] page. |
| - | The advantage of traditional software techniques is the | + | The advantage of traditional software techniques is the "easy" analysis, engineering and design |
of predictable object-oriented systems with [[Unified Modeling Language|UML]]. The drawbacks | of predictable object-oriented systems with [[Unified Modeling Language|UML]]. The drawbacks | ||
are brittleness and rigidity, low fault-tolerance and low scalability. | are brittleness and rigidity, low fault-tolerance and low scalability. | ||
| Line 38: | Line 38: | ||
[[Multi-Agent System|Multi-Agent Systems]], especially those with desirable | [[Multi-Agent System|Multi-Agent Systems]], especially those with desirable | ||
[[Emergence|emergent]] properties is notoriously difficult. Therefore | [[Emergence|emergent]] properties is notoriously difficult. Therefore | ||
| - | + | "Agent Oriented Software Engineering" or AOSE is more a name for a problem than | |
a name for a solution, like many other names as for example | a name for a solution, like many other names as for example | ||
| - | + | "Agent Based Software Engineering" (ABSE), "Agent Based Software Development" (ABSD), | |
| - | + | "Agent Oriented Programming" (AOP), or "Interaction Oriented Programming" (IOP). | |
| - | The problem in AOSE is familiar and well-known to many researchers: | + | The problem in AOSE is familiar and well-known to many researchers: "I |
| - | have a Multi-Agent System, but what is its purpose and function ? | + | have a Multi-Agent System, but what is its purpose and function ?" |
If an agent decides itself what it needs to do, how can we make sure that | If an agent decides itself what it needs to do, how can we make sure that | ||
it does something useful or something we want it to do? | it does something useful or something we want it to do? | ||
| Line 49: | Line 49: | ||
The '''Engineering of Self-Organizing Applications''' ([[ESOA|ESOA]]) is | The '''Engineering of Self-Organizing Applications''' ([[ESOA|ESOA]]) is | ||
like AOSE a name for a central problem, not its solution. The problem in ESOA | like AOSE a name for a central problem, not its solution. The problem in ESOA | ||
| - | is this: | + | is this: "I know some self-organizing systems in nature, but how do I engineer a |
| - | specific system for a certain problem? | + | specific system for a certain problem?" In other words "How do I organize |
| - | a system which is allowed to organize itself? | + | a system which is allowed to organize itself?" Whereas AOSE focuses |
on the conflict between autonomy and service-delivery (between agents and | on the conflict between autonomy and service-delivery (between agents and | ||
objects, autonomy vs. heteronomy), ESOA is about the conflict | objects, autonomy vs. heteronomy), ESOA is about the conflict | ||
between engineering and emergence (between imposed purpose and independent goals, | between engineering and emergence (between imposed purpose and independent goals, | ||
or planned organization vs. self-organization). | or planned organization vs. self-organization). | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== Proposed Solutions and Methodologies == | == Proposed Solutions and Methodologies == | ||
