Prof. Dr. Cesare Pautasso

On the Architecture of Liquid Software: Technology Alternatives and Design Space

Andrea Gallidabino, Cesare Pautasso, Ville Ilvonen, Tommi Mikkonen, Kari Systa, Jari-Pekka Voutilainen, Antero Taivalsaari

13th Working IEEE/IFIP Conference on Software Architecture (WICSA 2016), Venice, Italy

April 2016

Abstract

The liquid metaphor refers to software that operates seamlessly across multiple devices owned by one or multiple users. Liquid software architectures can dynamically deploy and redeploy stateful software components and transparently adapt them to the capabilities of heterogeneous target devices. The key design goal in liquid software development is to minimize the efforts that are related to multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home displays, cars and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present a design space for liquid software, categorizing and discussing the most important architectural issues and alternatives. These alternatives represent relevant capabilities offered by emerging technologies and deployment platforms that are then positioned and compared within the design space presented in the paper.

Download

DOI: 10.1109/WICSA.2016.14

PDF: ▼liquidjs-WICSA2016.pdf (184KB)

Citation

Bibtex

@inproceedings{liquidjs:2016:wicsa,
	author = {Andrea Gallidabino and Cesare Pautasso and Ville Ilvonen and Tommi Mikkonen and Kari Systa and Jari-Pekka Voutilainen and Antero Taivalsaari},
	title = {On the Architecture of Liquid Software: Technology Alternatives and Design Space},
	booktitle = {13th Working IEEE/IFIP Conference on Software Architecture (WICSA 2016)},
	year = {2016},
	month = {April},
	address = {Venice, Italy},
	abstract = {The liquid metaphor refers to software that operates seamlessly across multiple devices owned by one or multiple users. Liquid software architectures can dynamically deploy and redeploy stateful software components and transparently adapt them to the capabilities of heterogeneous target devices. The key design goal in liquid software development is to minimize the efforts that are related to multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home displays, cars and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present a design space for liquid software, categorizing and discussing the most important architectural issues and alternatives. These alternatives represent relevant capabilities offered by emerging technologies and deployment platforms that are then positioned and compared within the design space presented in the paper.},
	keywords = {design space, liquid software, liquid.js},
	doi = {10.1109/WICSA.2016.14}
}