You are on page 1of 61

Analysing The Bank Customer

Mining the E-commerce Data to Analyze the Target Customer Behavior

Analysing The Bank Customer

1. INTRODUCTION TO PROJECT
1.1 SCOPE Here, the part of the proposed methodology being done by k-means algorithm. A stationary sensor network is a static ad hoc network composed of hundreds or thousands of sensor nodes. Each sensor node is equipped with a sensing device, a low computational capacity processor a short-range wireless transmitter-receiver and a limited battery-supplied energy .Sensors monitor some surrounding environmental phenomenon, process the sensed data and forward it towards a close base station (i.e. a sink). This latter collects the data from the different sensor nodes and transmits this data to some remote control station where the data will be exploited at the application level. 1.2 OBJECTIVE The proposed tool to mining of e-commerce data is powerful. It gathering the information about the various customers behavior by processing of data and make them in to wide category to get a quality decision to place the organizations policy. Once clear with data types and quality decisions, it lead to survey the society to launch the product and the services and get a good revenue.

Analysing The Bank Customer

2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
The traditional methods for predicting and analyzing customer demands have found a wide range of applications. They are mainly used for predicting the total quantity of products that belong to the same family rather than the relationship between the different customer groups and associated product groups.

2.2 PROPOSED SYSTEM


E-commerce is changing the face of business. It allows better customer management, new strategies for marketing, an expanded range of products, and more efficient operations. A key enabler of this change is the widespread use of increasingly sophisticated data mining tools. The term data mining is used to describe the process of analyzing a companys internal data for customer profiling and targeting. In ecommerce application, the end goal of data mining is to improve processes that contribute to delivering value to the end customer. E-commerce data are classified as usage data, content data, structure data, and user data. Usage data contain details of user sessions and page views. Once the data types are clear, data preparation is easily achieved. The author then proposes association rules, sequential and navigational patterns, and clustering approaches for personalization of transactions as well as web pages.By using K-Means algorithm to cluster, results from the data were segmented in few clusters. Based on the statistical results of customer usage, e-banking transactions, our desired information have been achieved.

Analysing The Bank Customer

2.3 SOFTWARE REQUIREMENTS SPECIFICATION 2.3.1 FUNCTIONAL REQUIREMENTS

The Functional Requirements package details behavioral requirements that specify how a proposed system will process and handle information. It details the features and rules that must be present to fully implement the functionality desired. 2.3.1.1 ACCOUNT MANAGEMENT The system must have a feature to create an account, modify account and removing the account. This must also consider the terms and conditions for creating removing accounts. 2.3.1.2 CASH DEPOSITE The cash deposit means add the cash to the existing bank account. This must also have to check weather the account can accommodate that account and currency conversion details... Etc., 2.3.1.3 CASH WITHDRAWAL This transaction deals with withdrawing the cash from the bank account. The system must check weather there is sufficient funds in the account or not. This must also include checks like minimum account balance...Etc 2.3.1.4 A-TO-A TRANSACTION This deals with the transfer of money from one account to another account. The system must ensure that there are sufficient funds in the source account. The system must also take care of the transaction that must be successfully completed are not. This must also ensure that all the ACID properties are implemented successfully.

Analysing The Bank Customer 2.3.1.5 SINGLE USER ANALYSIS

The system must have a provision to implement the data mining techniques to analyze the customer behavior.

2.3.2 NON-FUNCTIONAL REQUIREMENTS

2.3.2.1 PERFORMANCE Performance requirements define parameters such as transactions per second, network latency, form load times and other measurable aspects of the system that govern overall speed and responsiveness. 2.3.2.2 COMPUTATIONAL COST The system must be built based on the low computational cost. This enables to use the best algorithm in implementing all the areas of which are used frequently. 2.3.2.3 PASSWORD STORAGE Best algorithm must be used to ensure the password security of the online transactions of the customers. 2.3.2.4 PRIVACY The system must implement sandbox model to ensure the security of the system. 2.3.2.5 MICROSOFT ACCESS The entire system relays on the Microsoft access database backend to store and retrieve the transaction information as well as the account information.

2.3.3 SOFTWARE AND HARDWARE DESCRIPTION 2.3.3.1 SOFTWARE REQUIREMENTS

Analysing The Bank Customer

Programming Language Technologies Operating System Database(back end)

JAVA 2 Standard Edition Jdbc,java-swings Microsoft Windows Xp

2.3.3.2 HARDWARE REQUIREMENTS Processor Hard Disk Ram Intel p4 80GB 512MB

3. SYSTEM DESIGN

Analysing The Bank Customer

The purpose of the design phase is to plan a solution of the problem specified by the requirement document. This phase is the first step in moving from problem domain to the solution domain. The design of a system is perhaps the most critical factor affecting the quality of the software, and has a major impact on the later phases, particularly testing and maintenance. The output of this phase is the design document. This document is similar to a blue print or plan for the solution, and is used later during implementation, testing and maintenance. The design activity is often divided into two separate phase-system design and detailed design. System design, which is sometimes also called top-level design, aims to identify the modules that should be in the system, the specifications of these modules, and how they interact with each other to produce the desired results. At the end of system design all the major data structures, file formats, output formats, as well as the major modules in the system and their specifications are decided. During detailed design the internal logic of each of the modules specified in system design is decided. During this phase further details of the data structures and algorithmic design of each of the modules is specified. The logic of a module is usually specified in a high-level design description language, which is independent of the target language in which the software will eventually be implemented. In system design the focus is on identifying the modules, whereas during detailed design the focus is on designing the logic for each of the modules.

3.1DATAFLOW DIAGRAMS

Analysing The Bank Customer

A data flow diagram is graphical tool used to describe and analyse movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component in a DFD is labelled with a descriptive name. Process is further identified with a number that will be used for identification purpose. The development of DFDS is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD. The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail is described for analyst to understand the process. 3.1.1 DFD SYMBOLS In the DFD, there are four symbols 1. A square defines a source(originator) or destination of system data 2. An arrow identifies data flow. It is the pipeline through which the information flows 3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows. 4. An open rectangle is a data store, data at rest or a temporary repository of data

Analysing The Bank Customer Process that transforms data flow

Source or Destination of data Data flow Data Store Fig 3.1 symbols of DFD

3.1.2 CONSTRUCTING A DFD Several rules of thumb are used in drawing DFDS: 1. Process should be named and numbered for an easy reference. Each name should be representative of the process. 2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it is marked with a short diagonal. 3. When a process is exploded into lower level details, they are numbered. 4. The names of data stores and destinations are written in capital letters. Process and dataflow names have the first letter of each work capitalized. A DFD typically shows the minimum contents of data store. Each data store should contain all the data elements that flow in and out. Questionnaires should contain all the data elements that flow in and out. Missing interfaces redundancies and like is then accounted for often through interviews. 3.1.3 SALIENT FEATURES OF DFDs

Analysing The Bank Customer

1. The DFD shows flow of data, not of control loops and decision are controlled considerations do not appear on a DFD. 2. The DFD does not indicate the time factor involved in any process whether the dataflow take place daily, weekly, monthly or yearly. 3. The sequence of events is not brought out on the DFD. Data Flow Diagrams are of two types: 1.Physical Data Flow Diagrams: These are implementation-dependent i.e., they show the actual devices, departments, people, etc., involved in the system. 2.Logical Data Flow Diagrams: These diagrams describe the system independently of how it is actually implemented, they show what takes places, rather than how an activity is accomplished.

The DFD is intended to represent information Flow but it is not a flow chart and is not intended decision-making, flow of control, loops and other procedural aspects of the system. DFD is a useful Graphical tool and is applied at the earlier stages of requirements analysis. It may be further refined at preliminary design stage and is used as mechanism for top-level structural design for software. The DFD drawn first at a preliminary level is further expanded into greater details: The context diagram is decomposed and represented with multiple rectangles. Each of these rectangles may be decomposed further and given as more detailed DFD. Explanation of DFD

Analysing The Bank Customer

3.2 UNIFIED MODELING LANGUAGE DIAGRAMS 3.2.1 OBJECTIVE DESIGNING AN INFORMATION SYSTEM

Analysing The Bank Customer

Following are the main objective of the system design phase Specify the logical elements Support business activities Ensure that a system feature meets user requirements Provide detailed software development specification

3.2.2 UNIFIED MODELING LANGUAGE


There are three different models of a system:

The Use case model, represented in UML with use case diagrams, The Object model, represented in UML with class diagram, describes the The Dynamic model, represented in UML with sequence diagrams, state

describes the functionality of the system from the users point of view.

structure of a system in terms of objects, attributes, associations and operations.

chart diagrams, activity diagram describes the internal behavior of the system.

The heart of object-oriented problem solving is the construction of a model. The model abstracts the essential details of the underlying problem from its usually complicated real world. Several modeling tools are wrapped under the heading of the UML, which stands for Unified Modeling Language. The purpose of this course is to present important highlights of the UML.

Analysing The Bank Customer

At the center of the UML are its nine kinds of modeling diagrams, which we describe here.

Use case diagrams Class diagrams Object diagrams Sequence diagrams Collaboration diagrams Statechart diagrams Activity diagrams Component diagrams Deployment diagrams

3.2.2.1 USE CASE DIAGRAM


Use case Diagrams represent the functionality of the system from a users point of view. Use cases are used during requirements elicitation and analysis to represent the functionality of the system. Use cases focus on the behavior of the system from external point of view. Actors are external entities that interact with the system. Examples of actors include users like administrator, bank customer etc., or another system like central database.

Analysing The Bank Customer


u c Pri m a ry U s e Ca s e s

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V
The System Boundary shows the and the system Mining e-commerce data for analyzing target customerbeing described. behavior

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V logical interface between users

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V
Analyzes Each

Customer EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V View s Accounts Details

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

Analyses EA 7.1 Unregistered Trial Version EA 7.1all customers Unregistered Trial Version EA 7.1 Unregistered Trial V Admin Changes Options

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V
creates new Account

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V
Prints Customer balences

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V
Makes Transcations

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version Usecase diagram for admin Version EA 7.1 Unregistered Trial V Fig:3.1 EA 7.1 Unregistered Trial

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial Version EA 7.1 Unregistered Trial V

Analysing The Bank Customer 3.2.2 CLASS DIAGRAM

A logical entity encapsulating data and behavior. A class is a template for an object - the class is the design, the object the runtime instance.

Login UserName Password Login() WithDraw getId() Load() BankSyste m getAccNO() BankSyste m() FindRecord( ) Quit() Show() NewAccount newAccount( ) saveArray() saveFile() Dep.Money Depsoit()
Load()

CreditAnaly si creditAnaly s Load() ShoeRec()

showRec()

DelCustomer delCustomer( ) deleteFile() delRec() ViewOne btnEnable()


populateArray ()

ViewCustm er getId() showRec()

showRec()

Fig:3.2 class diagram

Analysing The Bank Customer 3.2.2.3 SEQUENCE DIAGRAM

Sequence diagrams describe patterns of communication among a set of interacting objects. An object interacts with another object by sending messages. The reception of a message by an object triggers the execution of an operation, which in turn may send messages to other objects. Arguments may be passed along with a message and are bound to the parameters of the executing operation in the receiving object. Each column represents an object that participates in the interaction. The vertical axis represents time top to bottom. Arrows show messages. Labels on arrows represent message names and may contain arguments. Activations are depicted by vertical rectangles. Actors are shown as the leftmost column. Sequence diagrams can be used to describe either an abstract sequence (i.e., all possible interactions) or concrete sequences (i.e., one possible interaction). When describing all possible interactions, sequence diagrams also provide notations for conditionals and iterations.

Analysing The Bank Customer

s d S e q u e n ce

E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e


: D l D o nw w E A 7 . 1 : LUo g ni n r :eB ag n ik sS ytEseCt eArr meed 7idt A. n:1Ta el ryUesi iat sen Cl r:uVs et gp moir ssesi rttEeoFoArinn eed 7Ad c. c1ToN ue rUitAanc lcr:oWVu ingteht dir srsa tEeoMArno en 7ed y . 1T rUi an l r V e e Mi : y e i e

E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e


L o g in ()

A d m in

E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e


g e tA c c o u n tN o ()

E A 7 . 1 U C nr e dr iet A gn ai sl y tsEies (Ar) e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e
D o B o g u sT a sk(in t) c v E A 7 . 1 U n sru eb mg i it (sA tEet i oArn eE 7d e. n1Tt ) rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e

E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e


D e p o si tM o n e y (S tri n g , S tri n g )

d e l e tio n ()

E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e


fin d R e c ()

E A 7 . 1 U n r e g i s tEe Ar e N7de .w 1T c rcUoi aunnl tr( V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e A ) E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e
fi n d R e c ()

E A 7 . 1 U n r e g i s tEe Ar e 7d . W1T i t hrUid arna lwr MV ogn eir sys( t)Eeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tsEheooArn eR 7ed c. ( 1iTn t )rUi an l r V ee i ee i w e
r E ( f Ao m 7A .c 1t o r sU) n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e

E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e E A 7 . 1 U n r e g i s tEe Ar e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V g ir ss tEeo Arn e 7d . 1T rUi an l r V ee i ee i e

Fig:3.3 Sequence diagram

Analysing The Bank Customer 3.2.2.4 E-R DIAGRAM

The entity-relationship data model allows us to describe the data involved in real world enterprise in terms of objects (entities) and their relationships, and is widely used to develop an initial database design. The ER model is important for its role in database design. It provides a useful concept that allows changing the detailed and informal description of what users want to a precise and formal description that can be implemented in a DBMS. Within the overall design process, the ER model is used in a phase called Conceptual database design.

Authenticati on

Chec k

With draw

Create Account

Deposit

Store

Personal Details

Fig:3.4 E-R diagram

Analysing The Bank Customer

ACTIVITY DIAGRAM The outgoing transitions are triggered by the completion of an action associated with the state. This is called an action state. The name of a state denotes a condition, whereas the name of an action state denotes an action. Activity diagrams are state chart diagrams whose states are action states. An alternative and equivalent view if activity diagram is to interpret action states as a control LOGIN flow between activities and transitions; that is, the arrows are interpreted as sequential constraints between activities. Decisions are branches in the control flow. They denote alternative transitions based on a condition of the state of an object or a set of objects. Decisions are depicted by a diamond with one or more incoming arrows and two or more outgoing arrows. The outgoing arrows are labelled with the conditions that select a branch in the control flow.
Delete Customer Add New Acc. Find Record Bank System

Deposit Money

With Draw Money Credit Analysis

Analysing The Bank Customer

Fig:3.5 Activity diagram

3.3 DATA BASE SCHEMAS


The most important aspect of the system is data design.The data must be organized according to the system requirements. The database approach is used to store and organize the data in developing the system.The database is an integrated collection of data stored in different types of tables. Some general objectives in establishing a database is as follows: Integrating all data Incorporating update easily

Analysing The Bank Customer Provide data security from unauthorized users

Field Name USERNAME PASSWORD

Data Type VARCHAR2 VARCHAR2

Size 30 30

Constraint NOTNULL NOTNULL

Table 3.1:Authentication

Field Name
ACCNO ACCNAME DEPOSITEDDATE TOTALAMOUNT

Data Type
NUMBER VARCHAR2 DATE NUMBER

Size
10 30 10

Constraint
NOTNULL NOTNULL

Table 3.2:Deposit

Field Name ACCOUNTNO CUSNAME ACCDATE AMOUNT INITIALAMOUNT

Data Type NUMBER VARCHAR2 DATE NUMBER NUMBER

Size 10 30

Constraints NOTNULL

10 10

NOTNULL NOTNULL

Table 3.3:New account

Field Name ACCNO DATEOFBIRTH

Data Type NUMBER DATE

Size 10

Constraints NOTNULL

Analysing The Bank Customer


AGE ADDRESS PHONENO USERNAME PASSWORD PHOTOS NUMBER VARCHAR2 NUMBER VARCHAR2 VARCHAR2 VARCHAR2 3 200 15 30 30 200 NOTNULL NOTNULL NOTNULL

Table 3.4:Personaldetails

4.IMPLEMENTATION
4.1 MODULE DESCRIPTION
The system after careful analysis has been identified to be presented with the following modules: The modules involved are 1.Admin 2. Account Maintained module 4.1.1 ADMIN MODULE The user will click on new account creation to create a new account in thebanking system and account delete or modify.Admin can able to print the account details. 4.1.2 ACCOUNT MAINTAINED MODULE

Analysing The Bank Customer

The user will make transactions like , deposit and withdraw. The model subsystem will consider the actual business logic to be implemented. The transactions like deposit, withdraw, account creation, account deletion.. etc. will be considered here.The user will view the account details by person or one by one. 4.1.3 THEME DESIGN MODULE The options will enable the user to change the application theme, background color etc.The UI subsystem will consider the code for the designing the user interface, look and feel, screen designing and data presentation.

4.2 ARCHITECTURE 4.2.1 3-TIER ARCHITECTURE 4.2.1.1 Definition and motivation A 3-tier application is a program which is organized into three major disjunctive tiers. These tiers are

Presentation Tier (Front end) Logical Tier (Middleware) Data Tier (Backend).

Each layer can be deployed in geographically separated computers in a network. Some architects divide Logic Tier in to two sub tiers Business and Data Access Tiers, in order to increase scalability and transparency. The tiers can be deployed on physically separated machines. The characteristic of the tier communication is that the tiers will communicate only to their adjacent neighbours. For an example, The Presentation Tier will interact directly with the Business Tier and not directly with Data Access or Data Tiers.

Analysing The Bank Customer

Fig: 4.1 3-tier architecture The Figure shows a typical 3.Tier Architecture scenario. I think, we should look back the history of computing to understand the advantages of 3.Tier Architecture. Mainframes ruled the it-landscape until mid 1980s the main characteristic of a Host Architecture is that the application and databases reside on the same host computer and the user interacts with the host using an unfriendly and dump terminal. This monolith architecture does not support distributed computing (the host applications are not able to connect a database of a strategically allied partner). Some mangers found that developing a host application take too long and expensive. In fact, Client Server(C/S) architecture is 2-Tier architecture because the client does not distinguish between Presentation Tier and Logical Tier. That is why we call this type of client as Fat Client. The increasing demands on GUI difficulty to manage the mixture of source code from GUI Business Logic. Further, C/S Architecture does not support enough the change Management. Let us suppose that the government increases the consume tax rate from 14% to 16 %, then in the C/S case, you have to send an update to each clients and they must update synchronously on a specific time otherwise you may store corrupt information. and

Analysing The Bank Customer

Let us assume that about five hundred clients are working on a data server then we will have five hundred ODBC connections and several ruffian record sets, which must be transported from the server to the clients (because the Business Logic Tier is situated in the client side). The fact that C/S does not have any caching abilities like in ASP.NET caused additional traffic in the network. In the late1990s, designers have shifted the Business Logic from the client to server to elude the handicaps from C/S Architecture. Normally, a server has a better hardware than client therefore it is able compute algorithms faster than a client, so this fact is so an additional pro argument for the 3.Tier Architecture .Now let us go back to our 3.Tier Architecture and start to explore the tiers. 4.2.1.2 DATA TIER This Tier is responsible for retrieving, storing and updating from Information therefore this tier can be ideally represented through a commercial database. We consider stored procedures as a part of the Data Tier. Usage of stored procedures increases the performance and code transparency of an application. 4.2.1.3 LOGICAL TIER This is the brain of the 3.Tier Application. Some architects do not make any distinction between Business Tier and Data Access Tier. Their main argumentation is that additional tiers will screw down performance. I think that we will have more advantages, if we separate Logical Tier in to Business Tier and Data Access Tier. Some of these advantages are Increases code transparency Supports changes in Data Layer. You can change or alter database without touching the Business Layer and this would be a very minimum touch up 4.2.1.4 BUSINESS TIER This sub tier contents classes to calculate aggregated values such like total revenue, cash flow and debit and this tier doesnt know about any GUI controls and how

Analysing The Bank Customer to access databases. The classes of Data Access Tier will supply the needy information from the databases to this sub tier.

4.2.1.5 DATA ACCESS TIER This tier acts as an interface to Data Tier. This tier knows, how to (from which database) retrieve and store information. 4.2.1.6 PRESENTATION TIER This Tier is responsible for communication with the users and web service consumers and it will use objects from Business Layer to response GUI raised events. After this brief theory, I think we should move now to the practical part.

Analysing The Bank Customer

LOGIN

Analysing The Bank Customer

HOMEPAGE

Analysing The Bank Customer

REGISTRATION FORM

Analysing The Bank Customer

PRINT RECORD

Analysing The Bank Customer

DEPOSIT MONEY

Analysing The Bank Customer

WITHDRAWL MONEY

Analysing The Bank Customer

VIEW ACCOUNT HOLDERS

Analysing The Bank Customer

DELETE ACCOUNT HOLDERS

Analysing The Bank Customer

DELETED RECORD

Analysing The Bank Customer

Analysing The Bank Customer

CHOOSE BACKGROUND COLOR

Analysing The Bank Customer

Analysing The Bank Customer

ANALYSING FOR ONE MEMBER

Analysing The Bank Customer

ANALYSING STARTED

Analysing The Bank Customer

ANALYSING

Analysing The Bank Customer

ANALYSING COMPLETED

Analysing The Bank Customer

CHECKING DETAILS

Analysing The Bank Customer

OPENING NEW ACCOUNT

Analysing The Bank Customer

EDITING

Analysing The Bank Customer

VIEWING

Analysing The Bank Customer

SOFTWARE PROFILE
About Java
Initially the language was called as oak but it was renamed as Java in 1995. The primary motivation of this language was the need for a platform-independent (i.e., architecture neutral) language that could be used to create software to be embedded in various consumer electronic devices. Java is a programmers language. Java is cohesive and consistent. Except for those constraints imposed by the Internet environment, Java gives the programmer, full control. Finally, Java is to Internet programming where C was to system programming.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands the Universe of objects that can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the Server and the Personal computer. They are: Passive information and Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the areas of Security and probability. But, Java addresses those concerns and by doing so, has opened the door to an exciting new form of program called the Applet.

Java can be used to create two types of programs

Applications and Applets: An application is a program that runs on our Computer under the operating system of that computer. It is more or less like one creating

Analysing The Bank Customer

using C or C++. Javas ability to create Applets makes it important. An Applet is an application designed to be transmitted over the Internet and executed by a Java compatible web browser. An applet is actually a tiny Java program, dynamically downloaded across the network, just like an image. But the difference is, it is an intelligent program, not just a media file. It can react to the user input and dynamically change. Features Of Java Security
Every time you that you download a normal program, you are risking a viral infection. Prior to Java, most users did not download executable programs frequently, and those who did scanned them for viruses prior to execution. Most users still worried about the possibility of infecting their systems with a virus. In addition, another type of malicious program exists that must be guarded against. This type of program can gather private information, such as credit card numbers, bank account balances, and passwords. Java answers both these concerns by providing a firewall between a network application and your computer. When you use a Java-compatible Web browser, you can safely download Java applets without fear of virus infection or malicious intent.

Portability
For programs to be dynamically downloaded to all the various types of platforms connected to the Internet, some means of generating portable executable code is needed .As you will see, the same mechanism that helps ensure security also helps create portability. Indeed, Javas solution to these two problems is both elegant and efficient.

The Byte code


The key that allows the Java to solve the security and portability problems is that the output of Java compiler is Byte code. Byte code is a highly optimized set of instructions designed to be executed by the Java run-time system, which is called the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter for byte code.

Analysing The Bank Customer

Translating a Java program into byte code helps makes it much easier to run a program in a wide variety of environments. The reason is, once the run-time package exists for a given system, any Java program can run on it. Although Java was designed for interpretation, there is technically nothing about Java that prevents on-the-fly compilation of byte code into native code. Sun has just completed its Just In Time (JIT) compiler for byte code. When the JIT compiler is a part of JVM, it compiles byte code into executable code in real time, on a piece-by-piece, demand basis. It is not possible to compile an entire Java program into executable code all at once, because Java performs various run-time checks that can be done only at run time. The JIT compiles code, as it is needed, during execution.

Java Virtual Machine (JVM)


Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embedded within a web browser or an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process, a class loader is invoked and does byte code verification makes sure that the code thats has been generated by the compiler will not corrupt the machine that its loaded on. Byte code verification takes place at the end of the compilation process to make sure that is all accurate and correct. So byte code verification is integral to the compiling and executing of Java code.

Overall Description

Java Source
Java

Java byte code .Class

JavaV M

Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first box indicates that the Java source code is located in a. Java file that is processed with a Java compiler called javac. The Java compiler produces a file called a. class file, which contains the byte code. The. Class file is then loaded across the network or loaded locally on your machine into the execution environment is the Java virtual machine, which

Analysing The Bank Customer interprets and executes the byte code. Java Architecture

Java architecture provides a portable, robust, high performing environment for development. Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then interpreted on each platform by the run-time environment. Java is a dynamic system, able to load code when needed from a machine in the same room or across the planet. Compilation of code When you compile the code, the Java compiler creates machine code (called byte code) for a hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed to execute the byte code. The JVM is created for overcoming the issue of portability. The code is written and compiled for one machine and interpreted on all machines. This machine is called Java Virtual Machine.

Analysing The Bank Customer

Compiling and interpreting Java Source Code

Source Code .. ..
Macintosh PC Compiler Java Java Interpreter (PC) Java Java Interpreter Interpreter (Spare) (Platform SPARC Indepen dent) (Macintosh)

Byte code

..

Compiler

Compiler

During run-time the Java interpreter tricks the byte code file into thinking that it is running on a Java Virtual Machine. In reality this could be a Intel Pentium Windows 95 or SunSARC station running Solaris or Apple Macintosh running system and all could receive code from any computer through Internet and run the Applets.
Simple

Java was designed to be easy for the Professional programmer to learn and to use effectively. If you are an experienced C++ programmer, learning Java will be even easier. Because Java inherits the C/C++ syntax and many of the object oriented features of C++. Most of the confusing concepts from C++ are either left out of Java or implemented in a cleaner, more approachable manner. In Java there are a small number of clearly defined ways to accomplish a given task.

Analysing The Bank Customer

Object-Oriented

Java was not designed to be source-code compatible with any other language. This allowed the Java team the freedom to design with a blank slate. One outcome of this was a clean usable, pragmatic approach to objects. The object model in Java is simple and easy to extend, while simple types, such as integers, are kept as high-performance non-objects.
Robust

The multi-platform environment of the Web places extraordinary demands on a program, because the program must execute reliably in a variety of systems. The ability to create robust programs was given a high priority in the design of Java. Java is strictly typed language; it checks your code at compile time and run time. Java virtually eliminates the problems of memory management and deallocation, which is completely automatic. In a well-written Java program, all run time errors can and should be managed by your program.

Client Server

Over view: With the varied topic in existence in the fields of computers, Client Server is one, which has generated more heat than light, and also more hype than reality. This technology has acquired a certain critical mass attention with its dedication conferences and magazines. Major computer vendors such as IBM and DEC; have declared that Client Servers is their main future market. A survey of DBMS magazine reveled that 76% of its readers were actively looking at the client server solution. The growth in the client server development tools from $200 million in 1992 to more than $1.2 billion in 1996.

Analysing The Bank Customer

Client server implementations are complex but the underlying concept is simple and powerful. A client is an application running with local resources but able to request the database and relate the services from separate remote server. The software mediating this client server interaction is often referred to as MIDDLEWARE. The typical client either a PC or a Work Station connected through a network to a more powerful PC, Workstation, Midrange or Main Frames server usually capable of handling request from more than one client. However, with some configuration server may also act as client. A server may need to access other server in order to process the original client request.

The key client server idea is that client as user is essentially insulated from the physical location and formats of the data needs for their application. With the proper middleware, a client input from or report can transparently access and manipulate both local database on the client machine and remote databases on one or more servers. An added bonus is the client server opens the door to multi-vendor database access indulging heterogeneous table joins.

What is a Client Server

Two prominent systems in existence are client server and file server systems. It is essential to distinguish between client servers and file server systems. Both provide shared network access to data but the comparison dens there! The file server simply provides a remote disk drive that can be accessed by LAN applications on a file-by-file basis. The client server offers full relational database services such as SQL-Access, Record modifying, Insert, Delete with full relational integrity backup/ restore performance for high volume of transactions, etc. the client server middleware provides a flexible interface between client and server, who does what, when and to whom.

Analysing The Bank Customer Why Client Server

Client server has evolved to solve a problem that has been around since the earliest days of computing: how best to distribute your computing, data generation and data storage resources in order to obtain efficient, cost effective departmental an enterprise wide data processing. During mainframe era choices were quite limited. A central machine housed both the CPU and DATA (cards, tapes, drums and later disks). Access to these resources was initially confined to batched runs that produced departmental reports at the appropriate intervals. A strong central information service department ruled the corporation. The role of the rest of the corporation limited to requesting new or more frequent reports and to provide hand written forms from which the central data banks were created and updated. The earliest client server solutions therefore could best be characterized as SLAVE-MASTER.

Time-sharing changed the picture. Remote terminal could view and even change the central data, subject to access permissions. And, as the central data banks evolved in to sophisticated relational database with non-programmer query languages, online users could formulate adhoc queries and produce local reports with out adding to the MIS applications software backlog. However remote access was through dumb terminals, and the client server remained subordinate to the Slave\Master.

Front end or User Interface Design

The entire user interface is planned to be developed in browser specific environment with a touch of Intranet-Based Architecture for achieving the Distributed Concept.

The browser specific components are designed by using the HTML standards, and the dynamism of the designed by concentrating on the constructs of the Java Server Pages.

Analysing The Bank Customer Communication or Database Connectivity Tier

The Communication architecture is designed by concentrating on the Standards of Servlets and Enterprise Java Beans. The database connectivity is established by using the Java Data Base Connectivity.

The standards of three-tire architecture are given major concentration to keep the standards of higher cohesion and limited coupling for effectiveness of the operations.

Coding

Analysing The Bank Customer

Chapter 06

Testing

Analysing The Bank Customer

Analysing The Bank Customer

Chapter 07

Analysing The Bank Customer

Conclusions E-commerce companies are shifting from the old world of mass production where standardized products, homogeneous markets, and long product life and development cycles were the rule to the new world where variety and customization supplant standardized products. Instead of tens of thousands of products in a superstore, consumers may choose among millions of ones in an online store to satisfy the personalization demands. It is clear that target customers marketing can be effective when a e-commerce company is able to collect rich information about buyers behavior on ecommerce site. According to this study, the majority of the customers in e-commerce were male and online period was between 6 hours to 17.59 hours. The age is also an important factor that affects customer behavior. This can cause a market segment in the e-commerce. Personal computer at home are more popular for ecommerce than at work that can be attributed to the convenience of online purchasing at home. Chinese is more popular than English because Cluster 6 which used English was about 16%. It shows that some customers begin to access English e-commerce site to engage in international trade.

Analysing The Bank Customer

References [1] Randall S. Sexton, Richard A. and Michael A. Predicting Internet/e-commerce use, Internet Research, vol.5,2002, pp. 402-410. [2] N R Srinivasa Raghavan. Data Mining in E-commerce: A Servey. Sadhana, vol,30, no.2, 2005, pp.275-289. [3] Mobasher. B. Web Usage Mining and Personalization. Practical Handbook of Internet Computing (ed.) M P Singh (CRC Press), 2004. [4] Liuying Shen, Jana Hawley, etc. E-commerce Adoption for Aupply Chain Management in U.S. Apparel manufacturers. Journal of Textile and apparel, technology and management, vol.4, no.1, 2004, pp.1-10. [5] Strader, T.J., Shaw, M. J. Electronic Markets: Impact and implications, in: Shaw, M., Blanning, R., Strader, T.,

Analysing The Bank Customer Whinston, A. Handbook on Electronic Commerce, Springer, Berlin, 2000, pp.77-98. [6] Quinlan, J.R., Induction of Decision Trees, Machine Learning, Morgan Kaufmann Publishers, Inc, CA, 1990. [7] John A. Rodgers, David C. Yen and David C. Chou. Developing E-business: a Strategic Approach, Information Management & Computer Security, no.4, 2002, pp.184-192.

You might also like