28-01-2012, 12:38 PM
INTRODUCTION
In the recent years there has been explosion of Internetbased
electronic banking applications (Liao & Cheung,
2003). Beckett, Hewer & Howcroft (2000) states that the
emergence of new forms of technology has created highly
competitive market conditions for bank providers.
However, the changed market conditions demand for
banks to better understanding of consumers' needs [1].
Liao et al. (2003) stress that the success in Internet
banking will be achieved with tailored financial products
and services that fulfill customer' wants, preferences and
quality expectations. Mattila (2001) concedes that
customer satisfaction is a key to success in Internet
banking and banks will use different media to customize
products and services to fit customers' specific needs in
the future. Liao et al. (2003) suggest that consumer
perceptions of transaction security, transaction accuracy,
user friendliness, and network speed are the critical
factors for success in Internet banking. From this
perspective, Internet banking includes many challenges
for human computer interaction (HCI) [2].
Hiltunen et al (2004) have remarked that there are at
least two major HCI challenges in Internet banking. The
first challenge is related to the problem how to increase
the number of services of Internet banking and
simultaneously guarantee the quality of service for
individual customers [3]. The second challenge is related
to the problem how to understand customer's needs,
translate them into targeted content and present them in a
personalized way in usable user interface. Hiltunen et al.
(2004) imply that Internet banking research will
concentrate more on HCI factors in the future [4].
Recently, Lindgaard & Dudek (2003) emphasize that now
is an ideal time for HCI researchers to analyse user
satisfaction, because there is growing interest in how to
attract and increase the number of online customers in ebusiness
and e-commerce. Lindgaard et al. (2003) stress
that HCI researchers should reveal a structure of user
satisfaction, determine how to evaluate it and conclude
how it is related to the overall user experience of online
customers. The concept of electronic banking has been
defined in many ways (e.g. Daniel, 1999). According to
Karjaluoto (2002) electronic banking is a construct that
consists of several distribution channels. Daniel (1999)
defines electronic banking as the delivery of banks'
information and services by banks to customers via
different delivery platforms that can be used with
different terminal devices such as a personal computer
and a mobile phone with browser or desktop software,
telephone or digital television [5].
The system models are abstract view of a system that
ignores some system details. Complementary system
models can be developed other information about the
system. And they are graphical representations that
describe business processes, the problem to be solved and
our system is to be developed. This reading may be
difficult to interpret. It is presented to cover the entire
concept of process modeling using the specific language
of systems design. In the homework for this module and
in a separate module reading (the Demonstration Project),
you will see these concepts applied to real situations
which will help you integrate the concepts [6].
System models play an important role in systems
development. Because system analysts are dealing with
unstructured problems (and end-users, too, deal with
them), there needs to be a systematic, logic-based
approach to converting a real-world problem, no matter
JOURNAL OF COMPUTING, VOLUME 2, ISSUE 5, MAY 2010, ISSN 2151-9617
HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/
WWW.JOURNALOFCOMPUTING.ORG
134
how vague, into a representation (or model) that captures
the main points and relationships so that the problem can
be analyzed. A model is a representation of the designer's
interpretation of reality. Models can be building for
existing systems as a way to understand better those
systems, or for proposed systems as a way to document
the organizational and information requirements or
technical designs [7].
SEQUENCE DIAGRAM
UML sequence diagrams model the flow of logic within
your system in a visual manner, enabling you both to
document and validate your logic, and are commonly
used for both analysis and design purposes.
Sequence diagrams are the most popular UML artifact for
dynamic modeling, which focuses on identifying the
behavior within your system. Sequence diagrams, along
with class diagrams and physical data models are in
experts’ opinion the most important design-level models
for modern business application development.
The Message Sequence Chart technique has been
incorporated into the Unified Modeling Language (UML)
diagram under the name of Sequence Diagram. A
sequence diagram shows, as parallel vertical lines,
different processes or objects that live simultaneously,
and, as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This
allows the specification of simple runtime scenarios in a
graphical manner. The dotted lines extending downwards
indicate the timeline, time flows from top to bottom. The
arrows represent messages (stimuli) from an actor or
object to other objects [9].
The UML 2.0 Sequence Diagram supports similar notation
to the UML 1.x Sequence Diagram with added support
for modeling variations to the standard flow of events. If
the lifeline is that of an object, it is underlined (if not it is a
role). Note that leaving the instance name blank can
represent anonymous and unnamed instances. In order to
display interaction, messages are used. These are
horizontal arrows with the message name written above
them. Solid arrows with full heads are synchronous calls,
solid arrows with stick heads are asynchronous calls and
dashed arrows with stick heads are return messages. This
definition is true as of UML 2, considerably different from
UML 1.x. Activation boxes, or method-call boxes, are
opaque rectangles drawn on top of lifelines to represent
that processes are being performed in response to the
message. Objects calling methods on themselves use
messages and add new activation boxes on top of any
others to indicate a further level of processing. When an
object is destroyed (removed from memory), an X is
drawn on top of the lifeline, and the dashed line ceases to
be drawn below it. It should be the result of a message,
either from the object itself, or another. A message sent
from outside the diagram can be represented by a
message originating from a filled-in circle. A UML
diagram may perform a series of steps, called a super
step, in response to only one external stimulus [10].
Sequence diagrams are typically used to model:
Usage scenarios. A usage scenario is a description of a
potential way your system is used. The logic of a
