Privacy Policy Inference of User-Uploaded Images on

Content Sharing Sites

An Internship report submitted in partial fulfillment of the requirement
for the Award of the Degree

BACHELOR OF ENGINEERING

in

COMPUTER SCIENCE AND ENGINEERING

by
Gangaram Sreeya (160714733061)
Yeruva Sravya(160714733064)
Ch.Vatsalya Pooja(160714733084)

Under the Guidance of

Mr.R. Sandeep, Assistant Professor, Dept. of CSE

Department of Computer Science and Engineering

Methodist College of Engineering and Technology
King Koti, Abids, Hyderabad-500001.
2019-2020
 Methodist College of Engineering and Technology,
King Koti, Abids, Hyderabad-500001,

Department of Computer Science and Engineering

DECLARATION BY THE CANDIDATES

We, Gangaram Sreeya(160714733061), Yeruva Sravya(160714733064) and Ch.Vatsalya

Pooja(160714733084) students of Methodist College of Engineering and Technology, pursuing
Bachelor’s degree in Computer Science and Engineering, hereby declare that this internship
report entitled “Privacy Policy Inference of User-Uploaded Images on Content Sharing
Sites", carried out under the guidance of Mr.R. Sandeep submitted in partial fulfillment of the
requirements for the degree of Bachelor of Engineering in Computer Science. This is a record
work carried out by us and the results embodied in this report have not been reproduced/copied
from any source.

Gangaram Sreeya (160714733061)

Yeruva Sravya (160714733064)
Ch.Vatsalya Pooja(160714733084)
 Methodist College of Engineering and Technology,
King Koti, Abids, Hyderabad-500001.

Department of Computer Science and Engineering

CERTIFICATE BY THE SUPERVISOR

This is to certify that this Internship report entitled “Privacy Policy Inference of User-Uploaded
Images on Content Sharing Sites” being submitted by Gangaram Sreeya(160714733061), Yeruva
Sravya (160714733064) and Ch.Vatsalya Pooja (160714733084), submitted in partial fulfillment of
the requirements for the degree of Bachelor of Engineering in Computer Science and Engineering,
during the academic year 2019-2020, is a bonfide record of work carried out by them.

Mr. R. Sandeep
Assistant Professor,

Date:
 Methodist College of Engineering and Technology,
King Koti , Abids , Hyderabad-500001.

Department of Computer Science and Engineering

CERTIFICATE BY THE HEAD OF THE DEPARTMENT

This is to certify that this Internship report entitled “PRIVACY POLICY INFERENCE OF
USER-UPLOADED IMAGES ON CONTENT SHARING SITES“ BY Gangaram
Sreeya(160714733061), Yeruva Sravya(160714733064), Ch.Vatsalya Pooja(160714733084),
submitted in partial fulfillment of the requirements for the degree of Bachelor of Engineering in
Computer Science and Engineering of the Osmania University, Hyderabad, during the academic
year 2019-2020, is a bonafide record of work carried out by them.

Mrs. P. Lavanya
Associate Professor,
DATE
 ACKNOWLEDGEMNTS

We would like to express our sincere gratitude to my Internship guide Mr. Sandeep R,
Assistant Professor, for giving us the opportunity to work on this topic. It would never be
possible for us to take this project to this level without his innovative ideas and his relentless
support and encouragement.

We would like to thank our Internship coordinator Mr. Sandeep R, Assistant Professor, who
helped us by being an example of high vision and pushing towards greater limits of achievement.

Our sincere thanks to Mrs. P. Lavanya, Associate Professor and Head of the Department of
Computer Science and Engineering, for her valuable guidance and encouragement which has
played a major role in the completion of the project and for helping us by being an example of
high vision and pushing towards greater limits of achievement.

We would like to express a deep sense of gratitude towards the Dr. G. Ravinder Reddy,
Principal, Methodist College of Engineering and Technology, for always being an inspiration
and for always encouraging us in every possible way.

We would like to express a deep sense of gratitude towards the Dr. Lakshmipathi Rao,
Director, Methodist College of Engineering and Technology, for always being an inspiration
and for always encouraging us in every possible way.

We are indebted to the Department of Computer Science & Engineering and Methodist College
of Engineering and Technology for providing us with all the required facility to carry our work
in a congenial environment. We extend our gratitude to the CSE Department staff for providing
us to the needful time to time whenever requested.

We would like to thank our parents for allowing us to realize our potential, all the support they
have provided us over the years was the greatest gift anyone has ever given us and also for
teaching us the value of hard work and education. Our parents has offered us with tremendous
support and encouragement, thanks to our parents for all the moral support and the amazing
opportunities they have given us over the years.
 ABSTRACT

With the increasing volume of images users share through social sites, maintaining privacy has
become a major problem, as demonstrated by a recent wave of publicized incidents where users
inadvertently shared personal information. In light of these incidents, the need of tools to help
users control access to their shared content is apparent. Toward addressing this need, we propose
an Adaptive Privacy Policy Prediction (A3P) system to help users compose privacy settings for
their images. We examine the role of social context, image content, and metadata as possible
indicators of user’s privacy preferences. We propose a two-level framework which according to
the user’s available history on the site, determines the available privacy policy for the user’s
images being uploaded. Our solution relies on an image classification framework for image
categories which may be associated with similar policies, and on a policy prediction algorithm to
automatically generate a policy for each newly uploaded image, also according to users’ social
features. Over time, the generated policies will follow the evolution of users’ privacy attitude.
 Contents

Abstract
Introduction……………………………………………………………….…..01
Design Analysis………………………………………………………………...05
3.1 System architecture………………………………………………………………….05
3.2 Data flow diagram…………………………………………………………………..06

3.3 Entity-Relationship Diagram………………………………………………………..07

3.4 Unified Modeling Language………………………………………………………..08
3.5 Use Case Diagram…………………………………………………………………..09

3.6 Class Diagram………………………………………………………………………10

3.7 Sequence Diagram…………………………………………………………………..11
3.8 Activity Diagram…………………………………………………………………….13

Implementation……………………………………………………………......14
4.1 Modules………………………………………………………………………………14
 4.2 Modules Description…………………………………………………………………14
4.2.1 System Construction Module………………………………………………14
4.2.2 Content-Based Classification………………………………………...….....14
4.2.3 Metadata –Based Classification……………………………………………15
4.2.4 Adaptive Policy Prediction………………………………………………...15

Graphical User Interface……………………………………………………..18

6.1 Input Design………………………………………………………………………….18
6.2 Output Design………………………………………………………………………..18
Testing………………………………………………………………………….20
7.1 System Testing……………………………………………………………………….20
7.2 Testing Methodologies………………………………………………………………20

7.2.1 Unit testing…………………………………………………………………20

7.2.2 Integration Testing…………………………………………………………20
7.2.3 User Acceptance Testing………………………..…………………………22

7.2.4 Test Cases…………………………………………………………………..22

7.3 Screenshots…………………………………………………………………………..23

Conclusion………………………………………………………………………..33
References………………………………………………………………………...34
Appendix A: Sample Code………………………………………………………36
Appendix C: Technologies Used………………………………………………...46
 List of Figures

Figure 3.1: System Architecture

Figure 3.2.1: DFD Level0
Figure 3.2.2: DFD Level1
Figure 3.3: E-r Diagram
Figure 3.5: Use Case Diagram
Figure 3.6: Class Diagram
Figure 3.7.1: Sequence Diagram for Upload
Figure 3.7.2: Sequence Diagram for Search
Figure 3.8.1: Activity diagram for User
Figure 3.8.2: Activity Diagram for Admin
Figure 7.3.1: Home Page
Figure 7.3.2: Admin Page
Figure 7.3.3: Admin Login Page
Figure 7.3.4: Admin Image Details page
Figure 7.3.5: Admin Images with Ranking Page
Figure 7.3.6: Admin-View Search History Page
Figure 7.3.7: Admin-View all users page
Figure7.3.8: User-View Profile Page

Figure 7.3.9: User-add image page

Figure 7.3.10: User-search page
Figure 7.3.11: User-Search based on Tag page

Figure 7.3.12: User- search based on Friends page

Figure 7.3.13: User-search based on metadata page
Figure 7.3.14: User-send friend request page
Figure 7.3.15: User-search other friends page
Figure 7.3.16: User-My search history page

Figure 7.3.17: User-recommend images to other friends page

Figure 7.3.18: User-view all friend requests page

Figure 7.3.19: User-set policies page
Figure 7.3.20: Registration form page
 List of Tables

Table 7.2.4.1: Image Upload

Table 7.2.4.2: Set Policies on Image
 1. INTRODUCTION
Images are now one of the key enablers of users’ connectivity. Sharing takes place
both among previously established groups of known people or social circles (e.g., Google+, Flickr or
Picasa), and also increasingly with people outside the users social circles, for purposes of social
discovery-to help them identify new peers and learn about peers interests and social surroundings.
However, semantically rich images may reveal content sensitive information. Consider a photo of a
student’s 2012 graduation ceremony, for example. It could be shared within a Google+ circle or
Flickr group, but may unnecessarily expose the students, family members and other friends. Sharing
images within online content sharing sites, therefore, may quickly lead to unwanted disclosure and
privacy violations. Further, the persistent nature of online media makes it possible for other users to
collect rich aggregated information about the owner of the published content and the subjects in the
published content .The aggregated information can result in unexpected exposure of one’s social
environment and lead to abuse of one’s personal information.
Most content sharing websites allow users to enter their privacy preferences.
Unfortunately, recent studies have shown that users struggle to set up and maintain such privacy
settings .One of the main reasons provided is that given the amount of shared information this
process can be tedious and error-prone. Therefore, many have acknowledged the need of policy
recommendation systems which can assist users to easily and properly configure privacy settings.
However, existing proposals for automating privacy settings appear to be inadequate to address the
unique privacy needs of images due to the amount of information implicitly carried within images,
and their relationship with the online environment wherein they are exposed. In this paper, we
propose an Adaptive Privacy Policy Prediction (A3P) system which aims to provide users a hassle
free privacy settings experience by automatically generating personalized policies.
The A3P system handles user uploaded images, and factors in the following criteria
that influence one’s privacy settings of images: The impact of social environment and personal
characteristics. Social context of users, such as their profile information and relationships with others
may provide useful information regarding users’ privacy preferences. For example, users interested
in photography may like to share their photos with other amateur photographers. Users who have
several family members among their social contacts may share with them pictures related to family
events. However, using common policies across all users or across users with similar traits may be
too simplistic and not satisfy individual preferences. Users may have

1
drastically different opinions even on the same type of images. For example, a privacy adverse
person may be willing to share all his personal images while a more conservative person may
just want to share personal images with his family members. In light of these considerations, it is
important to find the balancing point between the impact of social environment and users’
individual characteristics in order to predict the policies that match each individual’s needs.
Moreover, individuals may change their overall attitude toward privacy as time passes. In order
to develop a personalized policy recommendation system, such changes on privacy opinions
should be carefully considered.
The role of image’s content and metadata. In general, similar images often incur
similar privacy preferences, especially when people appear in the images. For example, one may
upload several photos of his kids and specify that only his family members are allowed to see
these photos. He may upload some other photos of landscapes which he took as a hobby and for
these photos, he may set privacy preference allowing anyone to view and comment the photos.
Analyzing the visual content may not be sufficient to capture users’ privacy preferences. Tags
and other metadata are indicative of the social context of the image, including where it was taken
and why and also provide a synthetic description of images, complementing the information
obtained from visual content analysis. Corresponding to the aforementioned two criteria, the
proposed A3P system is comprised of two main building blocks: A3P-Social and A3P-Core.
The A3P-core focuses on analyzing each individual user’s own images and
metadata, while the A3P-Social offers a community perspective of privacy setting
recommendations for a user’s potential privacy improvement. We design the interaction flows
between the two building blocks to balance the benefits from meeting personal characteristics
and obtaining community advice. To assess the practical value of our approach, we built a
system prototype and performed an extensive experimental evaluation. We collected and tested
over 5,500 real policies generated by more than 160 users. Our experimental results demonstrate
both efficiency and high prediction accuracy of our system. A preliminary discussion of the
A3P-core was presented in. In this work, we present an overhauled version of A3P, which
includes an extended policy prediction algorithm in A3P-core (that is now parameterized based
on user groups and also factors in possible outliers), and a new A3P-social module that develops
the notion of social context to refine and extend the prediction power of our system.

2
 DESIGN ANALYSIS

3.1 System Architecture:

Figure 3.1: System Architecture

3.2 Data Flow Diagram:

• A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modelling its process aspects.

• A DFD is often used as a preliminary step to create an overview of the system without
going into great detail, which can later be elaborated.

Figure 3.2.1: DFD Level0

Figure 3.2.2:DFD Level1

6
3.3 E-R Diagram:
An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how
“entities” such as people, objects or concepts relate to each other within a system. ER Diagrams
are most often used to design or debug relational databases in the fields of software engineering,
business information systems, education and research. Also known as ERDs or ER Models, they
use a defined set of symbols such as rectangles, diamonds, ovals and connecting lines to depict
the interconnectedness of entities, relationships and their attributes. They mirror grammatical
structure, with entities as nouns and relationships as verbs.

Figure 3.3:E-R Diagram

7
 Implementation

4.1 MODULES
This project consists of the following modules:
 System Construction Module

 Content-Based Classification

 Metadata-Based Classification

 Adaptive Policy Prediction

4.2 MODULES DESCSRIPTION

4.2.1 System Construction Module

The A3P system consists of two main components: A3P-core and A3P-social. The
overall data flow is the following. When a user uploads an image, the image will be first sent to
the A3P-core. The A3P-core classifies the image and determines whether there is a need to
invoke the A3P-social. In most cases, the A3P-core predicts policies for the users directly based
on their historical behavior. If one of the following two cases is verified true, A3P-core will
invoke A3Psocial: (i) The user does not have enough data for the type of the uploaded image to
conduct policy prediction; (ii) The A3P-core detects the recent major changes among the user’s
community about their privacy practices along with user’s increase of social networking
activities (addition of new friends, new posts on one’s profile etc).

4.2.2 Content-Based Classification

To obtain groups of images that may be associated with similar privacy preferences,
we propose a hierarchical image classification which classifies images first based on their contents
and then refine each category into subcategories based on their metadata. Images that do not have
metadata will be grouped only by content. Such a hierarchical classification gives a higher priority to
image content and minimizes the influence of missing tags. Note that it is

14
possible that some images are included in multiple categories as long as they contain the typical
content features or metadata of those categories.
Our approach to content-based classification is based on an efficient and yet accurate image
similarity approach. Specifically, our classification algorithm compares image signatures defined
based on quantified and sanitized version of transformation. For each image, the wavelet
transform encodes frequency and spatial information related to image color, size, invariant
transform, shape, texture, symmetry, etc. Then, a small number of coefficients are selected to
form the signature of the image. The content similarity among images is then determined by the
distance among their image signatures.

4.2.3 Metadata-Based Classification

The metadata-based classification groups images into subcategories under aforementioned
baseline categories. The process consists of three main steps. The first step is to extract keywords
from the metadata associated with an image. The metadata considered in our work are tags,
captions, and comments. The second step is to derive a representative hypernym (denoted as h)
from each metadata vector. The third step is to find a subcategory that an image belongs to. This
is an incremental procedure. At the beginning, the first image forms a subcategory as itself and
the representative hypernyms of the image becomes the subcategory’s representative hypernyms.

4.2.4 Adaptive Policy Prediction

The policy prediction algorithm provides a predicted policy of a newly uploaded image to the
user for his/her reference. More importantly, the predicted policy will reflect the possible
changes of a user’s privacy concerns. The prediction process consists of three main phases: (i)
policy normalization; (ii) policy mining; and (iii) policy prediction
 GRAPHICAL USER INTERFACE

6.1 Input Design

Input Design plays a vital role in the life cycle of software development, it
requires very careful attention of developers. The input design is to feed data to the application
as accurate as possible. So inputs are supposed to be designed effectively so that the errors
occurring while feeding are minimized. According to Software Engineering Concepts, the input
forms or screens are designed to provide to have a validation control over the input limit, range
and other related validations.

This system has input screens in almost all the modules. Error messages are
developed to alert the user whenever he commits some mistakes and guides him in the right way
so that invalid entries are not made. Let us see deeply about this under module design.

Input design is the process of converting the user created input into a computer-
based format. The goal of the input design is to make the data entry logical and free from errors.
The error is in the input are controlled by the input design. The application has been developed in
user-friendly manner. The forms have been designed in such a way during the processing the
cursor is placed in the position where must be entered. The user is also provided with in an
option to select an appropriate input from various alternatives related to the field in certain cases.

Validations are required for each data entered. Whenever a user enters an
erroneous data, error message is displayed and the user can move on to the subsequent pages
after completing all the entries in the current page.

6.2 OUTPUT DESIGN

The Output from the computer is required to mainly create an efficient method of
communication within the company primarily among the project leader and his team members, in
other words, the administrator and the clients. The output of VPN is the system which allows the
project leader to manage his clients in terms of creating new clients and assigning new projects to
them, maintaining a record of the project validity and providing folder level access to each client

18
on the user side depending on the projects allotted to him. After completion of a project, a new
project may be assigned to the client. User authentication procedures are maintained at the initial
stages itself. A new user may be created by the administrator himself or a user can himself
register as a new user but the task of assigning projects and validating a new user rests with the
administrator only.

The application starts running when it is executed for the first time. The server
has to be started and then the internet explorer in used as the browser. The project will run on the
local area network so the server machine will serve as the administrator while the other
connected systems can act as the clients. The developed system is highly user friendly and can be
easily understood by anyone using it even for the first time.

19
 TESTING

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

7.2 Testing Methodologies:

The following are the Testing Methodologies:
• Unit Testing.
• Integration Testing.
• User Acceptance Testing.
• Output Testing.
• Validation Testing.

7.2.1 Unit Testing

Unit testing focuses verification effort on the smallest unit of Software design that
is the module. Unit testing exercises specific paths in a module’s control structure to ensure
complete coverage and maximum error detection. This test focuses on each module individually,
ensuring that it functions properly as a unit. Hence, the naming is Unit Testing.
During this testing, each module is tested individually and the module interfaces
are verified for the consistency with design specification. All important processing path are
tested for the expected results. All error handling paths are also tested.

20
7.2.2 Integration Testing

Integration testing addresses the issues associated with the dual problems of
verification and program construction. After the software has been integrated a set of high order
tests are conducted. The main objective in this testing process is to take unit tested modules and
builds a program structure that has been dictated by design. The following are the types of
Integration Testing:
1. Top Down Integration
This method is an incremental approach to the construction of program structure.
Modules are integrated by moving downward through the control hierarchy, beginning with the
main program module. The module subordinates to the main program module are incorporated
into the structure in either a depth first or breadth first manner.
2. Bottom-up Integration
This method begins the construction and testing with the modules at the lowest
level in the program structure. Since the modules are integrated from the bottom up, processing
required for modules subordinate to a given level is always available and the need for stubs is
eliminated. The bottom up integration strategy may be implemented with the following steps:

• The low-level modules are combined into clusters into clusters that perform a specific
Software sub-function.

• A driver (i.e.) the control program for testing is written to coordinate test case input and
output.
• The cluster is tested.

7.2.3 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 user acceptance by constantly keeping in touch with the
prospective system users at the time of developing and making changes wherever required. The
system developed provides a friendly user interface that can easily be understood even by a
person who is new to the system.

21
7.3 Screenshots

Figure 7.3.1:HomePage

Figure 7.3.2:Admin Page

23
Figure 7.3.3: Admin Login Page

Figure 7.3.4: Admin Image Details

24
Figure 7.3.5:Admin images with Ranking

Figure 7.3.6: Admin-View Search History

25
Figure 7.3.7:Admin-view all users

Figure 7.3.8: User-View Profile

26
Figure 7.3.9: User-Add Image
 CONCLUSION
We have proposed an Adaptive Privacy Policy Prediction (A3P) system that helps
users automate the privacy policy settings for their uploaded images. The A3P system provides a
comprehensive framework to infer privacy preferences based on the information available for a
given user. We also effectively tackled the issue of cold-start, leveraging social context
information. Our experimental study proves that our A3P is a practical tool that offers significant
Improvements over current approaches to privacy.

33
 REFERENCES

[1] A. Acquisti and R. Gross, “Imagined communities: Awareness, information sharing, and
privacy on the facebook,” in Proc. 6th Int. Conf. Privacy Enhancing Technol. Workshop, 2006,
pp. 36–58.
[2] R. Agrawal and R. Srikant,“Fast algorithms for mining association rules in large databases,”
in Proc. 20th Int. Conf. Very Large Data Bases, 1994, pp. 487–499.
[3] S. Ahern, D. Eckles, N. S. Good, S. King, M. Naaman, and R. Nair, “Over-exposed?: Privacy
patterns and considerations in online and mobile photo sharing,” in Proc. Conf. Human Factors
Comput. Syst., 2007, pp. 357–366.
[4] M. Ames and M. Naaman, “Why we tag: Motivations for annotation in mobile and online
media,” in Proc. Conf. Human Factors Comput. Syst., 2007, pp. 971–980.
[5] A. Besmer and H. Lipford, “Tagged photos: Concerns, perceptions, and protections,” in Proc.
27th Int. Conf. Extended Abstracts Human Factors Comput. Syst., 2009, pp. 4585–4590.
[6] D. G. Altman and J. M. Bland ,“Multiple significance tests: The bonferroni method,” Brit.
Med. J., vol. 310, no. 6973, 1995.
[7] J. Bonneau, J. Anderson, and L. Church, “Privacy suites: Shared privacy for social networks,”
in Proc. Symp. Usable Privacy Security, 2009.
[8] J. Bonneau, J. Anderson, and G. Danezis, “Prying data out of a social network,” in Proc. Int.
Conf. Adv. Soc. Netw. Anal. Mining., 2009, pp.249–254.
[9] H.-M. Chen, M.-H. Chang, P.-C. Chang, M.-C. Tien, W. H. Hsu, and J.-L. Wu, “Sheepdog:
Group and tag recommendation for flickr photos by automatic search-based learning,” in Proc.
16th ACM Int. Conf. Multimedia, 2008, pp. 737–740.
[10] M. D. Choudhury, H. Sundaram, Y.-R. Lin, A. John, and D. D. Seligmann, “Connecting
content to community in social media via image content, user tags and user communication,” in
Proc. IEEE Int. Conf. Multimedia Expo, 2009, pp.1238–1241.
[11] L. Church, J. Anderson, J. Bonneau, and F. Stajano, “Privacy stories: Confidence on privacy
behaviors through end user programming,” in Proc. 5th Symp. Usable Privacy Security, 2009.
[12] R. da Silva Torres and A. Falc~ao, “Content-based image retrieval: Theory and
applications,” Revista de Inform_atica Te_orica e Aplicada, vol. 2, no. 13, pp. 161–185, 2006.
 APPENDIX - A

Sample code

Add_image.jsp

<!DOCTYPE html>

<html lang="en">

<head>

<title>PPI : Add Image page</title>

<meta charset="utf-8">

<link rel="stylesheet" href="css/reset.css"

type="text/css" media="screen">

<link rel="stylesheet" href="css/style.css"

type="text/css" media="screen">

<link rel="stylesheet" href="css/layout.css" type="text/css"

media="screen">

<script type="text/javascript" src="js/jquery-1.6.min.js"></script>

<script src="js/cufon-yui.js" type="text/javascript"></script> <script
src="js/cufon-replace.js" type="text/javascript"></script> <script
src="js/Open_Sans_400.font.js" type="text/javascript"></script>
<script src="js/Open_Sans_Light_300.font.js"
type="text/javascript"></script>
<script src="js/Open_Sans_Semibold_600.font.js"
type="text/javascript"></script>

<script type="text/javascript" src="js/tms-0.3.js"></script> <script

type="text/javascript" src="js/tms_presets.js"></script> <script
type="text/javascript" src="js/jquery.easing.1.3.js"></script> <script
src="js/FF-cash.js" type="text/javascript"></script>

36
<!--[if lt IE 9]>

<script type="text/javascript" src="js/html5.js"></script>

<link rel="stylesheet" href="css/ie.css" type="text/css" media="screen">

<![endif]--></head>

<body id="page1">

<!-- header -->

<div class="bg">

<div class="main">

<header>

<div class="row-1">

<h1 style="width:600px;"> <span class="slog">Privacy Policy

Inference of User-Uploaded Images on Content Sharing Sites</span> </h1>

<form id="search-form" action="#" method="post"

enctype="multipart/form-data">

<fieldset>

<div class="search-form">

<input type="text" name="search" value="Type Keyword

Here" onBlur="if(this.value=='') this.value='Type Keyword Here'"
onFocus="if(this.value =='Type Keyword Here' ) this.value=''" />

<a href="#">Search</a> </div>

</fieldset>

</form>

</div>

</header>

<!-- content -->

<section id="content">

<div class="padding">
 APPENDIX B
Software and Hardware Requirements

Software Requirements

Operating System : Windows Family

Technology : Java , J2EE(JSP, Servlet, Java Bean)

Web Technologies : Html, JavaScript, CSS

IDE : Net Beans

Web Server : Tomcat 7.0

Database : My SQL

Java Version : 1.7

Hardware Requirements

Hardware : Pentium IV 3.4 GHz.

Floppy Drive : 1.44Mb

RAM : 1GB

Hard Disk : 40 GB

45
 APPENDIX - C
Technology Used
JAVA

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

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

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

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.

Tomcat 7.0 web server

Tomcat is an open source web server developed by Apache Group. Apache Tomcat is
the servlet container that is used in the official Reference Implementation for the Java Servlet and
JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed
by Sun under the Java Community Process. Web Servers like Apache Tomcat support

47
only web components while an application server supports web components as well as business
components (BEAs Weblogic, is one of the popular application server).To develop a web
application with jsp/servlet install any web server like JRun, Tomcat etc to run your application.

50