Information Technology Reference
In-Depth Information
Figure 2. The conceptual meta-model
Context as a Dynamic Product Line
feature, we have adopted a simplified criteria
composed of the three steps shown below, fol-
lowed by the correspondent modeling decisions:
According to (Northrop 2002), a software product
line (SPL) is a set of software-intensive systems
sharing a common, managed set of features that
satisfy specific needs of a particular market or mis-
sion, and that are developed from a common set of
core assets in a prescribed way. Feature modeling
is a domain modeling technique, which has gener-
ated a lot of interest in the software product line
(SPL) community. Modeling product family as a
hierarchy of features their similarities, differences
and relationships among them, feature models
can be used for modeling common and variable
requirements of products in a SPL, scoping SPLs,
and product configuration and derivation.
Commonly there are five types of relations
possible in a feature model (Wang et al. 2007) (See
Table 1). Additional constraints between features
may exist that describe how features interact with
each other e.g. requires and excludes constraints.
In order to identify which of the context in-
formation is eligible for being modeled as a
•
Identify the context information required
by the application adaptation e.g. user lo-
cation. This should be represented by a ge-
neric feature in the feature model.
•
Identify the context model transforma-
tions or interpretations of the currently
available context information in order to
be shared by all application instances e.g.
room-, floor-, and building-resolution user
location information. These interpretations
should be represented by different feature
variants.
•
Regrouping the different identified context
features into a logical hierarchy of features
in a top-down manner that could be reused
by different applications.
The context feature model will be published in
a public registry. When an application developer
Search WWH ::
Custom Search