Contents

1.

2.

3.

Use Cases.................................................................................................................................2
1.1.

Login:................................................................................................................................2

1.2.

Connectivity:.....................................................................................................................3

1.3.

Search:...............................................................................................................................4

1.4.

Accessing data:.................................................................................................................5

1.5.

Data Sharing:.....................................................................................................................6

1.6.

Server Notification:...........................................................................................................7

1.7.

Use Case Diagram:............................................................................................................8

Activity Diagrams:...................................................................................................................9
2.1.

Login.................................................................................................................................9

2.2.

Connectivity....................................................................................................................10

2.3.

Search..............................................................................................................................10

2.4.

Accessing data:...............................................................................................................10

2.5.

Data Sharing:...................................................................................................................11

2.6.

Server Notification:.........................................................................................................11

Sequence Diagrams................................................................................................................11
3.1.

Connectivity....................................................................................................................12

3.2.

Search..............................................................................................................................13

3.3.

Accessing data.................................................................................................................14

3.4.

Data Sharing....................................................................................................................15

3.5.

Server Notification..........................................................................................................16

4.

Class Diagram:.......................................................................................................................17

5.

System Design:.......................................................................................................................18

1. Use Cases
1.1. Login:
USE CASE NO
USE CASE NAME

UC-C1.
Login.

PRIMARY ACTOR

Any Authenticated User.

GOAL IN CONTEXT

When any of the Users wants to connect, he/she will

PRE-CONDITIONS

provide Username and Password to Login into Cloud.

Must beRegistered user.

NORMAL COURSE OF EVENTS

Actor Action

System Response

Step 1:
The user will start the application by
Clicking the Icon of the Application.

Step 2:
The Software checks whether the WiFi/Bluetooth is ON.

Step 3:
User Enter his/her Username and
Password.

Step 4:
The Software will connect to the
Server machine and Validate User.

ALTERNATE COURSE
Step 5:
The System Shall Display appropriate Error Message in Case of Invalid User.
PRIORITY

High Priority.

WHEN AVAILABLE

All the time.

FREQUENCY OF USE

Many times per day.

CHANNEL TO ACTOR

Via Wi-Fi or Bluetooth.

SECONDARY ACTORS

None.

1.2. Connectivity:
USE CASE NO

UC-C2.

USE CASE NAME

Connectivity.

PRIMARY ACTOR

Any Authenticated User.

GOAL IN CONTEXT

When any of the User wants to connect, he/she will

use the connectivity Process of mobile device with
Cloud.
Must be a Registered user.

PRE-CONDITIONS
NORMAL COURSE OF EVENTS
Actor Action

System Response

Step 1:
The user should select the Network
Wi-Fi or Bluetooth.

Step 2:
The Software checks whether the WiFi or Bluetoothis ON or NOT.

Step 3:
Select a Cloud Community.

Step 4:
The Software will connect to the
Cloud Community.

ALTERNATE COURSE
Step 5:
The System Shall Display appropriate Error Message in Case of Lost Connection.
PRIORITY

High Priority.

WHEN AVAILABLE

All the time.

FREQUENCY OF USE

Many times per day.

CHANNEL TO ACTOR

Via Wi-Fi or Bluetooth

1.3. Search:
SECONDARY ACTORS

None.

USE CASE NO

UC-C3

USE CASE NAME

Search

PRIMARY ACTOR

Any Authenticated User.

GOAL IN CONTEXT

When any of the users wants to search data from that

PRE-CONDITIONS

particular cloud community.

Must be an authenticated user

NORMAL COURSE OF EVENTS

Actor Action

System Response

Step 1:
The User Click on the Search button.
Step 2:

Step 3:

The User Enter Query and submit.

The Administrator

Machine

will

Respond according to the Query.

Step 4:
If the query was not satisfied from
that cloud then it will search from
Google.

ALTERNATE COURSE
Step 3:
The System Shall Display appropriate Error Message in Case of any problem.
PRIORITY
High Priority.
WHEN AVAILABLE
FREQUENCY OF USE

All the time

Many times per day.

CHANNEL TO ACTOR

Via Wi-Fi or Bluetooth

SECONDARY ACTORS

None.

1.4. Accessing data:

USE CASE NO
USE CASE NAME

UC-C4
Accessing data

PRIMARY ACTOR

Any Authenticated User.

GOAL IN CONTEXT

Using this feature, the Software will be able to share data

between the members of that cloud community.

PRE-CONDITIONS
Must be an authenticated user
NORMAL COURSE OF EVENTS
Actor Action

System Response

Step 1:
To use click on the share folder

Step 2:

button.

The Server shows all the shared data

of Members in cloud.

ALTERNATE COURSE
Step 5:
The System Shall Display appropriate Error Message in Case of any problem.
PRIORITY

High Priority.

WHEN AVAILABLE

When Require.

FREQUENCY OF USE

Many times per day.

CHANNEL TO ACTOR

Mobile Screen.

SECONDARY ACTORS

None.

1.5. Data Sharing:

USE CASE NO
USE CASE NAME

UC-C5
Data Sharing

PRIMARY ACTOR

Any Authenticated User.

GOAL IN CONTEXT

Using this feature, the Software will be able to share data

between the members of that cloud community.

PRE-CONDITIONS
Must be an authenticated user
NORMAL COURSE OF EVENTS
Actor Action

System Response

Step 1:
To use click on the share folder

Step 3:

button.

The Server shows all the shared data

Step 2:

of Members in cloud.

The user will request to copy desired

Step 4:

data.

The Server will return Desired Data.

ALTERNATE COURSE
Step 5:
The System Shall Display appropriate Error Message in Case of any problem.
PRIORITY

High Priority.

WHEN AVAILABLE

When Require.

FREQUENCY OF USE

Many times per day.

CHANNEL TO ACTOR

Mobile Screen.

SECONDARY ACTORS

None.

1.6. Server Notification:

USE CASE NO
USE CASE NAME

UC-C6
Server Notification

PRIMARY ACTOR

Any Authenticated User.

GOAL IN CONTEXT

Using this feature, the Software will be able to change the

server for that cloud community.

PRE-CONDITIONS
Admin
NORMAL COURSE OF EVENTS
Actor Action

System Response

Step 1:
Admin click on the Change server

Step 3:

button.

The Server shows all the possible sub-

Step 2:

servers of that cloud community.

The Admin will request to make

Step 4:

specific user a Server.

The Server will be changed.

Step 5:
The Server will send appropriate
message to all members.

ALTERNATE COURSE
Step 5:The System Shall Display appropriate Error Message in Case of any problem.
PRIORITY

High Priority.

WHEN AVAILABLE

When Require.

FREQUENCY OF USE

Many times per day.

CHANNEL TO ACTOR

Mobile Screen.

SECONDARY ACTORS

None.

1.7. Use Case Diagram:

2. Activity Diagrams:
2.1. Login

2.2. Connectivity:

2.3. Search:

2.4. Accessing data:

2.5. Data Sharing:

2.6. Server Notification:

3. Sequence Diagrams
Login

3.1.

Connectivity:

3.2. Search

3.3. Accessing data

3.4. Data Sharing

3.5. Server Notification

4. Class Diagram:

5. System Design: