ity to a quality of service model, can be achieved.
In order to build such models we’ll need some
framework to provide us with a common set of con-
cepts to describe all the parts and their relations. Be-
ing this investigation under the scope of the Center
for Organizational Design and Engineering (CODE)
the preferred framework for this task will be the CEO
(Vasconcelos et al., 2007). Because CEO framework
does not consider fuzzy logic and some quality of ser-
vice related concepts, an extension proposal will be
presented in order to enable the creation of the mod-
els required to this investigation.
2 RELATED WORK
To have models, we perform modeling. According
to (Silva and Videira, 2001) modeling is both an art
and a science, and a model is the interpretation of a
subset from the real world. Through the simplifica-
tion of the reality down to a set of concepts and rela-
tions, different languages can be used to describe the
model according to the audience expectations, knowl-
edge and/or objectives.
2.1 Quality of Service
Quality is generally defined as a multidimensional
concept (Khaddaj et al., 2004). These dimensions are
used to construct a quality model, as also described
in the International Standard ISO 9126. As for ser-
vice, in the domain of enterprise architectures, (Open,
2006) defines it as a mechanism that provides access
to capabilities. In the field of networking, the notion
of quality of service is associated with the guaran-
tees of performance transporting a flow of informa-
tion, measured mostly through specific metrics.
A broad review of quality of service investigation
is presented in (Campbell et al., 1996), which de-
fends that investigation is mostly focused on individ-
ual layers, instead of addressing the overall QoS Ar-
chitecture. Also, a generalized QoS framework is de-
scribed, to include principles about its construction,
specification and mechanism to handle the system’s
behaviour. QoS specification is described as the cap-
turing of quality level requirements and management
policies, which will be different for each architectural
layer. As for QoS Mechanisms, it will vary accord-
ing to the specification and can be separated in three
groups: provision, control and management mecha-
nisms.
On the topic of QoS specification, (S.O. et al.,
2010) presents a survey of models, according to a
classification set. The authors conclude that perfor-
mance is itself subjective and open to different in-
terpretations. Also, most models were found to be
limited by their inability of handle uncertainty and
imprecision. Some approaches, like the probabilistic
models, which can handle vagueness, is however not
adequate to handle information expressed in natural
language.
2.2 Enterprise Architectures
Based on (Lankhorst, 2005) to manage the complex-
ity of large systems it’s necessary to have an archi-
tecture, which captures all the components, their re-
lationships with each other and their surrounding en-
vironment. An architecture also provides a common
language to describe the system, it’s components and
their relations, improving overall communication be-
tween the stakeholders.
This notion was extended to the field of enterprise
engineering and from that originated the term of En-
terprise Architecture (EA). An enterprise is seen as
a complex system where through a ”whole of princi-
ples, methods and models” it can be decomposed in
individual functional parts with respective relations.
2.2.1 Framework CEO
CEO framework (Vasconcelos et al., 2007) originated
in CODE investigation group, and its goal was set to
describe organizational knowledge as its various lev-
els and the dependency between them. CEO decom-
poses an organization on three separate levels: organi-
zational goals, business processes and resources, each
with adequate forms of representation according to
the concepts in question.
CEO uses the Unified Modeling Language (UML)
for implementation, with the help of developed
stereotypes. In order to represent information sys-
tems’ concepts, the framework extended its meta
model with the necessary concepts, which will be the
starting point for our own extension proposal.
3 SOLUTION PROPOSAL
Our solution is targeted at reducing some of the com-
plexity in models by creating models that don’t force
the removal of uncertainty. That will be achieved
through the use of fuzzy logic’s concepts, using the
method described in the following section.
FUZZY LOGIC BASED QUALITY OF SERVICE MODELS
517