CONTENTS

LIST OF FIGURES

LISTOF TABLES

LIST OF ABBREVIATION

ABSTRACT

CHAPTER-1- INTRODUCTION

1.1 BackGround…………………………………………………………1
1.2 Problem Statement………………………………………………….1
1.3 Purpose Of This Document…………………………………………1
1.4 Scope Of The Development Project………………………………..2
1.5 Existing System……………………………………………………...2
1.6 Proposed System…………………………………………………….3

CHAPTER-2- OVERVIEW AND PLANNING

2.1 Proposed System Overview………………………………………….4
2.2 Challenges…………………………………………………………….4
2.3 Assumptions…………………………………………………………..4
2.4 Architecture Specifications…………………………………………..5
2.5 Hardware Requirements……………………………………………..5
2.6 Software Requirements………………………………………………5
2.7 Software Specification………………………………………………..6
2.7.1 Front End Used………………………………………………...6
2.7.2 Features Of Microsoft Visual Studio DOT Net………………6
 2.7.3 Features Of DOT Net…………………………………………..7
2.7.4 The DOT Net Framework……………………………………..7
2.7.5 Managed Code……………………………………………….…8
2.7.6 Managed Data………………………………………………..…8
2.7.7 Common Type System…………………………………………8
2.7.8 Common Language Specification………………………...…..9
2.7.9 The Class Library…………………………………………......9
2.7.10 Languages Supported By DOT Net……………………...…9
2.7.11 DOT Net Advantages…………………...………………......10
2.7.12 DOT Net Disadvantages…………………………………....11
2.7.13 Back End Used…………………………..………………….11
2.7.14 Features Of SQL Server 2005…………..………………….11
2.7.15 SQL Server………………………………..………………...11
2.8 Features Of SQL Procedures………………………………………13
2.9 Work Breakdown Structure…………………….…………………14

CHAPTER-3- LITERATURE SURVEY AND REVIEW

3.1 Literature Survey…………………………………………….…….15
3.2 Literature Summary………………………………………….……17

CHAPTER-4- SYSTEM DESIGN

4.1 High-Level Design……………………………………………..…..18
4.1.1 Data Flow Diagram…………………………………….....18
4.2 Low- Level Design………………………………………………....22
4.2.1 UML Diagrams…………………………………………...22
 4.2.2 Class Diagram……………………………………….….....22
4.2.3 Use Case Diagram………………………………………...23
4.2.4 Sequence Diagram………………………………...………24
4.2.5 Activity Diagram……………………………………….....25
4.2.6 State Chart Diagram……………………………………...26
4.2.7 Entity Relationship Diagram……………….………..…..27
4.3 Codes And Standards……………………………………………. 28
4.4 Constrains And Tradeoffs………………………………………..29

4.5 Test Case Generation……………………………………………..29

4.5.1 Testing……………………………………………………29
4.5.2 Functional Testing…………………………………….…30
4.5.3 System Testing…………………………………………..30
4.5.4 White Box Testing…………………………………..…...31
4.5.5 Black Box Testing………………………………….…....31
4.5.6 Acceptance Testing……………………………………...31
4.5.7 Unit Testing……………………………………………..31
4.5.8 Test Strategy And Approach…………………….….….32
4.5.9 Test Objectives………………………………….……….32
4.5.10 Integration Testing……………………………….…….32
4.5.11 Test Result……………………………………………...33

CHAPTER-5- SYSTEM IMPLEMENTATION

5.1 Source Code………………………………………………………35
CHAPTER-6- RESULTS AND DISCUSSION
6.1 Output/Results…………………………………………………...46
6.1.1 Customer Sign In……………………………….……..46
6.1.2 Brand List……………………………………….……..46
6.1.3 Add To Card…………………………………….…….47
6.1.4 Card List………………………………………………47
6.1.5 Payment Option…………………………………….…48
6.1.6 Offline Payment Details………………………………48
6.1.7 Admin Process……………………………..………….49
6.1.8 Add New Category……………………………………49
6.1.9 Category List………………………………………….50
6.1.10 Add New Brand………………………………….…..50
6.1.11 Product List………………………………………….51

CHAPTER-7- CONCLUSION AND FUTURE WORK

7.1 Conclusion……………………………………………………...52
7.2 Future Work……………………………………………………53

CHAPTER-8- REFERENCES
8.1 References………………………………………………………54
 LIST OF FIGURES

S.NO FIG.NO TITLE PAGE.NO

1. 2.1 System Architecture 5

2. 2.2 Work Breakdown 14

3. 4.1 Admin Data Flow Diagram 19

4. 4.2 Seller Data Flow Diagram 20

5. 4.3 User Data Flow Diagram 21

6. 4.4 Class Diagram 23

7. 4.5 Use Case Diagram 24

8. 4.6 Sequence Diagram 25

9. 4.7 Activity Diagram 26

10. 4.8 State Chart Diagram 27

11. 4.9 ER Diagram 28

 LIST OF TABLES

S.NO TITLE PAGE.NO

1. Literature Survey 15

2. Unit & Integration Testing 33

 LIST OF ABBREVATION

ACRONYM EXPANSION

SVM Support Vector Machine

API Application Programming Interface

BART Bayesian Additive Regression Trees

FAQ Frequently Asked Questions

GUIs Graphical User Interfaces

PAN Permanent Account Number

SSVS Stochastic Search Variable Selection

E-COMMERCE SHOPPING CART
FOR B2B IMPLEMENTATION
ABSTARCT
ABSTARCT

We consider the problem of building online machine-learned models for detecting auction
frauds in e-commence web sites. Since the emergence of the World Wide Web, online shopping
and online auction have gained more and more popularity. While people are enjoying the benefits
from online trading, criminals are also taking advantages to conduct fraudulent activities against
honest parties to obtain illegal profit. Hence proactive fraud-detection moderation systems are
commonly applied in practice to detect and prevent such illegal and fraud activities. Machine-
learned models, especially those that are learned online, are able to catch frauds more efficiently
and quickly than human-tuned rule-based systems. In this paper, we propose an online probit
model framework which takes online feature selection, coefficient bounds from human knowledge
and multiple instances learning into account simultaneously. By empirical experiments on a real-
world online auction fraud detection data we show that this model can potentially detect more
frauds and significantly reduce customer complaints compared to several baseline models and the
human-tuned rule-based system.
 CHAPTER 1
INTRODUCTION

1.1 BACKGROUND

The continuous growth in the size and use of the World Wide Web imposes new methods
of design and development of online information services. Most Web structures are becoming
complicated and users often miss the goal of their inquiry, or receive ambiguous results when they
try to navigate through them which lead a user to untrusted websites, products and links. On the
other hand, the E-business sector is rapidly evolving and the needs for web market places that
anticipate the needs of the customers and the trust towards a product are equally more evident than
ever. While people are enjoying the benefits from online trading, criminals are also taking
advantages to conduct fraudulent activities against honest parties to obtain illegal profits.
Therefore the requirement for predicting user needs and trust providence towards a product in
order to improve the usability and user retention of a website can be addressed by personalizing
and using a fraud product detection system.

The application for storage of data has been planned to use the SQL and all the user
interfaces has been designed using the ASP.NET Technologies. The application takes care of
different modules and their associated functionalities as per the applicable strategies.

1.2 PROBLEM STATEMENT

The traditional online shopping business model allows seller to sell a product or service at
a preset price, where buyers can choose to purchase if they find it to be a good deal. Online auction
however is a different business model by which items are sold through price bidding. There is
often a starting price and expiration time specified by the sellers. Once the auction starts, potential
buyers bid against each others, and the winner gets with their highest winning bid.

1.3 PURPOSE OF THIS DOCUMENT

• Improves Customer Seller relationship in our application, more productive and engaging.
• Valuable to you and your organization, because it drives desired business results such as
increasing visitor response or promoting customer retention.

1
 • Most importantly, keep the process simple. Stay focused on the business goals, tackle
manageable projects, measure the success or failure of your changes, and learn from your
mistakes.
• Improves the productivity by simplifying access to information
• More likely to increase sales of trusty companies

1.4 SCOPE OF THE DEVELOPMENT PROJECT

This Project investigates the entry criteria for providing a new auction service through
the real options approach, where the entry criteria is established by using an Online auctioning
system designed for the use of normal users (individuals), Industrialists, Entrepreneurs,
Organizations and Academicians under transaction rate uncertainty.
• Customer must have a unique and authorized User Id and password to login to the system
• If a wrong password is given more than three times in continuous, that account will be
locked and the customer will not be able to use it. When an invalid password is entered a
warning is given to the user that his account is going to get locked.
• After the valid user logs in his details like PAN card number, license number etc. are
verified.
• FAQ test is also provided for end users benefit.
• For safe bidding user is required to pay initial amount for confirmation.

1.5 EXISTING SYSTEM

The traditional online shopping business model allows sellers to sell a product or
service at a preset price, where buyers can choose to purchase if they find it to be a good deal.
Online auction however is a different business model by which items are sold through price
bidding. There is often a starting price and expiration time specified by the sellers. Once the
auction starts, potential buyers bid against each other, and the winner gets the item with their
highest winning bid.

2
1.6 PROPOSED SYSTEM

We propose an online profit model framework which takes online feature selection, coefficient
bounds from human knowledge and multiple instances learning into account simultaneously. By
empirical experiments on a real-world online auction fraud detection data we show that this model
can potentially detect more frauds and significantly reduce customer complaints compared to
several baseline models and the human-tuned rule-based system. Human experts with years of
experience created many rules to detect whether a user is fraud or not. If the fraud score is above
a certain threshold, the case will enter a queue for further investigation by human experts. Once it
is reviewed, the final result will be label as Boolean, i.e, fraud or clean. Cases with higher scores
have higher priorities in the queue to be reviewed. The cases whose frauds Score are below the
threshold are determined as clean by the system without any human judgment.

3
 CHAPTER 2
OVERVIEW AND PLANNING

2.1 PROPOSED SYSTEM OVERVIEW

We propose an online probit model framework which takes online feature selection,
coefficient bounds from human knowledge and multiple instances learning into account
simultaneously. By empirical experiments on a real-world online auction fraud detection data we
show that this model can potentially detect more frauds and significantly reduce customer
complaints compared to several baseline models and the human-tuned rule-based system. Human
experts with years of experience created many rules to detect whether a user is fraud or not. If the
fraud score is above a certain threshold, the case will enter a queue for further investigation by
human experts. Once it is reviewed, the final result will be labelled as Boolean, i.e. fraud or clean.
Cases with higher scores have higher priorities in the queue to be reviewed. The cases whose
frauds Score are below the threshold are determined as clean by the system without any human
judgment.

2.2 CHALLENGES
Fraud product detection allows a user or a customer to know about the product
trustworthiness through the other user’s feedback for that product. Fraud detection and web
personalization are the key technologies needed in various e-business applications to,

• Manage customer organization relationships

• Promote products
• Manage Web site content
• Provide knowledge to the user about the product.

2.3 ASSUMPTIONS
Product it was once acceptable for companies to sell their products to very defined and
localized markets within certain logical timeframes, the advent of online shopping has completely
redefined the way companies now market themselves in order to establish a market presence.
However, the introduction of this dynamic medium of conducting business has brought with it its

4
own complex set of problems. Fraud product detection allows a user or a customer to know about
the product trustworthiness through the other user’s feedback for that product.

2.4 ARCHITECTURE SPECIFICATIONS

Fig 2.1 System Architecture

2.5 HARDWARE REQUIREMENTS

• Processor : Pentium-IV
• RAM : 512 MB Ram
• Hard disk : 40 GB
• Monitor : Colour Monitor
• Keyboard : Standard 104 Keys
• Mouse : Two Button Scroll Mouse

2.6 SOFTWARE REQUIREMENTS

• Operating System : Windows XP Professional
• Programming Language : Microsoft Studio .NET 2008
• Front-End : ASP.NET
• Back-End : SQL SERVER 2005
• Web Server : IIS

5
2.7 SOFTWARE SPECIFICATION

2.7.1 FRONT END USED:

Microsoft Visual Studio dot Net is used as front end tool. The reason for selecting Visual
Studio dot Net as front end tool is as follows.

2.7.2 FEATURES OF MICROSOFT VISUAL STUDIO DOT NET:

• Visual Studio .Net has flexibility, allowing one or more language to interoperate to
provide the solution. This Cross Language Compatibility allows us to do projects at
faster rate.
• Visual Studio. Net has Common Language Runtime, which allows the entire
component to converge into one intermediate format and then interact.
• Visual Studio. Net provides excellent security when an application is executed in the
system
• Visual Studio.Net has flexibility, allowing us to configure the working environment to
best suit our individual style. We can choose between a single and multiple document
interfaces, and we can adjust the size and positioning of the various IDE elements.
• Visual Studio. Net has intelligent feature that makes the coding easy and also dynamic
help provides very less coding time.
• The working environment in Visual Studio.Net is often referred to as Integrated
Development Environment because it integrates many different functions such as
design, editing, compiling and debugging within a common environment.
• After creating a Visual Studio. Net application, if we want to distribute it to others we
can freely distribute any application to anyone who uses Microsoft windows. We can
distribute our applications on disk, on CDs, across networks, or over an intranet or the
internet.
• Toolbars provide quick access to commonly used commands in the programming
environment. We click a button on the toolbar once to carry out the action represented
by that button. By default, the standard toolbar is displayed when we start Visual Basic
dot Net. Additional toolbars for many parts of Visual Studio are context sensitive.
Context sensitive means we can get help on these parts directly without having to go

6
 through the help menu. For example, to get help on any keyword in the Visual Basic
language, place the insertion point on that keyword in the code window and press F1.
• Visual Studio interprets our code as we enter it, catching and highlighting most syntax
or spelling errors on the fly. It’s almost like having an expert watching over our
shoulder as we enter our code.
2.7.3 FEATURES OF. NET

Microsoft .NET is a set of Microsoft software technologies for rapidly building and
integrating XML Web services, Microsoft Windows-based applications, and Web solutions.
The .NET Framework is a language-neutral platform for writing programs that can easily and
securely interoperate. There’s no language barrier with .NET, there are numerous languages
available to the developer including Managed C++, C#, Visual Basic and Java Script. The
.NET framework provides the foundation for components to interact seamlessly, whether
locally or remotely on different platforms. It standardizes common data types and
communications protocols so that components created in different languages can easily
interoperate.

“.NET” is also the collective name given to various software components built upon
the .NET platform. These will be both products (Visual Studio.NET and Windows.NET
Server, for instance) and services (like Passport, .NET My Services, and so on.

2.7.4 THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).

2. A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the environment
within which programs run. The most important features are
 Conversion from a low-level assembler-style language, called
Intermediate Language (IL), into code native to the platform being
executed on.
 Memory management, notably including garbage collection.

7
  Checking and enforcing security restrictions on the running code.
 Loading and executing programs, with version control and other such
features.
 The following features of the .NET framework are also worth description.
2.7.5 MANAGED CODE

The code that targets .NET, and which contains certain extra Information “metadata”
to describe itself. While both managed and unmanaged code can run in the runtime, only
managed code contains the information that allows the CLR to guarantee, for instance, safe
execution and interoperability.

2.7.6 MANAGED DATA

With Managed Code comes Managed Data. CLR provides memory allocation and
Deal location facilities, and garbage collection. Some .NET languages use Managed Data by
default, such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do not.
Targeting CLR can depending on the language using, impose certain constraints on the
features available.

As with managed and unmanaged code, one can have both managed and unmanaged
data in .NET applications, data that doesn’t get garbage collected but instead is looked after
by unmanaged code.

2.7.7 COMMON TYPE SYSTEM

The CLR uses something called the Common Type System (CTS) to strictly enforce
type-safety. This ensures that all classes are compatible with each other, by describing types
in a common way. CTS define how types work within the runtime, which enables types in one
language to interoperate with types in another language, including cross-language exception
handling. As well as ensuring that types are only used in appropriate ways.

8
2.7.8 COMMON LANGUAGE SPECIFICATION

The CLR provides built-in support for language interoperability. To ensure that you
can develop managed code that can be fully used by developers using any programming
language, a set of language features and rules for using them called the Common Language
Specification (CLS) has been defined. Components that follow these rules and expose only
CLS features are considered CLS-compliant.

2.7.9 THE CLASS LIBRARY

.NET provides a single-rooted hierarchy of classes, containing over 7000 types. The
root of the namespace is called System; this contains basic types like Byte, Double, Boolean,
and String, as well as Object. All objects derive from System. Object. As well as objects, there
are value types. Value types can be allocated on the stack, which can provide useful flexibility.
There are also efficient means of converting value types to object types if and when necessary.

The set of classes is pretty comprehensive, providing collections, file, screen, and
network I/O, threading, and so on, as well as XML and database connectivity.

The class library is subdivided into a number of sets (or namespaces), each providing
distinct areas of functionality, with dependencies between the namespaces kept to a minimum.

2.7.10 LANGUAGES SUPPORTED BY .NET

The multi-language capability of the .NET Framework and Visual Studio .NET
enables developers to use their existing programming skills to build all types of applications
and XML Web services. The .NET framework supports new versions of Microsoft’s old
favorites Visual Basic and C++ (as VB.NET and Managed C++), but there are also a number
of new additions to the family.

Visual Basic .NET has been updated to include many new and improved language
features that make it a powerful object-oriented programming language. These features
include inheritance, interfaces, and overloading, among others. Visual Basic also now
supports structured exception handling, custom attributes and also supports multi-threading.

9
 Visual Basic .NET is also CLS compliant, which means that any CLS-compliant
language can use the classes, objects, and components you create in Visual Basic .NET.

Managed Extensions for C++ and attributed programming are just some of the
enhancements made to the C++ language. Managed Extensions simplify the task of migrating
existing C++ applications to the new .NET Framework.

VB is Microsoft’s new language. It’s a C-style language that is essentially “C++ for
Rapid Application Development”. Unlike other languages, its specification is just the
grammar of the language. It has no standard library of its own, and instead has been designed
with the intention of using the .NET libraries as its own.

Microsoft Visual J# .NET provides the easiest transition for Java-language developers
into the world of XML Web Services and dramatically improves the interoperability of Java-
language programs with existing software written in a variety of other programming
languages.

Active State has created Visual Perl and Visual Python, which enable .NET-aware
applications to be built in either Perl or Python. Both products can be integrated into the Visual
Studio .NET environment. Visual Perl includes support for Active State’s Perl Dev Kit.

2.7.11 .NET ADVANTAGES:

1. Newest technology from MS for app development

2. Supports fully managed, but also a hyrid mix of managed and native through P/Invoke
and Managed/Unmaged C++, which means that its easier to write code that doesn't have
lots of memory leaks

3. WPF and WCF are the new way of buildign UI's and Communicating between processes
and systems

4. Fully integrated IDE available

5. Linux and Mac support through 3rd parties (Mono)

10
 6. Many languages available, both dynamic (IronPython and IronRuby) and static (C#,
VB.NET, C++), both object oriented (C#, VB.NET, C++) and functional (F#)

2.7.12 .NET DISADVANTAGES

• Multi platform support isn't available from MS and isn't available straight after installing
Visual Studio

• Managed code can be slower than native code.

2.7.13 BACK END USED:

Microsoft SQL SERVER 2005 is used as back end tool. The reason for selecting SQL
SERVER 2000 as a back end tool is as follows:

2.7.14 FEATURES OF SQL SERVER 2005

The OLAP Services feature available in SQL Server version 7.0 is now called SQL Server
2005 Analysis Services. The term OLAP Services has been replaced with the term Analysis
Services. Analysis Services also includes a new data mining component. The Repository
component available in SQL Server version 7.0 is now called Microsoft SQL Server 2000 Meta
Data Services. References to the component now use the term Meta Data Services. The term
repository is used only in reference to the repository engine within Meta Data Services.

2.7.15 SQL-SERVER

SQL server database consist of five type of objects.

1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO

11
1) TABLE:
A database is a collection of data about a specific topic. We can View a table in two
ways,
a) Design View
b) Datasheet View
a) Design View
To build or modify the structure of a table, we work in the table design view. We
can specify what kind of datas will be holded.
b) Datasheet View
To add, edit or analyses the data itself, we work in tables datasheet view mode.

2) QUERY:
A query is a question that has to be asked to get the required data. Access gathers
data that answers the question from one or more table. The data that make up the answer is either
dynaset (if you edit it) or a snapshot (it cannot be edited).Each time we run a query, we get latest
information in the dynaset. Access either displays the dynaset or snapshot for us to view or perform
an action on it, such as deleting or updating.

3) FORMS:
A form is used to view and edit information in the database record. A form displays only
the information, we want to see in the way we want to see it. Forms use the familiar controls
such as textboxes and checkboxes. This makes viewing and entering data easy.
We can work with forms in several views. Primarily there are two views,
They are,
a) Design View
b) Form View

a) Design View
To build or modify the structure of a form, we work in form’s design view. We can add control
to the form that are bound to fields in a table or query, includes textboxes, option buttons, graphs
and pictures.

12
 4) REPORT:
A report is used to view and print the information from the database. The report
can ground records into many levels and compute totals and average by checking values
from many records at once. Also the report is attractive and distinctive because we have
control over the size and appearance of it.

5) MACRO:
A macro is a set of actions. Each action in a macro does something, such as opening a
form or printing a report .We write macros to automate the common tasks that work easily
and save the time.

2.8 FEATURES OF SQL PROCEDURES

sql procedures are characterized by many features. sql procedures:

• Can contain SQL Procedural Language statements and features which support the
implementation of control-flow logic around traditional static and dynamic SQL
statements.
• Are supported in the entire DB2 family brand of database products in which many if not
all of the features supported in DB2 Version 9 are supported.
• Are easy to implement, because they use a simple high-level, strongly typed language.
• SQL procedures are more reliable than equivalent external procedures.
• Adhere to the SQL99 ANSI/ISO/IEC SQL standard.
• Support input, output, and input-output parameter passing modes.
• Support a simple, but powerful condition and error-handling model.
• Allow you to return multiple result sets to the caller or to a client application.
• Allow you to easily access the SQLSTATE and SQLCODE values as special variables.
• Reside in the database and are automatically backed up and restored.
• Can be invoked wherever the CALL statement is supported.

13
2.9 WORK BREAKDOWN STRUCTURE

Personalized system for fraud

product detection.

Off-line
Website infrastructure

Website Website Web service Internal capacity Internal capacity on

Layout Content infrastructure on shopping communications
operation with foreign client

Web site Network Web server

text ready Ready ready
Internal capacity
on maintenance of
web content

Product’s
image ready Web server
Hardware
Installed Installed
Internal capacity
on maintenance of
web server

Fig: 2.2 Work breakdown structure

14
 CHAPTER 3

LITERATURE SURVEY AND REVIEW

3.1 LITERATURE SURVEY

Disadvantage Year of
Title Description
Publish
1. Bart:Bayesian 1. BART is a nonparametric • The method does not
Additive Regression Bayesian regression approach provide a principled 2010
which uses dimensionally
Trees adaptive random basis assessment of
elements. uncertainty about the
2. BART can be viewed as a prediction
Bayesian nonparametric • It has strong feature
approach that fits a parameter independence
rich model using a strongly assumptions.
influential prior distribution.

3. Its performance was seen to

be remarkably robust to hyper
parameter specification, and
remained effective when the
regression function was buried
in ever higher dimensional
spaces.

2. Bayesian Multiple 1. Propose a novel Bayesian • It is not always

Instance Learning: multiple instance learning possible for a teacher 2008
algorithms.
Automatic Feature to provide labeled
2. This algorithm automatically
Selection and identities the relevant feature examples for training
Inductive Transfer subset, and utilizes inductive • They don’t specify
transfer when learning multiple
their actual prior, but
classifiers.

15
 3. Experimental results indicate rather one which is
that the proposed MIL method convenient
is more accurate than previous
MIL algorithms and selects a
much smaller set of useful
features.

3. Unbiased Online 1. Unlabeled samples can be • Errors introduced by

Active Learning in intelligently selected for variations in the 2011
Data Streams labeling to minimize functions used to
classification error. model the peak
shapes are
2. Focus on Binary
investigated
classification problems and
study selective labeling in data
streams where a decision is
required on each sample
sequentially.

3. The unbiasedness property in

the sampling process, and
design optimal instrumental
distributions to minimize the
variance in the stochastic
process.

16
4. A Machine- 1. Online auction and shopping • Most online auction
Learned Proactive are gaining popularity with the houses agree to 2011
Moderation System growth of web-based passive approaches to
for Auction Fraud eCommerce. the coordination of
Detection reputation systems
2. Proactive moderation
and management
systems are deployed to detect
policies that could
suspicious events for further
address fraudulent
inspection by human experts.
schemes.
3. In both offline evaluations
and online bucket tests, the
proposed system significantly
outperforms the rule-based
system on various metrics,
including area under ROC
(AUC), loss rate of labeled
frauds and customer
complaints.

3.2 LITERATURE SUMMARY

In this project considering the problem of building online fraud product detection in
shopping websites. Increasing use of internet, online shopping and online auction have gained
more importance. Hence fraud product detection moderation systems are commonly applied in
practice to detect and prevent such illegal and fraud products. In this project, we propose an online
probity model framework which takes online feature selection, coefficient bounds from human
knowledge and multiple instances learning into account simultaneously. By observations on a real-
world online auction fraud product detection data we show that this model can potentially detect
more frauds products and significantly reduce customer complaints compared to several base line
models and the human-tuned rule-based system.

17
 CHAPTER 4

SYSTEM DESIGN

4.1 HIGH-LEVEL DESIGN

4.1.1 DATA FLOW DIAGRAM
The DFD takes an input-process-output view of a system i.e. data objects flow into the
software, are transformed by processing elements, and resultant data objects flow out of the
software.

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.

18
LEVEL 0

Admin

Yes No
Che
ck

Unauthorized
View new
user
seller

Allow new
sellers

View Products

View
complaints

Set untrusted

Fig: 4.1 Admin Data Flow Diagram

19
LEVEL 1

Seller

Yes No
Che
ck

Unauthorized
Launch
user
products

View Products

Offers for
products

End Process

Fig 4.2 Seller Data Flow Diagram

20
LEVE1 2

User

Yes No
Chec
k

Unauthorized
View offer
user

Purchase
products

Send
Complaints

End Process

Fig 4.3 User Data Flow Diagram

21
4.2 LOW-LEVEL DESIGN

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

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

22
 Fig 4.4 Class Diagram

4.2.3 USE 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

23
 Fig 4.5 Use case Diagram

4.2.4 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
24
 /user /seller /Datbase
/Admin

1 : upload products()

2 : upload offers()

3 : view products()

4 : view compalints()

5 : search offers() 6 : set trusted products()

7 : purchase products()
8 : send complaint()

9 : block untrusted products()

Fig 4.6 Sequence Diagram

4.2.5 ACTIVITY DIAGRAM

An activity diagram is a variation or special case of a state machine, in which the states are
activities representing the performance of operations and the transitions are triggered by the
completion of the operations

25
 Fig 4.7 Activity Diagram

4.2.6 STATE CHART DIAGRAM

A state diagram shows the behavior of classes in response to external stimuli. Specifically
a state diagram describes the behavior of a single object in response to a series of events in a
system. Sometimes it's also known as a state machine diagram. This UML diagram models the
dynamic flow of control from state to state of a particular object within a system.

26
 Start

User login

Registered

Browse do:/examine
all items

Select
NotWantItem
Item checked Item Review /getNewItem
(not all checked)
/ Get Next Item

Want item

Checked payment Get new item

details

Bid
Accepted
Not Accepted Payment

Do:/send payment

Item

Item Received

fig 4.8 state chart diagram

4.2.7 ENTITY RELATIONSHIP DIAGRAM

An entity-relationship diagram (ERD) is a data modeling technique that graphically
illustrates an information system's entities and the relationships between those entities. An ERD is
a conceptual and representational model of data used to represent the entity framework
infrastructure.

27
 Fig 4.9 ER Diagram

4.3 CODES AND STANDARDS

Coding standards are guidelines to programming that focuses on the physical structure and
appearance of the program. They make the code easier to read, understand and maintain. This
phase of the system actually implements the blueprint developed during the design phase. The
coding specification should be in such a way that any programmer must be able to understand the
code and can bring about changes whenever felt necessary. Some of the standard needed to achieve
the above-mentioned objectives are as follows:

28
 • Program should be simple, clear and easy to understand.
• Naming conventions
• Value conventions
• Script and comment procedure
• Message box format
• Exception and error handling

4.4 CONSTRAINTS AND TRADEOFFS

Constraints in analysis are Constraints as Informal Text, Constraints as Operational

Restrictions, Constraints Integrated in Existing Model Concepts, Constraints as a Separate
Concept, Constraints Implied by the Model Structure constraints in design are
Determination of the Involved Classes, Determination of the Involved Objects.
Determination of the Involved Actions, Determination of the Require Clauses, Global
actions and Constraint Realization. Constraints in implementation are a hierarchical
structuring of relations may result in more classes and a more complicated structure to
implement. Therefore it is advisable to transform the hierarchical relation structure to a
simpler structure such as a classical flat one. It is rather straightforward to transform the
developed hierarchical model into a bipartite, flat model, consisting of classes on the one
hand and flat relations on the other. Flat relations are preferred at the design level for
reasons of simplicity and implementation ease. There is no identity or functionality
associated with a flat relation. A flat relation corresponds with the relation concept of
entity-relationship modeling and many object oriented methods.

4.5 TEST CASES GENERATION

4.5.1 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

29
expectations and does not fail in an unacceptable manner. There are various types of test. Each test
type addresses a specific testing requirement.

4.5.2 FUNCTIONAL TESTING

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

4.5.3 SYSTEM TESTING

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.

30
4.5.4 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.

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

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

4.5.7 UNIT TESTING:

Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program input 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

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

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.

4.5.8 TEST STRATEGY AND APPROACH:

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

4.5.9 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

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

32
4.5.11 TEST RESULTS:

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

TESTING

Expected
S.No Procedure Test Condition Test Data Data

1 1.Validate the 1. If the Username [email protected] Successfully

User login Username and entered
page Password are login
available in the Password sara@123 Account
Database.

2.Enter the 2.If the Username sara Error

Username and Username and message
Password Password are not will display
available in Password sara
Database

Result on
3.click login 3.Authentication Fail / Pass database
button verification verification

4.Cancel 4.Password will Fail / Pass Process

be terminated terminator

Test Result : Success

4.10. Unit & Integration Testing

33
 INTEGRATION TESTING

Expected
S.No Procedure Test Test Data Data
Condition

1 1.Add New 1. Enter user UName [email protected] New User

user Details details valid firstName Sara added
on database Last name san Successfully
DOB 12/3/2000
Gender Female
Contact No 2266776
Email id [email protected]
Hint Color
Answer Pink
Address 12 Vellore
Country India
State Tamil Nadu
City Vellore
Zip code 632007

2.Enter 2.Enter First name Sara

Shipping shipping Last name san
details details Email id [email protected] Shipping
Gender female details
Contact no 2266776 added
Address 12 Vellore successfully
Country India
State Tamil Nadu
City Vellore

3.Payment 3.Enter user Cart amt $26

Details payment Tax amt $2.21 Payment
details Ship amt $10 details
Net pay $38.21 added
Card No 1234-1212-0101 successfully
Card code 3245
Expire date 01/10/2016

4. To submit 4. Check the Check the

the button Details on Fail / Pass valid details
database

Test Result : Success

34
 CHAPTER 5

SYSTEM IMPLEMENTATION

5.1 SOURCE CODE

Frmadmin.Aspx

using System;

using System.Data;

using System.Configuration;

using System.Collections;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;

using System.Diagnostics;

public partial class Admin_frmadmin : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
}

protected void LinkButton1_Click(object sender, EventArgs e)

35
Process p = new Process();

p.StartInfo.FileName = "C:\\Sudha\\2015-Major Projects\\2-Shopping\\2-

Shopping\\Shopping\\Admin\\AdminCatalog\\Release\\GMail sender.exe";

p.Start();

Categorylist.Aspx

using System;

using System.Data;

using System.Configuration;

using System.Collections;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;

using System.IO;

using ShoppingCart.BL;

public partial class ucategoryListl : System.Web.UI.UserControl

protected void Page_Load(object sender, EventArgs e)

36
if (!IsPostBack)

BindList();

panelCategoryTop.Visible = true;

panelNewCategory.Visible = false;

private void BindList()

DataSet ds = ProductController.getALLCategories();

lblMsg.Text = "";

if (ds.Tables[0].Rows.Count > 0)

dlCategory.DataSource = ds;

dlCategory.DataBind();

else

lblMsg.Text = "No such Item !!! Please add one";

protected void lBtnNewCategory_Click(object sender, EventArgs e)

37
lblNewCAtegoryHeader.Text = "Add New Category";

panelCategoryTop.Visible = false;

panelNewCategory.Visible = true;

IbtnCatSubmit.AlternateText = "Submit";

txtCategoryName.Text = "";

txtCatDescriptrion.Text = "";

// imgCatLogo.Visible = false;

//lblImage.Visible = false;

protected void IbtnCatSubmit_Click(object sender, ImageClickEventArgs e)

string catname="", description="", imageurl="",image="";

if (txtCategoryName.Text.Trim().Length > 0)

catname = txtCategoryName.Text.Trim();

else

lblMsgNewCat.Text = "Enter Category Name";

description = txtCatDescriptrion.Text.Trim();

if (fileCat.FileName != null && fileCat.FileName.Trim()!="")

imageurl = "~/Browse/Images/" + fileCat.FileName;

fileCat.SaveAs(Server.MapPath(imageurl));

image=fileCat.FileName;

38
else

{
if (imgCatLogo.ImageUrl != null)
{
image = Path.GetFileName(imgCatLogo.ImageUrl);
}
else
image = "na.jpg";
}
if (IbtnCatSubmit.AlternateText == "Submit")
{
ProductController.InsertCategory(catname, description, image);
}
else
{
int catid = int.Parse(lblCatID.Text);
ProductController.UpdateCategory(catid,catname, description, image);
}
BindList();
panelCategoryTop.Visible = true;
panelNewCategory.Visible = false;
}
protected void dlCategory_ItemCommand(object source, DataListCommandEventArgs e)
{
if (e.CommandName == "Edit")
{
lblNewCAtegoryHeader.Text = "Update Category";
DataSet ds =
ProductController.GetAllCategoriesBYCategoryID(int.Parse(e.CommandArgument.ToString()))
;
if (ds.Tables[0].Rows.Count > 0)

39
{

lblCatID.Text = e.CommandArgument.ToString();

txtCategoryName.Text = ds.Tables[0].Rows[0]["Name"].ToString();

txtCatDescriptrion.Text = ds.Tables[0].Rows[0]["Description"].ToString();

imgCatLogo.ImageUrl = String.Format("~/Browse/Images/{0}",
ds.Tables[0].Rows[0]["Image"].ToString());

IbtnCatSubmit.AlternateText = "Update";

panelCategoryTop.Visible = false;

panelNewCategory.Visible = true;
}
}
if (e.CommandName == "Delete")
{
lblCatID.Text = e.CommandArgument.ToString();
int catid = int.Parse(lblCatID.Text);
//Response.Write(catid);

ProductController.DeleteCategory(catid);

BindList();

protected void IBtnCatCancel_Click(object sender, ImageClickEventArgs e)

{
panelCategoryTop.Visible = true;
panelNewCategory.Visible = false;

40
}

Userlist.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.IO;
using ShoppingCart.BL;

public partial class Admin_AdminCatalog_AdminUsers_ucUsersList :

System.Web.UI.UserControl
{
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
BindList();
panelTop.Visible = true;
panelupdate.Visible = false;
}
}
private void BindList()
{
DataSet ds = UserController.getALLUsers();

41
lblMsg.Text = "";
if (ds.Tables[0].Rows.Count > 0)
{
dlBrand.DataSource = ds;
dlBrand.DataBind();
}
else
{
lblMsg.Text = "No such Item !!! Please add one";
}
country();
state();
city();
}
protected void ddlcountry_SelectedIndexChanged(object sender, EventArgs e)
{
DataSet dsState =
ProductController.getAllStatesByCountryID(int.Parse(ddlcountry.SelectedValue));
BindDDL(ddlstate, dsState, "Name", "ID");
DataSet dscity = ProductController.getCitydetailsByStateID(int.Parse(ddlstate.SelectedValue));
BindDDL(ddlcity, dscity, "Name", "ID");
}
protected void ddlstate_SelectedIndexChanged(object sender, EventArgs e)
{
DataSet dscity = ProductController.getCitydetailsByStateID(int.Parse(ddlstate.SelectedValue));
BindDDL(ddlcity, dscity, "Name", "ID");
}
private void state()
{
DataSet dsState = ProductController.getAllStatedetails();
BindDDL(ddlstate, dsState, "Name", "ID");

42
}
private void country()
{
DataSet dsCountry = ProductController.getCountrydetails();
BindDDL(ddlcountry, dsCountry, "Name", "ID");
}
private void BindDDL(DropDownList ddl, DataSet ds, string txtField, string valField)
{
ddl.DataSource = ds;
ddl.DataTextField = txtField;
ddl.DataValueField = valField;
ddl.DataBind();
}
private void city()
{
DataSet dscity = ProductController.getCitydetails();
BindDDL(ddlcity, dscity, "Name", "ID");
}
protected void IbtnBrandSubmit_Click(object sender, ImageClickEventArgs e)
{
string BrandName = "", Description = "", imageurl = "", Logo = "";
int AddressID = Convert.ToInt32(lblAddressID.Text.Trim());
int UserID = Convert.ToInt32(lblUserID.Text.Trim());
UserController.UpdateUserDetails(txtuser.Text, txtfname.Text, txtlname.Text,
GMDatePicker1.Date, txtcontact.Text, rdSex.SelectedValue, txtmail.Text, txtaddr.Text,
int.Parse(ddlcountry.SelectedValue), int.Parse(ddlstate.SelectedValue),
int.Parse(ddlcity.SelectedValue), txtZipCode.Text, AddressID, UserID);
lblres.Text = "Done!!!";
BindList();
panelTop.Visible = true;
panelupdate.Visible = false;

43
}
protected void dlBrand_ItemCommand(object source, DataListCommandEventArgs e)
{
ListItem li = null;
if (e.CommandName == "Edit")
{
DataSet ds = UserController.GetUserBYUserID(int.Parse(e.CommandArgument.ToString()));
if (ds.Tables[0].Rows.Count > 0)
{
lblUserID.Text = e.CommandArgument.ToString();
lblAddressID.Text = ds.Tables[0].Rows[0]["AddressId"].ToString();
txtuser.Text = ds.Tables[0].Rows[0]["UserName"].ToString();
txtaddr.Text = ds.Tables[0].Rows[0]["Address"].ToString();
txtcontact.Text = ds.Tables[0].Rows[0]["ContactNo"].ToString();
txtfname.Text = ds.Tables[0].Rows[0]["FirstName"].ToString();
txtlname.Text = ds.Tables[0].Rows[0]["LastName"].ToString();
txtmail.Text = ds.Tables[0].Rows[0]["EmailID"].ToString();
txtZipCode.Text = ds.Tables[0].Rows[0]["ZipCode"].ToString();
li = ddlcity.Items.FindByText(ds.Tables[0].Rows[0]["CityName"].ToString());
if(li!=null)
{
ddlcity.ClearSelection();
li.Selected = true;
}
li = ddlcountry.Items.FindByText(ds.Tables[0].Rows[0]["CountryName"].ToString());
if (li != null)
{
ddlcountry.ClearSelection();
li.Selected = true;
}
li = ddlstate.Items.FindByText(ds.Tables[0].Rows[0]["StateName"].ToString());

44
if (li != null)
{
ddlstate.ClearSelection();
li.Selected = true;
}
li = rdSex.Items.FindByText(ds.Tables[0].Rows[0]["Gender"].ToString());
if (li != null)
{
rdSex.ClearSelection();
li.Selected = true;
}
GMDatePicker1.Date = Convert.ToDateTime(ds.Tables[0].Rows[0]["DOB"].ToString());
panelTop.Visible = false;
panelupdate.Visible = true;
}
}
if (e.CommandName == "Delete")
{
lblUserID.Text = e.CommandArgument.ToString();
int UserId = int.Parse(lblUserID.Text);
UserController.DeleteUserByUserID(UserId);
BindList();
}
}
protected void IBtnBrandCancel_Click(object sender, ImageClickEventArgs e)
{
panelupdate.Visible = false;
panelTop.Visible = true;

45
 CHAPTER 6
RESULTS AND DISCUSSION

6.1 OUTPUT/RESULTS
6.1.1 CUSTOMER SIGN IN

6.1.2 BRAND LIST

46
6.1.3 ADD TO CARD

6.1.4 CARD LIST

47
6.1.5 PAYMENT OPTION

6.1.6 OFFLINE PAYMENT DETAILS

48
6.1.7 ADMIN PROCESS

6.1.8 ADD NEW CATEGORY

49
6.1.9 CATEGORY LIST

6.1.10 ADD NEW BRAND

50
6.1.11 PRODUCT LIST

51
 CHAPTER 7

CONCLUSION AND FUTURE WORK

7.1 CONCLUSION

Since the emergence of the World Wide Web (WWW), electronic commerce, commonly
known as e-commerce, has become more and more popular, websites benefits everyone in terms
of convenience and profitability. The traditional online shopping business model allows sellers to
sell a product or service at a preset price, where buyers can choose to purchase find it to be a good
deal but we build online model for fraud product detection while concentrating on customer needs.
In this proposed system we provide the responsibility of selling the trustful products by the website
itself managed by the admin. So when a customer wishes to buy a product he will get an idea about
the product to how much extent he can believe in that product. If he has faced any problem he can
make others aware of that product by complaining about the product. This model though it cannot
be the ideal way of detecting frauds but it can do the maximum extent in detecting the sellers
selling the fraud products.

The true online shopping is that which discovers each customer’s known interests and
needs on an individual level and gives a much more powerful platform from which to optimize
content and offers, a vital key to long-term brand engagement and loyalty.

52
7.2 FUTURE WORK
Regarding to future work, one direction is to include the adjustment of the selection bias
in the online model training process. It has been proven to be very effective for offline models.
The main idea there is to assume all the unlabeled samples have response equal to 0 with a very
small weight. Since the unlabeled samples are obtained from an effective moderation system, it is
reasonable to assume that with high probabilities they are non-fraud.
This can be easily extended to too many other applications, such as web spam detection,
content optimization and so forth websites that delivers highly personalized and trusted
experiences top the traffic and revenue rankings across the globe.
Web spam has been an important problem affecting both the consumers and web service
providers since the invention of World Wide Web. So we can attempt to build a spam detection
system for classification of websites as spam or non-spam. Here we try to explore if the spam web-
sites follow certain pattern in terms of the links they are out linked/in linked to or in terms of
contents of such websites. For this, we use various features based on the link graph or the contents
of only the host pages. The benefit of host based labelling instead of individual page based
labelling is that we can cover a larger number of websites to build the model. We define spam city
as the probability with which a page can be classified as spam (0 for non-spam page and 1 for
spam page).

53
 CHAPTER 8
REFERENCES

8.1 REFERENCES
1. By Hugh A. Chipman, Edward I. George and Robert E. McCulloch” Bart: Bayesian
Additive Regression Trees” 2010
2. Liang Zhang Jie Yang Belle Tseng, “Online Modeling of Proactive Moderation System for
Auction Fraud Detection” April 16–20, 2012.
3. Wei Chu, Wei Chu, Lihong Li, “Unbiased Online Active Learning in Data Streams” 2011.
4. Liang Zhang, Jie Yang, “A Machine-Learned Proactive Moderation System for Auction
Fraud Detection” Apr 16, 2012.
5. H. Chipman, E. George, and R. McCulloch. Bart: Bayesian additive regression trees. The
Annals of Applied Statistics, 4(1):266–298, 2010.
6. W. Chu, M. Zinkevich, L. Li, A. Thomas, and B. Tseng. Unbiased online active learning
in data streams. In Proceedings of the 17th ACM SIGKDD international conference on
Knowledge discovery and data mining, pages 195–203. ACM, 2011.
7. C. Chua and J. Wareham. Fighting internet auction fraud: An assessment and proposal.
Computer, 37(10):31–37, 2004.
8. R. Collins, Y. Liu, and M. Leordeanu. Online selection of discriminative tracking features.
IEEE Transactions on Pattern Analysis and Machine Intelligence, pages 1631–1643, 2005.
9. N. Cristianini and J. Shawe-Taylor. An introduction to support Vector Machines: and other
kernel-based learning methods. Cambridge university press, 2006.

54
55