2010
DOI: 10.1016/j.jss.2009.11.002
|View full text |Cite
|
Sign up to set email alerts
|

Dealing with variability in context-aware mobile software

Abstract: Mobile context-aware software pose a set of challenging requirements to developers as these applications exhibit novel features, such as handling varied sensing devices and dynamically adapting to the user's context (e.g. his or her location), and evolve quickly according to technological advances. In this paper, we discuss how to handle variability both across different domains and during the evolution of a single application. We present a set of design structures for solving different problems related with m… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
31
0
4

Year Published

2010
2010
2020
2020

Publication Types

Select...
6
2
1

Relationship

2
7

Authors

Journals

citations
Cited by 32 publications
(35 citation statements)
references
References 38 publications
0
31
0
4
Order By: Relevance
“…The logical description of a mashup instance is an important artifact, which is used in later phases to suggest implementation possibilities or to exchange components at run-time, especially in telco-specific scenarios such as roaming. We suggest using RDF-based description languages and dedicated knowledge models to enable automatic composition and context adaption tasks [23].…”
Section: Fig 3 Telco Mashup Lifecyclementioning
confidence: 99%
“…The logical description of a mashup instance is an important artifact, which is used in later phases to suggest implementation possibilities or to exchange components at run-time, especially in telco-specific scenarios such as roaming. We suggest using RDF-based description languages and dedicated knowledge models to enable automatic composition and context adaption tasks [23].…”
Section: Fig 3 Telco Mashup Lifecyclementioning
confidence: 99%
“…An important feature of COIVA is the decoupling of modules to support scalability; this method also provides a way to anticipate future changes. For example, our approach separates the context model from behavioral mechanisms; Fortier et al 54 and Lu et al 55 studied in detail this requirement for context‐aware architectures. In general, the separation of the knowledge base from the inference engine is desirable from at least two standpoints.…”
Section: Background Literature and Contributionsmentioning
confidence: 99%
“…connectivity, location, etc.) [2], which rises the need for run-time adaptation and recomposition as depicted in [3].…”
Section: Introductionmentioning
confidence: 99%