On the Module of Internet Banking System

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 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].

A System Context Diagram is the highest level view of a system, similar to Block Diagram, showing a (normally software-based) system as a whole and its inputs and outputs from/to external factors. The Context Diagrams show the interactions between a system and other actors with which the system is designed to face. They are also typically drawn using labeled boxes to represent each of the external entities and another labeled box to represent the system being developed. The relationship is drawn as a line between the entities and the system being developed [7].

Context Diagram is a data flow diagram showing data flows between a generalized application within the domain and the other entities and abstractions with which it communicates. One thing that differentiates the use of data flow diagrams in domain analysis from other typical uses is that the variability of the data flows across the domain boundary must be accounted for with either a set of diagrams or text describing the differences [8].

Before we construct

…(Full text truncated)…