SYNOPSIS
This project entitled”detecting group shilling attack in online recommender system on
bisecting k-means clustering”Extract the rating track of each item and divide the rating tracks
to generate candidate groups according to a fixed time interval. Second, we propose item
attention degree and user activity to calculate the suspicious degrees of candidate groups.
Fake reviews and ratings becomes annoying forever in the user perspective and in the
field of consumer utilization. Some users crate and inject fake user profiles consisting of
biased ratings which affects the recommendation ranking and manipulate the user’s decision.
Attacks on recommender system behaviour is known as a “shilling” attack or “profile
injection” attack. The fake Users involved in shilling attacks were coined as shillers. Existing
shilling attack detection doesn’t have a clear approach mainly on identifying individual
attackers in online recommender systems and rarely address the detection of group shilling
attacks in which a group of attackers colludes to bias the output of an online recommender
system by injecting fake profiles. In this project, group shilling attack detection can be
achieved based on bisecting K-means clustering algorithm. Time based manipulation is the
base idea – First, we extract the rating track of each item and divide the rating tracks to
generate candidate groups according to a fixed time interval. Second, we propose item
attention degree and user activity to calculate the suspicious degrees of candidate groups.
Finally, we employ the bisecting K-means algorithm to cluster the candidate groups
according to their suspicious degrees and obtain the attack groups. Experiments on the
Netflix and Amazon data sets with the algorithm implementation indicate that the proposed
method outperforms the baseline methods.
1
1.INTRODUCTION:
The explosive growth of online information, the phenomenon of information overload
becomes a key issue. Online recommender systems make recommendations for their users,
which can alleviate the information overload problem to some extent. However, the online
recommender systems are vulnerable to shilling attacks in which attackers inject a large
number of attack profiles to bias the output of the recommender system . Shilling attacks can
be divided into push attacks and nuke attacks, which are used for promoting and demoting
target items (e.g., movies or products) to be recommended, respectively . The well-studied
shilling attacks include random attack, average attack, band- wagon attack, reverse
bandwagon attack , average-target shift attack, average-noise injecting attack , and so on. In
these attacks, attackers usually separately inject attack profiles into recommender systems. In
fact, a group of attackers might collude to make a tactical attack. Such shilling behaviours
have been termed group shilling attacks, which are more threatening to the system than
traditional shilling attacks. Therefore, how to effectively identify group shilling attacks has
become a key issue needed to be addressed.
To protect recommender systems, various approaches have been presented to detect
shilling attacks over the past decade. However, these approaches focus mainly on detecting
individual attackers in recommender systems and rarely consider the collusive shilling
behaviours among attackers. Although some approaches have been proposed to detect
shilling behaviours at the group level, they divide candidate groups and identify attack groups
according to profile similarity. There are some group attack models that can generate attack
profiles with great diversity. As a result, these approaches cannot fully detect attack groups,
which causes poor precision and recall. Recently, some approaches have been presented to
detect spammer groups in review websites. However, the group shilling attacks in
recommender systems are different from the spammer groups in review websites. Therefore,
the spammer group detection approaches are not applicable to the detection of group shilling
attacks.
2
1.1 SYSTEM SPECIFICATONS:
1.1.1 HARDWARE CONFIGURATION:
· System
:
Pentium IV 2.4 GHz.
· Hard Disk
:
250 GB.
· Monitor
:
15 VGA Color.
· Mouse
:
Optical.
· Ram
:
1 GB
1.1.2 SOFTWARE SPECIFICATIONS:
· Operating system
:
Windows 10
· Coding Language
:
Java (Jdk 1.6) with Servlet and JSP.
· Database
:
My-SQL 5.0
. Server
:
Glassfish
. IDE
:
Netbeans
3
2. SYSTEM STUDY:
2.1 EXISTING SYSTEM:
The existing system is developed to identify attacks from individual users of the
recommendation system. The existing system is designed such a way that it is useful for
finding attacks from individual users to alleviate the results produced by the recommendation
system. But in recent time, groups of users work on to alleviate the results of the
recommendation system. So the existing system is not sufficient enough to detect such
attacks. So we need a new system that detects the group shilling attacks in the recommender
system.
2.1.1 DESCRIPTION:
To mask the attack profile as genuine and make it difficult to detect, attackers try to
forge ratings to match those of genuine profiles. According to the composition of attack
profiles, different attack model are defined. Details of attack models will be introduced later.
Push and nuke attacks are two types based on the attackers’ intentions. Push attacks are
aimed at boosting items and increasing their rankings, while nuke attacks are designed to
downgrade items and reduce their rankings. In this paper, we mean push attacks if not
specialized.
2.1.2 DRAWBACKS:
1. Easily make the fake feedback on the system
2. No reliable recommendation
3. Finding he malicious user feedback is very difficult
2.2 PROPOSED SYSTEM:
The proposed system is designed to detect the group shilling attacks that occurs in the
recommender system. Here a group of users creates their profiles and enters the
recommendation system and purposely tend to change the original rating given by the users
for the products in the recommender system. So the original rating of the product is tend to be
4
changed and the fake rating is produced to the users. First, the proposed system extract the
rating track of each item and divide the rating tracks to generate candidate groups according
to a fixed time criteria. Second, it proposes item attention degree and user activity to calculate
the suspicious degrees of candidate groups. By this method it filters the fake ratings given by
group shilling attacks and displays the original rating of the products in the recommender
system.
The quality of attack profiles depends on prior knowledge attackers gained before
they perform an attack. More prior knowledge is obtained, the attack profiles are more
complex, and the profiles appear more genuine. The main difference between attack models
is the distribution of variance ratings for filler set and selected set.
2.2.1 DESCRIPTION:
Random attack uses a normal distribution to evaluate randomly choose filler items
around the system’s average ratings, which is described ]. Highest or lowest score are
assigned to target items according to attack types. The average attack requires priori
knowledge of average rating of items in the recommender system. Normal distribution is used
to randomly rate items with the average score set as the mean rating of items according to the
standard deviation . Attackers disguise themselves and are more difficult to distinguish than
genuine users, thus giving them greater impact on recommendations. The target items’ ratings
are the same like random attack models. Bandwagon and segment attack models are
evaluated from random and average attack models.
These profiles select a lot of items of a certain kind, for example, popular or high
rated items. Selected items in segment attacks and bandwagon attacks are group attacks. The
rationale behind group attacks is attackers focus on those who are already inclined to the
product, which can promote attack efficiency. In other words, an attacker intending to
promote a particular item not to all us
2.2.2 ADVANTAGES:
1. Easily identify the fake rating
2. Segregate the fake group users by using the clustering algorithm
3. By using this segregation easily find the fake recommendations.
5
2.3 SOFTWARE DESCRIPTIONS:
JAVA TECHNOLOGY
Java technology is both a programming language and a platform.
THE JAVA PROGRAMMING LANGUAGE
Strong typing allows for more error checking to be done at compile time also,
less error appear at runtime.
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.
The Java programming language is a high-level language that can be characterized by all of
the following buzzwords:
1. Simple
2. Architecture neutral
3. Object oriented
4. Portable
5. Distributed
6. High performance
7. Interpreted
8. Multithreaded
9. Robust
10. Dynamic
11. 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.
6
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.
THE JAVA PLATFORM
A platform is the hardware or software environment in which a program runs. We’ve
already mentioned some of the most popular platforms like Windows 2000, Linux, Solaris,
and MacOS. Most platforms can be described as a combination of the operating system and
hardware. The Java platform differs from most other platforms in that it’s a software-only
platform that runs on top of other hardware-based platforms.
The Java platform has two components:
1.
The Java Virtual Machine (Java VM)
2.
The Java Application Programming Interface (Java API)
You’ve already been introduced to the Java VM. It’s the base for the Java platform and is
ported onto various hardware-based platforms.
The Java API is a large collection of ready-made software components that provide
many useful capabilities, such as graphical user interface (GUI) widgets. The Java API is
grouped into libraries of related classes and interfaces; these libraries are known as packages.
The next section, What Can Java Technology Do? Highlights what functionality some of the
packages in the Java API provide.
The following figure depicts a program that’s running on the Java platform. As the figure
shows, the Java API and the virtual machine insulate the program from the hardware.
Native code is code that after you compile it, the compiled code runs on a specific hardware
platform. As a platform-independent environment, the Java platform can be a bit slower than
native code. However, smart compilers, well-tuned interpreters, and just-in-time byte code
compilers can bring performance close to that of native code without threatening portability.
7
WHAT CAN JAVA TECHNOLOGY DO?
The most common types of programs written in the Java programming language are
applets and applications. If you’ve surfed the Web, you’re probably already familiar with
applets. An applet is a program that adheres to certain conventions that allow it to run within
a Java-enabled browser.
However, the Java programming language is not just for writing cute, entertaining
applets for the Web. The general-purpose, high-level Java programming language is also a
powerful software platform. Using the generous API, you can write many types of programs.
An application is a standalone program that runs directly on the Java platform. A special kind
of application known as a server serves and supports clients on a network. Examples of
servers are Web servers, proxy servers, mail servers, and print servers. Another specialized
program is a servlet. A servlet can almost be thought of as an applet that runs on the server
side. Java Servlets are a popular choice for building interactive web applications, replacing
the use of CGI scripts. Servlets are similar to applets in that they are runtime extensions of
applications. Instead of working in browsers, though, servlets run within Java Web servers,
configuring or tailoring the server.
How does the API support all these kinds of programs? It does so with packages of
software components that provides a wide range of functionality. Every full implementation
of the Java platform gives you the following features:
1.
The essentials: Objects, strings, threads, numbers, input and output, data structures,
system properties, date and time, and so on.
2.
Applets: The set of conventions used by applets.
3.
Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram
Protocol) sockets, and IP (Internet Protocol) addresses.
4.
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.
5.
Security: Both low level and high level, including electronic signatures, public and
private key management, access control, and certificates.
6.
Software components: Known as JavaBeansTM, can plug into existing component
architectures.
7.
Object serialization: Allows lightweight persistence and communication via Remote
Method Invocation (RMI).
8
8.
Java Database Connectivity (JDBCTM): Provides uniform access to a wide range of
relational databases.
The Java platform also has APIs for 2D and 3D graphics, accessibility, servers,
collaboration, telephony, speech, animation, and more. The following figure depicts
what is included in the Java 2 SDK.
HOW WILL JAVA TECHNOLOGY CHANGE MY LIFE?
We can’t promise you fame, fortune, or even a job if you learn the Java programming
language. Still, it is likely to make your programs better and requires less effort than other
languages. We believe that Java technology will help you do the following:
Get started quickly: Although the Java programming language is a powerful object-oriented
language, it’s easy to learn, especially for programmers already familiar with C or C++.
Write less code: Comparisons of program metrics (class counts, method counts, and so on)
suggest that a program written in the Java programming language can be four times smaller
than the same program in C++.
Write better code: The Java programming language encourages good coding practices, and
its garbage collection helps you avoid memory leaks. Its object orientation, its JavaBeans
component architecture, and its wide-ranging, easily extendible API let you reuse other
people’s tested code and introduce fewer bugs.
Develop programs more quickly: Your development time may be as much as twice as fast
versus writing the same program in C++. Why? You write fewer lines of code and it is a
simpler programming language than C++.
Avoid platform dependencies with 100% Pure Java: You can keep your program portable
by avoiding the use of libraries written in other languages. The 100% Pure JavaTM Product
Certification Program has a repository of historical process manuals, white papers, brochures,
and similar materials online.
Write once, run anywhere: Because 100% Pure Java programs are compiled into machineindependent byte codes, they run consistently on any Java platform.
Distribute software more easily: You can upgrade applets easily from a central server.
Applets take advantage of the feature of allowing new classes to be loaded “on the fly,”
without recompiling the entire program.
9
ODBC:
Microsoft Open Database Connectivity (ODBC) is a standard programming interface
for application developers and database systems providers. Before ODBC became a de facto
standard for Windows programs to interface with database systems, programmers had to use
proprietary languages for each database they wanted to connect to. Now, ODBC has made the
choice of the database system almost irrelevant from a coding perspective, which is as it
should be. Application developers have much more important things to worry about than the
syntax that is needed to port their program from one database to another when business needs
suddenly change.
Through the ODBC Administrator in Control Panel, you can specify the particular
database that is associated with a data source that an ODBC application program is written to
use. Think of an ODBC data source as a door with a name on it. Each door will lead you to a
particular database. For example, the data source named Sales Figures might be a SQL Server
database, whereas the Accounts Payable data source could refer to an Access database. The
physical database referred to by a data source can reside anywhere on the LAN.
The ODBC system files are not installed on your system by Windows 95. Rather, they
are installed when you setup a separate database application, such as SQL Server Client or
Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a file called
ODBCINST.DLL. It is also possible to administer your ODBC data sources through a standalone program called ODBCADM.EXE. There is a 16-bit and a 32-bit version of this
program
and
each
maintains
a
separate
list
of
ODBC
data
sources.
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
10
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 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:
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.
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 nonstandard functionality in a manner that is suitable for its users.
11
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.
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.
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.
12
3. SYSTEM DESIGN AND DEVELOPMENT:
3.1 FILE DESIGN:
A file system is the data structure designed to support the abstraction of the data blocks as an
archive and collection of files. In other words, a file system organizes the data blocks into
files, directories, and file information.
File Design Information systems in business are file and database oriented. Data are
accumulated into files that are processed or maintained by the system. The systems analyst is
responsible for designing files, determining their contents and selecting a method for
organising the data.
3.2 INPUT DESIGN:
Input design is one of the most expensive phases of the operation of computerized system and
is often the major problem of a system. A large number of problems with the system can
usually be traced back to fault input design and method. Needless to say, therefore that the
input data is the life block of a system and has to be analyzed and designed with the most
consideration.
The decisions made during the input design are:
1. To provide cost effective method of input.
2. To achieve the highest possible level of accuracy.
3. To ensure that input is understood by the user.
System analysts decide the following input design details like, what data item to input, what
medium to use, how the data should be arranged or coded data items and transaction needing
validations to detect errors and at last the dialogue to guide users in providing input. Input
data of a system may not be necessarily a raw data captured in the system form scratch. These
can also be the output of another system or sub-system. The design of input covers all phases
of input from the certain of initial data to actual entering the data to the system for
processing.
13
3.3 OUTPUT DESIGN:
Output design generally refers to the results and information that are generated by the system.
For many end-users, output is the main reason for developing the system and the basis on
which they evaluate the usefulness of the application.
The objective of a system finds its shape in terms of output. The analysis of the objective of a
system leads to determination of outputs. Outputs of a system can take various forms. The
most common are reports, screens displays printed form, graphical drawing etc. the outputs
vary in terms of their contents, frequency, timing and format. The users of the output, its
purpose and sequence of details to be printed are all considered.
When designing output, the system analyst must accomplish things like, to determine what
information to be present, to decide whether to display or print the information and select the
output medium to distribute the output to intended recipients.
External outputs are those, whose destination will be outside the organization and which
require special attention as the project image of the organization.
Internal outputs are those, whose destination is within the organization. It is to be carefully
designed, as they are the user’s main interface with the system. Interactive outputs are those,
which the user uses in communication directly with the computer.
3.4 CODE DESIGN:
Code design refers to the process of planning and organizing code in a way that makes it easy
to read, understand, and maintain. It involves deciding on the overall structure of the code,
the names and functions of variables and functions, and the relationships between different
parts of the code. Good code design is important because it can improve the quality and
efficiency of the code, make it easier to debug and update, and reduce the risk of errors and
bugs.
14
Some key principles of good code design include:
Simplicity: Code should be easy to understand and follow, with clear, concise, and consistent
naming conventions.
Modularity: Code should be organized into modular components that can be reused and
easily modified.
Abstraction: Code should be abstracted to hide implementation details and reduce
complexity.
Separation of concerns: Different parts of the code should be responsible for different
concerns, such as data storage, user input, or business logic.
Cohesion: Code should be organized around specific tasks or functions, with each function
having a clear and focused purpose.
Loose coupling: Different parts of the code should be loosely coupled, with minimal
dependencies between them.
Testability: Code should be designed with testing in mind, so that it is easy to write and run
tests to ensure its correctness.
Overall, good code design is an important aspect of software development that can make
code more efficient, easier to maintain, and more resilient to bugs and errors.
3.5 DATABASE DESIGN:
Database design is the process of creating a logical and functional representation of a
database. This involves determining what data needs to be stored, how it should be organized,
and how it should be accessed.
Here are the key steps involved in designing a database:
1. Identify the purpose of the database: Before you start designing a database, you need
to have a clear understanding of why you need it and what it will be used for.
15
2. Determine the data requirements: Once you know the purpose of the database, you
need to identify the data that needs to be stored in it. This involves defining entities,
attributes, and relationships between them.
3. Choose the database management system: The database management system (DBMS)
is the software that will be used to store and manage the data. There are many
different DBMS options available, each with its own strengths and weaknesses.
4. Design the schema: The schema is the blueprint for the database. It defines the tables,
columns, keys, and other components that make up the database.
5. Normalize the data: Normalization is the process of organizing data to minimize
redundancy and dependency. This helps to ensure data consistency and accuracy.
6. Implement the schema: Once the schema has been designed and normalized, it needs
to be implemented in the DBMS. This involves creating the tables and other
components that make up the database.
7. Test and refine: Finally, the database needs to be tested to ensure that it is working
properly. Any issues or bugs should be identified and fixed, and the database should
be refined as needed to improve its performance and functionality.
8. Overall, designing a database requires careful planning, attention to detail, and a
thorough understanding of the data and the business processes that the database will
support.
3.6 SYSTEM DEVELOPMENT:
MODULES:
Authority Privilege
1. Add or Delete Category
2.Add or Delete items
3. Manage Orders
4..Detected fake users Details
End User Session
1.Registration
2. Login
16
3. Give review about products
4. Detect fake users:
3.7 DESCRIPTION OF MODULES:
Authority privilege:
Once the user submit their details the information are accepted and the user can login
with their username and password for posting review or opinion about the products. Only the
registered users can post reviews. In this module it checks whether the authorized persons is
accessing and it does not allow other users to access.
Add/Update/Delete Category
If the Administrator wants to Add or Delete or Update a product category then he can
insert or delete a product categoryusing his administration rights and the category table will
be updated in the database.
Add/Update/Delete Item Details
If the Administrator wants to add or delete and then he can insert or delete or update
itemdetails like item name,price,featuresetcusing his administration rights and the details
table will be updated in the database.
Manage Orders
If the Administrator wants to View an order then he can view all orders done within
the website using his administration rights. The admin can view the user/customer details.
Detected Fake user Details
Here we display the detected fake users for the taking the further action.
End user session:
Registration
If the user doesn’t have an account then he will be asked to register.The user will
enter details in the registration form according to the required fieldslikeUsername, Password,
confirm password, first name, last name, email, Address, Phone and other relevant details.
17
Login
If the user wants to get access to all the functionalities shopping page he should login
using his username and password.
Give Review
If the user wants to give review according to his opinion for an item he/she give review for
a particular product.
Detect fake users:
Collect data: Collect user behavior data, such as their ratings or purchase history.
Pre-process data: Normalize the data to account for differences in scale or measurement.
Cluster users: Apply Bisecting K-Means to cluster users based on their behavior data. The
number of clusters can be determined based on the system's requirements.
Evaluate clusters: Evaluate the resulting clusters to identify any that exhibit suspicious
behavior. This can be done by looking for clusters with a high percentage of users who rate or
purchase items in a similar way.
Monitor clusters: Continuously monitor the clusters to detect any changes in behavior that
may indicate a group shilling attack. This can be done by comparing the behavior of users in
the clusters over time.
Take action: If a group shilling attack is detected, take appropriate action, such as removing
the offending users or reconfiguring the recommender system.
18
4. TESTING AND IMPLEMENTATION:
4.1 SYSTEM TESTING:
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to check
the functionality of components, sub-assemblies, assemblies and/or a finished product It is
the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.
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 available
as specified by the business and technical requirements, system documentation, and user
manuals.
19
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.
WHITE BOX TESTING
White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
BLACK BOX TESTING
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the
software under test is treated, as a black box .you cannot “see” into it. The test provides
inputs and responds to outputs without considering how the software works.
TEST STRATEGY AND APPROACH
Field testing will be performed manually and functional tests will be written in detail.
20
TEST OBJECTIVES
1. All field entries must work properly.
2. Pages must be activated from the identified link.
3. The entry screen, messages and responses must not be delayed.
FEATURES TO BE TESTED
1. Verify that the entries are of the correct format
2. No duplicate entries should be allowed
3. All links should take the user to the correct page.
INTEGRATION TESING
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.
The task of the integration test is to check that components or software applications,
e.g. components in a software system or – one step up – software applications at the company
level – interact without error.
ACCEPTANCE TESTING
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.
21
4.2 SYSTEM IMPLEMENTATION:
The purpose of System Implementation can be summarized as follows: making the
new system available to a prepared set of users (the deployment), and positioning on-going
support and maintenance of the system within the Performing Organization (the transition).
At a finer level of detail, deploying the system consists of executing all steps necessary to
educate the Consumers on the use of the new system, placing the newly developed system
into production, confirming that all data required at the start of operations is available and
accurate, and validating that business functions that interact with the system are functioning
properly. Transitioning the system support responsibilities involves changing from a system
development to a system support and maintenance mode of operation, with ownership of the
new system moving from the Project Team to the Performing Organization.
A key difference between System Implementation and all other phases of the lifecycle
is that all project activities up to this point have been performed in safe, protected, and secure
environments, where project issues that arise have little or no impact on day-to-day business
operations. Once the system goes live, however, this is no longer the case. Any miscues at
this point will almost certainly translate into direct operational and/or financial impacts on the
Performing Organization. It is through the careful planning, execution, and management of
System Implementation activities that the Project Team can minimize the likelihood of these
occurrences, and determine appropriate contingency plans in the event of a problem.
22
5.CONCLUSION:
In conclusion, detecting group shilling attacks in online recommender systems is a
crucial task to maintain fairness and integrity. Bisecting K-Means clustering can be an
effective technique for identifying groups of users with similar behavior and detecting
suspicious clusters that may indicate a shilling attack. By continuously monitoring the
behavior of users and clusters, recommender systems can take appropriate action to mitigate
the impact of shilling attacks, such as removing the offending users or reconfiguring the
recommendation algorithm. However, it is important to recognize that shilling attacks can
evolve over time, and the detection techniques need to be updated accordingly to stay
effective. By implementing robust and adaptive detection methods, recommender systems
can provide fair and reliable recommendations to all users.
FUTURE ENHANCEMENT:
Here are some potential future enhancements for detecting group shilling attacks in online
recommender systems based on Bisecting K-Means clustering:
1. Incorporating additional features: In addition to user behavior data, other features
such as demographic information or user feedback can be included in the clustering
analysis to improve the accuracy of identifying suspicious clusters.
2. Using advanced machine learning algorithms: More sophisticated machine learning
algorithms, such as deep learning or ensemble learning, can be explored to improve
the accuracy of detecting shilling attacks and reduce false positives.
3. Considering dynamic behavior patterns: By analyzing user behavior patterns over
time, dynamic changes in user behavior can be detected, which may indicate shilling
attacks. Techniques such as time-series analysis and anomaly detection can be applied
to identify such changes.
4. Implementing a feedback loop: When a shilling attack is detected, feedback can be
provided to the clustering algorithm to update the clustering model and improve its
accuracy in detecting future attacks.
5. Collaborating with other systems: Collaborating with other online systems, such as
social networks, can provide additional insights into user behavior and improve the
accuracy of detecting shilling attacks.
.
23
6.BIBLOGRAPHY:
[1] Shuo Qiu, Student Member, IEEE, Boyang Wang, Ming Li, Member, IEEE, Jiqiang Liu,
and Yanfeng Shi, “Toward Practical Privacy-Preserving Frequent Itemset
Mining on Encrypted Cloud Data”, IEEE Transactions on Cloud Computing, 2020.
[2] Cai, Hongyun; Zhang, Fuzhi " An Unsupervised Approach for Detecting Group Shilling
Attacks in Recommender Systems Based on Topological Potential and Group Behaviour
Features.", Security & Communication Networks . 9/27/2021, p1-18. 18p.
[3] M. Si and Q. Li, “Shilling attacks against collaborative recommender systems: a review,”
Artificial Intelligence Review, vol. 53, no. 1, pp. 291–319, 2020.
[4] A. M. Turk and A. Bilge, “Robustness analysis of multicriteria collaborative filtering
algorithms against shilling attacks,” Expert Systems with Applications, vol. 115, pp. 386–
402, 2019.
[5] K. Vivekanandan and N. Praveena, “Hybrid convolutional neural network (CNN) and
long-short term memory (LSTM) based deep learning model for detecting shilling
attack in the social-aware network,” Journal of Ambient Intelligence and Humanized
Computing, vol. 12, no. 1, pp. 1197–1210, 2021.
[6] Fuzhi Zhang, Weiqi Meng, Ru Ma, Dingli Gao, Shilei Wang, "User embedding-based
approach for detecting group shilling attacks", 2021 IEEE International Conference on
Artificial Intelligence and Computer Applications (ICAICA), pp.639-643, 2021
[7] Shilei Wang, Hui Wang, Hongtao Yu, Fuzhi Zhang, "Detecting shilling groups in
recommender systems based on hierarchical topic model", 2021 IEEE International
Conference on Artificial Intelligence and Computer Applications (ICAICA), pp.832-837,
2021
[8] Hongtao Yu, Shengyu Yuan, Yishu Xu, Ru Ma, Dingli Gao, Fuzhi Zhang, "Group attack
detection in recommender systems based on triangle dense subgraph mining", 2021 IEEE
International Conference on Artificial Intelligence and Computer Applications (ICAICA),
pp.649-653, 2021
24
7.APPENDICES:
A.DATA FLOW DIAGRAM: USER
USER
NO
REGISTRATION
UNAME
& PWD
YES
REVIEW
PRODUCTS
LOGIN
NO
DETECTING
SHILLING ATTAKERS
YES
VERIFY
UNAME
& PWD
USER
HOME
PAYMENT
PURCHASE
PRODUCT
M_USER
25
ADMIN
ADMIN
ADD PRODUCT
LOGIN
NO
YES
VERIFY
UNAME &
PWD
ADMIN
HOME
VIEW PURCHASE
DETAILS
M_ADMIN
VIEW DETECTED
SHILLING ATTAKERS
26
B.TABLE DESIGN:
M_FEED_WORDS
M_ADDTOCART
M_CARDTYPE
27
M_CONTACT
M_ITEMSOFPRODUCT
28
M_PRODUCTITEMDETAILS
M_LOGIN
M_PRODUCTS
29
M_SHIPPING
M_SOLDPRODUCTS
30
C.SAMPLE CODE:
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class adminlogin : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
if (TextBox1.Text =="admin" && TextBox2.Text =="admin")
{
Response.Redirect("~/admin/welcome.aspx");
}
31
}
}
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;
using System.Data.SqlClient;
public partial class BharathExp : System.Web.UI.Page
{
SqlCommand
con
=
SqlCommand(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlDataAdapter da;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
32
new
}
protected void GridView1_RowEditing(object sender, GridViewEditEventArgs e)
{
}
protected void GridView1_RowDeleting(object sender, GridViewDeleteEventArgs e)
{
}
protected
void
GridView1_RowCancelingEdit(object
sender,
GridViewCancelEditEventArgs e)
{
}
protected void GridView1_RowUpdating(object sender, GridViewUpdateEventArgs e)
{
}
}
using System;
using System.Collections;
using System.Configuration;
using System.Data;
33
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;
using System.Data.SqlClient;
public partial class BharathExp : System.Web.UI.Page
{
SqlCommand
con
=
SqlCommand(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlDataAdapter da;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void GridView1_RowEditing(object sender, GridViewEditEventArgs e)
{
}
34
new
protected void GridView1_RowDeleting(object sender, GridViewDeleteEventArgs e)
{
}
protected
void
GridView1_RowCancelingEdit(object
sender,
GridViewCancelEditEventArgs e)
{
}
protected void GridView1_RowUpdating(object sender, GridViewUpdateEventArgs e)
{
}
}
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
35
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class CustomerRegistration : System.Web.UI.Page
{
SqlConnection
con
=
new
SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlDataAdapter da;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
Label16.Text = Guid.NewGuid().ToString().Substring(0, 6);
if (con.State == ConnectionState.Closed)
{
con.Open();
}
}
protected void TextBox9_TextChanged(object sender, EventArgs e)
{
da = new SqlDataAdapter("select count(uname) from tbl_login where uname='" +
TextBox9.Text + "' ", con);
ds = new DataSet();
da.Fill(ds, "tbl_login");
36
if
(ds.Tables["tbl_login"].Rows.Count
==
1
&&
ds.Tables["tbl_login"].Rows[0][0].ToString() == "1")
{
Label17.Text = "Username is not Available.";
Label17.BackColor = System.Drawing.Color.Red;
TextBox9.Focus();
}
else
{
Label17.Text = "Username is Available.";
Label17.BackColor = System.Drawing.Color.Green;
TextBox10.Focus();
}
}
private int GetUid(string uname)
{
da
=
new
SqlDataAdapter("select
uid
from
tbl_login
uname.ToString() + "' ", con);
return Convert.ToInt32(da.SelectCommand.ExecuteScalar());
}
protected void Button1_Click(object sender, EventArgs e)
{
37
where
uname='"
+
if (Label17.Text == "Username is Available.")
{
da=newSqlDataAdapter("insertintotbl_login(uname,password,securitycode,status,cdate)value
s('" + TextBox9.Text + "','" + TextBox10.Text + "','" + TextBox11.Text +
"','Activate',getdate())", con);
da.SelectCommand.ExecuteNonQuery();
int uid = GetUid(TextBox9.Text);
if (uid > 0)
{
da
=
new
SqlDataAdapter("insert
into
tbl_contact(uid,fname,lname,gender,email,city,state,country,mobileno,cdate)values(" + uid +
",'" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text
+ "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "','" +
TextBox8.Text + "',getdate())", con);
int n=da.SelectCommand.ExecuteNonQuery();
if (n == 1)
{
Response.Redirect("~/Userlogin.aspx");
}
}
}
else
{
Label1.Text = "The Username is already taken.Choose another Name.";
Label1.BackColor = System.Drawing.Color.Red;
}
38
}
}
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class e_Business : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
}
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
39
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class MasterPage : System.Web.UI.MasterPage
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
Response.Redirect("~/Home.aspx");
}
protected void Button2_Click(object sender, EventArgs e)
{
Response.Redirect("~/Contactus.aspx");
}
protected void Button4_Click(object sender, EventArgs e)
{
Response.Redirect("~/UserLogin.aspx");
}
protected void Button5_Click(object sender, EventArgs e)
40
{
Response.Redirect("~/salesmanlogin.aspx");
}
protected void Button6_Click(object sender, EventArgs e)
{
Response.Redirect("~/adminlogin.aspx");
}
}
<%@
Page
Language="C#"
AutoEventWireup="true"
MasterPageFile="~/MasterPage.master"
CodeFile="UserLogin.aspx.cs"
Inherits="UserLogin"
Title="Customer login" %>
<asp:Content
ID="Content1"
ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div style="text-align: left">
<table style="width: 1107px; position: static; height: 100px; margin-right: 141px;">
<tr>
<td align="center" colspan="3" valign="top">
<strong>User Login</strong></td>
</tr>
<tr>
<td align="center" colspan="3" valign="top">
<asp:Label
ID="Label1"
runat="server"
ForeColor="#FF8080" Height="28px"
Style="position: static" Width="424px"></asp:Label></td>
</tr>
41
Font-Bold="True"
<tr>
<td style="height: 22px" align="center" colspan="3">
Username&nbsp;
:<asp:TextBox
ID="TextBox1"
runat="server"
Style="position: static"></asp:TextBox></td>
</tr>
<tr>
<td align="center" colspan="3">
Password&nbsp; :<asp:TextBox ID="TextBox2" runat="server" Style="position:
static" TextMode="Password"></asp:TextBox></td>
</tr>
<tr>
<td align="center" colspan="3">
<asp:Button ID="Button1" runat="server" Font-Bold="True" Style="position:
static"
Text="SignIn" OnClick="Button1_Click" />
</td>
</tr>
<tr>
<td style="width: 69px">
</td>
<td style="width: 100px">
</td>
<td style="width: 100px">
</td>
</tr>
42
<tr>
<td style="width: 69px">
New User ?</td>
<td style="width: 100px">
<asp:LinkButton
ID="LinkButton1"
runat="server"
Font-Bold="True"
Style=”position:static”Width="152px" PostBackUrl="~/CustomerRegistration.aspx">SignUp
Click here....</asp:LinkButton></td>
<td style="width: 100px">
</td>
</tr>
<tr>
<td colspan="3">
&nbsp;</td>
</tr>
<tr>
<td style="width: 800px; background-image: url('ads/background.JPG'); height:
1000px;"
colspan="3">
&nbsp;</td>
</tr>
</table>
</div>
</asp:Content>
43
D.INPUT SCREEN :
ONLINE PRODUCT SHOPPING PORTAL
44
ADMIN LOGIN:
45
USER REGISTRATION:
46
USER REVIEW:
47
E.OUTPUT SCREEN:
REVIEW FOR PRODUCTS(RECOMMENDATION):
48
GROUP SHILLING ATTACKERS DETAILS(AFTER DETECTION)
49