ESOA
From CasGroup
| Line 1: | Line 1: | ||
| - | |||
'''Engineering Self-Organizing Applications''' (ESOA) is the attempt | '''Engineering Self-Organizing Applications''' (ESOA) is the attempt | ||
to apply the concept of [[Self-Organization|self-organization]] to engineering, | to apply the concept of [[Self-Organization|self-organization]] to engineering, | ||
| Line 5: | Line 4: | ||
The goal (or hope) is to achieve complex collective tasks with relatively | The goal (or hope) is to achieve complex collective tasks with relatively | ||
simple individual elements, units and behaviors. The name ESOA is sometimes | simple individual elements, units and behaviors. The name ESOA is sometimes | ||
| - | also used as an abbreviation for | + | also used as an abbreviation for "Enterprise [[Service-Oriented_Architecture|SOA]]", |
| - | i.e. to describe a | + | i.e. to describe a "Service-Oriented Architecture for Enterprises". |
== A Name for a Problem == | == A Name for a Problem == | ||
EOSA is like [[AOSE]] more a name for a problem than its solution. | EOSA is like [[AOSE]] more a name for a problem than its solution. | ||
| - | It is closely related to the problem of | + | It is closely related to the problem of "[[Engineering_Emergence|engineering emergence]]". |
Engineering is at odds with [[Emergence|emergence]], a phenomenon which | Engineering is at odds with [[Emergence|emergence]], a phenomenon which | ||
usually accompanies self-organization, and planned organization | usually accompanies self-organization, and planned organization | ||
