Difference between revisions of "Design Patterns for engineering SOS"
From Self-Organization Wiki
| Line 3: | Line 3: | ||
* The usage of design patterns depends on the nature of the desired system | * The usage of design patterns depends on the nature of the desired system | ||
* Focus on mechanisms that cause systems to be SOS | * Focus on mechanisms that cause systems to be SOS | ||
| − | * | + | * Use a pattern at design time, so that a SOS runtime behaviour shows up |
* Kategorize types of SOS and assign possible design patterns, which are useful for which type | * Kategorize types of SOS and assign possible design patterns, which are useful for which type | ||
* Checklist seems currently to be more appropriate, we know what is necessary to get SOS | * Checklist seems currently to be more appropriate, we know what is necessary to get SOS | ||
Revision as of 10:32, 13 July 2010
Design Patterns for SOS?
- The idea of reuse existing, proven solutions seems to be interesting...
- The usage of design patterns depends on the nature of the desired system
- Focus on mechanisms that cause systems to be SOS
- Use a pattern at design time, so that a SOS runtime behaviour shows up
- Kategorize types of SOS and assign possible design patterns, which are useful for which type
- Checklist seems currently to be more appropriate, we know what is necessary to get SOS
- Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations
- Runtime effects to show up: spatial temporal structures, muliple stability, parameter bifurcation
Desing Patterns
- Patterns of coordination
- Stigmergy
- Combine positive/negative Feedback w. Balance
- Control Theory -> Feedback
- Coupling between local interactions and global behaviour
