A Project Report

On
Cloud File Storage Authenticated User

Submitted to
DEPARTMENT OF COMPUTER SCIENCE

CHAITANYA POST GRADUATE COLLEGE (Autonomous)

in fulfillment of the requirement
for the II Year II Semester
Of
MASTER OF COMPUTER SCIENCE

BY

B.AKHIL (09617-47013)
P.SAIKUMAR (09617-47012)

Under the guidance of

Mr s. V. SHOBHA RANI
Asst.Professor

DEPARTMENT OF COMPUTER SCIENCE

CHAITANYA POST GRADUATE COLLEGE

(Autonomous)
(Affiliated to Kakatiya University, Warangal)
KISHANPURA, HANAMKONDA, WARANGAL (A.P)-506001
2017-2018

CHAITANYA POSTGRADUATE COLLEGE

(Autonomous)
 KISHANPURA, HANAMKONDA, WARANGAL (A.P)-506001

DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE

This is to certify that B.AKHIL(09617-47013)bearing P.SAIKUMAR(09617-

47012) at, Chaitanya Postgraduate College Autonomous University has satisfactory
completed the project entitled “CLOUD FILE STORAGE AUTHENTICATED USER”
the requirements for the II Year II Semester of degree Master of Computer Application
during the academic year 2017-2018.

Guide Head Of the Department Principal

Mr s.V.Shobha Rani V.Madhukar Dr. B.S Anuradha
Asst. Professor Asst. Professor Professor

INTERNAL EXAMINER EXTERNAL EXAMINER

 DECLARATION

We hereby declare that the project report titled “CLOUD FILE STORAGE
AUTHENTICATED USER” is an original work done at Chaitanya Postgraduate
College (Autonomous), Hanamkonda, Warangal, submitted in partial fulfillment for the
MCA II Year 4TH Semester to the department of Computer Science. We assure you that
this project has not been submitted by any degree anywhere in any college or university.

B.AKHIL
P.SAIKUMAR
 ACKNOWLEDGEMENT

We express our sincere gratitude to Dr. CH. V. PURUSHOTHAM REDDY,

Secretary & Correspondent, Dr. B.S ANURADHA Principal of CHAITANYA
POSTGRADUATE COLLEGE for their unstrained interest in providing us facilities to
complete the project successfully Mrs.V.SHOBHA RANI, Head of the Department
V.MADHUKAR of computer science who helped immensely with their valuable guidance
and valuable suggestions during the completion of this project work and who allowed us to
do the project work and given us a lot of support and constant encouragement throughout this
project.
We thank all the faculty members of the Department of Computer Science for sharing
their invaluable knowledge with us. We extend our thanks to the technical staff of the
department for their valuable suggestions to technical problems. We also thanks to our family,
friends for their helping hand in bringing this project to this present shape.

B.AKHIL
P.SAIKUMAR
 CONTENTS

Title: CLOUD FILE STORAGE AUTHENTICATED USER

Page No
1. Introduction
2. System Analysis
a. Existing System
b. proposed System

3. Feasibility Report

a.Feasibility
b. Operational Feasibility
c. Economical Feasibility
4. System Requirement Specification Document
a. Overview
b. Modules Description
c. Process Flow
d. Software Requirements
e. Hardware Requirements
5. System Design
a. UML
b. Data Dictionary
6. Technology Description
7. Testing & Debugging Techniques
8. Output Screens
9. Conclusion
10. Bibliography

INTRODUCTION
 using store the files irrespective of the file extension. This Application

has designed in such a way that user can easily interact with a user friendly UI.

This Cloud File Storage provides security for user file through authentication

process i.e. When user wants to store any personal data they should register

themselves in the site. After registering user will be provided a folder in the

cloud with a user desired name. Whenever user stores the files the files will be

stored in the respective folder. The user can upload files from PC to cloud and
user can download, and delete those files which are saved in cloud .The user can

view the files in folder in a tree structure. We are giving this service with the

help of Amazon S3 (Simple Storage Service).

Amazon S3 is a repository for Internet data. Amazon S3 provides access to reliable,
fast, and inexpensive data storage infrastructure. It is designed to make web-scale computing
easy by enabling you to store and retrieve any amount of data, at any time, from within
Amazon EC2 or anywhere on the web. Amazon S3 stores data objects redundantly on
multiple devices across multiple facilities and allows concurrent read or write access to these
data objects by many separate clients or application threads. You can use the redundant data
stored in Amazon S3 to recover quickly and reliably from instance or application failures.

1. System Analysis

Existing System:
 In Existing System user did not have any GUI structure to directly communicate with
cloud services directly. Generally a user can store files online in some fixed format only.

Proposed System:
We propose this system to standardize the existing system and reduce the managerial
overhead so that we can get better output in a timely manner. Here we are synchronizing all
the activities so we will get best possible outcome. It is supported to all file formats and the
user can access it from anywhere irrespective of his location.

Business Scenario:
This application can be used by companies who are willing to provide online storage services
with cloud to user

Feasibility Study

Technical Feasibility:
the technical feasibility is the trickiest part of a feasibility study. This is because, at
this point in time, not too many detailed design of the system, making it difficult to access
issues like performance, costs on (on account of the kind of technology to be deployed) etc. A
number of issues have to be considered while doing a technical analysis.

i) Understand the different technologies involved in the proposed system:

Before commencing the project, we have to be very clear about what are the
technologies that are to be required for the development of the new system.

ii) Find out whether the organization currently possesses the required technologies:
 o Is the required technology available with the organization?

o If so is the capacity sufficient?

For instance –
“Will the current printer be able to handle the new reports and forms required for the
new system?”

OPERATIONAL FEASIBILITY:

Proposed project is beneficial only if it can be turned into information systems that will meet
the organizations operating requirements. Simply stated, this test of feasibility asks if the
system will work when it is developed and installed. Are there major barriers to
Implementation? Here are questions that will help test the operational feasibility of a project:

Is there sufficient support for the project from management from users? If the current system
is well liked and used to the extent that persons will not be able to see reasons for change,
there may be resistance.

Are the current business methods acceptable to the user? If they are not, Users may welcome
a change that will bring about a more operational and usefulsystems.

Have the user been involved in the planning and development of the project?

Early involvement reduces the chances of resistance to the system and in general and
increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships encountered. In the existing
manual system, the new system was considered to be operational feasible.

ECONOMICAL FEASIBILITY:

Economic feasibility attempts 2 weigh the costs of developing and implementing a

new system, against the benefits that would accrue from having the new system in place. This
feasibility study gives the top management the economic justification for the new system.
A simple economic analysis which gives the actual comparison of costs and benefits are
much more meaningful in this case. In addition, this proves to be a useful point of reference
to compare actual costs as the project progresses. There could be various types of intangible
benefits on account of automation. These could include increased customer satisfaction,
improvement in product quality better decision making timeliness of information, expediting
activities, improved accuracy of operations, better documentation and record keeping, faster
retrieval of information, better employee morale.

System Requirement Specification

Modules:
1. Authentication Module
 2. User Module

SDLC METHODOLOGIES:
This document play a vital role in the development of life cycle (SDLC) as it
describes the complete requirement of the system. It means for use by developers and
will be the basic during testing phase. Any changes made to the requirements in the
future will have to go through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model
of Software Development and Enhancement. This model was not the first model to
discuss iterative development, but it was the first model to explain why the iteration
models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each
phase starts with a design goal and ends with a client reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye
toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
 The new system requirements are defined in as much details as possible. This
usually involves interviewing a number of users representing all the external or
internal users and other aspects of the existing system.

 A preliminary design is created for the new system.

 A first prototype of the new system is constructed from the preliminary design.
This is usually a scaled-down system, and represents an approximation of the
characteristics of the final product.

 A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

 At the customer option, the entire project can be aborted if the risk is deemed too
great. Risk factors might involved development cost overruns, operating-cost
miscalculation, or any other factor that could, in the customer’s judgment, result
in a less-than-satisfactory final product.

 The existing prototype is evaluated in the same manner as was the previous
prototype, and if necessary, another prototype is developed from it according to
the fourfold procedure outlined above.

 The preceding steps are iterated until the customer is satisfied that the refined
prototype represents the final product desired.
  The final system is constructed, based on the refined prototype.

 The final system is thoroughly evaluated and tested. Routine maintenance is

carried on a continuing basis to prevent large scale failures and to minimize down
time.

3. Requirement analysis

Software Requirements:
Operating System : Windows XP
Programming Language : .Net
Web Applications :Visual Studio 2008
Hardware Requirements : Operating System Microsoft Windows, Linux
orManyversion
Hard Disk : 40GB or High
RAM : 256 MB or High

Language: c#.net
Technologies: asp.net
Database: SQL server2008

3.1.2 Hardware requirements

Proceesor: Pentium about
RAM: 512MB
Hard disk: 40

Client Side:

 Processor: Intel Pentium IV/core 2 duo.

 RAM: 500 MB.

 Disk Space: 100 MB.

Server Side:

 Processor: Intel Pentium IV.Core 2 duo.

 RAM: 1GB.

 Disk space: 4GB.

Recommended requirements:
Client side:
 Processor: All Intel processors
 RAM: 1GB
 Disk Space: 100MB
Server side:
 Processor: All Intel processors
 RAM: 1GB
 Disk Space: 4GB

 Functional Requirements:
 Create and manage number accounts
 Fat rate setting
 Daily milk collection
 Search features based on various parameters such as name, keyword&salary
areas.
 Message alert to the member
 Print data
 Generate salary
 Create new login user account
 4. Design

4.1 Database Design

1. Admin (user name, password,)

2. User (User Name, Password,)

5. System Design
Data Flow Diagram:

A graphical tool used to describe and analyze the moment of data through a system manual or

automated including the process, stores of data, and delays in the system. Data Flow

Diagrams are the central tool and the basis from which other components are developed. The

transformation of data from input to output, through processes, may be described logically

and independently of the physical components associated with the system. The DFD is also

know as a data flow graph or a bubble chart.

DFDs are the model of the proposed system. They clearly should show the requirements on

which the new system should be built. Later during design activity this is taken as the basis

for drawing the system’s structure charts. The Basic Notation used to create a DFD’s are as

follows:

1. Dataflow: Data move in a specific direction from an origin to a destination.

2. Process: People, procedures, or devices that use or produce (Transform) Data. The

physical component is not identified.

3. Source: External sources or destination of data, which may be People, programs,

organizations or other entities.

4. Data Store: Here data are stored or referenced by a process in the System.

UML Diagram (Unified Modeling Language)

The Unified Modeling Language allows the software engineer to express an analysis
model using the modeling notation that is governed by a set of syntactic semantic and
pragmatic rules.
A UML system is represented using five different views that describe the system from
distinctly different perspective. Each view is defined by a set of diagram, which is as follows.
 User Model View:
 i. This view represents the system from the users perspective.
ii. The analysis representation describes a usage scenario from the end-users
perspective.

4.1.1 ER Diagram:

Size
Data
4.1.1ER
U_namDia Date
Last
e F_id
name U_id
Conten
F_nam Gmail t
U-id
e
Uplo
User View ad LinFile Files
pwd Gender Registrio
Reset F_idFils F_id
F_Nam Delete F_nam Download
F_nam
F_id
k
 UML Diagrams:
Admin has the authority add and delete the user add the product details.veiws
the report of the status of the issue
 login

view users

acc...

del...

admin
update user

logout

Registration
Registration

User Login
upload file

user login

User Case For User: Download file

User
Edit profile

User logout
Activity:
Activity Diagram For Admin:

Activity diagram or graphical representation of work flows of stepwise and activity

and action with support for choice instruction and concurrence .in the unified modeling
language, activity diagrams can be used to describe the business and operational step by setup
work flows components in system .an activity diagram shows the overall flow of control

Admin Login

View User Accept Users Delete Users

Logout
Activity Diagram for User:
Class Diagram:
 In software engineering a class diagram in the unified modeling language (UML)is
type of static structures diagrams the describes the structure of a system by showing systems
classes their attributes operations or methods and the relationship among the classes it
explains which class contains information
Sequence Diagram:

Sequence for User:

User Upload Download Edit Profile Cloud

1.Upload file

2.save()

3.Response()

4.Download file

5.Download Request()

6.File Download()

7.Edit Profile

8.save in cloud()

9.response()
4.1.2Tables
Registration Table:

Files:
Files:
Screens:
System Test Cases & System Test Report:
The System Test Cases mentioned below are expected to work and give the expected
behavior if the explorer is configured to run jar files as mentioned in the project folder.
Validation Testing:
At the end of Integration Testing software is completely assembled as a package.
Validation testing is the next stage which can be defined as successful when the software
functions in the manner reasonably expected by the customer.
System Testing:
System Testing is actually a series of different tests whose primary purpose is to fully
exercise the computer-based system. Although each test has a different purpose, all
work to verify that all system elements have been properly integrated to perform
allocated functions.
Recovery Testing:
It is a system test that forces the system to fail in a variety of ways and verities that the
recovery is properly performed.
Security Testing;
Attempts to verify the protection mechanisms built into the system.
Performance Testing:
This method is designed to test runtime performance of software within the context of
an integrated system

Test Cases for Insurance System With Tracking Manager:

Test Case for User Registration

Pre-Condition Input Actual output Expected
output
If any User wants to 1. If User enters 1. Registration is 1. Registration
register they have to new Username with Successful. Your is Successful.
enter the fields in valid fields. Details Your Details
Registration Module. 2. If User enters 2. Error Message. 2. Error
Existing User Name Try Again! Message. Try
and all the fields. Again!
Test Case for User Login
Pre-Condition Input Expected Actual Output
Output
Registration is 1. If User enters 1. Login is 1. Login is successful
Mandatory. valid User Name & successful and and displays Welcome
Password. displays Welcome Page.
2. If User enters Page. 2. Error Message,
invalid User Name 2. Error Message, Invalid
& Password. Invalid User UserEmail&password
Email &
password

9. CONCLUSION

Amazon S3 is a repository for Internet data. Amazon S3 provides access to

reliable, fast, and inexpensive data storage infrastructure. It is designed to make web-

scale computing easy by enabling you to store and retrieve any amount of data. When

user wants to store any personal data they should register themselves in the site. After

registering user will be provided a folder in the cloud with a user desired name.

Whenever user stores the files the files will be stored in the respective folder. The user

can upload files from PC to cloud and user can download, and delete those files which

are saved in cloud .The user can view the files in folder in a tree structure. We are giving

this service with the help of Amazon S3 (Simple Storage Service).

10.BIBLIOGRAPHY
 ASP .NET (Black Book).
 Professional ASP .NET (Wrox Publication)
 ASP .NET Complete Reference.
 Software Engineering on concepts by Pressman.

Web Sites: