Architecting liquid software
Research output: Contribution to journal › Article › Scientific › peer-review
Details
| Original language | English |
|---|---|
| Pages (from-to) | 433-470 |
| Number of pages | 38 |
| Journal | Journal of Web Engineering |
| Volume | 16 |
| Issue number | 5-6 |
| DOIs | |
| Publication status | Published - 1 Sep 2017 |
| Publication type | A1 Journal article-refereed |
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.
ASJC Scopus subject areas
Keywords
- Design space, Liquid software, Multi-device programming, Multiple device ownership, Software architecture