remove or include any interface object at a webpage
without the necessity of reloading the page.
Some of the first very popular applications using
Ajax are Google Suggest, Google Maps and Gmail.
Nowadays, Ajax is widely used in web development
and many platforms and development tools support
Ajax. The World Wide Web Consortium (W3C) is
also now working to standardize key Ajax
technologies such as the XMLHttpRequest
specification (W3C, 2009).
2.3 Norms and Flexible Interfaces
From the conceptual and theoretical points of view,
the proposed framework is based on Norm Analysis
Method (NAM) from MEASUR. Norms describe the
relationships between an intentional use of signs and
the resulting behaviour of responsible agents in a
social context; they also describe beliefs,
expectations, commitments, contract, law, culture, as
well as business.
“Norms can be represented in all kinds of signs,
whether in documents, oral communication, or
behaviour, in order to preserve, to spread and to
follow them. However, one cannot always put one’s
hands conveniently on a norm, as one might grasp a
document that carries information through an
organization. A norm is more like a field of force
that makes the members of the community tend to
behave or think in a certain way.” (Stamper et al.
2000, p. 15)
Besides the description of the agents’
responsibilities in the organisational context, Norm
Analysis can also be used to analyse the
responsibilities of maintaining, adapting and
personalising the system features.
Norms can be represented by the use of natural
language or Deontic Logic in the late stages of
modelling. The following format is suitable for
specifying behavioural norms (Liu, 2000):
<Norm>::= whenever <condition> if <state> then
<agent> is <D> to do <Action>
Where <D> is a deontic operator that specifies that
the action is obligatory, permitted or prohibited. The
norms are not necessarily obeyed by all agents in all
circumstances; they are social conventions (laws,
roles and informal conventions) that should be
obeyed. For example: a norm specifies that the
agents are obliged to pay a tax; if an agent has no
money it will not pay, but usually there is a cost
when an agent does not obey the norms.
Bonacin et al. (2009) present the foundations, a
framework, and a set of tools for personalized
service provision using norms simulation. Part of
their framework is used in this proposal; however
their framework is limited by using “thin client”
solutions, since a page reload is necessary for each
interface change. This work expands the possibilities
from the technological and practical points of view
by using the Ajax technology. In addition it is
provided an easier and more productive way to
develop flexible interfaces. In this work norms can
be evaluated during interaction with the system and
be immediately reflected in interface changes.
We propose to simulate the norms and deduce
the expected behavior of users and organizations
during the user interaction (real-time). For example,
if someone accesses an e-Government portal, and is
obliged to pay a tax, then he/she will probably be
interested in accessing information about the
payment procedure. So the system can be
immediately adapted according to the user needs and
preferences.
Norms are susceptible to changes in the
organizational context and in carrying the intentions
of agents in society. In the proposed approach,
domain specialists, designers and users maintain the
norms specifications according to the changes in
their socio-pragmatic (Stamper, 1973) context.
3 THE FRAMEWORK
PROPOSAL
In order to help the development of flexible
interfaces we propose FAN: an Ajax framework
using norms. FAN stands for Flexibility through
Ajax and Norms. The framework’s architecture is
described in section 3.1 and its execution aspects are
explained in section 3.2.
3.1 Framework Architecture
The framework we propose provides powerful
capabilities but it has a relatively simple architecture
which is shown in Figure 1. Basically, the
framework is composed of four modules:
Perception, SOAP Client, Action and Users’ Facts
Storage. These modules are responsible for tasks
such as creating, storing and loading contexts and
facts about the users, capturing events on the
presentation layer (interface, which is usually
constructed with HTML and CSS), accessing
NBIC/ICE web services (which maintain and
interpret Norms) and customizing the interface.
Regarding the development technologies, the
Perception, SOAP Client and Action modules were
ICEIS 2010 - 12th International Conference on Enterprise Information Systems
32