banktrace

7/28/2019 banktrace

1/31

Co-Operative Provalable Data Possession For Integrity Verification In Multi-Cloud Storage

1. INTRODUCTION

1.1 PURPOSE

The advancement in Information technology and Internet penetration has greatly enhanced

various business processes and communication between companies and customers of which

car industry is not left out. The Online Car Club is developed to provide tools through which

users can search for available new cars online prior to purchase them.

1.2 SCOPE

Develop and deliver a new Web 2.0 website which will allow users to access and view the

information of various cars.

Ease of search.

Time saving

Giving comfort to the user to get the car information Online by reducing their

physical work.

1.3 Aim of Project

Possession for Integrrty Verification in Multi-Cloud Storage. Provable data possession(pdp)

is a provider to cooperatively store and maintain the clients data.

To ensure that the system achieves privacy protection.

To store and maintain clients data in multiple cloud system.

To provides hybrid cloud storage system.

PAHER UNIVERSITY Dept. Of MCA jan-june 2013

7/28/2019 banktrace

2/31


2. LITERATURE SURVEY

2.1 EXISTING SYSTEM (DRAWBACKS)

Most of the people still prefer to visit the agencies authorized by different car makers that

really is a tedious job and causes difficulties to people. Whereas using the manual way the

user has to fill in the provided form and give the necessary details. Problems that had been

identified in the current system are:

Customers having difficulty making a registration because of the manual system the

company was using.

Mistakes in giving right car information to the correct customer due to data

redundancies that occurred because of the manual way.

Misunderstandings of the customers actual need.

Keeping track of cars is a bit difficult to be done since it is using manual way.

Inconvenient searching.

Tedious job of enquiring your car.

Time consuming.

Information overload.


7/28/2019 banktrace

3/31


2.2 PROPOSED SYSTEM

Through our website the admin can add cars, update information, edit information and user

can search the cars and compare their features. User friendly interface is the primary way the

systems interact with the user and allow him or her to interact with. This will reduce the

work-load and paper work will reduce the manual work.

Saves time for user.

The major advantage of this application is that it uses the data available in theinternet.

Provides a common platform to get informations of different cars.

Provides budget based searching besides the search by brand and model name.

Provide comparison and recommendations for different cars with the similar features.

The online system will maintain all the record at each level. It will help the user toretrieve the valuable information whenever needed. Every data will be stored in the

computer memory to reduce the space being used.

The new system will take less time in entering the data, processing it and getting its

output. Fewer resources will be used as no large registers, files, Ledgers, pens;

correctors will be needed or used. Therefore, less time will be taken to process the

data that will help to do more jobs in less time.

2.3 Features of Distributed Storage Environment: Usability aspect: In the way of collaboration, a client should utilize

the integrity check in a distributed cloud storage system.

Security aspect : Our scheme should provide adequate security

features to resist some existing attacks..

Performance aspect: Our scheme should have the lower

communication and computation overheads than non-cooperative

solution.


7/28/2019 banktrace

4/31


3. HARDWARE & SOFTWARE REQUIREMENTS

3.1 HARDWARE REQUIREMENTS

Minimum 512 MB of RAM

Minimum 40 GB of HARD DISK

Processor Intel Pentium 4

Operating System :Windows XP and above

3.2 SOFTWARE REQUIREMENTS

Apache Tomcat Server and upper

Jdk 1.7

Jre

4. SOFTWARE REQUIREMENTS SPECIFICATION

4.1 FUNCTIONAL REQUIREMENTS


7/28/2019 banktrace

5/31


Requirement analysis is a software engineering technique [1] that is composed of the various

tasks that determine the needs or conditions that are to be met for a new or altered product,

taking into consideration the possible conflicting requirements of the various users.

Functional requirements are those requirements that are used to illustrate the internal working

nature of the system, the description of the system, and explanation of each subsystem. It

consists of what task the system should perform, the processes involved, which data should

the system holds and the interfaces with the user. The functional requirements identified are:

Search: Customer can search for a particular car online.

Technical Specification: customer can see the technical details of

selected car.

Features: customer can see the features of selected car.

Accessories: customer can see the Accessories of selected car.

4.2 NON-FUNCTIONAL REQUIREMENTS

It describes aspects of the system that are concerned with how the system provides the

functional requirements. They are:

Performance and Response time:

The system should have high performance rate when executing users

input and should be able to provide feedback or response within a short

time span usually 50 seconds for highly complicated task and 20 to25seconds for less complicated task.

Availability:

This system should always be available for access at 24 hours, 7 days a

week. Also in the occurrence of any major system malfunctioning, the

system should be available in 1 to 2 working days, so that the business

process is not severely affected.

Reliability: It provides an assured way to search a car.


7/28/2019 banktrace

6/31


Efficient: It provides a fast and easy way to search for cars.

Usability: The system provides an easy way to use Interface with the

different modules.

Maintainability: Changes can be made to the System.

4.3 USERS OF THE SYSTEM

User (Who can upload file)

TPA (who provide security and Upload data on cloud)

Admin (who allow data to upload on cloud)

User

The user is a person who can upload his file on cloud and can manage his file.


7/28/2019 banktrace

7/31


Tpa

Its Third party authentication which is provide data security to user and upload data on

different different cloud.

ADMIN

The Admin is a person or server which can only see the uploaded file or data by tpa on his

server and can allow to update this file on his cloud.

He is unable to change or delete data which upload by tpa.

SYSTEM DESIGN

Data Flow Diagram / Use Case Diagram / Flow Diagram

The DFD is also called as bubble chart. It is a simple graphical formalism that

can be used to represent a system in terms of the input data to the system, various processing

carried out on these data, and the output data is generated by the system.

SYSTEM DESIGN :( Admin)


7/28/2019 banktrace

8/31


Check

unauthorized user

Yes No

View New Files

Maintain All Files Details

End Process

Allow New Files

CLOUD ADMIN

User


7/28/2019 banktrace

9/31


Check

unauthorized user

Yes No

Upload Files

Download Files

End Process

Update Files

USER

TPA


7/28/2019 banktrace

10/31


Check

unauthorized user

Yes No

View New Files

End Process

Upload To Cloud

TPA

View File Alerts

User Case Diagram


7/28/2019 banktrace

11/31


User FIle Upload

ADMIN

USER

View File Blocks

Upload to Multi Cloud

Update Files

View Modification Alert

View All Alerts

TPA

Allow User F iles

Download Files

View All Files

Class Diagram


7/28/2019 banktrace

12/31


Login()_

User namePassword

check valid()unvalid()

USER login()

Upload FilesUpdate FilesDownload Files

User process()

ADMIN login()

View New FilesAllow New FilesMaintain All Files Details

ADMIN process()

TPA login()

View File BlocksUpload to Multi CloudView File AlertsView All File Alerts

TPA process()

Activity Diagram


7/28/2019 banktrace

13/31


Uload Files

View Files

Update Files

View New Files

Main File Details

ADMIN LOGIN

Start

End Process

Allow New Files

Downlaod Files

USER LOGIN

TPA LOGIN

View New Files

Upload To Multi cloud

View File Alerts

All File Alerts

Sequence Diagram


7/28/2019 banktrace

14/31


5. IMPLEMENTATION


UserAdmin

Cloud

Tpa

File Upload

View New Files

Upload Tp Multi Cloud

View New Files

Allow New Files

Update FilesView Files

View File Alerts

All File Alerts

Download Files

7/28/2019 banktrace

15/31


5.1 SCREEN SHOTS:-

5.1.1:-Home Page..

This page show when we Start the Project. Home page show all the content of project.

5.1.2:- User Register..


7/28/2019 banktrace

16/31


For Performing all the activity of project User must register. Thru this sign up page

User Can Register Our Self and then access the project.

5.1.2:- User Login..


7/28/2019 banktrace

17/31


If the user is already registered than he can access this project after Login Here.

Its an Entrance Of user.....

5.1.2:- User Home..

Its User Home Page Here U can see all info about user.

5.1.2:- User File Upload..


7/28/2019 banktrace

18/31


Thru this page User Can Choose His File and can upload it on server.

5.1.2:- User File View..

After Upload File will divide in three Parts so that user can safely upload his file on multi-

cloud.


7/28/2019 banktrace

19/31


5.1.2:- User File Updating..

The User also can update his file later when he update his file his file automatically

updated on server.

5.1.2:- Tpa Home..

After Login of tpa this Home page are shown. On this page all the file shows which is

uploaded by user on server and which is pending for uploading.


7/28/2019 banktrace

20/31


5.1.2:- Tpa Encrypt file..

When Tpa want to show the Upload page of admin than simply he can see this all info in

encrypt form After Decrypt the info using his Key he can see the info And allow to upload

file on server.


7/28/2019 banktrace

21/31


5.1.2:- Tpa Decrypt File..

The user upload file, tpa can see after Decrypt the file threw the file key.


7/28/2019 banktrace

22/31


5.1.2:- Admin Home..

This is the admin home page After Login of admin this page show. On this page Admin can

see all the information about user and his file which is successfully uploaded on server butonly that file which is tpa allow to upload on server.


7/28/2019 banktrace

23/31


5.1.2:- Admin All Files..

On this page All the file which is allowed by user to upload on his cloud are shown.


7/28/2019 banktrace

24/31


5.1.2:- Admin All Files..

Admin can see the file content which is uploaded by server to his cloud.

DATA BASE :-

In Our web side we use data base for access our web pages. In the web side we access all the

data from data base.


7/28/2019 banktrace

25/31


In our data base we use three table as four table user (For storing user information), Tpa (For

storing tpa information), Admin (For storing admin data) And file (For storing file data)

TESTING


7/28/2019 banktrace

26/31


Testing[1] is a process of executing a program with the intent of finding an error. A good test

case is one that has a high probability of finding an as-yet-undiscovered error. A successful

test is one that uncovers an as-yet-undiscovered error. Once source code is generated;

software must be tested to uncover (and correct) as many errors, as possible before delivering

to customer.

5.2 Testing Methodologies

The various testing done on the system are as follows:

Unit Testing

Integration Testing

Load Testing

Performance Testing

User Acceptance Testing

5.2.1 UNIT TESTING

Unit testing techniques are the strategy adopted during this project testing. Unit testing

focuses verification effort on the smallest unit of software design- the software component or

module. The unit test is white-box oriented. The module interface is tested to ensure that

information properly flows in and out of the program unit under test the local data structure

has been examined to ensure that data stored temporarily maintains its integrity during all

steps in an algorithms execution.

5.2.2 INTEGRATION TESTING

Integration testing is the phase of software testing in which individual software modules are

combined and tested as a group. It follows unit testing and precedes system testing.

Integration testing takes as its input modules that have been checked out by unit testing,

groups them in larger aggregates, applies tests defined in an Integration test plan to those

aggregates, and delivers as its output the integrated system ready for system testing.


7/28/2019 banktrace

27/31


5.2.3 LOAD TESTING

Load testing is a blanket term that is used in many different ways across the professional

software testing community.

Load testing generally refers to the practice of modelling the expected usage of a software

program by simulating multiple users accessing the program's services concurrently. When

the load placed on the system is accelerated beyond normal usage patterns, in order to test the

system's response at unusually high or peak loads, it is known as Stress testing. The load is

usually so great that error conditions are the expected result, although there is a gray area

between the two domains and no clear boundary exists where you could say that an activity

ceases to be a load test and becomes a stress test.

5.2.4 PERFORMANCE TESTING

Performance testing is testing that is performed to determine how fast some aspect of a

system performs under a particular workload.

Performance testing can serve different purposes. It can demonstrate that the system meets

performance criteria. It can compare two systems to find which performs better. Or it can

measure what parts of the system or workload cause the system to perform badly. In

performance testing, it is often crucial (and often difficult to arrange) for the test conditions to

be similar to the expected actual use.

5.2.5 USER ACCEPTANCE TESTING

User acceptance testing (UAT) is one of the final stages of a software project and it is often

performed before a new system is accepted by the customer.

Users of the system will perform these tests which ideally are derived from the User

Requirements Specification, to which the system should conform. A formal test plan will be

drawn up and a range of severity levels devised, usually from simple problems (spelling

mistakes, cosmetic problems) right through to show stoppers (major problems like the

software crashing, software will not run etc.).


7/28/2019 banktrace

28/31


5.3 TEST CASES

A test case is a set of conditions or variables and inputs that are developed for a particular

goal or objective to be achieved on a certain application to judge its capabilities or features. It

might take more than one test case to determine the true functionality of the application being

tested. Every requirement or objective to be achieved needs at least one test case.

TEST

DESCRIPTION

ACTUAL RESULT EXPECTED

RESULT

RESULT

(PASS/FAIL)

USER REQUEST

BY BRAND &

MODEL

PAGE FOUND

AND DATA

SHOWN

PAGE FOUND

AND DATA

SHOWN

PASS

USER REQUEST

BY BUDGET

PAGE FOUND

AND DATA

SHOWN

PAGE FOUND

AND DATA

SHOWN

PASS

COMPARE CAR COMPARISON

DONE

COMPARISON

DONE

PASS

SERVER DOWN PAGE NOT

FOUND

PAGE NOT FOUND PASS

Table 7.2.1 Test Case Scenarios[1]


7/28/2019 banktrace

29/31


6. CONCLUSION

After we have completed the project we are sure that the problems in the existing system

would overcome. Cooperative PDP for integrity in multi cloud storage process is made

computerized to reduce human errors and to increase the efficiency. The main focus of this

project is to lessen human efforts. The maintenance of the records is made efficient, as all the

records are stored in the database, through which data can be retrieved easily.

The implemented system presents the construction of an efficient PDP scheme for

distributed cloud storage. Based on homomorphism verifiable response and hash

index hierarchy.

The proposed system consist a cooperative PDP scheme to support dynamic

scalability on multiple storage servers.

The proposed scheme also optimized the probabilistic query and periodic verification

to improve the audit performance.


7/28/2019 banktrace

30/31


7. FUTURE ENHANCEMENT

The Future Enhancements for Online Car Club project are as follows

Since the implemented scheme of simulation approaches only a small amount of

computation and communication overheads, so it can be treated as a new candidate

for data integrity verification outsourcing data storage system.

The implemented scheme can be extended to explore more effective CPDP

constructions .


7/28/2019 banktrace

31/31


8. BIBLIOGRAPHY

References

1. Ian Sommerville, Software Engineering, Pearson Education, 7th Edition, 2008.

2. Herbert Schildt, JSP 2.0 The Complete Reference, Tata McGraw-Hill, 3rd

Edition, 2003.

3. www.w3schools.com

4. www.stackoverflow.com

5. www.ph.net/manual/en/intro-whatis.php
http://www.w3schools.com/http://www.stackoverflow.com/http://www.w3schools.com/http://www.stackoverflow.com/

banktrace

Documents