https://mobile.aau.at/selforganized-wiki/api.php?action=feedcontributions&feedformat=atom&user=Hlindner 2026-10-22T20:26:49Z User contributions MediaWiki 1.28.1 https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=624 2010-07-13T09:50:08Z

<p>Hlindner: </p> <hr /> <div>== Design Patterns for SOS? ==<br /> * The idea of reuse existing, proven solutions seems to be interesting, but...<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * The usage of design patterns depends on the nature of the desired system <br /> ** Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> ** Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, multiple stability, parameter bifurcation<br /> <br /> <br /> == Design Patterns ==<br /> * Achitectural patterns<br /> ** Observer-Controller Architecture (Organic Computing)<br /> ** MAPE (Monitor, Analyze, Process, Execute) Cycle (IBM Autonomic Computing)<br /> * Patterns for (interaction) mechanisms<br /> ** Artificial Hormone System (moving/placing resources/load balancing)<br /> ** Ant foraging (reliably find shortest routes)<br /> ** Pulse-coupled oscillators<br /> ** Plain diffusion, replication, chemotaxis, and stigmergy, …<br /> <br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback loop<br /> * Coupling between local interactions and global behaviour<br /> <br /> <br /> == Related Work on Design Patterns ==<br /> <br /> In software engineering: ''a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations'' [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29]<br /> * Design Patterns for Self-organising Systems, Gardelli et al.<br /> * Design Patterns from Biology for Distributed Computing, Babaoglu et al.<br /> * Design patterns for decentralised coordination in self-organising, De Wolf et al.</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=621 2010-07-13T09:47:49Z

<p>Hlindner: </p> <hr /> <div>== Design Patterns for SOS? ==<br /> * The idea of reuse existing, proven solutions seems to be interesting, but...<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * The usage of design patterns depends on the nature of the desired system <br /> ** Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> ** Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, multiple stability, parameter bifurcation<br /> <br /> <br /> == Design Patterns ==<br /> * Achitectural patterns<br /> ** Observer-Controller Architecture (Organic Computing)<br /> ** MAPE (Monitor, Analyze, Process, Execute) Cycle (IBM Autonomic Computing)<br /> * Patterns for (interaction) mechanisms<br /> ** Artificial Hormone System (moving/placing resources/load balancing)<br /> ** Ant foraging (reliably find shortest routes)<br /> ** Pulse-coupled oscillators<br /> ** Plain diffusion, replication, chemotaxis, and stigmergy, …<br /> <br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour<br /> <br /> <br /> == Related Work on Design Patterns ==<br /> <br /> In software engineering: ''a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations'' [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29]<br /> * Design Patterns for Self-organising Systems, Gardelli et al.<br /> * Design Patterns from Biology for Distributed Computing, Babaoglu et al.<br /> * Design patterns for decentralised coordination in self-organising, De Wolf et al.</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=617 2010-07-13T09:43:04Z

<p>Hlindner: </p> <hr /> <div>== Design Patterns for SOS? ==<br /> * The idea of reuse existing, proven solutions seems to be interesting, but...<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * The usage of design patterns depends on the nature of the desired system <br /> ** Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> ** Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, multiple stability, parameter bifurcation<br /> <br /> <br /> == Design Patterns ==<br /> * Achitectural patterns<br /> ** Observer-Controller Architecture (Organic Computing)<br /> ** MAPE (Monitor, Analyze, Process, Execute) Cycle (IBM Autonomic Computing)<br /> * Patterns for (interaction) mechanisms<br /> ** Artificial Hormone System (moving/placing resources/load balancing)<br /> ** Ant foraging (reliably find shortest routes)<br /> ** Pulse-coupled oscillators<br /> ** Plain diffusion, replication, chemotaxis, and stigmergy, …<br /> <br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour<br /> <br /> == Related Work on Design Patterns ==<br /> <br /> In software engineering: ''a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations'' [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29]<br /> * Design Patterns for Self-organising Systems, Gardelli et al.<br /> * Design Patterns from Biology for Distributed Computing, Babaoglu et al.<br /> * Design patterns for decentralised coordination in self-organising, De Wolf et al.</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=612 2010-07-13T09:40:00Z

<p>Hlindner: /* Desing Patterns */</p> <hr /> <div>== Design Patterns for SOS? ==<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * The usage of design patterns depends on the nature of the desired system <br /> ** Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> ** Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, multiple stability, parameter bifurcation<br /> <br /> <br /> == Design Patterns ==<br /> * Achitectural patterns<br /> ** Observer-Controller Architecture (Organic Computing)<br /> ** MAPE (Monitor, Analyze, Process, Execute) Cycle (IBM Autonomic Computing)<br /> * Patterns for (interaction) mechanisms<br /> ** Artificial Hormone System (moving/placing resources/load balancing)<br /> ** Ant foraging (reliably find shortest routes)<br /> ** Pulse-coupled oscillators<br /> ** Plain diffusion, replication, chemotaxis, and stigmergy, …<br /> <br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour<br /> <br /> == Related Work on Design Patterns ==<br /> <br /> In software engineering: ''a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations'' [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29]<br /> * Design Patterns for Self-organising Systems, Gardelli et al.<br /> * Design Patterns from Biology for Distributed Computing, Babaoglu et al.<br /> * Design patterns for decentralised coordination in self-organising, De Wolf et al.</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=609 2010-07-13T09:39:01Z

<p>Hlindner: </p> <hr /> <div>== Design Patterns for SOS? ==<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * The usage of design patterns depends on the nature of the desired system <br /> ** Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> ** Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, multiple stability, parameter bifurcation<br /> <br /> <br /> == Desing Patterns ==<br /> * Achitectural patterns<br /> ** Observer-Controller Architecture (Organic Computing)<br /> ** MAPE (Monitor, Analyze, Process, Execute) Cycle (IBM Autonomic Computing)<br /> * Patterns for (interaction) mechanisms<br /> ** Artificial Hormone System (moving/placing resources/load balancing)<br /> ** Ant foraging (reliably find shortest routes)<br /> ** Pulse-coupled oscillators<br /> ** Plain diffusion, replication, chemotaxis, and stigmergy, …<br /> <br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour<br /> <br /> <br /> == Related Work on Design Patterns ==<br /> <br /> In software engineering: ''a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations'' [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29]<br /> * Design Patterns for Self-organising Systems, Gardelli et al.<br /> * Design Patterns from Biology for Distributed Computing, Babaoglu et al.<br /> * Design patterns for decentralised coordination in self-organising, De Wolf et al.</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=605 2010-07-13T09:36:49Z

<p>Hlindner: </p> <hr /> <div>== Design Patterns for SOS? ==<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * The usage of design patterns depends on the nature of the desired system <br /> ** Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> * Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, multiple stability, parameter bifurcation<br /> <br /> <br /> == Desing Patterns ==<br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour<br /> <br /> == Related Work on Design Patterns ==<br /> <br /> In software engineering: ''a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations'' [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29]<br /> * Design Patterns for Self-organising Systems, Gardelli et al.<br /> * Design Patterns from Biology for Distributed Computing, Babaoglu et al.<br /> * Design patterns for decentralised coordination in self-organising, De Wolf et al.</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=603 2010-07-13T09:35:27Z

<p>Hlindner: </p> <hr /> <div>=== Design Patterns for SOS? ===<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * The usage of design patterns depends on the nature of the desired system <br /> ** Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> * Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, muliple stability, parameter bifurcation<br /> <br /> <br /> === Desing Patterns ===<br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour<br /> <br /> == Related Work on Design Patterns ==<br /> <br /> In software engineering: ''a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations'' [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29]<br /> * Design Patterns for Self-organising Systems, Gardelli et al.<br /> * Design Patterns from Biology for Distributed Computing, Babaoglu et al.<br /> * Design patterns for decentralised coordination in self-organising, De Wolf et al.</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=600 2010-07-13T09:32:11Z

<p>Hlindner: </p> <hr /> <div>=== Design Patterns for SOS? ===<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * The usage of design patterns depends on the nature of the desired system <br /> * Focus on mechanisms that cause systems to be SOS<br /> * Use a pattern at design time, so that a SOS runtime behaviour shows up<br /> * Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> * Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, muliple stability, parameter bifurcation<br /> <br /> <br /> === Desing Patterns ===<br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=598 2010-07-13T09:27:59Z

<p>Hlindner: </p> <hr /> <div>=== Design Patterns for SOS? ===<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * The usage of design patterns depends on the nature of the desired system <br /> * Focus on mechanisms that cause systems to be SOS<br /> * Design time patterns, we that show a SOS runtime behaviour<br /> * Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> * Checklist for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition, Feedback, Multiple intercations<br /> * Runtime effects to show up: spatial temporal structures, muliple stability, parameter bifurcation<br /> <br /> <br /> === Desing Patterns ===<br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=594 2010-07-13T09:21:19Z

<p>Hlindner: </p> <hr /> <div>=== Design Patterns for SOS? ===<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * Usage Design Patterns depends on the nature of the system<br /> * Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> * Define Patterns for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition<br /> * positive feedback, neg. feedback, fluctuation, multiple intercations<br /> * Design Time components to show up: spatial temporal structures, muliple stability, parameter bifurcation<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Design time patterns we that show a SOS runtime behaviour<br /> *<br /> <br /> === Desing Patterns ===<br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=593 2010-07-13T09:20:29Z

<p>Hlindner: </p> <hr /> <div>=== Design Patterns for SOS?<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * Usage Design Patterns depends on the nature of the system<br /> * Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Checklist seems currently to be more appropriate, we know what is necessary to get SOS<br /> * Define Patterns for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition<br /> * positive feedback, neg. feedback, fluctuation, multiple intercations<br /> * Design Time components to show up: spatial temporal structures, muliple stability, parameter bifurcation<br /> * Focus on mechanisms that cause systems to be SOS<br /> * Design time patterns we that show a SOS runtime behaviour<br /> *<br /> <br /> === Desing Patterns<br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Combine positive/negative Feedback w. Balance<br /> * Control Theory -&gt; Feedback<br /> * Coupling between local interactions and global behaviour</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Design_Patterns_for_engineering_SOS&diff=586 2010-07-13T08:56:18Z

<p>Hlindner: New page: === Design Patterns for SOS? * The idea of reuse existing, proven solutions seems to be interesting... * Usage Design Patterns depends on the nature of the system * Kategorize types of SOS...</p> <hr /> <div>=== Design Patterns for SOS?<br /> * The idea of reuse existing, proven solutions seems to be interesting...<br /> * Usage Design Patterns depends on the nature of the system<br /> * Kategorize types of SOS and assign possible design patterns, which are useful for which type<br /> * Define Patterns for basic properties of SOS: Adaptivity, Emergence, Autonomy, Decentralisation, Cognition<br /> <br /> <br /> === Desing Patterns<br /> * Patterns of coordination<br /> ** Stigmergy<br /> ** Connections async/sync</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Main_Page&diff=577 2010-07-13T08:39:42Z

<p>Hlindner: /* Lakeside Research Days */</p> <hr /> <div>== A Wiki on Self-Organizing Networked Systems ==<br /> <br /> * [[Definition of Self-Organizing Systems]]<br /> * [[Misconceptions]]<br /> * [[Self-Organization being a Discipline on its own?]]<br /> * [[Robustness]]<br /> * [[Adaptation]]<br /> * [[Designing Robust Self-Organizing Systems]]<br /> <br /> === Resources ===<br /> <br /> * [[Self-Organizing Systems Research Groups]]<br /> * [[Self-Organizing Systems Conferences]]<br /> * [[Self-Organizing Systems Literature Recommendations]]<br /> * [[Programming and Modeling Tools]]<br /> <br /> == Lakeside Research Days ==<br /> <br /> * [[Lakeside Research Days|Lakeside Research Days General Information]]<br /> * [[Lakeside Research Days'10]]<br /> ** Group Work: [[Challenges in Engineering Self-Organizing Systems]]<br /> ** Group Work: [[Design Patterns for engineering SOS]]<br /> * [[Lakeside Research Days'09]]<br /> ** [http://mobile.uni-klu.ac.at/selforganized-wiki/index.php/Lakeside_Research_Days%2709#Scheduled_Talks Research Talks]<br /> ** [[Curriculum on Self-Organizing Networked Systems]]<br /> ** Group Work: [[Case Studies for Robust Self-Organizing Systems]]<br /> ** Group Work: [[Modeling Techniques for Self-Organizing Systems]]<br /> ** Group Work: [[Research Areas on Self-Organizing Systems]]<br /> * [[Lakeside Research Days'08]]<br /> <br /> == IWSOS TPC Chairing ==<br /> * [[Schedule]]<br /> * [[Call for Papers]]<br /> * [[TPC Members]]<br /> <br /> == How to use the Wiki ==<br /> <br /> Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.<br /> <br /> === Getting started ===<br /> <br /> * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br /> * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br /> * [http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]</div>

Hlindner https://mobile.aau.at/selforganized-wiki/index.php?title=Main_Page&diff=576 2010-07-13T08:38:59Z

<p>Hlindner: /* Lakeside Research Days */</p> <hr /> <div>== A Wiki on Self-Organizing Networked Systems ==<br /> <br /> * [[Definition of Self-Organizing Systems]]<br /> * [[Misconceptions]]<br /> * [[Self-Organization being a Discipline on its own?]]<br /> * [[Robustness]]<br /> * [[Adaptation]]<br /> * [[Designing Robust Self-Organizing Systems]]<br /> <br /> === Resources ===<br /> <br /> * [[Self-Organizing Systems Research Groups]]<br /> * [[Self-Organizing Systems Conferences]]<br /> * [[Self-Organizing Systems Literature Recommendations]]<br /> * [[Programming and Modeling Tools]]<br /> <br /> == Lakeside Research Days ==<br /> <br /> * [[Lakeside Research Days|Lakeside Research Days General Information]]<br /> * [[Lakeside Research Days'10]]<br /> ** Group Work: [[Challenges in Engineering Self-Organizing Systems]]<br /> ** Group Work: [[Dseign Patterns for engineering SOS]]<br /> * [[Lakeside Research Days'09]]<br /> ** [http://mobile.uni-klu.ac.at/selforganized-wiki/index.php/Lakeside_Research_Days%2709#Scheduled_Talks Research Talks]<br /> ** [[Curriculum on Self-Organizing Networked Systems]]<br /> ** Group Work: [[Case Studies for Robust Self-Organizing Systems]]<br /> ** Group Work: [[Modeling Techniques for Self-Organizing Systems]]<br /> ** Group Work: [[Research Areas on Self-Organizing Systems]]<br /> * [[Lakeside Research Days'08]]<br /> <br /> == IWSOS TPC Chairing ==<br /> * [[Schedule]]<br /> * [[Call for Papers]]<br /> * [[TPC Members]]<br /> <br /> == How to use the Wiki ==<br /> <br /> Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.<br /> <br /> === Getting started ===<br /> <br /> * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br /> * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br /> * [http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]</div>

Hlindner