A PROJECT REPORT

ON

CODETECT FINANCIAL FRAUD DETECTION WITH

ANOMALY FEATURE DETECTION
Submitted by partial fulfillment of the requirements for the award of the degree of

Bachelor of Technology
In
COMPUTER SCIENCE AND ENGINERRING
BY
P.KALYANI (16MG1A0579)

T.K.K.V.PRASAD (17MG5A0506)

A.GANGA BHAVANI (16MG1A0553)

CH.BHARGAV REDDY (16MG1A0588)

Under the Esteemed guidance of

Mr. P.SOMARAJU M.TECH

Asst.Professor. Dept. Of CSE

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

SREE VAHINI INSTITUTE OF SCIENCE AND TECHNOLOGY

(Approved by A.I.C.T.E, New Delhi, Affiliated to JNTU, Kakinada)

Tiruvuru, Krishna Dist-521235, ANDHRA PRADESH

2016-2020
 SREE VAHINI INSTITUTE OF SCIENCE AND TECHNOLOGY
(Approved by A.I.C.T.E, New Delhi, Affiliated to JNTU, Kakinada)

Tiruvuru, Krishna Dist-521235, ANDHRA PRADESH

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE
This is certify that the project report entitled “CODETECT FINANCIAL
FRAUD DETECTION WITH ANOMALY FEATURE DETECTION” submitted by
P.KALYANI (16MG1A0579), T.K.K.V.PRASAD (17MG5A0506), A.GANGA BHAVANI
(16MG1A0553) , CH.BHARGAV REDDY (16MG1A0588) in partial fulfillment of the
requirements for the award of the degree of BACHELOR OF TECHNOLOGY in
COMPUTER SCIENCE AND ENGINEERING from Dept..Of CSE, SREE VAHINI
INSTITUTE OF SCIENCE AND TECHNOLOGY Tiruvuru, A.P.Affiliated to
JNTUK, Kakinada, is a Record of Bonafied work carried out by them under my Guidance

INTERNAL GUIDE HEAD OF THE DEPART MENT

Mr.P.SOMARAJU.M.TECH K.V.PANDURANGARAO M.TECH (Ph.D.)
Asst.Professor. Dept. Of CSE Prof., Dept.of.CSE

External Examiner
 DECLARATION BY THE CANDIDATES

We, P.KALYANI (16MG1A0579), T.K.K.V.PRASAD (17MG5A0506),

A.GANGA BHAVANI (16MG1A0553), and CH.BHARGAV REDDY (16MG1A0588)
hereby declare that the project report entitled “CODETECT FINANCIAL
FRAUD DETECTION WITH ANOMALY FEATURE DETECTION”
under the supervision of Mr. P.SOMARAJU Asst Prof. Submitted in partial
fulfillment of the requirements for the award of the degree of Bachelor of Technology
in Computer Science and Engineering. This is a record of work carried from any
source and have not been submitted to any other University or Institute for the award of
any other degree or diploma.

P.KALYANI (16MG1A0579) T.K.K.V.PRASAD (17MG5A0506)

A.G.BHAVANI (16MG1A0553) CH.BHARGAV REDDY (16MG1A0588)

 ACKNOWLEDGEMENT
We thank the almighty for giving us the courage and perseverance in completing
this project. This project itself is acknowledgment for all those people who have given us
their heartfelt co-operation in making this project a grand success.

We are greatly indebted to our project guide Mr.P.SOMARAJU, Asst.Professor.

Dept. Of CSE, Sree Vahini Institute of Science and Technology, tiruvuru, for his time
co-operation and his valuable suggestions while carrying out this project work.

With extreme jubilance and deepest gratitude we would like to thank

Prof.K.V.PandurangaRao, HOD, Dept. of CSE, for his encouragement and valuable
guidance for completing our project successfully

We extreme our sincere thanks to Dr. R.NagendraBabu, Principal, Sree Vahini

Institute of Science and Technology, Tiruvuru, for the successful completion of our
degree.

Our special thanks to All Teaching and Non-Teaching Members of CSE

Department, Sree Vahini Institute of Science and Technology, Tiruvuru, for their timely
co-operation and valuable suggestions while carrying out this project.

Last but not the least, we would like to express our deep sense of gratitude and
earnest thanks giving to our dear parents for their normal support and heart full co-
operation in doing this project.

P.KALYANI (16MG1A0579) T.K.K.V.PRASAD (17MG5A0506)

A.G.BHAVANI (16MG1A0553) CH.BHARGAV REDDY (16MG1A0588)

ABSTRACT
 ABSTRACT

Financial fraud, such as money laundering, is known to be a serious

process of crime that makes illegitimately obtained funds go to terrorism or
other criminal activity. This kind of illegal activities involve complex
networks of trade and financial transactions, which makes it difficult to
detect the fraud entities and discover the features of fraud. Fortunately,
trading/transaction network and features of entities in the network can be
constructed from the complex networks of the trade and financial
transactions. The trading/transaction network reveals the interaction between
entities, and thus anomaly detection on trading networks can reveal the
entities involved in the fraud activity; while features of entities are the
description of entities, and anomaly detection on features can reflect details
of the fraud activities. Thus, network and features provide complementary
information for fraud detection, which has potential to improve fraud
detection performance. However, the majority of existing methods focus on
networks or features information separately, which does not utilize both
information. In this paper, we propose a novel fraud detection framework,
CoDetect, which can leverage both network information and feature
information for financial fraud detection. In addition, the CoDetect can
simultaneously detecting financial fraud activities and the feature patterns
associated with the fraud activities. Extensive experiments on both synthetic
data and real-world data demonstrate the efficiency and the effectiveness of
the proposed framework in combating financial fraud, especially for money
laundering.
 CONTENTS
S.NO NAME OF THE TOPIC PAGE.NO

LIST OF FIGURES i

LIST OF ABBERIVATIONS ii

1. INTRODUCTION 1-3

2. SYSTEM ANALYSIS 4-8

2.1 Existing System

2.2 Proposed system

2.3 System requirements

3. IMPLEMENTATION 9-10

3.1 Modules

3.2 Modules Description

4. SYSTEM STUDY 11-12

4.1 Feasibility Study

4.1.1 Economical Feasibility

4.1.2 Technical Feasibility

4.1.3 Social Feasibility

5. SOFTWARE ENVIRONMENT 13-32

5.1 Java Technology

5.2 ODBC

5.3 JDBC

5.3.1 JDBC Goals

 6. SYSTEM DESIGN 33-46

6.1 System Architecture

6.2 UML Diagrams

6.2.1 Use Case Diagram

6.2.2 Class Diagram

6.2.3 Sequence Diagram

6.2.4 Deployment Diagram

6.3 Data Flow Diagram

6.4 ER-Diagrams

7 SAMPLE CODE 47-54

8. SYSTEM TESTING 55-58

8.1 Types Of Tests

8.1.1 Unit Testing

8.1.2 Integration Testing

8.1.3 Functional Testing

9. OUTPUT SCREENS 59-65

10. CONCLUSION 66

11. BIBLIOGRAPHY 67-69

 LIST OF FIGURES

FIG.NO NAME OF THE FIGURES PAGE.NO

1 SYSTEM ARCHITECTURE 33
2 USE CASE DIAGRAM 36
3 CLASS DIAGRAM 38
4 SEQUENCE DIAGRAM 40
5 DEPLOYMENT DIAGRAM 41
6 DATA FLOW DIAGRAM 43

i
 LIST OF ABBREVIATIONS

ICT : information and communication technology

JSP : java server pages

URL : uniform resource locator

HTML : hyper text markup language

HTTP : hyper text transfer protocol

TCP : Transmission control protocol

JVM : java virtual machine

JAVAEE : java enterprise edition

GWT : Google web tool kit

JDBC : java data base connectivity

ODBC : open data base connectivity

API : Application programming interface

DFD :data flow diagram

UML : unified modeling language.

ii
CODETECT FINANCIAL FRAUD
DETECTION WITH ANOMALY
FEATURE DETECTION
INTRODUCTION
 SVIST INTRODUCTION

1. INTRODUCTION
In recent years, financial fraud activities such as credit card fraud,
money laundering, increase gradually. These activities cause the loss of
personal and/or enterprises' properties. Even worse, they endanger the
security of nation because the port from fraud may go to terrorism [1], [25].
Thus, accurately detecting financial fraud and tracing fraud are necessary
and urgent. However, financial fraud detection is not an easy task due to the
complex trading networks and transactions involved. Taking money
laundering as an example, money laundering is denied as the process of
using trades to move money/goods with the intent of obscuring the true
origin of funds. Usually, the prices, quantity or quality of good son an
invoice of money laundering are fake purposely. The misrepresentation of
prices, quantity or quality of goods on an invoice merely exposes slight
difference from regular basis if we use these numbers as features to generate
detection policy. Under certain circumstances, this kind of detector may
work well with relatively stable trading entities. Unfortunately, the real
world situation is more complicated, especially within Free Trade Zones
(FTZs) where international trade involves complex procedures and exchange
of information between trading entities. The fraud activities, especial money
laundering, are deeper stealth. Money laundering activities may take
different forms [1] such as the concealing transportation of cash using
trading operations; the acquisition and sale of intangibles; and related party
transactions. Not only the trading of goods shows on much more diversity,
but also different type of companies, shell and front companies involve in to
facilitate money laundering. In contrast with other fraud activities, money

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 1

 SVIST INTRODUCTION

laundering demonstrates special characteristic which presents high risk to

financial system with obscuring the money trail, collectivization behavior
and wild trading regions in FTZs.
May fraud detection models work with attribute value data points that
are generated from transactions data. Some aggregation methods are also
used to enrich the information of data [28]. After generating feature points
from transactions, supervised and unsupervised methods can be used to
perform detection [26], [27], [34]. Usually, these data points are assumed to
be independent and identically distributed (i.e.). However, the characteristic
of money laundering is different from attribute-value data. The
collectivization behavior means the data is inherently linked or partly linked.
Obviously, trading activity involves at least two business entities. Linked
data is patently not independent and identically distributed, which
contradicts the assumptions of traditional supervised and unsupervised
methods. On the other side, some linked data is auto correlated. For
example, trading between business entity A and B implies that feature points
A and B are correlated. Some features used to describe the properties of
trading goods can be identical between A and B.
This characteristic of auto correlation reduces the effective size of
data for learning. Furthermore, feature points don't fuse the interaction
information in data. The relations between any business entities indicate the
potential causality that means, if businesses on going, fraud entity can be
located by other identified fraud entity. This means the entity, which has
connection with fraud entity, are suspicious. Consequently, feature based
detection models with supervised or unsupervised methods have inherent

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 2

 SVIST INTRODUCTION

limitation of incapacity of identifying what the fraud relations are. What the
fraud relations are. Graph-based mining methods are one of the most
important theories that attempt to identify relations between data points [3],
[7], [13], as Fig. 1(a) shows. Financial activities can be modeled as a
directed graph, and then a sparse adjacent matrix can represent this graph.
With graph-mining method, the sparse matrix can be approximated as
summation of low-rank matrix and outlier matrix. The outlier matrix is a
sign of suspicious fraud activities. Exploiting the graph based mining
provides a new perspective for fraud detection and enables us to do
advanced research on fraud detection. With the fraud activities detected by
graph-based detection technique we are able to draw the conclusion that
several business entities involved in fraud, however, we still don't know how
these fraud activities are operated and why these activities labeled as fraud,
i.e., the detailed features of the fraud activities. The majority of this how-
and-why information is fused in features points, which have essential
meaning for financial fraud detection because of the tracing necessity. For
example, doing business with misrepresentation of the price may transfer
additional value to exporter. The value in this example reveals how the fraud
happened. This simple example requires the detection system to mark value
as fraud property. Another example, fraud activities might go deeper stealth
with multi-entities involved. If the same good or service invoices a number
of different business entities to make the payments, then there are several
properties should be consider as suspicious: business location, name,
direction, good or service etc. With the knowledge of these suspicious
properties, tracing fraud can be much easier for executives.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 3

SYSTEM ANALYSIS
 SVIST SYSTEM ANALYSIS

2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

 Bahnsen et al. [38] improve the detection performance by calibrating

probabilities before establishing Bayes model. HMM model is used to
model the customers' credit card shopping patterns for detection of
credit card fraud. The shopping items indicate the hidden state and the
corresponding prices from certain ranges are the observation. LR
(Logistic Regression), Support Vector Machines (SVMs) and Random
Forest (RF) are evaluated for credit card detection. The detection
models are built on primary features and derived features from
transaction.
 Whitrow et al. [28] proposed a new preprocessing strategy for better
fraud detection with SVMs and KNN classification. Transactions
aggregated in term of time window, and then data with new features is
used to model the pattern.
 Wei et al. [29] addressed the problem of unbalanced financial data and
employed cost-sensitive neural network to punish the misclassification
of fraud transaction. Sahin et al. [33] incorporate cost function into
decision tree to boost performance on unbalanced data. Following the
general procedure of classification, feature selection is proceeded to
boost the detection performance of credit card fraud.
 Perols [35] performed a systematic analysis of financial fraud detection
with popular statistical and machine learning models. The evaluation is
under the supervised manner. All these methods rely on accurate

CODETECT FNANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 4

 SVIST SYSTEM ANALYSIS

identification of fraud patterns from data set and these methods also
suffer from the problem of unbalanced data. Bolton and David perform
fraud detection with clustering methods. This unsupervised manner is
under the assumption that small cluster indicates the anomaly in data.
 CoDetect is an unsupervised model which is based on matrices co
factorization. The matrices from graph represent the genuine proprieties
(features and connections) of financial data. The detection results give a
better understanding of fraud patterns and furthermore, help to trace the
originate of fraud groups.

Disadvantages

 There is no Evaluation with Subspace Clustering Methods.

 There is no SVM Classification in Credit Card Fraud Detections.

CODETECT FNANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 5

 SVIST SYSTEM ANALYSIS

2.2 PROPOSED SYSTEM

 In the proposed system, the system would like to develop a novel

framework for fraud detection by considering the special detecting and
tracing demanding of fraud entities and behaviors. Specifically, we
investigate: (1) how to utilize both graph matrix and feature matrix for
fraud detection and fraud tracing; (2) how to mathematically model
both graph matrix and feature matrix so as to simultaneously achieve
the tasks of fraud detection and tracing. In an attempt to solve these
challenges.
 The system proposed a novel detection framework CoDetect for
financial data, especially for money laundering data. The system
incorporates fraud entities detection and anomaly feature detection in
the same framework to find fraud patterns and corresponding features
simultaneously. Combining entities detection and feature detection
enables us to build a novel fraud detection framework for noisy and
sparse financial data: relevant fraud patterns help the identification of
fraud identities, and relevant features in turn help revealing of the
nature of fraud activities.

Advantages

 Provide an approach to establish weighted graph from financial

network, incorporating properties of nodes and links.
 Propose a novel unsupervised framework, CoDetect, for the problem
of

CODETECT FNANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 6

 SVIST SYSTEM ANALYSIS

complex patterns discovery and anomaly features identification,

employing two matrices residual analysis on graph-based financial
network.
 Evaluate framework using synthetic and real world data to
demonstrate both effectiveness and efficiency of the proposed
framework.

CODETECT FNANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 7

 SVIST SYSTEM ANALYSIS

2.3 SYSTEM REQUIREMENTS:

HARDWARE REQUIREMENTS:

 System : Pentium IV 2.4 GHz.

 Hard Disk : 40 GB.

 Floppy Drive : 1.44 Mb.

 Monitor : 15 VGA Colour.

 Mouse : Logitech.

 Ram : 512 Mb.

SOFTWARE REQUIREMENTS:

 Operating system : Windows XP/7.

 Coding Language : JAVA/J2EE

 IDE : Net beans 7.4

 Database : MYSQL

CODETECT FNANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 8

IMPLEMENTATION
 SVIST IMPLEMENTATION

3. IMPLEMENTATION

3.1 MODULES

 BANK ADMIN
 USER
 TRANSPORT COMPANY

3.2 MODULES DESCRIPTION

Bank Admin
In this module, the Admin has to login by using valid user name and
password. After login successful he can do some operations such as View
all users and authorize, View all Transport Users and authorize, Register and
Login (With Bank Name), View all users and authorize, View All Transport
company users and authorize, Add bank with its details such as bname,
baddress, blocation, bpin, bmailid, bcno, add building image, View Credit
card request and Process with Ac.No and CRN, credit limit, Card cvv (4
digit) number, Cash Limit. ,View all transport booking fees details for each
company based on cluster ,View all transport booked details for each
company based on cluster, View all type of Financial Fraud based on cluster,
View all users with Financial Fraud and give link to show number of same
user is fraud in chart

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 9

 SVIST IMPLEMENTATION

User

In this module, there are n numbers of users are present. User should
register with group option before doing some operations. After registration
successful he has to wait for admin to authorize him and after admin
authorized him. He can login by using authorized user name and password.
Login successful he will do some operations like Register and Login, View
your profile, Manage Bank Account ,Request Credit card with * Details and
view the same ,View Card Transactions based on transport booked details
,View your payments and transfer to your cc account (if user doesn’t have
enough amount to transfer then he is a fraud user or abnormal user) ,View all
transport company and select corresponding company and book, give
reviews, increment rank ,enter card cvv number(Find fraud if no balance in
cc, if cvv number is wrong) ,View all Booked transport

Transport Company

In this module, there are n numbers of users are present. Transport

Company user should register with group option before doing some
operations. After registration successful he has to wait for admin to
authorize him and after admin authorized him. He can login by using
authorized user name and password. Login successful he will do some
operations like Register with Company name and Login ,Add Transport
Details(See below) ,View all Transport Details ,View all Booked Transport
Details with total bill ,Find financial fraud -- View all normal and Fraud
users ,View Type of Financial frauds(Give link below to show numbers of
same frauds in chart ).
CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 10
SYSTEM STUDY
 SVIST SYSTEM STUDY

4. SYSTEM STUDY

4.1 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business
proposal is put forth with a very general plan for the project and some cost estimates.
During system analysis the feasibility study of the proposed system is to be carried out.
This is to ensure that the proposed system is not a burden to the company. For feasibility
analysis, some understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY
4.1.1 ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that the
system will have on the organization. The amount of fund that the company can pour into
the research and development of the system is limited. The expenditures must be
justified. Thus the developed system as well within the budget and this was achieved
because most of the technologies used are freely available. Only the customized products
had to be purchased.

4.1.2 TECHNICAL FEASIBILITY

This study is carried out to check the technical feasibility, that is, the
technical requirements of the system. Any system developed must not have a high
demand on the available technical resources. This will lead to high demands on the
available technical resources. This will lead to high demands being placed on the client.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 11

 SVIST SYSTEM STUDY

The developed system must have a modest requirement, as only minimal or null changes
are required for implementing this system.

4.1.3 SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the
user. This includes the process of training the user to use the system efficiently. The user
must not feel threatened by the system, instead must accept it as a necessity. The level of
acceptance by the users solely depends on the methods that are employed to educate the
user about the system and to make him familiar with it. His level of confidence must be
raised so that he is also able to make some constructive criticism, which is welcomed, as
he is the final user of the system.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 12

 SOFTWARE
ENVIRONMENT
 SVIST SOFTWARE ENVIRONMENT
5. SOFTWARE ENVIRONMENT

5.1 JAVA TECHNOLOGY:

Java technology is both a programming language and a platform.

The Java Programming Language

The Java programming language is a high-level language that can be
characterized by all of the following buzzwords:
 Simple
 Architecture neutral
 Object oriented
 Portable
 Distributed
 High performance
 Interpreted
 Multithreaded
 Robust
 Dynamic
 Secure
 With most programming languages, you either compile or interpret a program so that you
can run it on your computer. The Java programming language is unusual in that a
program is both compiled and interpreted. With the compiler, first you translate a
program into an intermediate language called Java byte codes —the platform-
independent codes interpreted by the interpreter on the Java platform. The interpreter
parses and runs each Java byte code instruction on the computer. Compilation happens
just once; interpretation occurs each time the program is executed. The following figure
illustrates how this works.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 13

 SVIST SOFTWARE ENVIRONMENT

You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether it’s a development tool or a
Web browser that can run applets, is an implementation of the Java VM. Java byte codes
help make “write once, run anywhere” possible. You can compile your program into byte
codes on any platform that has a Java compiler. The byte codes can then be run on any
implementation of the Java VM. That means that as long as a computer has a Java VM,
the same program written in the Java programming language can run on Windows 2000,
a Solaris workstation, or on an iMac.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 14

 SVIST SOFTWARE ENVIRONMENT

The Java Platform

A platform is the hardware or software environment in which a program runs.
We’ve already mentioned some of the most popular platforms like Windows 2000,
Linux, Solaris, and MacOS. Most platforms can be described as a combination of the
operating system and hardware. The Java platform differs from most other platforms in
that it’s a software-only platform that runs on top of other hardware-based platforms.

The Java platform has two components:

 The Java Virtual Machine (Java VM)
 The Java Application Programming Interface (Java API)
You’ve already been introduced to the Java VM. It’s the base for the Java
platform and is ported onto various hardware-based platforms.

The Java API is a large collection of ready-made software components that provide
many useful capabilities, such as graphical user interface (GUI) widgets. The Java API is
grouped into libraries of related classes and interfaces; these libraries are known as
packages. The next section, What Can Java Technology Do? Highlights what
functionality some of the packages in the Java API provide.
The following figure depicts a program that’s running on the Java platform. As the
figure shows, the Java API and the virtual machine insulate the program from the
hardware.

Native code is code that after you compile it, the compiled code runs on
a specific hardware platform. As a platform-independent environment, the Java platform
can be a bit slower than native code. However, smart compilers, well-tuned interpreters,

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 15

 SVIST SOFTWARE ENVIRONMENT
and just-in-time byte code compilers can bring performance close to that of native code
without threatening portability.
What Can Java Technology Do?
The most common types of programs written in the Java programming language
are applets and applications. If you’ve surfed the Web, you’re probably already familiar
with applets. An applet is a program that adheres to certain conventions that allow it to run
within a Java-enabled browser.

However, the Java programming language is not just for writing cute, entertaining
applets for the Web. The general-purpose, high-level Java programming language is also a
powerful software platform. Using the generous API, you can write many types of
programs.
An application is a standalone program that runs directly on the Java platform. A
special kind of application known as a server serves and supports clients on a network.
Examples of servers are Web servers, proxy servers, mail servers, and print servers.
Another specialized program is a servlet. A servlet can almost be thought of as an applet
that runs on the server side. Java Servlets are a popular choice for building interactive web
applications, replacing the use of CGI scripts. Servlets are similar to applets in that they
are runtime extensions of applications. Instead of working in browsers, though, servlets
run within Java Web servers, configuring or tailoring the server.
How does the API support all these kinds of programs? It does so with packages of
software components that provides a wide range of functionality. Every full
implementation of the Java platform gives you the following features:
 The essentials: Objects, strings, threads, numbers, input and output, data
structures, system properties, date and time, and so on.
 Applets: The set of conventions used by applets.
 Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram
Protocol) sockets, and IP (Internet Protocol) addresses.
 Internationalization: Help for writing programs that can be localized for users
worldwide. Programs can automatically adapt to specific locales and be
displayed in the appropriate language.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 16

 SVIST SOFTWARE ENVIRONMENT

 Security: Both low level and high level, including electronic signatures, public
and private key management, access control, and certificates.
 Software components: Known as JavaBeansTM, can plug into existing
component architectures.
 Object serialization: Allows lightweight persistence and communication via
Remote Method Invocation (RMI).
 Java Database Connectivity (JDBCTM): Provides uniform access to a wide
range of relational databases.
The Java platform also has APIs for 2D and 3D graphics, accessibility, servers,
collaboration, telephony, speech, animation, and more. The following figure
depicts what is included in the Java 2 SDK.

How Will Java Technology Change My Life?

We can’t promise you fame, fortune, or even a job if you learn the Java
programming language. Still, it is likely to make your programs better and requires less
effort than other languages. We believe that Java technology will help you do the
following:
 Get started quickly: Although the Java programming language is a powerful
object-oriented language, it’s easy to learn, especially for programmers already
familiar with C or C++.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 17

 SVIST SOFTWARE ENVIRONMENT
 Write less code: Comparisons of program metrics (class counts, method counts,
and so on) suggest that a program written in the Java programming language can
be four times smaller than the same program in C++.
 Write better code: The Java programming language encourages good coding
practices, and its garbage collection helps you avoid memory leaks. Its object
orientation, its JavaBeans component architecture, and its wide-ranging, easily
extendible API let you reuse other people’s tested code and introduce fewer
bugs.
 Develop programs more quickly: Your development time may be as much as
twice as fast versus writing the same program in C++. Why? You write fewer
lines of code and it is a simpler programming language than C++.
 Avoid platform dependencies with 100% Pure Java: You can keep your
program portable by avoiding the use of libraries written in other languages. The
100% Pure JavaTM Product Certification Program has a repository of historical
process manuals, white papers, brochures, and similar materials online.
 Write once, run anywhere: Because 100% Pure Java programs are compiled into
machine-independent byte codes, they run consistently on any Java platform.
 Distribute software more easily: You can upgrade applets easily from a central
server. Applets take advantage of the feature of allowing new classes to be
loaded “on the fly,” without recompiling the entire program.
5.2 ODBC:
Microsoft Open Database Connectivity (ODBC) is a standard programming
interface for application developers and database systems providers. Before ODBC
became a de facto standard for Windows programs to interface with database systems,
programmers had to use proprietary languages for each database they wanted to connect
to. Now, ODBC has made the choice of the database system almost irrelevant from a
coding perspective, which is as it should be. Application developers have much more
important things to worry about than the syntax that is needed to port their program from
one database to another when business needs suddenly change.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 18

 SVIST SOFTWARE ENVIRONMENT
Through the ODBC Administrator in Control Panel, you can specify the particular
database that is associated with a data source that an ODBC application program is
written to use. Think of an ODBC data source as a door with a name on it. Each door will
lead you to a particular database. For example, the data source named Sales Figures
might be a SQL Server database, whereas the Accounts Payable data source could refer
to an Access database. The physical database referred to by a data source can reside
anywhere on the LAN.
The ODBC system files are not installed on your system by Windows 95. Rather,
they are installed when you setup a separate database application, such as SQL Server
Client or Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a
file called ODBCINST.DLL. It is also possible to administer your ODBC data sources
through a stand-alone program called ODBCADM.EXE. There is a 16-bit and a 32-bit
version of this program and each maintains a separate list of ODBC data sources.
From a programming perspective, the beauty of ODBC is that the application can be
written to use the same set of function calls to interface with any data source, regardless
of the database vendor. The source code of the application doesn’t change whether it
talks to Oracle or SQL Server. We only mention these two as an example. There are
ODBC drivers available for several dozen popular database systems. Even Excel
spreadsheets and plain text files can be turned into data sources. The operating system
uses the Registry information written by ODBC Administrator to determine which low-
level ODBC drivers are needed to talk to the data source (such as the interface to Oracle
or SQL Server). The loading of the ODBC drivers is transparent to the ODBC application
program. In a client/server environment, the ODBC API even handles many of the
network issues for the application programmer.

The advantages of this scheme are so numerous that you are probably thinking
there must be some catch. The only disadvantage of ODBC is that it isn’t as efficient as
talking directly to the native database interface. ODBC has had many detractors make
the charge that it is too slow. Microsoft has always claimed that the critical factor in
performance is the quality of the driver software that is used. In our humble opinion, this
is true. The availability of good ODBC drivers has improved a great deal recently. And

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 19

 SVIST SOFTWARE ENVIRONMENT
anyway, the criticism about performance is somewhat analogous to those who said that
compilers would never match the speed of pure assembly language. Maybe not, but the
compiler (or ODBC) gives you the opportunity to write cleaner programs, which means
you finish sooner. Meanwhile, computers get faster every year.
5.3 JDBC:
In an effort to set an independent database standard API for Java; Sun
Microsystems developed Java Database Connectivity, or JDBC. JDBC offers a generic
SQL database access mechanism that provides a consistent interface to a variety of
RDBMSs. This consistent interface is achieved through the use of “plug-in” database
connectivity modules, or drivers. If a database vendor wishes to have JDBC support, he
or she must provide the driver for each platform that the database and Java run on.
To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC.
As you discovered earlier in this chapter, ODBC has widespread support on a variety of
platforms. Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market
much faster than developing a completely new connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public
review that ended June 8, 1996. Because of user input, the final JDBC v1.0 specification
was released soon after.
The remainder of this section will cover enough information about JDBC for you to
know what it is about and how to use it effectively. This is by no means a complete
overview of JDBC. That would fill an entire book.
5.3.1 JDBC Goals:
Few software packages are designed without goals in mind. JDBC is one that,
because of its many goals, drove the development of the API. These goals, in
conjunction with early reviewer feedback, have finalized the JDBC class library into a
solid framework for building database applications in Java.
The goals that were set for JDBC are important. They will give you some insight
as to why certain classes and functionalities behave the way they do. The eight design
goals for JDBC are as follows:

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 20

 SVIST SOFTWARE ENVIRONMENT
1.SQL Level API
The designers felt that their main goal was to define a SQL interface for Java.
Although not the lowest database interface level possible, it is at a low enough level for
higher-level tools and APIs to be created. Conversely, it is at a high enough level for
application programmers to use it confidently. Attaining this goal allows for future tool
vendors to “generate” JDBC code and to hide many of JDBC’s complexities from the end
user.

1. SQL Conformance
SQL syntax varies as you move from database vendor to database vendor. In an effort
to support a wide variety of vendors, JDBC will allow any query statement to be passed
through it to the underlying database driver. This allows the connectivity module to
handle non-standard functionality in a manner that is suitable for its users.

2. JDBC must be implemental on top of common database interfaces

The JDBC SQL API must “sit” on top of other common SQL level APIs. This goal
allows JDBC to use existing ODBC level drivers by the use of a software interface. This
interface would translate JDBC calls to ODBC and vice versa.
3. Provide a Java interface that is consistent with the rest of the Java
system
Because of Java’s acceptance in the user community thus far, the designers feel that
they should not stray from the current design of the core Java system.

4. Keep it simple
This goal probably appears in all software design goal listings. JDBC is no exception.
Sun felt that the design of JDBC should be very simple, allowing for only one method of
completing a task per mechanism. Allowing duplicate functionality only serves to
confuse the users of the API.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 21

 SVIST SOFTWARE ENVIRONMENT
5. Use strong, static typing wherever possible
Strong typing allows for more error checking to be done at compile time;
also, less error appear at runtime.

6. Keep the common cases simple

Because more often than not, the usual SQL calls used by the programmer are simple
SELECT’s, INSERT’s, DELETE’s and UPDATE’s, these queries should be simple to
perform with JDBC. However, more complex SQL statements should also be possible.
Finally we decided to proceed the implementation using Java Networking.

And for dynamically updating the cache table we go for MS Access database.
Java ha two things: a programming language and a platform.

Java is a high-level programming language that is all of the following

Simple Architecture-neutral

Object-oriented Portable

Distributed High-performance

Interpreted multithreaded

Robust Dynamic

Secure

Java is also unusual in that each Java program is both compiled and interpreted.
With a compile you translate a Java program into an intermediate language called Java
byte codes the platform-independent code instruction is passed and run on the computer.
Compilation happens just once; interpretation occurs each time the program is executed.
The figure illustrates how this works

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 22

 SVIST SOFTWARE ENVIRONMENT

Java Program Interpreter

Compilers My Program

You can think of Java byte codes as the machine code instructions for the
Java Virtual Machine (Java VM). Every Java interpreter, whether it’s a Java development
tool or a Web browser that can run Java applets, is an implementation of the Java VM.
The Java VM can also be implemented in hardware.

Java byte codes help make “write once, run anywhere” possible. You can
compile your Java program into byte codes on my platform that has a Java compiler. The
byte codes can then be run any implementation of the Java VM. For example, the same
Java program can run Windows NT, Solaris, and Macintosh.

5.4 NETWORKING

TCP/IP stack
The TCP/IP stack is shorter than the OSI one:

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 23

 SVIST SOFTWARE ENVIRONMENT

TCP is a connection-oriented protocol; UDP (User Datagram Protocol) is a

connectionless protocol.

IP datagram’s

The IP layer provides a connectionless and unreliable delivery system. It considers

each datagram independently of the others. Any association between datagram must be
supplied by the higher layers. The IP layer supplies a checksum that includes its own
header. The header includes the source and destination addresses. The IP layer handles
routing through an Internet. It is also responsible for breaking up large datagram into
smaller ones for transmission and reassembling them at the other end.

UDP:

UDP is also connectionless and unreliable. What it adds to IP is a checksum for the
contents of the datagram and port numbers. These are used to give a client/server model
- see later.

TCP

TCP supplies logic to give a reliable connection-oriented protocol above IP. It

provides a virtual circuit that two processes can use to communicate.

Internet addresses

In order to use a service, you must be able to find it. The Internet uses an
address scheme for machines so that they can be located. The address is a 32 bit integer
which gives the IP address. This encodes a network ID and more addressing. The
network ID falls into various classes according to the size of the network address.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 24

 SVIST SOFTWARE ENVIRONMENT
Network address

Class A uses 8 bits for the network address with 24 bits left over for other
addressing. Class B uses 16 bit network addressing. Class C uses 24 bit network
addressing and class D uses all 32.

Subnet address

Internally, the UNIX network is divided into sub networks. Building 11 is currently
on one sub network and uses 10
10-bit
bit addressing, allowing 1024 different hosts.

Host address

8 bits are finally used for host addresses within our subnet. This places a limit of 256
machines that can be on the subnet.

Total address

The 32 bit address is usually written as 4 integers separated by dots.

Port addresses

A service exists on a host, and is identified by its port. This is a 16 bit number. To
send a message to a server, you send it to the port for that service of the host that it is
running on. This is not location transparency! Certain of these ports are "well known".

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 25

 SVIST SOFTWARE ENVIRONMENT
Sockets

A socket is a data structure maintained by the system to handle network

connections. A socket is created using the call socket. It returns an integer that is like a
file descriptor. In fact, under Windows, this handle can be used with Read File and
Write File functions.

#include <sys/types.h>

#include <sys/socket.h>

int socket(int family, int type, int protocol);

Here "family" will be AF_INET for IP communications, protocol will be

zero, and type will depend on whether TCP or UDP is used. Two processes wishing to
communicate over a network create a socket each. These are similar to two ends of a pipe
- but the actual pipe does not yet exist.

JFree Chart

JFreeChart is a free 100% Java chart library that makes it easy for developers to
display professional quality charts in their applications. JFreeChart's extensive feature set
includes:

A consistent and well-documented API, supporting a wide range of chart types;

A flexible design that is easy to extend, and targets both server-side and
client-side applications;

Support for many output types, including Swing components, image files
(including PNG and JPEG), and vector graphics file formats (including PDF, EPS and
SVG);

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 26

 SVIST SOFTWARE ENVIRONMENT
JFreeChart is "open source" or, more specifically, free software. It is distributed
under the terms of the GNU Lesser General Public Licence (LGPL), which permits use in
proprietary applications.

1. Map Visualizations
Charts showing values that relate to geographical areas. Some examples include:
(a) population density in each state of the United States, (b) income per capita for each
country in Europe, (c) life expectancy in each country of the world. The tasks in this
project include:

Sourcing freely redistributable vector outlines for the countries of the world,
states/provinces in particular countries (USA in particular, but also other areas);

Creating an appropriate dataset interface (plus default implementation), a

rendered, and integrating this with the existing XYPlot class in JFreeChart;

Testing, documenting, testing some more, documenting some more.

2. Time Series Chart Interactivity

Implement a new (to JFreeChart) feature for interactive time series charts --- to
display a separate control that shows a small version of ALL the time series data, with a
sliding "view" rectangle that allows you to select the subset of the time series data to
display in the main chart.

3. Dashboards
There is currently a lot of interest in dashboard displays. Create a flexible
dashboard mechanism that supports a subset of JFreeChart chart types (dials, pies,
thermometers, bars, and lines/time series) that can be delivered easily via both Java Web
Start and an applet.

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 27

 SVIST SOFTWARE ENVIRONMENT
4. Property Editor

The property editor mechanism in JFreeChart only handles a small subset of the
properties that can be set for charts. Extend (or reimplement) this mechanism to provide
greater end-user control over the appearance of the charts.

J2ME (Java 2 Micro edition):-

Sun Microsystems defines J2ME as "a highly optimized Java run-

time environment targeting a wide range of consumer products, including pagers, cellular
phones, screen-phones, digital set-top boxes and car navigation systems." Announced in
June 1999 at the JavaOne Developer Conference, J2ME brings the cross-platform
functionality of the Java language to smaller devices, allowing mobile wireless devices to
share applications. With J2ME, Sun has adapted the Java platform for consumer products
that incorporate or are based on small computing devices.

1. General J2ME architecture

J2ME uses configurations and profiles to customize the Java Runtime

Environment (JRE). As a complete JRE, J2ME is comprised of a configuration, which

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 28

 SVIST SOFTWARE ENVIRONMENT
determines the JVM used, and a profile, which defines the application by adding domain-
specific classes. The configuration defines the basic run-time environment as a set of core
classes and a specific JVM that run on specific types of devices. We'll discuss
configurations in detail in the The profile defines the application; specifically, it adds
domain-specific classes to the J2ME configuration to define certain uses for devices.
We'll cover profiles in depth in the The following graphic depicts the relationship
between the different virtual machines, configurations, and profiles. It also draws a
parallel with the J2SE API and its Java virtual machine. While the J2SE virtual machine
is generally referred to as a JVM, the J2ME virtual machines, KVM and CVM, are
subsets of JVM. Both KVM and CVM can be thought of as a kind of Java virtual
machine -- it's just that they are shrunken versions of the J2SE JVM and are specific to
J2ME.

2.Developing J2ME applications

Introduction In this section, we will go over some considerations you need to keep
in mind when developing applications for smaller devices. We'll take a look at the way
the compiler is invoked when using J2SE to compile J2ME applications. Finally, we'll
explore packaging and deployment and the role pre verification plays in this process.

3.Design considerations for small devices

Developing applications for small devices requires you to keep certain strategies
in mind during the design phase. It is best to strategically design an application for a
small device before you begin coding. Correcting the code because you failed to
consider all of the "gotchas" before developing the application can be a painful process.
Here are some design strategies to consider:

* Keep it simple. Remove unnecessary features, possibly making those features a

separate, secondary application.

* Smaller is better. This consideration should be a "no brainer" for all

developers. Smaller applications use less memory on the device and require shorter

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 29

 SVIST SOFTWARE ENVIRONMENT
installation times. Consider packaging your Java applications as compressed Java
Archive (jar) files.

* Minimize run-time memory use. To minimize the amount of memory used at run time,
use scalar types in place of object types. Also, do not depend on the garbage collector.
You should manage the memory efficiently yourself by setting object references to null
when you are finished with them. Another way to reduce run-time memory is to use lazy
instantiation, only allocating objects on an as-needed basis. Other ways of reducing
overall and peak memory use on small devices are to release resources quickly, reuse
objects, and avoid exceptions.

4.Configurations overview

The configuration defines the basic run-time environment as a set of core classes
and a specific JVM that run on specific types of devices. Currently, two configurations
exist for J2ME, though others may be defined in the future:

* Connected Limited Device Configuration (CLDC)

is used specifically with the KVM for 16-bit or 32-bit devices with
limited amounts of memory. This is the configuration (and the virtual
machine) used for developing small J2ME applications. Its size limitations
make CLDC more interesting and challenging (from a development point of
view) than CDC. CLDC is also the configuration that we will use for
developing our drawing tool application. An example of a small wireless
device running small applications is a Palm hand-held computer.

* Connected Device Configuration (CDC)

is used with the C virtual machine (CVM) and is used for 32-bit architectures
requiring more than 2 MB of memory. An example of such a device is a Net TV box.

5.J2ME profiles

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 30

 SVIST SOFTWARE ENVIRONMENT
What is a J2ME profile?

As we mentioned earlier in this tutorial, a profile defines the type of device

supported. The Mobile Information Device Profile (MIDP), for example, defines classes
for cellular phones. It adds domain-specific classes to the J2ME configuration to define
uses for similar devices. Two profiles have been defined for J2ME and are built upon
CLDC: KJava and MIDP. Both KJava and MIDP are associated with CLDC and smaller
devices. Profiles are built on top of configurations. Because profiles are specific to the
size of the device (amount of memory) on which an application runs, certain profiles are
associated with certain configurations.

A skeleton profile upon which you can create your own profile, the Foundation
Profile, is available for CDC.

Profile 1: KJava

KJava is Sun's proprietary profile and contains the KJava API. The KJava profile
is built on top of the CLDC configuration. The KJava virtual machine, KVM, accepts the
same byte codes and class file format as the classic J2SE virtual machine. KJava contains
a Sun-specific API that runs on the Palm OS. The KJava API has a great deal in common
with the J2SE Abstract Windowing Toolkit (AWT). However, because it is not a standard
J2ME package, its main package is com.sun.kjava. We'll learn more about the KJava API
later in this tutorial when we develop some sample applications.

Profile 2: MIDP

MIDP is geared toward mobile devices such as cellular phones and pagers. The
MIDP, like KJava, is built upon CLDC and provides a standard run-time environment
that allows new applications and services to be deployed dynamically on end user
devices. MIDP is a common, industry-standard profile for mobile devices that is not
dependent on a specific vendor. It is a complete and supported foundation for mobile
application

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 31

 SVIST SOFTWARE ENVIRONMENT
development. MIDP contains the following packages, the first three of which are core
CLDC packages, plus three MIDP-specific packages.

* java.lang

* java.io

* java.util

* javax.microedition.io

* javax.microedition.lcdui

* javax.microedition.midlet

* javax.microedition.rms

CODETECT FINANCIAL FRAUD DETECTION WITH ANAMOLY FEATURE DETECTION Page 32

SYSTEM DESIGN
 SVIST SYSTEM DESIGN

6. SYSTEM DESIGN

6.1 SYSTEM ARCHITECTURE:

Bank Admin
1. Register and Login(With Bank
Name)
Upload
2. View all users and authorize
3. View All Transport company
Transport Company users and authorize
4. Add bank with its details such as
bname, baddress,
Database
Register and blocation,bpin,bmailid,bcno,add
login the User building image
5. View Credit card request and
1.Register with Company name and Login
Process with Ac.No and
2.Add Transport Details(See below)
CRN,credit limit,Card cvv(4
3. View all Transport Details
digit) number,Cash Limit.
4.View all Booked Transport Details with total
6. View all transport booking fees
bill
details for each company based
5. Find financial fraud -- View all normal and
on cluster
Fraud users
7. View all transport booked details
6. View Type of Financial frauds(Give link for each company based on
below to show numbers of same frauds in chart ) cluster
8. View all type of Financial Fraud
based on cluster

Remote User

1. Register and Login, View your profile, Manage Bank Account

2. Request Credit card with * Details and view the same
3. View Card Transactions based on transport booked details
4. View your payments and transfer to your cc account (if user doesn’t have enough amount to
transfer then he is a fraud user or abnormal user)

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 33

 SVIST SYSTEM DESIGN

6.2 UML DIAGRAMS

UML stands for Unified Modeling Language. UML is a standardized general-

purpose modeling language in the field of object-oriented software engineering. The
standard is managed, and was created by, the Object Management Group.
The goal is for UML to become a common language for creating models
of object oriented computer software. In its current form UML is comprised of two major
components: a Meta-model and a notation. In the future, some form of method or process
may also be added to; or associated with, UML.The Unified Modeling Language is a
standard language for specifying, Visualization, Constructing and documenting the
artifacts of software system, as well as for business modeling and other non-software
systems.
The UML represents a collection of best engineering practices that have proven
successful in the modeling of large and complex systems.
The UML is a very important part of developing objects oriented software and
the software development process. The UML uses mostly graphical notations to express
the design of software projects.
GOALS:
The Primary goals in the design of the UML are as follows:
1. Provide users a ready-to-use, expressive visual modeling Language so that
they can develop and exchange meaningful models.
2. Provide extendibility and specialization mechanisms to extend the core
concepts.
3. Be independent of particular programming languages and development
process.
4. Provide a formal basis for understanding the modeling language.
5. Encourage the growth of OO tools market.
6. Support higher level development concepts such as collaborations,
frameworks, patterns and components.
7. Integrate best practices.
CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 34
 SVIST SYSTEM DESIGN

6.2.1USE CASE DIAGRAM:

A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases. The
main purpose of a use case diagram is to show what system functions are performed for
which actor. Roles of the actors in the system can be depicted.
USECASE DIAGRAM:

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 35

 SVIST SYSTEM DESIGN

USECASE DIAGRAM
Add bank details

View Credit card

Manage Bank
Account

View Card
Transactions based on
User transport booked

Request Credit
card Details

Transport Company
View all transport
booking fees details

Add Transport
View all transport booked Details
details and View all type of
Financial Frauds
View all Transport Details
and View all Booked
Transport Details with
total bill

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 36

 SVIST SYSTEM DESIGN

6.2.2 CLASS DIAGRAM:

In software engineering, a class diagram in the Unified Modeling Language

(UML) is a type of static structure diagram that describes the structure of a system by
showing the system's classes, their attributes, operations (or methods), and the
relationships among the classes. It explains which class contains information.

CLASS DIAGRAM:

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 37

 SVIST SYSTEM DESIGN

Register with Company name

Register and Login(With Bank Name),View and Login, Add Transport
all users and authorize, View All Transport
Details, View all Transport
company users and authorize, Add bank
Details, and View all Booked
details ,View Credit card request and
Process ,View all transport booking fees
Transport Details with total bill,
details ,View all transport booked details Find financial fraud -- View all
,View all type of Financial Frauds ,View all normal and Fraud users
users with Financial Fraud
Users. ,View Type of Financial frauds
bname,baddress,blocation,bpin,bm
bname,baddress,blocation,bpin,bmailid,bc ailid,bcno,add building image,
no,add building image, Transporter name, Transporter name, desc, address,
desks, address, cno, email id, location, cno, email id, location, add image,
add image, from and to place, price from and to place, price

End User
Register and Login, View your profile,
Manage Bank Account, ,Request Credit Register, Reset
card Details ,View Card Transactions
Methods based on transport booked details, View Name, Password, DOB,
your payments and transfer to your cc
Gender, Address, City,
account ,View all transport company,
View all Booked transport. Country, Email, Mobile, Pin
code
Members
bname,baddress,blocation,bpin,bmailid,b
cno,add building image, Transporter
name, desc, address, cno, email id,
E-Commerce Website
location, add image, from and to place,
price.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 38

 SVIST SYSTEM DESIGN

6.2.3 SEQUENCE DIAGRAM:

A sequence diagram in Unified Modeling Language (UML) is a kind of

interaction diagram that shows how processes operate with one another and in what
order. It is a construct of a Message Sequence Chart. Sequence diagrams are sometimes
called event diagrams, event scenarios, and timing diagrams.

SEQUENCE DIAGRAM:

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 39

 SVIST SYSTEM DESIGN

System User Transport Company

Register and Login

Register and Login(With Bank Name)

View their own details

View all users and authorize

Manage Bank Account

View All Transport company

users and authorize Request Credit card Details

View your payments and transfer

sfer to your cc account

Add bank details

View Credit card request and Process

View all transport booking View Card Transactions based on transport booked details
fees details

View all transport booked details Add Transport Details

View all type of Financial Frauds

View all Transport Details

Details, View all Booked Transport Details with total
bill

Find financial
ial fraud -- View all normal and Fraud users, View Type of Financial
frauds

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 40

 SVIST SYSTEM DESIGN

6.2.4 DEPLOYMENT:

Component diagrams are used to describe the components and deployment

diagrams shows how they are deployed in hardware. UML is mainly designed to
focus on the software artifacts of a system. However, these two diagrams are
special diagrams used to focus on software and hardware components.

DEPLOYMENT DAIGRAM:

SERVER

Users ADMIN.

SVM.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 41

 SVIST SYSTEM DESIGN

6.3 DATA FLOW DIAGRAM:

1. The DFD is also called as bubble chart. It is a simple graphical formalism

that can be used to represent a system in terms of input data to the system,
various processing carried out on this data, and the output data is generated
by this system.
2. The data flow diagram (DFD) is one of the most important modeling tools.
It is used to model the system components. These components are the
system process, the data used by the process, an external entity that
interacts with the system and the information flows in the system.
3. DFD shows how the information moves through the system and how it is
modified by a series of transformations. It is a graphical technique that
depicts information flow and the transformations that are applied as data
moves from input to output.
4. DFD is also known as bubble chart. A DFD may be used to represent a
system at any level of abstraction. DFD may be partitioned into levels that
represent increasing information flow and functional detail.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 42

 SVIST SYSTEM DESIGN

DFD-DIAGRAM:

Add bank
Bank Admin details, Register
and Login
System

View all transport

Request company,View all
Booked transport
Response

Register
,View all users and
with the
authorize,View All
Transport company system
users and
authorize,View Credit
card request and
End User
View their
Own
Register with Company Details
name and Login ,Add
Manage Bank Transport Details ,View
Account, Request all Transport
Credit card Details, Details,View all Booked
View Card Transport Details with
Transactions based on
transport booked

Transport Company

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 43

 SVIST SYSTEM DESIGN

FLOW CHART1: USER

Start

User Register

Yes No
Login

Manage Bank Account Username &

Password Wrong

Request Credit card

Log Out
View Card Transactions based on
transport booked details

View your payments and

transfer to your cc account

View all transport

company,View all
Booked transport

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 44

 SVIST SYSTEM DESIGN

FLOW CHART 2: BANK ADMIN

Start

Admin Login

Yes No
Login

View all users and Username &

authorize No Password Wrong
Yes

View All Transport

company users and
authorize
Log Out

Add bank details

View Credit card request and

Process

View all transport booking fees details ,

View all users with Financial Fraud

View all transport booked

details, View all type of
Financial Frauds

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 45

 SVIST SYSTEM DESIGN

CHART 3: TRANSPORT COMPANY

Start

Login

Yes No
Login

Add Transport Details Username &

No
Password Wrong
Request
Yes

View all Transport

Details

Log Out
Response
View all Booked Transport
Details with total bill

Find financial fraud

View Type of Financial frauds

-- View all normal and

Fraud users

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 46

SAMPLE CODE
 SVIST SAMPLE CODE

7. SAMPLE CODE
HOME PAGE
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="keywords" content="" />
<meta name="description" content="" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Home Page</title>
<link href="style.css" rel="stylesheet" type="text/css" media="screen" />
<style type="text/css">
<!--
.style1 {
font-size: 18px;
color: #FF0000;
font-weight: bold;
}
.style2 {color: #0000FF}
-->
</style>
</head>
<body>
<div id="wrapper">
<div id="menu">
<ul>
<li class="current_page_item"><span><a
href="index.html">Home</a></span></li>
<li><a href="AdminLogin.jsp">Bank Admin</a></li>
<li><a href="CompanyLogin.jsp">Transport Company</a></li>
<li><a href="UserLogin.jsp">User</a></li>
<li><a href="#"></a></li>
<li><a href="#"></a></li>
</ul>
</div>
<!-- end #menu -->
<div id="header">

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 47

 SVIST SAMPLE CODE

<div id="logo">
<h1 style="color: RED"><a href="#" class="style1">CODETECT:FINANCIAL FRAUD
DETECTION WITH ANOMALY FEATURE DETECTION</a></h1>
</div>
<div id="search">
<form method="get" action="">
<fieldset>
<input type="text" name="s" id="search-text" size="15"
value="enter keywords here..." />
<input type="submit" id="search-submit" value="GO"
/>
</fieldset>
</form>
</div>
</div>
<div id="splash">&nbsp;</div>
<!-- end #header -->
<div id="page">
<div id="page-bgtop">
<div id="page-bgbtm">
<div id="content">
<div class="post">
<h2 class="title"><a
href="#">CoDetect:Financial Fraud Detection With Anomaly Feature Detection</a></h2>
<div class="entry">
<p class="style2">Financial fraud, such
as money laundering, is known to be a serious process of crime that makes illegitimately
obtained funds go to terrorism or other criminal activity. This kind of illegal activities
involve complex networks of trade and nancial transactions, which makes it difcult to
detect the fraud entities and discover the features of fraud. Fortunately,
trading/transaction network and features of entities in the network can be constructed
from the complex networks of the trade and nancial transactions. The trading/transaction
network reveals the interaction between entities, and thus anomaly detection on trading
networks can reveal the entities involved in the fraud activity; while features of entities
are the description of entities, and anomaly detection on features can reect details of the
fraud activities. Thus, network and features provide complementary information for fraud
detection, which has potential to improve fraud detection performance. However, the
majority of existing methods focus on networks or features information separately, which
does not utilize both information. In this paper, we propose a novel fraud detection
framework, CoDetect, which can leverage both network information and feature
CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 48
 SVIST SAMPLE CODE

information for nancial fraud detection. In addition, the CoDetect can simultaneously
detecting nancial fraud activities and the feature patterns associated with the fraud
activities. Extensive experiments on both synthetic data and real-world data demonstrate
the efciency and the effectiveness of the proposed framework in combating nancial fraud,
especially fo <br />
money laundering.</p>
</div>
</div>
<div style="clear: both;">&nbsp;</div>
</div>
<!-- end #content -->
<div id="sidebar">
<ul><li><h2>Menu</h2>
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="AdminLogin.jsp">Bank Admin</a></li>
<li><a href="CompanyLogin.jsp">Transport Company</a></li>
<li><a href="UserLogin.jsp">User</a></li>
</ul>
</li>
<li>
<h2>Concepts</h2>
<ul>
<li><a href="#">Anomaly feature detection, </a></li>
<li><a href="#">CoDetect, </a></li>
<li><a href="#">Financial fraud.</a><a
href="#"></a></li>
</ul> </li> <li>
<h2>&nbsp;</h2>
</li> </ul>
</div>
<!-- end #sidebar -->
<div style="clear: both;">&nbsp;</div>
</div></div></div>
<!-- end #page -->
</div>
</body>
</html>

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 49

 SVIST SAMPLE CODE

ADMIN PROFILE
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<%@ include file="connect.jsp" %>
<%@ page import="org.bouncycastle.util.encoders.Base64"%>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="keywords" content="" />
<meta name="description" content="" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Admin's Profile</title>
<link href="style.css" rel="stylesheet" type="text/css" media="screen" />
<style type="text/css">
<!--
.style1 {
font-size: 18px;
color: #FF0000;
font-weight: bold;
}
.style3 {color: #333333}
.style4 {color: #660000}
.style7 {color:#CC0066}
-->
</style>
</head>
<body>
<div id="wrapper">
<div id="menu">
<ul>
<li class="current_page_item"><span><a
href="index.html">Home</a></span></li>
<li><a href="AdminLogin.jsp">Bank Admin</a></li>
<li><a href="CompanyLogin.jsp">Transport Company</a></li>
<li><a href="UserLogin.jsp">User</a></li>
<li><a href="#"></a></li>
<li><a href="#"></a></li>
</ul>
</div>
<!-- end #menu -->

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 50

 SVIST SAMPLE CODE

<div id="header">
<div id="logo">
<h1><a href="#" class="style1">CoDetect: Financial Fraud Detection
With Anomaly Feature Detection</a></h1>
</div>
<div id="search">
<form method="get" action="">
<fieldset>
<input type="text" name="s" id="search-text" size="15"
value="enter keywords here..." />
<input type="submit" id="search-submit" value="GO"
/>
</fieldset>
</form>
</div>
</div>
<div id="splash">&nbsp;</div>
<!-- end #header -->
<div id="page">
<div id="page-bgtop">
<div id="page-bgbtm">
<div id="content">
<div class="post">
<h2 class="title"><a href="#">Bank Admin
<span class="style7"><%=(String)application.getAttribute("adname")%></span>'s
Profile..</a></h2>
<div class="entry">
<p>&nbsp;</p>
<table width="519" border="1.5" align="center" cellpadding="0" cellspacing="0" >

<%

String name=(String )application.getAttribute("adname");

String bank=(String )application.getAttribute("adbank");
String s1,s2,s3,s4,s5,s6;
int i=0;
try
{
String query="select * from bankadmin where username='"+name+"' and
bank='"+bank+"'";
CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 51
 SVIST SAMPLE CODE

Statement
st=connection.createStatement();
ResultSet rs=st.executeQuery(query);
if ( rs.next() )
{
i=rs.getInt(1);
s1=rs.getString(2);
s2=rs.getString(5);
s3=rs.getString(6);
s4=rs.getString(7);
s5=rs.getString(8);
s6=rs.getString(10);

%>
<tr>
<td width="226" rowspan="6" ><div class="style7 style26" style="margin:10px 13px
10px 13px;" ><strong><a class="#" id="img1" href="#" >
<input name="image" type="image"
src="user_Pic.jsp?picture=<%="bankadmin"%>&id=<%=i%>" style="width:200px; height:200px;"
/>
</a></strong></div></td>
</tr>
<tr>
<td valign="middle" height="60" style="color: #2c83b0;"><div align="left" class="style4"
style="margin-left:20px;"><strong>Bank Name </strong></div></td>
<td valign="middle" height="60" style="color:#000000;"><div align="left" class="style42
style41 style10" style="margin-left:20px;">
<%out.println(s1);%>
</div></td>
</tr>
<tr>
<td width="122" valign="middle" height="60" style="color: #2c83b0;"><div align="left"
class="style4" style="margin-left:20px;"><strong>E-Mail</strong></div></td>
<td width="163" valign="middle" height="60" style="color:#006666"><div align="left"
class="style42 style41 style10" style="margin-left:20px;">
<%out.println(s2);%>
</div></td>
</tr>
<tr>
CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 52
 SVIST SAMPLE CODE

<td width="122" valign="middle" height="60" style="color: #2c83b0;"><div align="left"

class="style4" style="margin-left:20px;"><strong>Mobile</strong></div></td>
<td width="163" valign="middle" height="60" style="color:#000000;"><div align="left"
class="style42 style41 style10" style="margin-left:20px;">
<%out.println(s3);%>
</div></td>
</tr>
<tr>
<td width="122" align="left" valign="middle" height="60" style="color: #2c83b0;"><div
align="left" class="style4" style="margin-left:20px;"><strong>Address</strong></div></td>
<td width="163" align="left" valign="middle" height="60" style="color:#000000;"><div
align="left" class="style42 style41 style10" style="margin-left:20px;">
<%out.println(s4);%>
</div></td>
</tr>
<tr>
<td width="122" align="left" valign="middle" height="60" style="color: #2c83b0;"><div
align="left" class="style4" style="margin-left:20px;"><strong>Date of Birth</strong></div></td>
<td width="163" align="left" valign="middle" height="60" style="color:#000000;"><div
align="left" class="style42 style41 style10" style="margin-left:20px;">
<%out.println(s5);%>
</div></td>
</tr>

<% }
connection.close();
}
catch(Exception e)
{
out.println(e.getMessage());
}
%>
</table>
<p align="right">&nbsp;</p>
<p align="left"><a href="AdminMain.jsp" class="style11">Back</a></p>

</div>
</div>
<div class="post"></div>
<div style="clear: both;">&nbsp;</div>
CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 53
 SVIST SAMPLE CODE

</div>
<!-- end #content -->
<div id="sidebar">
<ul><li><h2>Menu</h2>
<ul>
<li><a href="AdminMain.jsp">Home</a></li>

<li><a href="AdminLogin.jsp">Logout </a></li>

</ul></li ><li>
<h2>&nbsp;</h2>
</li> </ul> </div>
<!-- end #sidebar -->
<div style="clear: both;">&nbsp;</div>
</div></div></div>
<!-- end #page -->
</div>
<div align=center>This template downloaded form <a href='http://all-free-download.com/free-
website-templates/'>free website templates</a>
</div>
</body>
</html>

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 54

SYSTEM TESTING
 SVIST SYSTEM TESTING

8. SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to
check the functionality of components, sub assemblies, assemblies and/or a finished
product It is the process of exercising software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in
an unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.

8.1 TYPES OF TESTING:

8.1.1 Unit testing
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid outputs. All
decision branches and internal code flow should be validated. It is the testing of
individual software units of the application .it is done after the completion of an
individual unit before integration. This is a structural testing, that relies on knowledge of
its construction and is invasive. Unit tests perform basic tests at component level and test
a specific business process, application, and/or system configuration. Unit tests ensure
that each unique path of a business process performs accurately to the documented
specifications and contains clearly defined inputs and expected results.

8.1.2 Integration testing

Integration tests are designed to test integrated software components to determine
if they actually run as one program. Testing is event driven and is more concerned with
the basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically
aimed at exposing the problems that arise from the combination of components.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 55

 SVIST SYSTEM TESTING

8.1.3 Functional test

Functional tests provide systematic demonstrations that functions tested are
available as specified by the business and technical requirements, system documentation,
and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be

exercised.

Systems/Procedures : interfacing systems or procedures must be

invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes must
be considered for testing. Before functional testing is complete, additional tests are
identified and the effective value of current tests is determined.

System Test
System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test. System
testing is based on process descriptions and flows, emphasizing pre-driven process links
and integration points.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 56

 SVIST SYSTEM TESTING

White Box Testing

White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at least its
purpose. It is purpose. It is used to test areas that cannot be reached from a black box
level.

Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as most other
kinds of tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle, although it is not uncommon for coding and unit testing
to be conducted as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in
detail.

Test objectives

 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.
Features to be tested

 Verify that the entries are of the correct format

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 57

 SVIST SYSTEM TESTING

 No duplicate entries should be allowed

 All links should take the user to the correct page.

Integration Testing

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by
interface defects. The task of the integration test is to check that components or software
applications, e.g. components in a software system or – one step up – software
applications at the company level – interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires

significant participation by the end user. It also ensures that the system meets the
functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 58

OUTPUT SCREENS
 SVIST OUTPUT SCREENS

9. OUTPUT SCREENS

1. HOME PAGE

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 59

 SVIST OUTPUT SCREENS

2. ADMIN LOGIN

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 60

 SVIST OUTPUT SCREENS

3. ADMIN PROFILE

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 61

 SVIST OUTPUT SCREENS

4. USER LOGIN

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 62

 SVIST OUTPUT SCREENS

5. USER PROFILE

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 63

 SVIST OUTPUT SCREENS

6. TRANSPORT COMPANY LOGIN

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 64

 SVIST OUTPUT SCREENS

7. TRANSPORT COMPANY PROFILE

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 65

\

CONCLUSION
 SVIST CONCLUSION

10. CONCLUSION

We propose a new framework, CoDetect, which can perform fraud detection on graph-
based similarity matrix and feature matrix simultaneously. It introduces a new way to
reveal the nature of financial activities from fraud patterns to suspicious property.
Furthermore, the framework provides a more interpretable way to identify the fraud on
sparse matrix. Experimental results on synthetic and real world data sets show that the
proposed framework (CoDetect) can effectively detect the fraud patterns as well as
suspicious features. With this co detection framework, executives in financial supervision
cannot only detect the fraud patterns but also trace the original of fraud with suspicious
feature.
Financial activities are involving with time. We can represent these activities into
similarity tensor and feature tensor. So we would like to study how to integrate tensor
into codetect framework for fraud detection.

CODETECT FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 66

BIBLIOGRAPHY
 SVIST BIBLIOGRAPHY

11. BIBLIOGRAPHY

[1] C. Sullivan and E. Smith. ``Trade-Based Money Laundering: Risks and

Regulatory Responses,'' Social Sci. Electron. Publishing, 2012, p. 6.
[2] United Press International. (May 2009). Trade-Based Money Laundering
Flourishing.[Online].Available:http://www.upi.com/TopNews/2009/05/11/T
rade-based-money-laundering-_ourishing/UPI-17331242061466
[3] L. Akoglu, M. McGlohon, and C. Faloutsos, ``OddBall: Spotting
anomaliesin weighted graphs,'' in Proc. Pacic-Asia Conf. Knowl. Discovery
Data Mining, 2010, pp. 410_421.
[4] V. Chandola, A. Banerjee, and V. Kumar, ``Anomaly detection: A
survey,''ACMComput. Surv., vol. 41, no. 3, 2009, Art. no. 15.
[5] W. Eberle and L. Holder, ``Mining for structural anomalies in graph-
baseddata,'' in Proc. DMin, 2007, pp. 376_389.
[6] C. C. Noble and D. J. Cook, ``Graph-based anomaly detection,'' in
Proc.9th ACM SIGKDD Int. Conf. Knowl. Discovery Data Mining,
2003,pp. 631_636.
[7] H. Tong and C.-Y. Lin, ``Non-negative residual matrix factorization
withapplication to graph anomaly detection,'' in Proc. SIAM Int. Conf.
DataMining, 2011, pp. 1_11.
[8] S.Wang, J. Tang, and H. Liu, ``Embedded unsupervised feature
selection,''in Proc. 29th AAAI Conf. Artif. Intell., 2015, pp. 470_476.
[9] Z. Lin, M. Chen, and Y. Ma. (2010). ``The Augmented lagrange
multipliermethod for exact recovery of corrupted low-rank matrices.''
[Online].Available: https://arxiv.org/abs/1009.5055.

FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 67

 SVIST BIBLIOGRAPHY

[10] J. Sun, H. Qu, D. Chakrabarti, and C. Faloutsos,

``Neighborhoodformationand anomaly detection in bipartite graphs,'' in
Proc. 15th IEEE Int. Conf.Data Mining, Nov. 2005, p. 8.
[11] A. Patcha and J.-M. Park, ``An overview of anomaly detection
techniques:Existing solutions and latest technological trends,'' Comput.
Netw., vol. 51,no. 12, pp. 3448_3470, Aug. 2007.
[12] W. Li, V. Mahadevan, and N. Vasconcelos, ``Anomaly detection
andlocalization in crowded scenes,'' IEEE Trans. Pattern Anal. Mach.
Intell.,vol. 36, no. 1, p. 18_32, Jan. 2014.
[13] K. Henderson et al., ``It's who you know: Graph mining using
recursivestructural features,'' in Proc. 17th ACM SIGKDD Int. Conf. Knowl.
Discovery Data Mining, 2011, pp. 663_671.
[14] F. Keller, E. Müller, and K. Bohm, ``HiCS: High contrast subspaces
fordensity-based outlier ranking,'' in Proc. ICDE, Apr. 2012, pp. 1037_1048.
[15] D. Koutra, E. Papalexakis, and C. Faloutsos, ``Tensorsplat: Spotting
latentanomalies in time,'' in Proc. PCI, Oct. 2012, pp. 144_149.
[16] J. H. M. Janssens, I. Flesch, and E. O. Postma, ``Outlier detection
withone-class classi_ers from ML and KDD,'' in Proc. ICMLA, Dec.
2009,pp. 147_153.
[17] N. A. Heard, D. J. Weston, K. Platanioti, and D. J. Hand,
``Bayesiananomaly detection methods for social networks,'' Ann. Appl.
Statist., vol. 4,no. 2, pp. 645_662, 2010.
[18] J. Tang and H. Liu ``CoSelect: Feature selection with instance selection
forsocial media data,'' in Proc. SIAM Int. Conf. Data Mining, 2013, pp. 1_9.

FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 68

 SVIST BIBLIOGRAPHY

[19] Z. He, X. Xu, and S. Deng, ``Discovering cluster-based local

outliers,''PatternRecognit. Lett., vol. 24, nos. 9_10, pp. 1641_1650, 2003.
[20] M. Gupta, J. Gao, C. C. Aggarwal, and J. Han, Outlier Detection for
Tempo-ral Data (Synthesis Lectures on Data Mining and Knowledge
Discovery).San Rafael, CA, USA: Morgan & Claypool, 2014.
[21] J. Tang, Y. Chang, and H. Liu ``Mining social media with social
theories:A survey,'' ACM SIGKDD Explorations Newslett., vol. 15, no.
2,pp. 20_29, 2013.
[22] I. S. Dhillon, S. Mallela, and D. S. Modha, ``Information-theoretic
coclustering,''in Proc. 9th ACM SIGKDD Int. Conf. Knowl. Discovery
DataMining, 2003, pp. 89_98.

FINANCIAL FRAUD DETECTION WITH ANOMALY FEATURE DETECTION Page 69