D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

Dealing with Known Unknowns: A Goal-based Approach 23
one alternative works for both. This further reduces the number of truly alternative
configurations.
For example in the goal model of the AMAN system provided by ATM experts,
there are 54 goals (36 are leaves), 23 AND-decomposition, but only 6 design alternatives.
It means that the complexity of the join operator in this real world case
is less far than the number of nodes.
9 Related Works
Boyd [6] was one of the first who mentioned the term “enterprise model”. He
introduced many essentially concepts which later became pervasive in the area of
Enterprise Modeling (EM). Vernadat [40] defines EM as the process of building
models of the whole or part of an enterprise (e.g., process models, data models,
resource models, etc.)
There exists several techniques, frameworks, languages and tools for representation
of enterprise and its processes. They includes SADT, Data Flow Diagrams
(DFDs), IDEF0 and IDEF [32], activity diagrams in the UML, IEM [22],
GRAI/GIM [9], ARIS/EPC [34], UEML [39], CIMOSA [7], GERAM [5]. Besides
those, i* modeling framework [41] was introduced to support the modeling
of strategic relationships among organizational actors. It provides sets of concepts
that complement other approaches for organizational modeling (such as CIMOSA
and GERAM) to address the need for expressing complex organizational issues as
well as technology ones in an enterprise. However, these models do not cater for
the possibility of evolution.
Evolution was considered initially by Ba et al. [3] in their conceptual Enterprise
Modeling System (EMS). Their framework automatically builds and executes
task-specific models as needed in response to queries from users. The EMS
was designed to support strategic decision-making such as predicting the effects of
changes in business policies, analyzing possible reactions to internal and external
threats, and exploring new business opportunities. In general, the framework tried
to address the “what if”, “what should we do”, and “where should we go”-type of
questions. However, this framework was at high abstract level.
Loucopoulous and Kavakli [20] described an approach involving the explicit
modeling to express enterprise views in terms of the technical, social and teleological
dimensions and their relationship to information system goals. They also
illustrated their approach by a case study about Air Traffic Control. In another
work [21], they emphasized Enterprise Knowledge Management as the most important
factor to address the turbulent changes in many industry sectors. They
proposed an enterprise knowledge meta model which consisted of three main elements:
‘enterprise goals’ which are realized by ‘enterprise processes’ and implemented
by ‘information system components’. Each element has its own meta
model. The purpose of this enterprise knowledge was the improvement of the enterprise
in order to deal with changes. They recommended that enterprise change
management should be seen as a process of identifying business goals and relating
business processes to these goals. Though the authors did not have any concrete