Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

1. INTRODUCTION

INTRODUCTION
Internet services have brought human beings with ecommerce, social networking,
and entertainment platforms, which not only facilitate information exchange but also
provide chances to fraudsters. Fraudsters disguise themselves as ordinary users to publish
spam information or collect user privacy, compromising the interest of both platforms
and users. In addition, multiple entities on the Internet are connected with multiple
relationships. Traditional machine learning algorithms cannot handle this complicated
heterogeneous graph data well. The current approach is to model the data as a
heterogeneous information network so that similarities in characteristics and structure of
fraudsters can be discovered. Due to the effectiveness in learning the graph
representation, graph neural networks (GNNs) have already been introduced into fraud
detection areas including product review, mobile application distribution, cyber crime
identification and financial services . However, most existing GNN based solutions just
directly apply homogeneous GNNs, ignoring the underlying heterogeneous graph nature
and camouflage node behaviors. This problem has drawn great attention with many
solutions proposed . GraphConsis found that there are three inconsistency problems in
fraud detection and CAREGNN further proposed two camouflage behaviors. These
problems could be summarized as follows:
Camouflage: Previous work showed that crowd workers could adjust their behavior to
alleviate their suspicion via connecting to benign entities like connecting to highly
reputable users, disguise fraudulent URLs with special characters or generate domain-
independent fake reviews via generative language model to conceal their suspicious
activities.
Inconsistency: Two users with distinct interests could be connected via reviewing a
common product such as food or movies. Direct aggregation makes GNNs hardly
distinguish the unique semantic user pattern. Also, if a user is suspicious, then the other
one should be more likely to be distrustful if they are connected by commonactivity
relation since fraudulent users tend to post many fraudulent reviews in the same short
period.

SRTS, Kadapa Page 1

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

2. LITERATURE SURVEY
1. X. Wang, H. Ji, C. Shi, B. Wang, Y. Ye, P. Cui, and P. S. Yu, “Heterogeneous
graph attention network,” in WWW, 2019, pp. 2022–2032.
Graph neural network, as a powerful graph representation technique based on
deep learning, has shown superior performance and attracted considerable research
interest. However, it has not been fully considered in graph neural network for
heterogeneous graph which contains different types of nodes and links. The heterogeneity
and rich semantic information bring great challenges for designing a graph neural
network for heterogeneous graph. Recently, one of the most exciting advancements in
deep learning is the attention mechanism, whose great potential has been well
demonstrated in various areas. In this paper, we first propose a novel heterogeneous
graph neural network based on the hierarchical attention, including node-level and
semantic-level attentions. Specifically, the node-level attention aims to learn the
importance between a node and its meta-path based neighbors, while the semantic-level
attention is able to learn the importance of different meta-paths. With the learned
importance from both node-level and semantic-level attention, the importance of node
and meta-path can be fully considered. Then the proposed model can generate node
embedding by aggregating features from meta-path based neighbors in a hierarchical
manner. Extensive experimental results on three real-world heterogeneous graphs not
only show the superior performance of our proposed model over the state-of-the-arts, but
also demonstrate its potentially good interpretability for graph analysis.
2. S. Zhou, J. Bu, X. Wang, J. Chen, and C. Wang, “Hahe: Hierarchical attentive
heterogeneous information network embedding,” arXiv preprint arXiv:1902.01475,
2019.
Heterogeneous information network (HIN) embedding has recently attracted
much attention due to its effectiveness in dealing with the complex heterogeneous data.
Meta path, which connects different object types with various semantic meanings, is
widely used by existing HIN embedding works. However, several challenges have not
been addressed so far. First, different meta paths convey different semantic meanings,
while existing works assume that all nodes share same weights for meta paths and ignore
the personalized preferences of different nodes on different meta paths. Second, given a

SRTS, Kadapa Page 2

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

meta path, nodes in HIN are connected by path instances while existing works fail to
fully explore the differences between path instances that reflect nodes' preferences in the
semantic space. rTo tackle the above challenges, we propose aHierarchical Attentive
Heterogeneous information network Embedding (HAHE) model to capture the
personalized preferences on meta paths and path instances in each semantic space. As
path instances are based on a particular meta path, a hierarchical attention mechanism is
naturally utilized to model the personalized preference on meta paths and path instances.
Extensive experiments on several real-world datasets show that our proposed \model
model significantly outperforms the state-of-the-art methods in terms of various data
mining tasks.
3. S. Wang, Z. Chen, D. Li, Z. Li, L.-A. Tang, J. Ni, J. Rhee, H. Chen, and P. S. Yu,
“Attentional heterogeneous graph neural network: Application to program
reidentification,” in Proceedings of the 2019 SIAM International Conference on
Data Mining. SIAM, 2019, pp. 693–701.
Program or process is an integral part of almost every IT/OT system. Can we trust
the identity/ID (e.g., executable name) of the program? To avoid detection, malware may
disguise itself using the ID of a legitimate program, and a system tool (e.g., PowerShell)
used by the attackers may have the fake ID of another common software, which is less
sensitive. However, existing intrusion detection techniques often overlook this critical
program reidentification problem (i.e., checking the program's identity). In this paper, we
propose an attentional heterogeneous graph neural network model (DeepHGNN) to verify
the program's identity based on its system behaviors. The key idea is to leverage the
representation learning of the heterogeneous program behavior graph to guide the
reidentification process. We formulate the program reidentification as a graph
classification problem and develop an effective attentional heterogeneous graph
embedding algorithm to solve it. Extensive experiments --- using real-world enterprise
monitoring data and real attacks --- demonstrate the effectiveness of DeepHGNN across
multiple popular metrics and the robustness to the normal dynamic changes like program
version upgrades.

SRTS, Kadapa Page 3

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

4. Z. Hu, Y. Dong, K.Wang, and Y. Sun, “Heterogeneous graph transformer,” in

WWW, 2020, pp. 2704–2710.
Recent years have witnessed the emerging success of graph neural networks
(GNNs) for modeling structured data. However, most GNNs are designed for
homogeneous graphs, in which all nodes and edges belong to the same types, making it
infeasible to represent heterogeneous structures. In this paper, we present the
Heterogeneous Graph Transformer (HGT) architecture for modeling Web-scale
heterogeneous graphs. To model heterogeneity, we design node- and edge-type
dependent parameters to characterize the heterogeneous attention over each edge,
empowering HGT to maintain dedicated representations for different types of nodes and
edges. To handle Web-scale graph data, we design the heterogeneous mini-batch graph
sampling algorithm—HGSampling—for efficient and scalable training. Extensive
experiments on the Open Academic Graph of 179 million nodes and 2 billion edges show
that the proposed HGT model consistently outperforms all the state-of-the-art GNN
baselines by 9–21 on various downstream tasks. The dataset and source code of HGT are
publicly available at https://github.com/acbull/pyHGT.
5. G. Wang, S. Xie, B. Liu, and S. Y. Philip, “Review graph based online store
review spammer detection,” in ICDM. IEEE, 2011, pp. 1242–1247.
Online reviews provide valuable information about products and services to
consumers. However, spammers are joining the community trying to mislead readers by
writing fake reviews. Previous attempts for spammer detection used reviewers’
behaviors, text similarity, linguistics features and rating patterns. Those studies are able
to identify certain types of spammers, e.g., those who post many similar reviews about
one target entity. However, in reality, there are other kinds of spammers who can
manipulate their behaviors to act just like genuine reviewers, and thus cannot be detected
by the available techniques. In this paper, we propose a novel concept of a heterogeneous
review graph to capture the relationships among reviewers, reviews and stores that the
reviewers have reviewed. We explore how interactions between nodes in this graph can
reveal the cause of spam and propose an iterative model to identify suspicious reviewers.
This is the first time such intricate relationships have been identified for review spam
detection. We also develop an effective computation method to quantify the trustiness of

SRTS, Kadapa Page 4

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

reviewers, the honesty of reviews, and the reliability of stores. Different from existing
approaches, we don’t use review text information. Our model is thus complementary to
existing approaches and able to find more difficult and subtle spamming activities, which
are agreed upon by human judges after they evaluate our results.

SRTS, Kadapa Page 5

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

3. SYSTEM ANALYSIS

3.1 EXISTING SYSTEM

ChebNet [14] and GCN [15] are proposed to improve efficiency by using approximation.
For GNNs on spatial domain, GraphSAGE [16] samples a tree rooted at each node and
computes the root’s hidden representation by hierarchically aggregating hidden node
representations from the bottom to top. GAT [17] further proposes to learn in the spatial
domain by computing different importance of neighbor nodes via the masked
selfattention mechanism. All these methods are designed for homogeneous graphs. They
cannot be directly applied to a heterogeneous graph with multiple types of entities and
relations.

In recent years, lots of heterogeneous GNN based methods have been developed. HAN
[18], HAHE [19], and Deep- HGNN [20] transforms a heterogeneous graph into several
homogeneous graphs based on handcrafted meta-paths, applies GNN separately on each
graph, and aggregates the output representations by attention mechanism. GraphInception
[21] constructs meta-paths between nodes with the same object type. HetGNN [22] first
samples a fixed number of neighbors via random walk strategy. Then it applies a
hierarchical aggregation mechanism for intra-type and intertype aggregation. HGT [23]
extends transformer architecture to heterogeneous graphs. They directly calculate
attention scores for all the neighbors of a target node and perform aggregation
accordingly without considering domain knowledge.

For relation-aware graph fraud detectors, their main solution is to build multiple
homogeneous graphs based on edge type information of the original graph then perform
type independent node level aggregation and graph level concatenation. GEM [9] learns
weighting parameters for different homogeneous subgraph. Player2Vec [7] and
SemiGNN [8] both adopt attention mechanism in feature aggregation and SemiGNN

SRTS, Kadapa Page 6

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

further leverages a structure loss to guarantee the node embeddings homophily. Some
works directly aggregate heterogeneous information in the graph. For instance, under a
user-review-item heterogeneous graph, GAS [3] learns a unique set of aggregators for
different node types and updates the embeddings of each node type iteratively.

Disadvantages

 In the existing work, the system did not implement Fraud Aware
Heterogeneous Graph Transformer(FAHGT) to measure frauds exactly.
 This system is less performance due to lack of META RELATION
SCORING.
3.2 PROPOSED SYSTEM
Graph Consist addresses the inconsistency problem by computing the similarity score
between node embeddings, which cannot distinguish nodes with different types.
CAREGNN enhances GNN-based fraud detectors against camouflaged fraudsters by
reinforcement learning based neighbor selector and relation aware aggregator. Its
performance still suffers from the heterogeneous graph.
In this paper, the system introduces the Fraud Aware Heterogeneous Graph
Transformer(FAHGT), where we propose heterogeneous mutual attention to address the
inconsistency problem and design a label-aware neighbor selector to solve the
camouflage problem. Both are implemented in a unified manner called the “score head
mechanism”. We demonstrate the effectiveness and efficiency of FAHGT on many real
world datasets. Experimental results suggest that FAHGT can significantly improve KS
and AUC over state-of-the-art GNNs as well as GNN-based fraud detectors.
Advantages
The advantages of FAHGT can be summarized as follows.

 Heterogeneity: FAHGT is able to handle heterogeneous graphs with multi-

relation and multi-node type without designing meta-path manually.
 Adaptability: FAHGT attentively selects neighbors given a noise graph from real-
world data. The selected neighbors are either informative for feature aggregation
or risky for fraud detection.

SRTS, Kadapa Page 7

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

 Efficiency: FAHGT admits a low computational complexity via a parallelizable

multi-head mechanism in relation scoring and feature aggregation.
 Flexibility: FAHGT injects domain knowledge by introducing a flexible relation
scoring mechanism. The score of a relation connecting two nodes not only comes
from direct feature interaction but is also constrained by domain knowledge.
3.3 FEASIBILTY 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
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.
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. The developed
system must have a modest requirement, as only minimal or null changes are required for
implementing this system.

SRTS, Kadapa Page 8

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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 real 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 hat he is also able to make some constructive criticism, which is welcomed, as
he is the final user of the system.
3.4 MODULES OF THE PROJECT
3.4.1. Admin
In this module, admin has to login with valid username and password. After login
successful he can do some operations such as View and Authorize Users,Add & View
Categories, Add & View Sub-Categories, Add Product Items, Top Products Results,View
Users Search History,View Fraud Detection On Product Reviews, View Products with
Ranks and Comments, View Products Ranks Results.
Viewing and Authorizing Users
In this module, the admin views all users details and authorize them for login
permission. User Details such as User Name, Address, Email Id and Mobile Number.
3.4.2 User
In this module, there are n numbers of users are present. User should register
before doing some. After registration successful he can login by using valid user name
and password. Login successful he will do some operations Register and Login,My
Profile, Search Products & Give Review,View Top Products,My Search History.
Viewing Profile Details
In this module, the user can see their own profile details, such as their address,
email, mobile number, profile Image.

SRTS, Kadapa Page 9

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

4. HARDWARE AND SOFTWARE REQUIREMENT

SPECIFICATIONS
4.1 H/W REQUIREMENTS
Processor : Pentium –III/Above
Speed : 1.1 Ghz
RAM : 256 MB(min)
Hard Disk : 120 GB
4.2 SOFTWARE REQUIREMENTS
Operating system : Windows XP/7.
Coding Language : Java/J2EE
Web Server : Tomcat7.x
Database : MySQL5.5

SRTS, Kadapa Page 10

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

5. SYSTEM DESIGN
5.1 INTRODUCTION
A graphical tool used to describe and analyze the moment of data through a
system manual or automated including the process, stores of data, and delays in the
system. Data Flow Diagrams are the central tool and the basis from which other
components are developed. The transformation of data from input to output, through
processes, may be described logically and independently of the physical components
associated with the system. The DFD is also known as a data flow graph or a bubble
chart.
DFDs are the model of the proposed system. They clearly should show the
requirements on which the new system should be built. Later during design activity this is
taken as the basis for drawing the system’s structure charts. The Basic Notation used to
create a DFD’s are as follows:
1. Dataflow: Data move in a specific direction from an origin to a destination.

2. Process: People, procedures, or devices that use or produce (Transform) Data. The
physical component is not identified.

3. Source: External sources or destination of data, which may be People, programs,

organizations or other entities.

Systems design is the process or art of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified requirements. One could
see it as the application of systems theory to product development. There is some overlap
and synergy with the disciplines of systems analysis, systems architecture and systems
engineering. Database Designing is a part of the development process. In the linear
development cycle, it is used during the system requirements phase to construct the data
components of the analysis model. This model represents the major data objects and the

SRTS, Kadapa Page 11

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

relationship between them. It should not be confused with data analysis, which takes
place in the system design phase. As in a DFD, a model of data consists of a number of
symbols joined up according to certain conventions. System designers describe these
conceptual modeling using symbols from a modeling method known as entity
relationship analysis.
Entity Relationship Diagram
Entity relationship analysis uses three major abstractions to describe data. These
are
1. Entities, which are distinct things in the enterprise.
2. Relationships, which are meaningful interactions between the objects.
3. Attributes, which are the properties of the entities and relationship.
The relative simplicity and pictorial clarity of this diagramming technique may
well account in large part for the widespread use of ER model. Such a diagram consists
of the following major components.
E-R Diagram Components

Rectangles, which represent the entity set.

Ellipse, which represent attributes.

Diamonds, which represent relationship sets.

Lines, which link attributes to entity sets and
entity sets to relationships.

Double Ellipse, which represents multi valued attributes.

Double lines, which indicates total participation of an entity

in a relationship set.

SRTS, Kadapa Page 12

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Entity
 An entity is an object that exists and is distinguishable from other objects.
 An entity may be concrete or abstract.
 An entity is a set of entities of the same type.
 Entity sets need not be disjoint.
 An entity is represented by a set of attributes.

Mapping Constraints
An E-R diagram may define certain constraints which the contents of a database
must conform.
Mapping Cardinalities
It expresses the number of entities to which another entity can be associated via a
relationship. For binary relationship sets between entity sets A and B, the mapping
cardinality must be one of the following:
One-to-One – An entity in A is associated with at most one entity in B, and an entity in
B is associated with at most one entity in A.
One-to-many -An entity in A is associated with any number in B. An entity in B is
associated with any number in A.
Many-to-many – Entities in A and B are associated with any number from each other.
Cardinality: It indicates that which type relationship the business rule follows is called
cardinality.
Connectivity: It specifies that which type of notation the entities are connected in both
sides that one side or many side.
5.2 DATA DICTIONARY
The logical characteristics of current systems data stores, including name,
description, aliases, contents, and organization, identifies processes where the data are
used and where immediate access to information required, Serves as the basis for
identifying database requirements during system design.

SRTS, Kadapa Page 13

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Uses of Data Dictionary

 To manage the details in large systems.
 To communicate a common meaning for all system elements.
 To Document the features of the system.
 To facilitate analysis of the details in order to evaluate characteristics and
determine where system changes should be made.
 To locate errors and omissions in the system.
5.3 UML DIAGRAMS
It is a language to specifying, visualizing and constructing the artifacts of
software system as well as for business models. UML was originally motivated by the
desire to standardize the disparate notational system and approaches to software design
developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in
1994-95. The UML notation is useful for graphically depicting Object Oriented Analysis
and Object Oriented Design modules. The unified modeling language is a standard
language for specifying, Visualizing, Constructing and documenting the software system
and its components. It is a graphical language that provides a vocabulary and set of
semantics and rules. The UML focuses on the conceptual and physical representation of
the system. It captures the decisions and understandings about systems that must be
constructed. It is used to understand, design, configure, maintain and control information
about the systems.
An Overview of UML
The Unified Modeling Language is a language for
 Visualizing.
 Specifying.
 Constructing.
 Documenting.
UML Models
User model view
 This view represents the system from the user’s perspective.
 The analysis representation describes a usage scenario from the end-users
perspective.

SRTS, Kadapa Page 14

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Structural model view

 In this model the data and functionality are arrived from inside the system.
 This model view models the static structures.
Behavioral model view
It represents the dynamic of Behavioral as parts of the system, depicting the
interactions of collection between various structural elements described in the user model
and structural model view.
Implementation model view
In this the structural and behavioral as parts of the system are represented as they
are to be built.
Environmental model view
In this the structural and Behavioral aspects of the environment in which the
system is to be implemented are represented. UML is specifically constructed through
two different domains they are
 UML Analysis modeling, this focuses on the user model and structural model
views of the system.
 UML design modeling, which focuses on the Bahavioural modeling,
implementation modeling and environmental model views.
A Conceptual model of UML
 The three major elements of UML are
 The UML’s basic building blocks.
 The rules that dictate how those building blocks may be put together.
 Some common mechanisms that apply throughout the UML.
Basic building blocks of the UML
The vocabulary of UML encompasses three kinds of building blocks
 Things.
 Relationships.
 Diagrams.

SRTS, Kadapa Page 15

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Things
Things are the abstractions that are first-class citizens in a model. Relationships
tie these things together. Diagrams group the interesting collection of things. There are
four kinds of things in the UML
Structural things
Behavioral things
Grouping things
Annotational things
Structural Things
Structural things are the nouns of the UML models. These are mostly static parts
of the model, representing elements that are either conceptual or physical. In all, there
are seven kinds of Structural things.
Use Case
Use case is a description of a set of sequence of actions that a system performs
that yields an observable result of value to a particular things in a model. Graphically,
Use Case is rendered as an ellipse with dashed lines, usually including only its name as
shown below.

Fig : Sample Use case diagram

Class
A class is a description of a set of objects that share the same attributes,
operations, relationships, and semantics. A class implements one or more interfaces.
Graphically a class is rendered as a rectangle, usually including its name, attributes and
operations, as shown below.
Windows
Origin
Size
Open()
Close()
Move()
Display()

Fig :Sample Class Diagram

SRTS, Kadapa Page 16
 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Interface
An interface is a collection of operations that specify a service of a class or
component. An interface describes the externally visible behaviour of element.
Graphically the interface is rendered as a circle together with its name.

Fig : Interface
Collaboration
Collaboration defines an interaction and is a society of roles and other elements
that work together to provide some cooperative behaviour that’s bigger than the sum of
all the elements. Graphically, collaboration is rendered as an ellipse with dashed lines,
usually including only its name as shown below.

Fig : Sample Collaboration Diagram

Component
Component is a physical and replaceable part of a system that conforms to and
provides the realization of a set of interfaces. Graphically, a component is rendered as a
rectangle with tabs, usually including only its name, as shown below.

Fig : Sample Component Diagram

Node
A Node is a physical element that exists at run time and represents a
computational resource, generally having at least some memory and often, processing
capability. Graphically, a node is rendered as a cube, usually including only its name, as
shown below.

SRTS, Kadapa Page 17

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Fig : Sample Node Diagram

Behavioral Things
Behavioral things are the dynamic parts of UML models. These are the verbs of a
model, representing behavior over time and space.
Interaction
An interaction is a behavior that comprises a set of messages exchanged among a
set of objects within a particular context to accomplish a specific purpose.

Display
Fig : Sample Interaction Diagram
State Machine
A state machine is a behavior that specifies the sequence of states an object or an
interaction goes through during its lifetime on response to events, together with its
responses to those events. Graphically, a state is rendered as rounded rectangle usually
including its name and its sub-states, if any, as shown below.

Fig : Sample State Machine

3. Grouping Things
Grouping things are the organizational parts of the UML models. These are the
boxes into which a model can be decomposed.
Package A package is a general-purpose mechanism for organizing elements into
groups.

SRTS, Kadapa Page 18

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Fig : Sample Package Diagram

Annotational Things
Annotational things are the explanatory parts of the UML models.
Notes
A note is simply a symbol for rendering constraints and comments attached to an
element or a collection of elements. Graphically a note is rendered as a rectangle with
dog-eared corner together, with a textual or graphical comment, as shown below.

Fig : Sample Note Diagram

Relationships in the UML
There are four kinds of relationships in the UML
 Dependency.
 Association.
 Generalization.
 Realization.
These relationships are the basic relational building blocks of the UML. You use
them to write well-formed models. Graphically dependency is rendered as a dashed line,
possibly directed, and occasionally including a label.
------------------->
Fig : Dependency
Second, an association is a structural relationship that describes a set of links, a
link being a connection among objects. Aggregation is a special kind of association,
representing a structural relationship between a whole and its parts. Graphically, an
association is rendered as a solid line, possibly directed, occasionally including a label,
and often containing other adornments, such as multiplicity and role names.
Employer Employee
Fig : Association

SRTS, Kadapa Page 19

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Third, a generalization is a specialization/generalization relationship in which

objects of the specialized element are substitutable for objects of the generalized element
(the parent). In this way, the child shares the structure and the behavior of the parent.
Graphically a generalization relationship is rendered as a solid line with a hollow
arrowhead pointing to the parent.

Fig : Generalization
Fourth, a realization is a semantic relationship between classifiers, wherein one
classifier specifies a contract that another classifier guarantees to carry out. You’ll
encounter realization relationships in two places between interfaces and the classes or
components that realize them and between use cases and the collaborations that realize
them.

Fig : Realization
Each UML diagram is designed to let developers and customers view a software
system from a different perspective and in varying degrees of abstraction. Use Case
Diagram displays the relationship among actors and use cases.
Class Diagram models class structure and contents using design elements such as classes,
packages and objects. It also displays relationships such as containment, inheritance,
associations and others.
Interaction Diagrams
Sequence Diagram displays the time sequence of the objects participating in the
interaction. This consists of the vertical dimension (time) and horizontal dimension
(different objects).
 Collaboration Diagram displays an interaction organized around the objects and
their links to one another. Numbers are used to show the sequence of messages.
 State Diagram displays the sequences of states that an object of an interaction
goes through during its life in response to received stimuli, together with its
responses and actions.
SRTS, Kadapa Page 20
 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Activity Diagram
Activity Diagram displays a special state diagram where most of the states are
action states and most of the transitions are triggered by completion of the actions in the
source states. This diagram focuses on flows driven by internal processing.
Physical Diagrams
 Component Diagram displays the high level packaged structure of the code itself.
Dependencies among components are shown, including source code components,
binary code components, and executable components. Some components exist at
compile time, at link time, at run times well as at more than one time.
 Deployment Diagram displays the configuration of run-time processing elements
and the software components, processes, and objects that live on them. Software
component instances represent run-time manifestations of code.
Diagrams in the UML

5.3.1 Use Case Diagram

Use-case diagram graphically depict system behavior. These diagrams present a
high level view of how the system is used as viewed from an outsider’s (actor’s)
perspective. A use-case diagram may depict all or some of the use cases of a system.
A use-case diagram can contain:
 Actors
 Use cases
Interaction or relationship between actor and use cases in the system including the
associations, dependencies, and generalizations. Use-case diagram can be used during
analysis to capture the system requirements and to understand how the system should
work. During the design phase, you can use use-case diagrams to specify the behavior of
the systems implemented.

Use Case Diagram

SRTS, Kadapa Page 21

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

FIG:Usecase Diagram

SRTS, Kadapa Page 22

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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.

FIG: Class Diagram

SRTS, Kadapa Page 23

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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.

Fig : Sequence Diagram

SRTS, Kadapa Page 24

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

ACTIVITY DIAGRAM

FIG : Activity Diagram

SRTS, Kadapa Page 25

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

6. IMPLEMENTATION AND RESULTS

6.1 TECHNOLOGY USED
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.

Fig 6.1.1 : Java Compiler Architecture

SRTS, Kadapa Page 26

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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.

Fig 6.1.2 : Platform Independent Architecture

The Java Platform
A platformis 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)
 TheJava 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

SRTS, Kadapa Page 27

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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, 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

SRTS, Kadapa Page 28

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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

SRTS, Kadapa Page 29

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

Fig 6.1.3 : JRE

6.2 METHODS OF IMPLEMENTATIONS
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.
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

SRTS, Kadapa Page 30

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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:
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.
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-bit addressing, allowing 1024 different hosts.

SRTS, Kadapa Page 31

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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".
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);

SRTS, Kadapa Page 32

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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
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.
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.
1.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.
2.Property Editors
The property editor mechanism in JFreeChart only handles a small subset of the
properties that can be set for charts. Extend (or reemployment) 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

SRTS, Kadapa Page 33

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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.
6.3 DATABASE
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.
1. 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.
2. 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.
3. 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.
4. 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.

SRTS, Kadapa Page 34

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

5. 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.
They are,
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO
Table: A database is a collection of data about a specific topic.
Views Of Table: We can work with a table in two types,
1. Design View
2. Datasheet View
Design View: To build or modify the structure of a table we work in the table design
view. We can specify what kind of data will be hold.
Datasheet View: To add, edit or analyses the data itself we work in tables datasheet view
mode.
Query: A query is a question that has to be asked the 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 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.

SRTS, Kadapa Page 35

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

7. SAMPLE CODE
Connect.jsp
<%@ page import="java.sql.*"%>
<%@ page import="java.util.*" %>
<%
Connection connection = null;
try {
Class.forName("com.mysql.jdbc.Driver");
connection =
DriverManager.getConnection("jdbc:mysql://localhost:3306/fdop","root","root");
String sql="";
}
catch(Exception e)
{
System.out.println(e);
}
%>
Result.jsp

<%@ include file="connect.jsp"%>

<%@ page import="org.bouncycastle.util.encoders.Base64" %>

<%

String iname="";
int i=0,count=0,rank=0;

SRTS, Kadapa Page 36

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

try
{

%><html>
<head>
<title>Products rank</title>
<script type="text/javascript" src="sources/jscharts.js"></script>
</head>
<body>
<div id="graph">Loading graph...</div>
<script type="text/javascript">
var myData=new Array();
var colors=[];

<%

String query1="select * from products ";

Statement st1=connection.createStatement();
ResultSet rs1=st1.executeQuery(query1);
while ( rs1.next() )
{

iname=rs1.getString(2);
rank=rs1.getInt(8);

SRTS, Kadapa Page 37

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

%>

myData["<%=i%>"]=["<%= iname%>",<%= rank%>];

<%

i++;}
%>

var myChart = new JSChart('graph', 'bar');

myChart.setDataArray(myData);
myChart.setBarColor('#FF9900');
myChart.setBarOpacity(0.8);
myChart.setSize(700,250);
myChart.setBarBorderColor('#D9EDF7');
myChart.setBarValues(true);
myChart.setTitleColor('#8C8383');
myChart.setAxisColor('#777E89');
myChart.setAxisValuesColor('#000000');
myChart.draw();

</script>

</body>
</html>
<%

SRTS, Kadapa Page 38

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

}
catch(Exception e)
{
e.printStackTrace();
}
%>
Authentication.jsp

<%@ include file="connect.jsp" %>

<%

try
{

String value=request.getParameter("value");

if(value.equals("adminlogin"))
{

String username=request.getParameter("userid");
String password=request.getParameter("pass");
String sql="SELECT * FROM admin where
name='"+username+"' and pass='"+password+"'";
Statement stmt = connection.createStatement();
ResultSet rs =stmt.executeQuery(sql);

SRTS, Kadapa Page 39

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

if(rs.next())
{
response.sendRedirect("AdminMain.jsp");
}
else
{
response.sendRedirect("AdminRe-
Login.jsp");

}
else if(value.equals("userlogin"))
{
String username=request.getParameter("userid");
String password=request.getParameter("pass");
String sql = "SELECT * FROM user where
username='"+username+"' and password='"+password+"' ";
Statement stmt = connection.createStatement();
ResultSet rs = stmt.executeQuery(sql);
if (rs.next()==true)
{

String sql1="SELECT *
FROM user where username='"+username+"' and status='Authorized' ";
Statement stmt1 =
connection.createStatement();

SRTS, Kadapa Page 40

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

ResultSet rs1
=stmt1.executeQuery(sql1);
if(rs1.next()==true)
{
int i = rs1.getInt(1);
application.setAttribute("uname", username);
response.sendRedirect("UserMain.jsp");
}
else
{
%>
<style type="text/css">
<!--
.style1 {
color: #FF0000;
font-weight: bold;
font-size: 18px;
}
.style2 {
color: #0000FF;
font-weight: bold;
font-size: 16px;
}
-->
</style>
<br/>
<p align="center" class="style1">You are not Authorized by the Admin, Please wait!!
</p>

SRTS, Kadapa Page 41

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

<div align="center"><br/>
<br/>
<a href="UserLogin.jsp" class="style2">Back</a>
<%
}
}
else
{
response.sendRedirect("UserRe-Login.jsp");
}
}
else if(value.equals("userstatus"))
{
int id=Integer.parseInt(request.getParameter("id"));
String sql1="update user set status='Authorized' where id='"+id+"'";
Statement stmt1 = connection.createStatement();
int k =stmt1.executeUpdate(sql1);
if(k>0)
{
response.sendRedirect("A_AuthorizeUsers.jsp");
}
else
{
%>
<style type="text/css">
<!--
.style1 {

SRTS, Kadapa Page 42

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

color: #FF0000;
font-weight: bold;
font-size: 18px;
}
.style2 {
color: #0000FF;
font-weight: bold;
font-size: 16px;
}
-->
</style>
<br/>
<p align="center" class="style1">Permision Not Granted..Please Try Again..</p>
<div align="center"><br/>
<br/>
<a href="A_AuthorizeUsers.jsp" class="style2">Back</a>
<%
} }
else
{}
}
catch(Exception e)
{
out.print(e);
}
%>

SRTS, Kadapa Page 43

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

8. TESTING
Testing is a process, which reveals errors in the program. It is the major quality
measure employed during software development. During software development, during
testing, the program is executed with a set of test cases and the output of the program for
the test cases is evaluated to determine if the program is performing as it is expected to
perform.

8.1 Testing Methodologies

In order to make sure that the system does not have errors, the different levels
of testing strategies to that are applied to at differing phases of software development.

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.

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.

Functional test
Functional tests provide systematic demonstrations that functions tested are

SRTS, Kadapa Page 44

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

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.

Black Box Testing

In this strategy some test cases are generated as input conditions that fully execute
all functional requirements for the program. This testing has been uses to find errors in
the following categories:

 Incorrect or missing functions

 Interface errors
 Errors in data structure or external database access
 Performance errors
 Initialization and termination errors.

SRTS, Kadapa Page 45

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

In this testing only the output is checked for correctness. The logical flow of the data
is not checked.

White Box Testing

In this the test cases are generated on the logic of each module by drawing flow
graphs of that module and logical decisions are tested on all the cases. It has been uses to
generate the test cases in the following cases:

 Guarantee that all independent paths have been executed.

 Execute all logical decisions on their true and false Sides.
 Execute all loops at their boundaries and within their operational bounds
 Execute internal data structures to ensure their validity.

Integrating Testing

Integration testing ensures that software and subsystems work together a whole.
It tests the interface of all the modules to make sure that the modules behave properly
when integrated together.

System Testing

Here the entire software system is tested. The reference document for this process
is the requirements document, and the goal is to see if software meets its requirements.
Here entire ‘Cybernetic Protectors Application’ has been tested against requirements of
project and it is checked whether all requirements of project have been satisfied or not.

Acceptance Testing

Acceptance Test is performed with realistic data of the client to demonstrate that
the software is working satisfactorily. Testing here is focused on external behavior of the
system; the internal logic of program is not emphasized. In this project ‘Cybernetic
Protectors Application’ I have collected some data and tested whether project is working
correctly or not. Test cases should be selected so that the largest number of attributes of
an equivalence class is exercised at once. The testing phase is an important part of
software development. It is the process of finding errors and missing operations and also

SRTS, Kadapa Page 46

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

a complete verification to determine whether the objectives are met and the user
requirements are satisfied.

Test Approach
Testing can be done in two ways:

 Bottom up approach
 Top down approach
Bottom Up Approach

Testing can be performed starting from smallest and lowest level modules and
proceeding one at a time. For each module in bottom up testing a short program executes
the module and provides the needed data so that the module is asked to perform the way
it will when embedded with in the larger system.

Top down Approach

This type of testing starts from upper level modules. Since the detailed activities
usually performed in the lower level routines are not provided stubs are written. A stub is
a module shell called by upper level module and that when reached properly will return a
message to the calling module indicating that proper interaction occurred. No attempt is
made to verify the correctness of the lower level module.
Validation

The system has been tested and implemented successfully and thus ensured that all
the requirements as listed in the software requirements specification are completely
fulfilled. In case of erroneous input corresponding error messages are displayed.

SRTS, Kadapa Page 47

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

TEST CASES

EXPECTED
S. No. TEST CASES INPUT ACTUAL RESULT STATUS
RESULT

Registration
User User gets
1 Enter all fields Pass
Registration registered
is successful

Registration is
if user miss User not
2 User Fail
any field registered
Registration un successful

Admin home
Give the user Admin home
page should
3 Admin Login name and Page has been Pass
password opened
be opened

Admin page
Give Username Admin page has
4 Admin Login should be Pass
and password been opened
opened

Upload Details
Enter All the Details Should
5 Product Uploaded Pass
Details be Upload
Details Success Fully

Table 8.3.1: Test Case Results

SRTS, Kadapa Page 48

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

9. SCREENS

SRTS, Kadapa Page 49

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 50

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 51

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 52

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 53

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 54

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 55

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 56

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 57

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 58

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 59

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

SRTS, Kadapa Page 60

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

10. CONCLUSION

In this paper, we propose FAHGT, a novel heterogeneous graph neural network

for fraudulent user detection in online review systems. To handle inconsistent features,
we adopt heterogeneous mutual attention for automatic meta path construction. To detect
camouflage behaviors, we design the label aware scoring to filter noisy neighbors. Two
neural modules are combined in a unified manner called “score head mechanism” and
both contribute to edge weight computation in final feature aggregation. Experiment
results on real-world business datasets validate the excellent effect on fraud detection of
FAHGT. The hyper-parameter sensitivity and visual analysis further show the stability
and efficiency of our model. In summary, FAHGT is capable of alleviating inconsistency
and discover camouflage and thus achieves state-of-art performance in most scenarios.

SRTS, Kadapa Page 61

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

11. FUTURE ENHANCEMENTS

It is not possible to develop a system that makes all the requirements of the user. User
requirements keep changing as the system is being used. Some of the future enhancements that
can be done to this system are
In the future, we plan to extend our model in handing dynamic graphs data and
incorporate fraud detection into other areas, such as robust item recommendation in E-
commerce or loan default prediction in financial services.

SRTS, Kadapa Page 62

 Fraud Detection in Online Product Review Systems via Heterogeneous Graph Transformer

12. BIBLIOGRAPHY
[1] V. S. Tseng, J. Ying, C. Huang, Y. Kao, and K. Chen, “Fraudetector: A graph-
mining-based framework for fraudulent phone call detection,” in Proceedings of the 21th
ACM SIGKDD International Conference on Knowledge Discovery and Data Mining,
Sydney, NSW, Australia, August 10-13, 2015, L. Cao, C. Zhang, T. Joachims, G. I.
Webb, D. D. Margineantu, and G. Williams, Eds. ACM, 2015, pp. 2157–2166. [Online].
Available: https://doi.org/10.1145/2783258.2788623
[2] J. Wang, R. Wen, and C. Wu, “Fdgars: Fraudster detection via graph convolutional
networks in online app review system,” in WWW Workshops,2019.
[3] A. Li, Z. Qin, R. Liu, Y. Yang, and D. Li, “Spam review detection with graph
convolutional networks,” in CIKM, 2019.
[4] Z. Liu, Y. Dou, P. S. Yu, Y. Deng, and H. Peng, “Alleviating the inconsistency
problem of applying graph neural network to fraud detection,” in SIGIR, 2020.
[5] Y. Dou, Z. Liu, L. Sun, Y. Deng, H. Peng, and P. S. Yu, “Enhancing graph
neural network-based fraud detectors against camouflaged fraudsters,” in CIKM, 2020.
[6] R. Wen, J. Wang, C. Wu, and J. Xiong, “Asa: Adversary situation awareness via
heterogeneous graph convolutional networks,” in WWW Workshops, 2020.
[7] Y. Zhang, Y. Fan, Y. Ye, L. Zhao, and C. Shi, “Key player identification in
underground forums over attributed heterogeneous information network embedding
framework,” in CIKM, 2019.
[8] D. Wang, J. Lin, P. Cui, Q. Jia, Z. Wang, Y. Fang, Q. Yu, and J. Zhou, “A semi-
supervised graph attentive network for fraud detection,” in ICDM, 2019.
[9] Z. Liu, C. Chen, X. Yang, J. Zhou, X. Li, and L. Song, “Heterogeneous graph neural
networks for malicious account detection,” in CIKM, 2018.
[10] Y. Dou, G. Ma, P. S. Yu, and S. Xie, “Robust spammer detection by nash
reinforcement learning,” in KDD, 2020.

SRTS, Kadapa Page 63