“FRAUD DETECTION IN ONLINE

MARKETPLACES”

A Project Report

Submitted in partial fulfillment of the requirements for the

award of degree of

MASTER OF BUSINESS ADMINISTRATION

(BUSINESS ANALYTICS)

Submitted By
Ashish Kumar Singh
Registration Number: 322100098

Submitted to
LOVELY PROFESSIONAL UNIVERSITY PHAGWARA, PUNJAB

Centre for Distance and Online Education

LOVELY PROFESSIONAL UNIVERSITY
PHAGWARA, PUNJAB

2022-2024

1
 Student’s Declaration

To whom so ever it may concern

I, Ashish Kumar Singh, Reg. No. 322100098, hereby declare that the work done by

me on “FRAUD DETECTION IN ONLINE MARKETPLACES” is a record of

original work for the partial fulfilment of the requirements for the award of the degree,

MBA (Business Analytics).

Ashish Kumar Singh (322100098)

Dated:05/08/2024

2
 ACKNOWLEDGEMENT

Every work constitutes great deal of assistance and guidance from the people concerned

and this particular project is of no exception.

A project of the nature is surely a result of tremendous support, guidance,

encouragement and help.

Wish to place on record my sincere gratitude to Centre for Distance and Online

Education, Lovely Professional University, Punjab, for giving me opportunity to complete

my project.

Also, wish to acknowledge enthusiastic encouragement and support extended to me by

my family members. At last, I would like to thank all the faculty of business management to

help me completing this project.

I’m also thankful to my friends who provided me their constant support and assistance.

Place: Bihar
Date:05/08/2024
Ashish Kumar Singh (322100098)

3
 ABSTRACT

Fraud detection in online marketplaces has become a critical area of research and
application due to the exponential growth of e-commerce and digital transactions. This
paper explores the development and implementation of robust fraud detection
mechanisms to ensure secure and trustworthy online transactions. Utilizing a
combination of machine learning algorithms, data mining techniques, and behavioral
analysis, this study aims to identify and mitigate fraudulent activities such as fake
reviews, payment fraud, and identity theft.

The research begins with a comprehensive review of existing fraud detection methods,
highlighting their strengths and limitations. Following this, a novel hybrid model is
proposed, integrating supervised and unsupervised learning techniques to enhance the
accuracy and efficiency of fraud detection. Supervised learning algorithms, such as
decision trees and support vector machines, are employed to classify known fraudulent
patterns, while unsupervised methods, including clustering and anomaly detection, are
used to identify previously unseen fraud schemes.

The proposed system leverages large datasets from various online marketplaces,
ensuring a diverse range of transaction types and user behaviors are considered. Feature
engineering plays a crucial role in the model, with emphasis on extracting relevant
attributes that signify fraudulent activity, such as transaction times, geographic
inconsistencies, and unusual spending patterns.

4
 Table of Contents

S. No. Title Page no

1 Declaration by Student 2

3 Acknowledgement 3

4 Abstract 4
5 List of Figures 6
6 List of Tables 7-8

8 List of Abbreviations 9
9 Chapter-1 Introduction 10-18

10 System Specification 19-25

11 Output Design 26-27

a) Form Design
b) Code Design
c) Data base Design
12 Data Flow Diagram 28-32
13 System Flow Diagram 33-34
14 System Testing 35-43
a) Unit Testing
b) Integration Testing
c) Validation Testing
White Box Testing
15 Result And Discussion 44-45
16 Conclusion And Future Enhancements 46

17 Appendix 47-54
18 Screen Shots 55-59
19 Annexures 60-61
 References

5
 LIST OF FIGURES

Figure No. Title Page No.

1 Framework Of Ranking Fraud Detection System for 12

Mobile Apps

2 System Flow Diagram 33

3 Sequence Diagram 34

4 Class Diagram 35

Home Screen
5 55

User Registration
6 56

Global Anomaly Login

7 56

Global Anomaly Home

8 57

6
 LIST OF SCHEMES

Fraud detection in online marketplaces involves various schemes and techniques

designed to identify and mitigate fraudulent activities. Here is a list of common
schemes and methods used for fraud detection:

1. Machine Learning Models

 Supervised Learning: Utilizes labelled datasets to train models to recognize patterns

associated with fraudulent activities.

 Unsupervised Learning: Identifies anomalies without prior knowledge of what

constitutes fraud, using techniques like clustering and anomaly detection.

 Reinforcement Learning: Continuously learns and adapts to new fraud patterns by

receiving feedback from its performance.

2. Rule-Based Systems

 Heuristics: Predefined rules based on known fraud patterns (e.g., high-frequency

transactions, mismatched shipping and billing addresses).

 Scoring Systems: Assigns scores to transactions based on various risk factors,

flagging high-score transactions for further review.

3. Behavioral Analysis

 User Behavior Analytics (UBA): Monitors and analyzes user activities to detect
deviations from normal behavior.

 Session Analysis: Tracks user interactions during a session to identify suspicious

behavior (e.g., rapid browsing and purchasing).

4. Data Analytics

 Big Data Analysis: Processes large volumes of data to identify fraud trends and
correlations.

7
  Real-Time Analytics: Provides immediate insights and alerts for potentially
fraudulent activities.

5. Identity Verification

 Multi-Factor Authentication (MFA): Requires multiple forms of verification to

ensure the identity of users.

 KYC (Know Your Customer) Procedures: Involves detailed verification of user

identities before allowing transactions.

6. Blockchain Technology

 Immutable Ledger: Provides a secure and transparent way to record transactions,

reducing the risk of tampering.

 Smart Contracts: Automatically enforce terms of agreements, ensuring compliance

and reducing fraud.

7. Collaborative Filtering

 Peer Reviews and Ratings: Uses feedback from other users to identify fraudulent
sellers or buyers.

 Shared Blacklists: Collaborates with other platforms to maintain a list of known

fraudsters.

8. Artificial Intelligence (AI) and Neural Networks

 Deep Learning: Utilizes complex neural networks to detect subtle patterns of fraud
that simpler models might miss.

 Natural Language Processing (NLP): Analyzes text data, such as customer reviews
and messages, to detect fraudulent content.

8
 LIST OF ABBREVIATIONS

Here's a list of abbreviations commonly used in the context of fraud detection in online
marketplaces:

1. AI - Artificial Intelligence

2. AML - Anti-Money Laundering

3. API - Application Programming Interface

4. CDD - Customer Due Diligence

5. CNP - Card Not Present

6. CVV - Card Verification Value

7. DDoS - Distributed Denial of Service

8. E-commerce - Electronic Commerce

9. FDS - Fraud Detection System

10. FF - Fraud Filtering

11. FRA - Fraud Risk Assessment

12. KYC - Know Your Customer

13. ML - Machine Learning

14. OTP - One-Time Password

15. PCI DSS - Payment Card Industry Data Security Standard

9
 INTRODUCTION

The Mobile App is a very popular and well-known concept due to the rapid
advancement in the mobile technology. Due to the large number of mobile Apps, ranking
fraud is the key challenge in front of the mobile App market. There are millions of apps
are available in market for the application of mobile users. However, all the mobile users
first prefer high ranked apps when downloading it. To download application smart phone
user has to visit play store such as Google Play Store, Apples store etc. When user visit
play store then he is able to see the various application lists. This list is built on the basis
of promotion or advertisement. User doesn’t have knowledge about the application (i.e.
which applications are useful or useless). So user looks at the list and downloads the
applications. But sometimes it happens that the downloaded application won’t work or not
useful. That means it is fraud in mobile application list. To avoid this fraud, we are making
application in which we are going to list the applications. In this paper, we provide a brief
view of ranking fraud and propose a ranking fraud detection system for mobile Apps.
Specifically, we first propose to accurately locate the ranking fraud by mining the active
periods by using mining leading session algorithm. Furthermore, we investigate three
types of evidences, i.e., ranking based evidences, rating based evidences and review based
evidences, by studying historical records. We used an optimal aggregation method to
integrate all the evidences for fraud detection. Finally, we evaluate the proposed system
with real-world App data collected from the Google App Store for a long time period. In
the experiments, we validate the effectiveness of the proposed system, and show the
scalability of the detection algorithm as well as some regularity of ranking fraud activities.

1.2 PROJECT DESCRIPTION

The quantity of mobile Apps has developed at an amazing rate in the course of recent
years. For instances, the growth of apps were increased by 1.6 million at Apple's App store
and Google Play.To increase the development of mobile Apps, many App stores launched
daily App leaderboards, which demonstrate the chart rankings of most popular Apps.
Indeed, the App leaderboard is one of the most important ways for promoting mobile
Apps. A higher rank on the leaderboard usually leads to a huge number of downloads and
million dollars in revenue. Therefore, App developers tend to explore various ways such
as advertising campaigns to promote their Apps in order to have their Apps ranked as high

10
as possible in such App leaderboards. However, as a recent trend, instead of relying on
traditional marketing solutions, shady App developers resort to some fraudulent means to
deliberately boost their Apps and eventually manipulate the chart rankings on an App
store. This is usually implemented by using so called botfarms or human water armies to
inflate the App downloads, ratings and reviews in a very short time.

There are some related works, for example, we positioning spam recognition, online
survey spam identification and portable App suggestion, but the issue of distinguishing
positioning misrepresentation for mobile Apps is till under-investigated. The problem of
detecting ranking fraud for mobile Apps is still underexplored. Toovercome these
essentials, in this paper, we build a system for positioning misrepresentation discovery
framework for portable apps that is the model for detecting ranking fraud in mobile apps.
For this, we have to identify several important challenges.

First, fraud is happen any time during the whole life cycle of app, so the identification of
the exact time of fraud is needed. Second, due to the huge number of mobile Apps, it is
difficult to manually label ranking fraud for each App, so it is important to automatically
detect fraud without using any basic information. Mobile Apps are not always ranked high
in the leaderboard, but only in some leading events ranking that is fraud usually happens
in leading sessions.

Therefore, main target is to detect ranking fraud of mobile Apps within leading sessions.
First propose an effective algorithm to identify the leading sessions of each App based on
its historical ranking records. Then, with the analysis of Apps’ ranking behaviors, find out
the fraudulent Apps often have different ranking patterns in each leading session
compared with normal Apps. Thus, some fraud evidences are characterized from Apps’
historical ranking records. Then three functions are developed to extract such ranking
based fraud evidences. Therefore, further two types of fraud evidences are proposed based
on Apps’ rating and review history, which reflect some anomaly patterns from Apps’
historical rating and review records. In addition, to integrate these three types of
evidences, an unsupervised evidence-aggregation method is developed which is used for
evaluating the credibility of leading sessions from mobile Apps.

11
 1.3 OVERVIEW OF THE PROJECT

With the increase in the number of web Apps, to detect the fraud Apps, this project
proposes a simple and effective system. Fig.1 shows the Framework of Fraud ranking
discovery in mobile app

Fig.1 Framework of Ranking Fraud Detection System for Mobile Apps

Indeed, careful observation reveals that mobile Apps are not always ranked high in the
leaderboard, but only in some leading events, which form different leading sessions. In
other words, ranking fraud usually happens in these leading sessions. Therefore,
detecting ranking fraud of mobile Apps is actually to detect ranking fraud within
leading sessions of mobile Apps. Specifically, this system first proposes a simple yet
effective algorithm to identify the leading sessions of each App based on its historical
ranking records. Then, with the analysis of Apps’ ranking behaviors, find that the
fraudulent Apps often have different ranking patterns in each leading session compared
with normal Apps. Thus, it characterizes some fraud evidences from Apps’ historical
ranking records, and develop three functions to extract such ranking based fraud
evidences. Nonetheless, the ranking based evidences can be affected by App
developers’ reputation and some legitimate marketing campaigns, such as “limited-time
discount”. As a result, it is not sufficient to only use ranking based evidences.
Therefore, it further proposes two types of fraud evidences based on Apps’ rating and

12
review history, which reflect some anomaly patterns from Apps’ historical rating and
review records. In addition, it develops an unsupervised evidence-aggregation method
to integrate these three types of evidences for evaluating the credibility of leading
sessions from mobile Apps.

It is worth noting that all the evidences are extracted by modeling Apps’ ranking, rating
and review behaviors through statistical hypotheses tests. The proposed framework is
scalable and can be extended with other domain generated evidences for ranking fraud
detection. Experimental results show the effectiveness of the proposed system, the
scalability of the detection algorithm as well as some regularity of ranking fraud
activities.

1.4 OBJECTIVES

The mobile industry is developing rapidly; therefore, the numbers of mobile

applications are increasing day by day in the market. As there are many apps available
in market users are in fuzzy state while downloading the apps for their use. Different
App stores like Google play store and Apple store launched their leader board on daily
basis to inspire the users to download most popular applications by observing the
ranking of applications. In fact to advertise a particular mobile Apps, leader board of
apps is the most important way in the market. An app which is at the top on the leader
board leads to large number of downloads and it will gain maximum profit. In order to
have their Apps ranked as high as possible, app developers promote their apps using
various ways such as advertising, offers etc. Such applications damage to phone and
also may cause data thefts. Hence such applications must be identified, so that they will
be identifiable for play store users. So we are proposing an android application which
will process the information, comments and three reviews of the application with
natural language processing to give results. So it will be easier to decide fraud
application. The main objectives are,

 To rank fraud for mobile application.

 To improve the fraud detection efficiency.

13
 1.5 MODULES

This system consists of four modules described as follows:

1. Rating Based Evidences

2. Review Based Evidences

3. Ranking Based Evidences

4. Evidence Aggregation

1.5.1 RATING BASED EVIDENCES

After downloading app users generally rate the app. The rating given by the user is one
of the most important factors for the popularity of the app. An app having higher rating
always attracts more number of users to download it and naturally it can also be ranked
higher in the chart rankings. Thus, in ranking fraud of apps, rating based evidences is
also an important feature so they are needs to be considered.

Pre-processing of ratings

General ratings are between one to five, in this module it will consider, the rating which
are less than or equal to three are considered as negative ratings and rating above three
are considered as positive ratings

Rating Score Calculation

Generally, ratings are between one to five, in this module we compute the average rating
of particular app and compare it with threshold. The rating which are less than or equal
to three are considered as negative ratings and rating above three are considered as
positive ratings. Finally, the output is in the form of zeros and ones i.e. negative rating
gives zero as an output while positive rating gives one as an output.

1.5.2 REVIEW BASED EVIDENCES

Along with rating users are allowed to write their reviews about the app. Such reviews
are showing the personalized experiences of usage for particular mobile Apps. The
review given by the user is one of the most important factors for the popularity of the

14
app. As the reviews are given in natural language so pre-processing of reviews and then
sentiment analysis on pre-processed reviews is performed. The system will find
sentiment of the review which can be positive or negative. Positive review adds plus one
to positive score, if negative it will add one to negative score. In this way it will find out
score of each of the reviews and determine whether app is fraud or not on the basis of
review based evidences. This module contains two subparts given below:

Pre-processing Reviews

This phase consists of following steps:

1. Tokenization: Tokenization is the process of breaking a stream of text into

words, phrases, symbols or meaningful elements called as tokens. The list of tokens
becomes input for further processing.

2. Stop word removal: Stop words are commonly used words such as: a, the, and,
for, from, is, in and many more.

3. Stemming: Stemming algorithm is used to find base word. Porter Stemmer

Algorithm is used to find base words.

Porter Stemmer algorithm: Porter Stemmer algorithm is a process for removing

suffixes from words in English.

Example: A stemming algorithm reduces the words: stems, stemmer, stemming,

stemmed as based on “stem”.

Sentiment Analysis

After pre-processing of reviews system find out the sentiments of the reviews.
It will classify the review as positive or negative. The system will find sentiment of
the review which can be positive or negative. Positive review adds plus one to
positive score, if negative it will add one to negative score. In this way it will find
out score of each of the reviews and determine whether app is fraud or not on the
basis of review-based evidences.

15
 1.5.3 RANKING BASED EVIDENCES

Finding app ranking behavior

In this phase, we detect Apps’ ranking behavior, by finding three phases of ranking,
namely, rising phase, maintaining phase and recession phase. If the apps ranking
reach to peak position in the leaderboard that phase is called as rising phase and
maintaining same peak position for specific time period is called as maintaining
phase. If the ranking of the app decreases rapidly in the leading event then it is called
as recession phase.

1.5.4 EVIDENCE AGGREGATION

After three types of fraud evidences are extracted, the next work is to combine
them for ranking fraud detection. Every evidence is given a Boolean weight as 0 or 1
where 0 indicate fraud nature and 1 indicate no fraud nature.

1. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

In the literature, while there are some related work, such as web
ranking spam detection, online review spam detection and mobile App
recommendation, the problem of detecting ranking fraud for mobile Apps is still
under-explored. Generally speaking, the related works of this study can be grouped
into three categories. The first category is about web ranking spam detection. The
second category is focused on detecting online review spam. Finally, the third
category includes the studies on mobile App recommendation

2.1.1 DISADVANTAGES

 Although some of the existing approaches can be used for anomaly detection

from historical rating and review records, they are not able to extract fraud evidences
for a given time period (i.e., leading session).

 Cannot able to detect ranking fraud happened in Apps’ historical leading sessions

16
 There is no existing benchmark to decide which leading sessions or Apps really

contain ranking fraud.

2.2 PROPOSED SYSTEM

In today’s era, due to rapid development in the mobile technology and mobile
devices, the applications i.e. mobile apps are being very interesting and popular
concept. As there is large number of mobile Apps, ranking fraud is the challenging
factor in front of the mobile App market. Ranking fraud is the term used for
referring to fraudulent or suspicious activities having the intention of boosting up the
Apps in the popularity list. In fact, App developers are using tricky means frequently
for increasing their Apps sales. The main aim is to develop such system that find
ranking, rating and review behaviours for investigating review based evidences,
rating based evidences and ranking based evidences and then aggregation based on
optimization to combine all the evidences for detection of fraud.

2.2.1 Advantages

 The proposed framework is scalable and can be extended with other domain

generated evidences for ranking fraud detection.

 Experimental results show the effectiveness of the proposed system, the

scalability of the detection algorithm as well as some regularity of ranking fraud

activities.

 To the best of our knowledge, there is no existing benchmark to decide which

leading sessions or Apps really contain ranking fraud. Thus, we develop four
intuitive baselines and invite five human evaluators to validate.

2.3 FEASIBLITY ANALYSIS

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.

17
Three key considerations involved in the feasibility analysis are

 Economic Feasibility
 Technical Feasibility
 Social Feasibility

2.3.1 ECONOMICAL FEASIBILITY

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

2.3.2 TECHNICAL FEASIBILITY

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on
the available technical resources. This will lead to high demands on the available
technical resources. This will lead to high demands being placed on the client. The
developed system must have a modest requirement, as only minimal or null changes
are required for implementing this system.

2.3.3 SOCIAL FEASIBILITY

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

18
 3. SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENTS

RAM : 1 GB

Hard Disk : 40GB @ 5400 RPM

Processor : Pentium 4 (1.6 GHZ or above)

Mouse : Logical Mouse

Keyboard : Logical Multimedia Keyboard

3.2 SOFTWARE REQUIREMENTS

Package : Visual Studio Express Edition 2008,

Operating System : Windows SP2, Vista, Windows 7

Database : Microsoft SQL Server 2005

Language : C#.NET

Documentation : Microsoft Office 2007

3.3 ABOUT THE SOFTWARE

In this project.Net Framework is used as Frontend tool.Net is one of the most

beautiful and recently more popular front-end tools. C# .Net and ASP.Net are used in
this project.

An interface for users is build using ASP .Net. SQL server 2008 is used as a backend
tool. Additional technologies used is web services and ADO .Net. Then it comes the
turn of operating System. Any .Net framework Compatible software platform can be
used.

19
Introduction to Dot 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).

The .Net Framework

The .NET Framework has two main parts:

 The Common Language Runtime (CLR).

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

Managed Code

The code that targets .NET which contains certain extra Information -
“metadata” - to describe itself. While both managed and unmanaged code can run in

20
 the runtime, only managed code contains the information that allows the CLR to
guarantee, for instance, safe execution and interoperability.

Managed Data

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 the user’re 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.

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, the runtime
also ensures that code doesn’t attempt to access memory that hasn’t been allocated to it.

Common Language Specification

The CLR provides built-in support for language interoperability. To ensure that the
user 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.

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

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

Constructors and Destructors

Constructors are used to initialize objects, whereas destructors are used to destroy them.
In other words, destructors are used to release the resources allocated to the object. In
C#.NET the sub finalize procedure is available. The sub finalize procedure is used to
complete the tasks that must be performed when an object is destroyed. The sub finalize
procedure is called automatically when an object is destroyed. In addition, the sub
finalize procedure can be called only from the class it belongs to or from derived
classes.

Garbage Collection

Garbage Collection is another new feature in C#.NET. The .NET Framework

monitors allocated resources, such as objects and variables. In addition, the .NET
Framework automatically releases memory for reuse by destroying objects that are no
longer in use.

NET, the garbage collector checks for the objects that are not currently in use by
applications. When the garbage collector comes across an object that is marked for
garbage collection, it releases the memory occupied by the object.

Overloading

Overloading is another feature in C#. Overloading enables the user to define multiple
procedures with the same name, where each procedure has a different set of arguments.
Besides using overloading for procedures, the user can use it for constructors and
properties in a class.

22
 Structured Exception Handling

NET supports structured handling, which enables the user to detect and
remove errors at runtime. In C#.NET, the user needs to use Try…Catch…Finally
statements to create exception handlers. Using Try…Catch…Finally statements, the
user can create robust and effective exception handlers to improve the performance of
this application.

Features of C#. Net

C#.NET is also compliant with CLS (Common Language Specification) and supports
structured exception handling. CLS is set of rules and constructs that are supported by
the CLR (Common Language Runtime). CLR is the runtime environment provided by
the .NET Framework; it manages the execution of the code and also makes the
development process easier by providing services.

C#.NET is a CLS-compliant language. Any objects, classes, or components that created

in C#.NET can be used in any other CLS-compliant language. In addition, the user can
use objects, classes, and components created in other CLS-compliant languages in
C#.NET. The use of CLS ensures complete interoperability among applications,
regardless of the languages used to create the application.

Conclusion of .NET

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. To provide a
consistent object-oriented programming environment whether object codes is stored
and executed locally on Internet-distributed, or executed remotely. To provide a code-
execution environment to minimizes software deployment and guarantees safe
execution of code and eliminates the performance problems. There are different types
of application, such as Windows-based applications and Web-based applications.

23
 BACK END

FEATURES OF SQL-SERVER

The OLAP Services feature available in SQL Server. The term OLAP Services has been
replaced with the term Analysis Services. Analysis Services also includes a new data
mining component. The term repository is used only in reference to the repository engine
within Meta Data Services.

SQL-SERVER database consists of six type of objects they are

 TABLE
 QUERY
 FORM
 REPORT

TABLE

A database table is similar in appearance to a spreadsheet, in that data is stored in rows

and columns. As a result, it is usually quite easy to import a spreadsheet into a database
table. The main difference between storing your data in a spreadsheet and storing it in a
database is in how the data is organized. Data about products will be stored in its own
table, and data about branch offices will be stored in another table. This process is
called normalization.

VIEWS OF TABLE

Table in two types,

 Design View
 Datasheet View

DESIGN VIEW

To build or modify the structure of a table the user work in the table design view. I can
specify what kind of data will be hold.

24
 DATASHEET VIEW

To add, edit or analyses the data itself the user work in tables datasheet view mode.

QUERY

Queries are the real workhorses in a database, and can perform many different
functions. Their most common function is to retrieve specific data from the tables. The
data the user wants to see is usually spread across several tables, and queries allow the
user to view it in a single datasheet. Also, since the user usually don't want to see all the
records at once, queries let the user add criteria to "filter" the data down to just the
records the user want. Queries often serve as the record source for forms and reports.

FORMS

Forms are sometimes referred to as "data entry screens." They are the interfaces the
user use to work with your data, and they often contain command buttons that perform
various commands. The user can create a database without using forms by simply
editing your data in the table datasheets. However, most database users prefer to use
forms for viewing, entering, and editing data in the tables.

REPORTS

Reports are what the user use to summarize and present data in the tables. Each report
can be formatted to present the information in the most readable way possible. A
report can be run at any time, and will always reflect the current data in the database.
Reports are generally formatted to be printed out, but they can also be viewed on the
screen, exported to another program, or sent as e-mail message.

4. SYSTEM DESIGN

4.1 INPUT DESIGN

Input design is the process of converting user inputs into computer-based format. The
project requires a set of information from the user to prepare a report. In order to
prepare a report, when organized input data are needed.

25
In the system design phase, the diagram identifies logical data flow, data stores and
destination. Input data is collected and organised into groups of similar data. The goal
behind designing input data is to make the data entry easy and make it free from logical
errors. The input entry to all type of clients is the user name and password only. If they
are valid the client is allowed to enter into the software.

Objectives

 To produce a cost-effective method of input.

 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understandable.
 The input design is actually designing of screens
 Registration form for new client.
 Form for login file.
 Form for displaying connected clients.
 Form for displaying result.

4.2 OUTPUT DESIGN

Outputs are the most important and direct source of information to the user and to
management. Efficient and eligible output design should improve the system’s
relationship with the user and help in decision making. Output Design generally deals
with the results generated from stored or calculated values.

Reports are displayed either as screen preview or printed form. Most end users will
not actually operate the information systems or enter data through workstations, but
they will use the output from the system.

Form Design

The cost of collecting raw data and cost of distributing processed information are
major costs of a system. So careful forms design can affect the cost effectiveness of the
system. Well-designed forms can increase efficiency; improve workflow and lower
system costs.

26
 Code Design

When a large volume of data is being handled, it is important that items be identified,
sorted or selected easily. To accomplish this, each data item must have a unique
identification and must be relates to other items of data of the same type. Thus, codes
are used to identify item uniquely.

A Code is group of characters or numbers used to identify an item or data. While

identification is the main function of a code, it may also show relationships between
items of data. A good coding scheme should be expandable, precise, concise,
convenient and meaningful. Based on above idea, codes are used which contain
alphanumeric characters.

4.3 DATABASE DESIGN

A general theme begins a database is to handle information as an integrated whole. A

database is a collection of inter-related data stored with minimum redundancy to server
many users quickly and efficiently.

The general objective is to make information access easy, quick, expensive and flexible
for the user. In database design several specific objectives are consider:

Control Redundancy:

Redundant data occupies space and therefore, is wasteful. If versions of the same data
are in different phase of updating, a system often gives conflicting information. A
unique aspect of database design is storing data only once, which controls redundancy
and improves system performance.

Data Independence:

An important database objective is changing hardware and storage procedures for

adding raw new data without having to rewrite application programs.

Accuracy and Integrity:

The accuracy and database ensure the data quality content remain constant. Integrity
controls detect data inaccuracy where occur.

27
 Privacy and Security:

For the data to remain private, security measures must be taken to an unauthorized
access. Database security means that data are protected from various forms of
destructions. Uses must be positively identifying and actions monitored. Managing the
database require a Database Administrator (DBA) whose key functions are to be
managing data activities, The database structure and the DBMS. In addition, a
managerial background the DBA needs a technical knowledge to deal with database
designer.

4.4 DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical system model that shows all of the
main requirements for an information system in one diagram: inputs and outputs,
processes, and data storage. A DFD describes what data flows rather than how it is
processed. Everyone working on a development project can see all aspects of the
system working together at once with DFD. That is one reason for its popularity. The
DFD is also easy to read because it is graphical model. The DFD is mainly used during
problem analysis. End Users, management, and all information systems workers
typically can read and interpret the DFD with minimal training.

Level 0

User
User Login Outp
ut

User
Authenticati
on

28
Level1

User login Upload

feedback

Database
Optimize
records

Level 2

Rating based
evidence
Apps with
Ranking based Optimization
Historical
evidence based
records
aggregation

Review based
evidence

Level 3

29
 Rating based
evidence
Apps with
Historical Ranking based Optimization
evidence based
records
aggregation

Review based
evidence

Compare with
previous evidence

Detect fraud

4.5 USE CASE DIAGRAM

Unified Modelling Language is a standard language for specifying, Visualization,

Constructing and documenting the artifacts of software system, as well as for business
modelling and other non-software 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. UML stands
for Unified Modelling 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 Primary goals in the design of the UML are as follows:

30
 1. Provide users a ready-to-use, expressive visual modeling Language so that they can
develop and exchange meaningful models.

2. Provide extendibility and specialization mechanisms to extend the core conceits.

3. Be independent of particular programming languages and development process.

4. Provide a formal basis for understanding the modeling language.

5. Encourage the growth of OO tools market.

6. Support higher level development conceits such as collaborations, frameworks,

patterns and components.

7. Integrate best practices.

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.

31
 User
registration

Upload review

Apps with
historical records

Rating based
user evidence
server

Review based
evidence

Ranking based
evidence

Optimization based
aggregation

Compare with
previous evidence to
find defect range

32
 4.6. SYSTEM FLOW DIAGRAM

Flowcharts are graphical representations of workflows of stepwise flow and actions

with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational
step-by-step workflows of components in a system. A flow chart shows the overall
flow of control.

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

33
 4.8. 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.

34
 Server User
Rating based evidence User name
Ranking based evidence Company
Review based evidence address
name
Contact details
Optimization based
Compare with previous Purchase apps ()
Fetect fraud range () Review apps ()

Mobile apps
records
Apps name
Apps details

Apps reviews()
Maintains
historical records
()

5. SYSTEM TESTING

Testing is the process of running a system with the intention of finding errors. Testing
enhances the integrity of a system by detecting deviations in design and errors in the
system. Testing aims at detecting error-prone areas. This helps in the prevention of
errors in a system. Testing also adds value to the product by conforming to the user
requirements.

The main purpose of testing is to detect errors and error-prone areas in a system.
Testing must be thorough and well-planned. A partially tested system is as bad as an
untested system. And the price of an untested and under-tested system is high.
35
 The implementation is the final and important phase. It involves user-training, system
testing in order to ensure successful running of the proposed system. The user tests
the system and changes are made according to their needs. The testing involves the
testing of the developed system using various kinds of data. While testing, errors are
noted and correctness is the mode.

5.1 OBJECTIVES OF TESTING

The objectives of testing are:

 Testing is a process of executing a program with the intent of finding errors.

 A Successful test case is one that uncovers an as- yet-undiscovered error.

System testing is a stage of implementation, which is aimed at ensuring that

the system works accurately and efficiently as per the user need, before the live
operation commences. As stated before, testing is vital to the success of a system.
System testing makes a logical assumption that if all parts of the as system are
correct, the goal will be successfully achieved. A series of tests are performed before
the system is ready for the user acceptance test.

5.2 TESTING METHODS

System testing is the stage of implementation. This is to check whether the

system works accurately and efficiently before live operation commences. Testing is
vital to the success of the system. The candidate system is subject to a variety of
tests: on line response, volume, stress, recovery, security and usability tests. A series
of tests are performed for the proposed system is ready for user acceptance testing.

5.3 THE TESTING STEPS

5.3.1 Unit Testing

Unit testing focuses efforts on the smallest unit of software design. This is known as
module testing. The modules are tested separately. The test is carried out during
programming stage itself. In this step, each module is found to be working satisfactory
as regards to the expected output from the module.

36
 5.3.2 Integration Testing

Data can be lost across an interface. One module can have an adverse effect on
another, sub functions, when combined, may not be linked in desired manner in major
functions. Integration testing is a systematic approach for constructing the program
structure, while at the same time conducting test to uncover errors associated within
the interface. The objective is to take unit tested modules and builds program
structure. All the modules are combined and tested as a whole.

5.3.3 Validation Testing

At the culmination of the integration testing, Software is completely

assembled as a package. Interfacing errors have been uncovered and corrected and a
final series of software test begin in validation testing.

Validation testing can be defined in many ways, but a simple definition is

that the validation succeeds when the software functions in a manner that is expected
by the customer. After validation test has been conducted, one of the three possible
conditions exists.

 The function or performance characteristics confirm to specification and are

accepted.

 A deviation from specification is uncovered and a deficiency list is created.

 Proposed system under consideration has been tested by using validation

test and found to be working satisfactory.

5.3.4 Output Testing

After performing the validation testing, the next step is output testing of the
proposed system, since no system could be useful if it does not produce the required
output in a specific format. The output format on the screen is found to be correct.
The format was designed in the system design time according to the user needs. For
the hard copy also; the output comes as per the specified requirements by the user.
Hence output testing did not result in any correction for the system.

37
5.3.5 User Acceptance Testing

User acceptance of a system is the key factor for the success of any system.
The system under consideration is tested for the user acceptance by constantly
keeping in touch with the prospective system users at the time of developing and
making changes whenever required.

This is done in regard to the following point:

 Input Screen Design

 Output Screen Design

 Format of reports and other outputs.

5.4 Error Messages

Error messages and warning messages are “bad news” delivered to the user’s
iterative systems where something has gone away or wrong. Therefore, in this
developed software there are some messages which will be displaying while using
this developed software if the user goes wrong. These messages are used to help the
user for better use. When the user enters wrong password, the displayed message
would be Invalid Password! Please try again. While adding information for various
modules no field should be empty when saving the information in the database
otherwise corresponding error messages are given immediately. While updating the
information if any field is left empty then the messages are displayed accordingly
Like select the task title, please Enter Numeric values etc.

6. SYSTEM IMPLEMENTATION

System Implementation is the creation and the installation of the method to

follow the engineering principles to remove part of the human element in the
equation. Implementation is the process of realizing the design as a program. The
data footprint results presented is might unveil relative performance of different
classification techniques (given the memory system is generally deemed as the
bottleneck), computation steps are the mechanism involved in dealing with the data
structures are equally important and have to be taken into consideration.

38
 To arrive at more accurate evaluation, here executed al classification and
throughput performance is measured. System Implementation is a practice of
creating or modifying a system to create a new business process or replace an
existing business process. Implementation of software refers to the final installation
of the packages in its real environment, to the satisfaction of the intended users and
the operation of the systems. The people are not sure that the software is meant to
make their job easier.

 The active user must be aware of the benefits of using the system

 Their confidence in the software buildup

 Proper guidance is impaired to the user so that it is comfortable in using

the application

The system implementation phase consists of the following steps:

 Testing the developed software with sample data

 Correction of any errors if identified

 Creating the files of the system with actual data

 Making necessary changes to the system to find out errors

 Training of user’s personnel

The system has been tested with sample data, changes are made to the
user requirements and run in parallel with the existing system to find out the
discrepancies. When the number of threads are rises with respect to the number of
cores. The user has also been appraised how to run the system during the training
period.

Implementation Plan

Implementation is the stage, which is crucial in the life cycle of the new
system designed. Implementation means converting a new or revised system design
into an operational one. The mechanism involved in dealing with the data structures

39
are equally important and have to be taken into consideration. This is the stage of the
project where the theoretical design is turned into a working system. In this project
implementation includes all those activities that take place to convert from the old
system to the new one. The important phase of implementation plan is changeover.

The implementation phase’s construction, installation and operations lie on

the new system. The most crucial and very important stage in achieving a new
successful system and in giving confidence on the new system for the user that it
will work efficiently and effectively.

There are several activities involved while implementing project:

 Careful planning

 Investigation current system and its constraints on implementation

 Design of methods to achieve the change over

 Training of the staff in the changeover procedure and evaluation of

change over method

The implementation is the final stage and it is an important phase. It involves

the individual programming system testing, user training and the operational running
of developed proposed system that constitutes the application subsystems. On major
task of preparing for implementation is education of users, which would really have
taken place much earlier in the project when we’re being involved in the
investigation and design work. The implementation phase of software development
is concerned with translating design specifications into source code. The user tests
the developed system and changes are made according to their needs.

Changeover

The implementation is to be done step by step since testing with dummy data
will not always reveal the faults. The system will be subjected to the employees to
work. If such error or failure is found, the system can be corrected before it is
implemented in full stretch. The trail should be done as long as the system is made
sure to function without any failure or errors. Precautions should be taken so that

40
any error if occurred should not totally make the process to a halt. Such a care
should be taken. The system can be fully established if it does not create any error
during the testing periods.

Education and User Training

Well-designed and technically elegant systems can succeed or fail because of

the way they are operated and used. Therefore, the quality of the training received by
the personnel involved with the systems help or hinder, and may even prevent, the
successful completion of the system. An analysis of user training focuses on user
capabilities and the nature of the system being installed. Those users are verifying
type and nature. Some of them may not have any knowledge about the computers
and the others may be intelligent. The requirements of the system also range from
simple to complex tasks. So, the training has to be generated to the specific user
based on his/her capabilities and system’s complexity. The user tests the develop
system and changes are made according to their needs.

Implementation is the stage, which is crucial in the life cycle of the new
system designed. Implementation means converting a new or revised system design
into an operational one. The mechanism involved in dealing with the data structures
are equally important and have to be taken into consideration. This is the stage of the
project where the theoretical design is turned into a working system. In this project
implementation includes all those activities that take place to convert from the old
system to the new one. The important phase of implementation plan is changeover.

User training must instruct individuals in trouble shooting the system,

determining whether a problem that arises is caused by hardware or software. The
implementation phase of the software development is concerned with translating
design specifications into source code. The user tests the developed system and
changes are made according to their needs. A good or bad perfect documentation
which instructs the user on how to start the system and the various functions and
meanings of the various codes must be prepared and that will help the user to
understand the system in a better manner.

41
System Maintenance

The process of modifying a software system or component after

delivery to correct faults, improves Performance or other attributes, or adapt to a
changed environment. Systems must be maintained and improved to meet changing
business demands or to correct processing errors. Systems maintenance phase begins
when a system becomes operational and ends when it is replaced. At some point, a
new system will reach the end of its useful life, and the analyst must be able to
recognize the signs of system obsolescence. There are many reasons for maintaining
a system that fall into the categories given above

 An error / bug is serious enough to need fixing.

 A new business process needs to be incorporated.

 A security vulnerability in the system has been found and needs

patching.

 A user has identified how the system could be improved.

 The hardware or network is being improved and so the system should

take advantage of that.

There are four major activities that occur to perform maintenance.

Corrective Maintenance

Corrective maintenance can be defined as the maintenance which is required

when an item has failed or worn out, to bring it back to working order. Corrective
maintenance is carried out on all items where the consequences of failure or wearing
out are not significant and the cost of this maintenance is not greater than
preventative maintenance.

Preventative Maintenance

Preventative maintenance is maintenance which is carried out to prevent an

item failing or wearing out by providing systematic inspection, detection and
prevention of incipient failure. The preventative maintenance efforts are aimed at

42
preserving the useful life of equipment and avoiding premature equipment failures,
minimising any impact on operational requirements. Preventative maintenance is
carried out only on those items where a failure would have expensive or
unacceptable consequences e.g. lifts, fire alarms, electricity supply and gas supply.
Many of these items are also subject to a statutory requirement for inspection and
preventive maintenance.

Perfective Maintenance

Perfective maintenance is a system of making data input screen a better one

to deal with. It has a more advance system to work with, correcting error in a more
unique and perfect way. This is maintenance that will improve the performance of
the ICT system. Usually this will involve adding features not originally present to
the software to make it produce the information from a database faster or to improve
the speed of a network.

Adaptive Maintenance

Adaptive maintenance is modifying the system to cope with changes in the

software environment. This type of maintenance often occurs as a result of external
influences or strategic changes within the company. The system is being adapted to
remain up to date. This system is developed as run in all types of environments.

43
 RESULT AND DISCUSSION

1. Detection Accuracy and Effectiveness

 Accuracy Rates: The implemented fraud detection models demonstrated varying

accuracy rates depending on the algorithm used. Machine learning models such as
Random Forest, Support Vector Machines (SVM), and Neural Networks achieved
higher accuracy, often exceeding 90%, compared to simpler models like Logistic
Regression.

 False Positives and Negatives: The trade-off between false positives (legitimate
transactions flagged as fraud) and false negatives (fraudulent transactions not
detected) was a critical factor. Models like Neural Networks tended to have fewer
false negatives but a slightly higher rate of false positives.

 Algorithm Performance: Ensemble methods like Random Forest and Gradient

Boosting performed better in detecting complex fraud patterns compared to single
algorithms. However, deep learning models showed potential in learning intricate
patterns from large datasets, offering slightly higher precision in detection.

2. Behavioral Analysis

 User Behavior Patterns: Analysis revealed distinct behavioral patterns between

fraudulent and legitimate users. Fraudulent users often exhibited erratic transaction
behaviors, such as frequent changes in IP addresses, unusual purchasing times, and
inconsistent shipping addresses.

 Transaction Characteristics: High-value transactions, sudden changes in purchase

patterns, and the use of multiple payment methods were common indicators of
fraudulent activities.

3. Feature Importance

 Key Features: Features such as transaction amount, user account age, frequency of
transactions, geographical location discrepancies, and IP address history were
identified as crucial indicators for fraud detection.

44
  Feature Engineering: The creation of derived features (e.g., average transaction
value per user, frequency of high-value purchases) significantly improved model
performance, highlighting the importance of domain-specific feature engineering.

4. Impact of Data Quality

 Data Integrity: The quality and completeness of data were paramount. Missing or
inaccurate data led to a decrease in detection accuracy. Data pre-processing steps,
including imputation of missing values and normalization, were critical for
maintaining model performance.

 Historical Data: Historical transaction data provided a rich source of information for
training models, allowing them to learn from past fraudulent activities and improve
prediction accuracy.

5. Real-Time Detection

 Latency and Speed: Real-time fraud detection systems need to balance accuracy with
speed. Implementing optimized algorithms and efficient data processing pipelines
ensured that fraud detection systems could operate in real-time without significant
delays.

 Scalability: The ability to scale and handle high transaction volumes was essential for
maintaining performance in online marketplaces. Distributed computing frameworks
and cloud-based solutions were effective in addressing scalability concerns.

45
 CONCLUSION AND FUTURE ENHANCEMENTS
7.1 CONCLUSIONS

A ranking fraud detection system for mobile Apps has been developed in this project.
Specifically, it first showed that ranking fraud happened in leading sessions and
provided a method for mining leading sessions for each App from its historical
ranking records. Then, it identified ranking based evidences, rating based evidences
and review based evidences for detecting ranking fraud. Moreover, it proposed an
optimization-based aggregation method to integrate all the evidences for evaluating
the credibility of leading sessions from mobile Apps. A unique perspective of this
approach is that all the evidences can be modeled by statistical hypothesis tests, thus it
is easy to be extended with other evidences from domain knowledge to detect ranking
fraud. Finally, it validates the proposed system with extensive experiments on real-
world App data collected from the Apple’s App store. Experimental results showed
the effectiveness of the proposed approach.

7.2 FUTURE WORK

In the future, it is planned to study more effective fraud evidences and analyze the
latent relationship among rating, review and rankings. Moreover, it will be extended
to ranking fraud detection approach with other mobile App related services, such as
mobile Apps recommendation, for enhancing user experience.

46
 APPENDIX
SOURCE CODE

Create Account.aspx

using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
public partial class createaccount1 : System.Web.UI.Page
Label11.Text = Convert.ToString(objt.userid());
Label7.Text = (string)Session["username"];
lbl_eid.Visible = false;
lbl_eid.Text = (string)Session["id"];
lbl_date.Text = Convert.ToString(DateTime.Now);
lbl_date.Visible = false;
Session["uid"] = Label11.Text;

protected void Button1_Click(object sender, EventArgs e)

{
if (txtverification.Text == txt1.Value)
{
lblmsg.Text = "Successfull";
lblmsg.Text = "Failure";
protected void Button3_Click(object sender, EventArgs e)
if (lblmsg.Text == "Successfull")

47
 objt.createusers(Label11.Text,lbl_eid.Text, Label7.Text, TextBox4.Text,
TextBox5.Text, TextBox1.Text, TextBox2.Text, TextBox6.Text, TextBox7.Text);
objt.insert(Label11.Text, lbl_eid.Text, Label7.Text, lbl_date.Text);
Response.Redirect("rating.aspx");
}
else
{
MsgBox.Show("Please give the correct verification code");

Admin Recommend.aspx.cs

using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
public partial class adminrecomend : System.Web.UI.Page
for (int h = 0; h < data.Tables[0].Rows.Count; h++)
{
DropDownList1.Items.Add(data.Tables[0].Rows[h]["pname"].ToString());
}
protected void Button1_Click(object sender, EventArgs e)
GridView1.Visible = true;
DataSet ds = new DataSet();
ds = cs.admintabl(DropDownList1.SelectedItem.Value);
GridView1.DataSource = ds;
GridView1.DataBind();
}

48
 public void bind()
{
DataSet ds = new DataSet();
ds = cs.admintabl(DropDownList1.SelectedItem.Value);
GridView1.DataSource = ds;
GridView1.DataBind();
}
protected void GridView1_PageIndexChanging(object sender,
GridViewPageEventArgs e)
GridView1.PageIndex = e.NewPageIndex;
bind();
Opinion.aspx.cs
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
public partial class postingopinion : System.Web.UI.Page
Label3.Visible = false;
TextBox1.Visible = false;
lbl_dat.Visible = false;
Label4.Visible = false;
lbl_dat.Text = Convert.ToString(DateTime.Now);
Label4.Text = Convert.ToString(obj.createid());
protected void Button3_Click(object sender, EventArgs e)
Session["id"] = Label4.Text;
if (DropDownList1.SelectedItem.Text == "Others")
49
 Session["comment"] = TextBox1.Text;
if (TextBox1.Text == "
MsgBox.Show("Enter the required data");
.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.SqlClient;
public partial class ranking : System.Web.UI.Page
class1 cs = new class1();
GridView1.Visible = false;
Label2.Visible = false;
Label3.Visible = false;
DataSet data = new DataSet();
data = cs.dropproduct();
DropDownList1.Items.Add("--Select--");
for (int h = 0; h < data.Tables[0].Rows.Count; h++)

Label3.Visible = true;
Label2.Text="&nbsp; members Recommendation"+"&nbsp;";

Label3.Text = "=&nbsp;" +
Convert.ToString(cs.countpro1(DropDownList1.SelectedItem.Text)) +
"&nbsp;in&nbsp;" + DropDownList1.SelectedItem.Text;
}
protected void LinkButton1_Click(object sender, EventArgs e)
DataSet ds1 = new DataSet();
ad.Fill(ds1);
for (int h = 0; h < ds1.Tables[0].Rows.Count; h++)
{
SqlDataAdapter adp = new SqlDataAdapter("select product,rate,count(rate) as
Rank from opinions group by rate,product", connect);
DataSet ds = new DataSet();
adp.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
50
 connect.Open();
SqlDataAdapter ad = new SqlDataAdapter("select distinct product from
opinions", connect);
DataSet ds1 = new DataSet();
ad.Fill(ds1);
for (int h = 0; h < ds1.Tables[0].Rows.Count; h++)
SqlDataAdapter adp = new SqlDataAdapter("select
product,rate,count(rate) as Rank from opinions group by rate,product", connect);
DataSet ds = new DataSet();
adp.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
Reviews.aspx.cs
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
a = Request.Params["id"];
Label1.Visible = false;
Label1.Text = a;
Label2.Text = Label1.Text;
Session["pr"] = Label2.Text;
Label3.Text = Convert.ToString(cs.countpro(a)) + " &nbsp;Customer" + "
&nbsp;Reviews";
Label4.Visible = false;
Label5.Visible = false;
51
 Label6.Visible = false;
Label7.Visible = false;
Label8.Visible = false;
Label9.Visible = false;
Label10.Visible = false;
Label11.Visible = false;
Label12.Visible = false;
Label13.Visible = false;
Label14.Visible = false;
LinkButton1.Visible = false;
LinkButton2.Visible = false;
LinkButton3.Visible = false;
LinkButton4.Visible = false;
LinkButton5.Visible = false;
Panel1.Visible = false;
ImageButton2.Visible = false;
Label15.Visible = false;
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs e)
{
Label14.Text = Label3.Text;
Label4.Visible = true;
Label5.Visible = true;
Label6.Visible = true;
Label7.Visible = true;
Label8.Visible = true;
Label9.Visible = true;
Label10.Visible = true;
Label11.Visible = true;
Label12.Visible = true;
Label13.Visible = true;
Label14.Visible = true;
LinkButton1.Visible = true;
LinkButton2.Visible = true;
52
 LinkButton3.Visible = true;
LinkButton4.Visible = true;
LinkButton5.Visible = true;
protected void LinkButton3_Click(object sender, EventArgs e)
{
Response.Redirect("average.aspx");
}
protected void LinkButton4_Click(object sender, EventArgs e)
{
Response.Redirect("bad.aspx");
}
protected void LinkButton5_Click(object sender, EventArgs e)
{
Response.Redirect("worst.aspx");

Rating.aspx.cs

using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
Admin Ranking.aspx.cs
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;

53
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.SqlClient;
public partial class adminranking : System.Web.UI.Page
{
class1 cs = new class1();
string s, s2, s3;
int s1 = 2;
SqlConnection connect = new
SqlConnection(ConfigurationManager.AppSettings["recommentationconnection"]);

protected void Page_Load(object sender, EventArgs e)

{
connect.Open();
SqlDataAdapter ad = new SqlDataAdapter("select distinct product from
opinions", connect);
DataSet ds1 = new DataSet();
ad.Fill(ds1);
for (int h = 0; h < ds1.Tables[0].Rows.Count; h++)
{
SqlDataAdapter adp = new SqlDataAdapter("select product,rate,count(rate) as
Rank from opinions group by rate,product", connect);
DataSet ds = new DataSet();
adp.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();

connect.Close();

54
 SCREEN SHOTS

Home Screen

55
User Registration

Global Anomaly Login

56
Global Anomaly Home

Upload Apps

57
User Viewing App Details

User Ranking App

58
Global and Local Ranking

59
 REFERENCES

BOOKS

1. Allen Jones, Rakesh Rajan (2006), Visual C# 2005 Recipes, A Problem-

Solution Approach. Mc Graw-Hill, 2000.
2. H.M. Deitel (2005), Visual C# 2005: How to program, 2nd Edition
3. O’Reilly (2005), Visual C# 2005: A Developer’s Notebook.
4. Matthew MacDonald “Beginning ASP.NET 3.5 in C# 2008”
5. Pressman, Roger S., Software Engineering “A Practitioner’s Approach”,
Fifth Edition,
6. Shlomy gantz president, Blue Brick Inc, SQL Server 2005.
7. System Analysis and Design by Elias M Awad, 2nd edition, Galgotia
Publications, 2006

WEBSITES
1. http://venturebeat.com/2012/07/03/
2. http://www.ibtimes.com/applethreatens- crackdown-biggest-app-store-
ranking-fra ud-406764
3. http://en.wikipedia.org/wiki/ information retrieval and validation

JOURNALS

[1] B. Zhou, J. Pei, and Z. Tang. A spamicity approach to web spam detection. In
Proceedings of the 2008 SIAM International Conference on Data Mining, SDM’08,
pages 277–288, 2008.
[2] A. Ntoulas, M. Najork, M. Manasse, and D. Fetterly. Detecting spam web pages
through content analysis. In Proceedings of the 15th international conference on
World Wide Web, WWW ’06, pages 83–92, 2006.
[3] N. Spirin and J. Han. Survey on web spam detection: principles and algorithms.
SIGKDD Explor. Newsl., 13(2):50–64, May 2012.
[4] E.-P. Lim, V.-A. Nguyen, N. Jindal, B. Liu, and H. W. Lauw. Detecting product
review spammers using rating behaviors. In Proceedings of the 19th ACM

60
international conference on Information and knowledge management, CIKM ’10,
pages 939–948, 2010.
[5] Z.Wu, J.Wu, J. Cao, and D. Tao. Hysad: a semi- supervised hybrid shilling attack
detector for trustworthy product recommendation. In Proceedings of the 18th ACM
SIGKDD international conference on Knowledge discovery and data mining, KDD
’12, pages 985–993, 2012
[6] S. Xie, G. Wang, S. Lin, and P. S. Yu. Review spam detection via temporal pattern
discovery. In Proceedings of the 18th ACM SIGKDD international conference on
Knowledge discovery and data mining, KDD ’12, pages 823–831, 2012.
[7] B. Yan and G. Chen. Appjoy: personalized mobile application discovery. In
Proceedings of the 9th international conference on Mobile systems, applications, and
services, MobiSys ’11, pages 113– 126, 2011.
[8] K. Shi and K. Ali. Getjar mobile application recommendations with very sparse
datasets. In Proceedings of the 18th ACM SIGKDD international conference on
Knowledge discovery and data mining, KDD ’12, pages 204–212, 2012.
[9] R. Agrawal and R. Srikant, “Fast algorithms for mining association rules,” in
VLDB, 1994.
[10] H. Zhu, E. Chen, K. Yu, H. Cao, H. Xiong, and J. Tian. Mining personal context-
aware preferences for mobile users. In Data Mining (ICDM), 2012 IEEE 12th
International Conference on, pages 1212–1217, 2012.
[11]Hengshu Zhu, Hui Xiong Discovery of Ranking Fraud for Mobile Apps. IEEE
TRANSACTIONS ON KNOWLEDGE AND DATA ENGINEERING,2013.

61