International Workshop on
Ecosystem Architectures (WEA2013)
SAINT PETERSBURG, RUSSIA –– AUGUST 19, 2013
AT THE 9TH JOINT MEETING OF
THE EUROPEAN SOFTWARE ENGINEERING CONFERENCE AND
THE ACM SIGSOFT SYMPOSIUM ON THE FOUNDATIONS OF SOFTWARE
ENGINEERING (ESEC/FSE)
|
Abstract A prominent trend for software-intensive systems has
been established in recent years: increasing integration. Increased domain
complexity is addressed by the integration of single software systems into
ecosystems where the whole is more than just the sum of the individual parts.
At one end of the spectrum we find open source
ecosystems like Gnome, which emerge without explicit architectural
specifications and are driven by open source communities. At the other end of
the spectrum we find commercial or governmental ecosystems like SmartFarming
or SmartHealth, whose integration is explicit and which are typically driven
by multiple organizational stakeholders, each providing parts evolving at
their own pace. In all these cases, the architecture of a software
ecosystem is the engineering centerpiece and it can determine the success or
failure of the individual systems and of the software ecosystem as a whole. Workshop Format The first international Workshop on Ecosystem Architectures (WEA2013) will be a venue for practitioners and researchers to share experience and lessons learned about architectures of software ecosystems as well as discuss current and future engineering challenges. Participants can expect to benefit from interesting and fruitful discussions, exchange their experiences, meet researchers working in the same area, and make new friends. The workshop will be a highly interactive event,
comprising the discussion of position papers, break-out groups, and plenary
discussions. Topics We solicit submissions on technical topics related to scaling system architecture to the level of software ecosystems. What are relevant methods, processes, techniques and/or tools for architecting at scale? Which technical strategies are required to cope with the complexity of ecosystem architectures? How can architectural concepts assure end-to-end quality across system borders while keeping maintenance and evolution of the comprising systems independent from each other? What kind of capabilities do we need in terms of tools to analyze software ecosystems statically or monitor/diagnose them at run time? Relevant topics include but are not limited to: • Experience reports on best practices for architectural styles, tactics, or patterns vs. bad smells or anti-patterns in ecosystem architectures • Tools for inter-system static and/or dynamic analysis including but not limited to visualization, monitoring, and change awareness • Empirical studies of ecosystem phenomena as well as user needs in the context of software development within an ecosystem • Case studies of ecosystem architectures and their evolution • Working Processes for evolving software ecosystems as a whole that respect the autonomy of independent system contributors · Engineering methods for the design and documentation of evolving ecosystem
architectures Workshop Proceedings Workshop
proceedings will be published in the ACM digital library or as Fraunhofer
IESE Technical Report and will be made available electronically to all
participants. |
|
