17-10-2016, 12:32 PM
1459409841-ImageInferencePartIII.docx (Size: 295.19 KB / Downloads: 8)
INTRODUCTION
1.1 AIM
Enable privacy in sharing image, text and video content in online content sharing content sharing.
1.2 OVERVIEW OF THE PROJECT
Images are now one of the key enablers of user’s connectivity, over social networksSo sharing takes place outside the user’s groups for purposes of identify new peers and their interest this may reveal user’s sensitive information to the unknowns. Most content sharing websites allow users to enter their privacy preferences. Recent studies have shown that users struggle to set up and maintain such privacy settings. Therefore, many have acknowledged the need of policy recommendation systems which can assist users to easily and properly configure privacy settings.Most content sharing websites allow users to enter theirprivacy preferences. Unfortunately, recent studies haveshown that users struggle to set up and maintain such privacysettings. One of the main reasonsprovided is that given the amount of shared informationthis process can be tedious and error-prone. Therefore,many have acknowledged the need of policy recommendationsystems which can assist users to easily and properlyconfigure privacy settings. However,existing proposals for automating privacy settings appearto be inadequate to address the unique privacy needs ofimages due to the amount of informationimplicitly carried within images, and their relationship withthe online environment wherein they are exposed.In this paper, we propose an Adaptive Privacy Policy Prediction(A3P) system which aims to provide users a hasslefree privacy settings experience by automatically generatingpersonalized policies.
EXISTING SYSTEM
2.1 SYSTEM DESCRIPTION
1. Existing system propose an Adaptive Privacy Policy Prediction(A3P) system which provides users with privacy settings experience by automatically generating personalized policies
2. The A3P-core classifies the image and determines whether there is a need to invoke the A3P-social
3. It groups users into social communities with similar social context and privacy preferences and continuously monitors the social groups.
4. It predicts policies for the users directly based on their historical behavior
2.2 DRAWBACKS
1. Image content analysis, for classification and interpretation add very huge work load to the process
2. It helps sharing only image content but today content sharing website share different multimedia contents
PROPOSED SYSTEM
3.1 SYSTEM DESCRIPTION
1. Heterogenetic Adaptive Privacy Policy Prediction (HA3P) system which generates content sharing policies automatically for privacy setting based on user behavior
2. Contents are classified based on the meta information and similar policy is fetched and recommended to newly uploaded images
3. After user approval the policy is set to the uploaded multimedia content
4. We monitor the users behavior and create user groups with similar social context
5. The policy is updates whenever there is change in user behaviors
3.2 ADVANTAGES
1. Unlike existing system our proposed system helps different multimedia contents like image, text and videos
2. Users groups are created not only based on user profile attribute but also based on user behaviour which increase the policy preferences
SYSTEM ANALYSIS
System analysis is a process of examining business situation with intend of improving it through better procedure and methods. It is the process of gathering and interpreting facts, diagnosing the problems and using the information to recommend improvement to the system. Analysis is a detailed study of the various operations performed by the system and their recovering within and outside the system.
4.1 HARDWARE SPECIFICATIONS
Hard Disk - 80GB
RAM - 512mb
Processor - Pentium IV or higher
Monitor - 15”EQB/G
Keyboard - 104 Keys
Ethernet card - 1Mbps Ethernet card
4.2 SOFTWARE SPECIFICATIONS
Front-end - ASP.NET
Back-end - MS SQL server
IDE - Visual Studio 2005
Operating System - Windows XP
FEATURES OF THE COMMON LANGUAGE RUNTIME
The common language runtime provides an execution environment that manages the set of code targeted to the .NET Framework. Code management can include memory management, thread management, security management, code verification, and compilation of the code. All managed components must first be assigned a level of trust. The level or degree of trust can vary on the basis of the following origins:
Local computer
Internet connection
Enterprise local area network (LAN) connection
The common language runtime also uses a common type system (CTS) to enforce code robustness and language interoperability.
The common language runtime also should increase application performance. This may be accomplished in two ways: just in time (JIT) compliers and server side applications. The JIT compilers are used to compile all managed code to native machine binary code at execution.
Server side applications can house application logic and business rules on .NET Enterprise Servers such as Internet Information Server (IIS) and SQL Server.
4.3.2 NET FRAMEWORK CLASS LIBRARY
The .NET Framework class library is a collection of reusable classes, or types, that tightly integrate with the common language runtime. .NET applications benefit from using and extending or inheriting the functionality from the classes and types available in the class library. The class library is very hierarchical and well organized, as shown in Figure 4.2. It starts with the most generic classes and continues to build down to classes with very specific and precise functionality. Although this library is extensive, its organization makes it easy to learn and use. In an age of ever growing technology it is refreshing to see a new technology and a new architecture that promise a reduced learning curve.
This model also makes it easy for third party components to be integrated easily with the existing class library.
As expected in an object oriented class library, the .NET Framework classes enable developers to accomplish rapidly a wide range of common programming tasks, including things such as string management, file access, and database connectivity. Also, several classes facilitate highly specialized and custom development environments. These classes make the application development environment very flexible. The following types of applications are readily supported through the .NET Framework:
ASP.NET applications
Console applications
Windows applications (Windows Forms)
Web services
For example, the Windows Forms classes are used to create Windows graphical user interface (GUI) applications, which often are referred to as standalone applications. This is facilitated through a series of reusable graphical interface classes. Alternatively, in developing a Web based application, the HTML and Web Forms classes facilitate its rapid development. Either way the underlying framework provides the flexibility for feature rich applications regardless of the choice of application environment.
CLIENT APPLICATION DEVELOPMENT
Client applications represent the most common application environment in use today. These are the applications that one would invoke by opening some type of form and initiating an action. Examples of client applications range from word processing applications to a customized accounting package.
The traditional Windows programming environment has been replaced in .NET by the Windows Forms control. The managed Windows Forms control allows the application to be deployed over the Internet, and the user can view the application as a Web page. In the past developers created such applications by using C or C++ in conjunction with the Microsoft Foundation Classes (MFC) or with a rapid application development (RAD) environment such as Microsoft Visual Basic. The .NET Framework incorporates aspects of the earlier products into a single, consistent development environment. The goal of the single environment is to simplify the development of client applications.
Each object and Web server may have security rights different from those of another server. All security rights are evaluated even though the objects are used within a single application. Windows Forms applications still have some advantages over Web based applications. Windows Forms applications have a level of trust that is already assumed. This allows binary and natively executing code to interact with some of the resources on the local machine. This is used to perform the necessary GUI elements of the application.
ABOUT C# PROGRAMMING
C# is Microsoft’s programming language for its new .NET development environment. Microsoft’s goal with C# is to provide a simple, modern, object oriented .NET programming language that is Internet centric.
Although .NET code can be written in many languages, C# is the only language designed specifically for the .NET platform and for that reason may become the language of choice for this environment. C# may be deceptively simple. Although it has only about 80 keywords and a dozen intrinsic data types, it is highly expressive. It includes support for all types of modern component based, object oriented development.
C#, like C++ and Java, owes its origins to the C programming language. For that reason, C++ and Java developers will notice a striking similarity to those languages and enjoy an easy to learn and familiar programming environment. Specifically, C# is an elegant language object oriented language that:
Readily supports the definition of and working with classes and their properties and methods.
Supports the implementation of interfaces, or contracts, to implement functionality. While a class can only inherit, or extend, from a single class, it can implement multiple interfaces.
Supports struts, which are lightweight custom types that require fewer resources than does a more complex, robust type defined as a class.
The common language runtime now features a garbage collector, a process responsible for removing objects from memory that no longer have references to them. The developer is freed from the tedious and often fruitless activity of trying to assure that all objects have been destroyed.
4.3.3 ASP.NET:
ASP.NET is a Web application framework developed and marketed by Microsoft to allow programmers to build dynamic Web sites, Web applications and Web services.
It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages.
ASP.NET Web pages, known officially as Web Forms, are the main building block for application development. Web forms are contained in files with an ".aspx" extension; these files typically contain static (X)HTML markup, as well as markup defining server-side Web Controls and User Controls where the developers place all the required static and dynamic content for the Web page.
Additionally, dynamic code which runs on the server can be placed in a page within a block <% -- dynamic code -- %>, which is similar to other Web development technologies such as PHP, JSP, and ASP. With ASP.NET Framework 2.0, Microsoft introduced a new code-behind model which allows static text to remain on the .aspx page, while dynamic code remains in an .aspx.vb or .aspx.cs or .aspx.fs file (depending on the programming language used).
4.3.4 STRUCTURAL QUERY LANGUAGE
The SQL language is sub-divided into several language elements, including: Clauses, which are constituent components of statements and queries. (In some cases, these are optional.) Expressions, which can produce either scalar values or tables consisting of columns and rows of data.Predicates, which specify conditions that can be evaluated to SQL three-valued logic (3VL) or Boolean (true/false/unknown) truth values and which are used to limit the effects of statements and queries, or to change program flow. Queries, which retrieve the data based on specific criteria. This is the most important element of SQL. Statements, which may have a persistent effect on schemata and data, or which may control transactions, program flow, connections, sessions, or diagnostics. SQL statements also include the semicolon (";") statement terminator. Though not required on every platform, it is defined as a standard part of the SQL grammar. Insignificant whitespace is generally ignored in SQL statements and queries, making it easier to format SQL code for readability.
The most common operation in SQL is the query, which is performed with the declarative SELECT statement. SELECT retrieves data from one or more tables, or expressions. Standard SELECT statements have no persistent effects on the database. Some non-standard implementations of SELECT can have persistent effects, such as the SELECT INTO syntax that exists in some databases. Queries allow the user to describe desired data, leaving the database management system (DBMS) responsible for planning, optimizing, and performing the physical operations necessary to produce that result as it chooses. A query includes a list of columns to be included in the final result immediately following the SELECT keyword. An asterisk ("*") can also be used to specify that the query should return all columns of the queried tables. SELECT is the most complex statement in SQL, with optional keywords and clauses that include:
The FROM clause which indicates the table(s) from which data is to be retrieved. The FROM clause can include optional JOIN sub clauses to specify the rules for joining tables. The WHERE clause includes a comparison predicate, which restricts the rows returned by the query. The WHERE clause eliminates all rows from the result set for which the comparison predicate does not evaluate to True.
The GROUP BY clause is used to project rows having common values into a smaller set of rows. GROUP BY is often used in conjunction with SQL aggregation functions or to eliminate duplicate rows from a result set. The WHERE clause is applied before the GROUP BY clause. The HAVING clause includes a predicate used to filter rows resulting from the GROUP BY clause. Because it acts on the results of the GROUP BY clause, aggregation functions can be used in the HAVING clause predicate.
The ORDER BY clause identifies which columns are used to sort the resulting data, and in which direction they should be sorted (options are ascending or descending). Without an ORDER BY clause, the order of rows returned by an SQL query is undefined. Microsoft SQL Server 2000 automatically tunes many of the server configuration options, therefore requiring little, if any, tuning by a system administrator. Although these configuration options can be modified by the system administrator, it is generally recommended that these options be left at their default values, allowing SQL Server to automatically tune itself based on run-time conditions.
However, if necessary, the following components can be configured to optimize server performance
• SQL Server Memory
• I/O subsystem
• Microsoft Windows NT options
Indexes are structured to facilitate the rapid return of result sets. The two types of indexes that SQL Server supports are clustered and non-clustered indexes. Indexes are applied to one or more columns in tables or views. The characteristics of an index affect its use of system resources and its lookup performance. The Query Optimizer uses an index if it will increase query performance.
An index in SQL Server assists the database engine with locating records, just like an index in a book helps you locate information quickly. Without indexes, a query causes SQL Server to search all records in a table (table scan) in order to find matches. A database index contains one or more column values from a table (called the index key) and pointers to the corresponding table records. When you perform a query using the index key, the Query Optimizer will likely use an index to locate the records that match the query.
A B-tree is analogous to an upside-down tree with the root of the tree at the top, the leaf levels at the bottom, and intermediate levels in between. Each object in the tree structure is a group of sorted index keys called an index page. A B-tree facilitates fast and consistent query performance by carefully balancing the width and depth of the tree as the index grows. Sorting the index on the index key also improves query performance. All search requests begin at the root of a B-tree and then move through the tree to the appropriate leaf level. The number of table records and the size of the index key affect the width and depth of the tree. Index key size is called the key width. A table that has many records and a large index key width creates a deep and wide B-tree. The smaller the tree, the more quickly a search result is returned.
SQL SERVER TABLES
SQL Server stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database.
PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely identifies each record in the table. The Unique identifier is called the Primary Key, or simply the Key. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database.
RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be stored in one table. SQL Server makes it very easy to link the data in multiple tables. Matching an employee to the department in which they work is one example. This is what makes SQL Server a relational database management system, or RDBMS. It stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables.
FOREIGN KEY
When a field is one table matches the primary key of another field is referred to as a foreign key. A foreign key is a field or a group of fields in one table whose values match those of the primary key of another table.
REFERENTIAL INTEGRITY
Not only does SQL Server allow you to link multiple tables, it also maintains consistency between them. Ensuring that the data among related tables is correctly matched is referred to as maintaining referential integrity.
DATA ABSTRACTION
A major purpose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. Data abstraction is divided into three levels. Physical level: This is the lowest level of abstraction at which one describes how the data are actually stored. Conceptual Level: At this level of database abstraction all the attributed and what data are actually stored is described and entries and relationship among them. View level: This is the highest level of abstraction at which one describes only part of the database.
ADVANTAGES OF RDBMS
• Redundancy can be avoided
• Inconsistency can be eliminated
• Data can be Shared
• Standards can be enforced
• Security restrictions ca be applied
• Integrity can be maintained
• Conflicting requirements can be balanced
• Data independence can be achieved.
DISADVANTAGES OF DBMS
A significant disadvantage of the DBMS system is cost. In addition to the cost of purchasing of developing the software, the hardware has to be upgraded to allow for the extensive programs and the workspace required for their execution and storage. While centralization reduces duplication, the lack of duplication requires that the database be adequately backed up so that in case of failure the data can be recovered.
4.3.5 FEATURES OF SQL SERVER (RDBMS)
SQL SERVER is one of the leading database management systems (DBMS) because it is the only Database that meets the uncompromising requirements of today’s most demanding information systems. From complex decision support systems (DSS) to the most rigorous online transaction processing (OLTP) application, even application that require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the industry in both performance and capability
SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched performance, continuous operation and support for every database.SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed for online transactions processing and for handling large database application. SQL SERVER with transactions processing option offers two features which contribute to very high level of transaction processing throughput, which are the row level lock manager