Information Technology Reference
In-Depth Information
#
#")*#+ ,#
"""
%
%
%- %. %- %.
!
!
%
&
!
#
$
%&!'
%
%&!'"#
%&(
Fig. 1.
A Part of the E-Store [4] Software Product Line
Business process model templates are specified in a business process modeling
language. In Fig. 1, we use BPMN to specify a business process model tem-
plate. Such a template typically consists of process patterns like subprocesses
(
WishList
), activities (e.g.,
WishListNameEntry
), gateways (diamonds), condi-
tional sequence flows and data objects (
WishListName
). These process patterns
impose well-formedness constraints like grouping of activities.
Finally, mappings connect the features with elements of the solution space
model that implement the business logic of particular configurations. For ex-
ample, every configuration that contains the
Registration
feature, contains the
WishListName
data object. On the contrary, every configuration that does not
contain the feature
MultipleWishList
leads to a business process model where the
corresponding mapped activity
WishListNameEntry
is missing. All elements of
the business process model template that are not mapped to any feature are
contained in every business process model.
The problem in this context is given by the constraints of both modeling
spaces in combination with mappings between the feature model and the business
process model template. Given a particular feature configuration and a mapping,
we have to ensure, that the corresponding business process model satisfies the
well-formedness constraints of the template.
3 Solution Space Model Dependencies and Validation
In this paper, Description Logic (DL) [5] is used to formalize the constraints of
interests in models of interests and enable validation services. We could have
used some other formalism, but we opted for DL as it is precise and expressive
enough to serve our purpose - formalize constraints that need to hold between our
