Organic computing

Abstract: The laws that govern the collective behavior of social insects, flocks of birds, or fish schools continue to mesmerize researchers. While individuals are rather unsophisticated, in cooperation they can solve complex tasks, a prime example being the ability of ant colonies to find shortest paths between their nests and food sources. Task-solving results from self-organization, which often evolves from simple means of communication, either directly or indirectly via changing the environment, the latter referred to as stigmergy. Scientists have applied these principles in new approaches, for example to optimization and the control of robots. Characteristics of the resulting systems include robustness and flexibility. This field of research is now referred to as swarm intelligence. The contributing authors are among the top researchers in their domain. The book is intended to provide an overview of swarm intelligence to novices, and to offer researchers in the field an update on interesting recent developments. Introductory chapters deal with the biological foundations, optimization, swarm robotics, and applications in new-generation telecommunication networks, while the second part contains chapters on more specific topics of swarm intelligence research such as the evolution of robot behavior, the use of particle swarms for dynamic optimization, and organic computing.

Abstract: ion is the selection and (possibly) coarsening (i.e. quantisation) of certain system characteristics (attributes, performance indicators, parameters) from the total set of system characteristics. The abstraction process comprises: • A simplification (Example: The colour Red is an abstraction, which neglects the different possible shades of Red, the wavelengths, the intensity etc.), • an aggregation (Example: ‘Temperature’ condenses the myriad of individual molecule movements in a gas volume into a single number.), • and consequently: loss of information. The opposite of abstraction is concretisation. It comprises: • gain of information, • detailing, • refinement, • disaggregation, • in engineering: the design process. 3.2.2 System Boundary Systems are defined by their system boundary, which makes a distinction between inside and outside possible (i.e. between self and non-self, see Sect. 4.1). When 3.2 What is a System? 87 Fig. 3.3 Trade-off between initial development cost and later adaptation cost systems are designed, we must choose where to place the boundary. This involves a consideration of cost (Fig. 3.3): A narrow boundary will reduce the cost for planning and development in the first place but bears the risk of a high effort in case a subsequent adaptation and extension of the system should be necessary. A wide system boundary reverses the cost curves. Apparently, the total cost minimum lies somewhere in the middle. 3.2.3 Some System Types and Properties Most systems are transient, i.e. they change over time. They are developed, assembled, modified, destroyed. Reactive systems react on inputs (events, signals, sensor data) by applying outputs (events, control signals, commands) to the environment. All open systems are reactive! In a more focused definition: Only systems reacting in real time (within a predefined time) are reactive systems. Such real-time systems are characterised by (1) time restrictions (deadlines), and (2) time determinism (i.e. guarantees). Planned vs. Unplanned systems: During the development process of technical systems, only predictable events are taken into account in the designed core. But there will always be an unpredictable rest. Therefore, the ‘spontaneous closure’ (Fig. 3.4) has to cover these events. In technical systems, the exception handler or the diagnosis system play the role of a simple spontaneous closure. Living systems are characterised by a powerful spontaneous closure. Recurring reactions of the spontaneous closure become part of the designed core. This amounts to learning.

Abstract: Organic Computing (OC) assumes that current trends and recent developments in computing, like growing interconnectedness and increasing computational power, pose new challenges to designers and users. In order to tackle the upcoming demands, OC has the vision to make systems more life-like (organic) by endowing them with abilities such as self-organisation, self-configuration, self-repair, or adaptation. Distributing computational intelligence by introducing concepts like self-organisation relieves the designer from exactly specifying the low-level system behaviour in all possible situations. In addition, the user has the possibility to define a few high-level goals, rather than having to manipulate many low-level parameters.

Abstract: In the past, the focus of the computer industry has been to improve hardware performance and add more and more features to the software. As a result, more and more appliances surrounding us are equipped with embedded computational power and wireless communication. As such, they become ever more flexible and multifunctional, and almost indispensable in daily life. On the other hand, the resulting systems become increasingly complex and unreliable, posing new challenges to designer and user. Organic Computing (OC) has the vision to address the challenges of complex distributed systems by making them more life-like (organic), i.e. endowing them with abilities such as self- organization, self-configuration, self-repair, or adaptation. The designer's task is simplified, because it is no longer necessary to exactly specify the low-level system behavior in all possible situations that might occur, but instead leaving the system with a certain degree of freedom which allows it to react in an intelligent way to new situations. Also, use of such systems is simplified, as they can be controlled by setting few high-level goals, rather than having to manipulate many low-level parameters with unclear influence. In this paper, we give a general introduction to OC, and propose a generic observer-controller architecture as a framework for designing OC systems. Then, it is shown how to use this architecture at the example of a traffic light controller. The paper concludes with a summary and a discussion of future challenges.