Personalized Mobile Applications for Remote Monitoring

Personalized Mobile Applications for Remote Monitoring

Miguel A. Laguna (ETSI Informática, University of Valladolid, Valladolid, Spain) and Javier Finat (ETSI Informática, University of Valladolid, Valladolid, Spain)
Copyright: © 2013 |Pages: 11
DOI: 10.4018/jehmc.2013010101
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

The development of mobile applications is a challenging activity. The main problems are the limits of the mobile devices (in memory size, processing power, battery duration, etc.) and the diversity of target platforms, display sizes, or input modes (keypads or tactile screens). For these reasons, the software product line (SPL) development paradigm can improve the process of designing and implementing mobile systems. The authors’ approach to SPL development uses the package merge relationship of the standard UML to represent the variability in all the SPL design and implementation models. The combination of this technique and conventional CASE and IDE tools (Eclipse or MS Visual Studio) makes the developments of SPLs for mobile applications easier as it removes the need for specialized tools and personnel. This article presents a SPL that makes possible the remote monitoring of dependent people to facilitate their autonomy. The SPL generic architecture uses Bluetooth wireless sensors connected to mobile devices. These devices are remotely connected to a central system, which could be used in hospitals or aged person’s residences. Moderate cost sensors allow health parameters such as heart rate or oxygen saturation level to be controlled. Risk situations can also be detected using a range of predefined values or specific sensors. The diversity of individual situations and the resource limitations favor the use of the SPL paradigm, as only the required features are incorporated in each concrete product.
Article Preview

Software Product Lines: Techniques And Tools

Feature diagrams represent the variability and commonality of software product lines and permit the configuration of each specific application to be selected. Feature diagrams are the more specific SPL techniques, aimed to handle variability and traceability at each abstraction level of the product line. The product line development requires these diagrams to represent the SPL variability and as a mechanism to obtain the configuration of features that represent the selected combination of variants for each specific application.

However, the optional features must be connected with the related variation points of the architectural models that implement the SPL. This link allows the automatic instantiation of the SPL generic architecture into each specific application. This is derived from the complete architecture selecting or not each optional feature. The selected feature sub-model, through traceability relationships, guides the composition of the pre-existing code packages. The precondition for the success of this process is the existence of traceability links from features to design and from design to implementation.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 9: 4 Issues (2018): 1 Released, 3 Forthcoming
Volume 8: 4 Issues (2017)
Volume 7: 4 Issues (2016)
Volume 6: 4 Issues (2015)
Volume 5: 4 Issues (2014)
Volume 4: 4 Issues (2013)
Volume 3: 4 Issues (2012)
Volume 2: 4 Issues (2011)
Volume 1: 4 Issues (2010)
View Complete Journal Contents Listing