|
|
1 |
#includeInContext("Main.MacroSheet") |
|
|
2 |
#includeInContext("Events.MacroSheet") |
|
|
3 |
|
|
|
4 |
|
|
|
5 |
1 4th eCAS Workshop on Engineering Collective Adaptive Systems, 2019 |
|
|
6 |
|
|
|
7 |
##{image:ecas-logo-cut.png} |
|
|
8 |
|
|
|
9 |
In conjunction with the the 13th IEEE International Conference on Self-Adaptive and Self-Organizing Systems ([SASO 2019|http://saso2019.cs.umu.se/]) and the 16th IEEE International Conference on Autonomic Computing ([ICAC 2019|http://icac2019.cs.umu.se/]), |
|
|
10 |
[FAS* | https://www.fasstar.org]. |
|
|
11 |
|
|
|
12 |
*Location:* Umeå, Sweden |
|
|
13 |
|
|
|
14 |
1.1.1 Call for Papers |
|
|
15 |
|
|
|
16 |
Modern software systems are becoming more and more *collective* and are composed of many |
|
|
17 |
distributed and heterogeneous entities. These systems operate under continuous perturbations |
|
|
18 |
making manual adjustments infeasible. For a collective system to be resilient, its *adaptation* must |
|
|
19 |
also be collective, in the sense that multiple entities must adapt in a way that addresses critical |
|
|
20 |
runtime conditions while preserving the benefits of collaborative interdependencies. Decision- |
|
|
21 |
making in such systems is distributed and possibly highly dispersed, and interaction between the |
|
|
22 |
entities may lead to the emergence of unexpected phenomena. |
|
|
23 |
|
|
|
24 |
In such systems, a new approach for adaptation is needed to allow: (i) multiple entities to |
|
|
25 |
collectively adapt with (ii) negotiations to decide which collective changes are best. Collective |
|
|
26 |
adaptation also raises a second important challenge: Which parts of the system (things, services, |
|
|
27 |
people) should be engaged in an adaptation? This is nontrivial, as multiple solutions to the same |
|
|
28 |
problem may be generated at different levels. The challenge is to understand these levels and |
|
|
29 |
create mechanisms to decide the right scope for an adaptation for a given problem. |
|
|
30 |
|
|
|
31 |
This workshop solicits papers that address new methodologies, theories and principles that can |
|
|
32 |
be used to develop a better understanding of the fundamental factors underpinning the operation |
|
|
33 |
of such systems, so that they can be better designed, built, and analyzed, as well as case studies |
|
|
34 |
and applications showing such approaches in action. Interdisciplinary work is particularly |
|
|
35 |
welcomed. |
|
|
36 |
|
|
|
37 |
*Suggested Topics (but not limited to):* |
|
|
38 |
* Novel theories relating to operating principles of CAS |
|
|
39 |
* Novel design principles for building CAS systems |
|
|
40 |
* Insights into the short and long-term adaptation of CAS systems |
|
|
41 |
* Insights into emergent properties of CAS |
|
|
42 |
* Insights into general properties of large scale, distributed CAS |
|
|
43 |
* Decision-making approaches in CAS |
|
|
44 |
* Methodologies for studying, analyzing, and building CAS |
|
|
45 |
* Frameworks for analyzing or developing CAS case studies |
|
|
46 |
* Languages, platforms, APIs and other tools for CAS |
|
|
47 |
* Scenarios, case studies, and experience reports of CAS in different contexts (e.g., Smart Mobility, Smart Energy/Smart Grid, Smart Buildings, traffic management, emergency response, etc.) |
|
|
48 |
|
|
|
49 |
1.1.1 Important Dates |
|
|
50 |
|
|
|
51 |
* Extended Abstract Submission (optional): --March 8, 2019-- March 15, 2019 |
|
|
52 |
|
|
|
53 |
* *Extended Submission Deadline: --March 15, 2019-- March 22, 2019* |
|
|
54 |
|
|
|
55 |
* Notification of Acceptance: April 15, 2019 |
|
|
56 |
|
|
|
57 |
* Camera-Ready Version: April 20, 2019 |
|
|
58 |
|
|
|
59 |
* *Workshop: June 16, morning* |
|
|
60 |
|
|
|
61 |
1.1.1 Submission Instructions and Review Criteria |
|
|
62 |
|
|
|
63 |
We solicit two types of contributions: |
|
|
64 |
|
|
|
65 |
* *full papers* (max 6 pages, including references), for original research and experience reports; |
|
|
66 |
* *short/position papers* (max 4 pages, including references), for work-in-progress research, as a basis for discussion. |
|
|
67 |
|
|
|
68 |
Papers must follow the IEEE Computer Society Press proceedings style guide. |
|
|
69 |
All papers should be submitted in PDF format. You can submit the paper through EasyChair using this link: |
|
|
70 |
|
|
|
71 |
[ https://easychair.org/conferences/?conf=ecas2019 | https://easychair.org/conferences/?conf=ecas2019] |
|
|
72 |
|
|
|
73 |
By submitting a paper, the authors confirm that in case of acceptance, at least one author will attend the workshop to present the work. |
|
|
74 |
Papers will be peer reviewed on the basis of originality, readability, relevance to themes, soundness, and overall quality. Workshop proceedings will be published on IEEE Xplore in parallel with the main conference proceedings. |
|
|
75 |
|
|
|
76 |
|
|
|
77 |
1.1.1 Workshop organizers |
|
|
78 |
|
|
|
79 |
* [Roberto Casadei | mailto:roby.casadei@unibo.it], Alma Mater Studiorum--Università di Bologna, IT |
|
|
80 |
* [Soura Dasgupta| mailto:soura-dasgupta@uiowa.edu], University of Iowa, USA |