Tampere University of Technology

TUTCRIS Research Portal

Architecting liquid software

Research output: Contribution to journalArticleScientificpeer-review

Standard

Architecting liquid software. / Gallidabino, Andrea; Pautasso, Cesare; Mikkonen, Tommi; Systä, Kari; Voutilainen, Jari-Pekka; Taivalsaari, Antero.

In: Journal of Web Engineering, Vol. 16, No. 5-6, 01.09.2017, p. 433-470.

Research output: Contribution to journalArticleScientificpeer-review

Harvard

Gallidabino, A, Pautasso, C, Mikkonen, T, Systä, K, Voutilainen, J-P & Taivalsaari, A 2017, 'Architecting liquid software', Journal of Web Engineering, vol. 16, no. 5-6, pp. 433-470. https://doi.org/10.26421/JWE16.5-6

APA

Gallidabino, A., Pautasso, C., Mikkonen, T., Systä, K., Voutilainen, J-P., & Taivalsaari, A. (2017). Architecting liquid software. Journal of Web Engineering, 16(5-6), 433-470. https://doi.org/10.26421/JWE16.5-6

Vancouver

Gallidabino A, Pautasso C, Mikkonen T, Systä K, Voutilainen J-P, Taivalsaari A. Architecting liquid software. Journal of Web Engineering. 2017 Sep 1;16(5-6):433-470. https://doi.org/10.26421/JWE16.5-6

Author

Gallidabino, Andrea ; Pautasso, Cesare ; Mikkonen, Tommi ; Systä, Kari ; Voutilainen, Jari-Pekka ; Taivalsaari, Antero. / Architecting liquid software. In: Journal of Web Engineering. 2017 ; Vol. 16, No. 5-6. pp. 433-470.

Bibtex - Download

@article{6a99b731b76843a78660558abfd6efe5,
title = "Architecting liquid software",
abstract = "The Liquid Software metaphor refers to software that can operate seamlessly across multiple devices owned by one or multiple users. Liquid Software applications can take advantage of the computing, storage and communication resources available on all the devices owned by the user. Liquid Software applications can also dynamically migrate from one device to another, following the user’s attention and usage context. The key design goal in Liquid Software development is to minimize the additional efforts arising from multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home and car displays, and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present the design space for Liquid Software, categorizing and discussing the most important architectural dimensions and technical choices. We also provide an introduction and comparison of two frameworks implementing Liquid Software capabilities in the context of the World Wide Web.",
keywords = "Design space, Liquid software, Multi-device programming, Multiple device ownership, Software architecture",
author = "Andrea Gallidabino and Cesare Pautasso and Tommi Mikkonen and Kari Syst{\"a} and Jari-Pekka Voutilainen and Antero Taivalsaari",
note = "EXT={"}Mikkonen, Tommi{"} EXT={"}Taivalsaari, Antero{"}",
year = "2017",
month = "9",
day = "1",
doi = "10.26421/JWE16.5-6",
language = "English",
volume = "16",
pages = "433--470",
journal = "Journal of Web Engineering",
issn = "1540-9589",
publisher = "Rinton Press Inc.",
number = "5-6",

}

RIS (suitable for import to EndNote) - Download

TY - JOUR

T1 - Architecting liquid software

AU - Gallidabino, Andrea

AU - Pautasso, Cesare

AU - Mikkonen, Tommi

AU - Systä, Kari

AU - Voutilainen, Jari-Pekka

AU - Taivalsaari, Antero

N1 - EXT="Mikkonen, Tommi" EXT="Taivalsaari, Antero"

PY - 2017/9/1

Y1 - 2017/9/1

N2 - The Liquid Software metaphor refers to software that can operate seamlessly across multiple devices owned by one or multiple users. Liquid Software applications can take advantage of the computing, storage and communication resources available on all the devices owned by the user. Liquid Software applications can also dynamically migrate from one device to another, following the user’s attention and usage context. The key design goal in Liquid Software development is to minimize the additional efforts arising from multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home and car displays, and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present the design space for Liquid Software, categorizing and discussing the most important architectural dimensions and technical choices. We also provide an introduction and comparison of two frameworks implementing Liquid Software capabilities in the context of the World Wide Web.

AB - The Liquid Software metaphor refers to software that can operate seamlessly across multiple devices owned by one or multiple users. Liquid Software applications can take advantage of the computing, storage and communication resources available on all the devices owned by the user. Liquid Software applications can also dynamically migrate from one device to another, following the user’s attention and usage context. The key design goal in Liquid Software development is to minimize the additional efforts arising from multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home and car displays, and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present the design space for Liquid Software, categorizing and discussing the most important architectural dimensions and technical choices. We also provide an introduction and comparison of two frameworks implementing Liquid Software capabilities in the context of the World Wide Web.

KW - Design space

KW - Liquid software

KW - Multi-device programming

KW - Multiple device ownership

KW - Software architecture

U2 - 10.26421/JWE16.5-6

DO - 10.26421/JWE16.5-6

M3 - Article

VL - 16

SP - 433

EP - 470

JO - Journal of Web Engineering

JF - Journal of Web Engineering

SN - 1540-9589

IS - 5-6

ER -