Functional Requirement Document

Project: File Storage Application

 P a g e | 1-1

DOCUMENT CONTROL

Document Statistics

Type of Information Document Data

Title FRD - File Storage Application
Document Number FRD-0.1
Document version # 0.1
Last date document was updated 07-Sep-22
Document File name FRD- File Storage Application - v0.1
Document Owner Saurabh Kumar
Document Author Saurabh Kumar
Document Change Reviewers Chetan Sharma
Document Approvers
Document Distribution List

DOCUMENT VERSION

Version Date Approved

Version Date Nature of Change
V_0.1 07-Sep-22 File Storage Application
 P a g e | 1-2

Table of Contents
Project Summary ..................................................................................................................................... 1-3
Project Scope .......................................................................................................................................... 1-3
1 In Scope Functionality ...................................................................................................................... 1-3
2 Out of Scope Functionality ............................................................................................................... 2-3
Business Requirements............................................................................................................................ 2-3
Functional Requirements ......................................................................................................................... 2-3
Non-Functional Requirements ................................................................................................................. 2-4
Epics ........................................................................................................................................................ 2-4
1. Access Application ........................................................................................................................... 2-4
2. Buy Subscription .............................................................................................................................. 2-4
3. Browse ............................................................................................................................................ 2-5
4. File Management ............................................................................................................................. 2-5
5. Application Information ................................................................................................................... 2-5
User Stories ............................................................................................................................................. 2-5
1. Story: Login ...................................................................................................................................... 2-5
2. Story: Home Page ............................................................................................................................ 2-6
Use Case:................................................................................................................................................. 2-7
1. Login................................................................................................................................................ 2-8
2. Login................................................................................................................................................ 2-8
Appendix – Mockups ............................................................................................................................... 2-9
1. Login.............................................................................................................................................. 2-10
2. Home (Landing Page) ..................................................................................................................... 2-10
3. Add ................................................................................................................................................ 2-11
 P a g e | 2-3

PROJECT SUMMARY

Company A have entrusted Prescient to develop a SAAS based product solutions to save data in the cloud
using a mobile phone. The Company A needs to capture and store loads of files, mainly images using a
mobile phone, to be used for later analysis. The vision is to scale it within a year to 1 million users.

PROJECT SCOPE

1 In Scope Functionality
 Ability to Register.
 Ability to Sign In & Sign out
 Availability for buy subscription
 Ability to Upload/Download Images to/From cloud storage application Select Report
Parameters
 Ability to perform basic operation such as Folder CRUD operation, Rename Images,
Share Images.

2 Out of Scope Functionality

 Web based cloud application
 File Formats other than JPG, BMP, and PNG

BUSINESS REQUIREMENTS

Business Objective:

 Ability to upload images on to the cloud storage using mobile phone, to be used for later analysis.
 Ability to download images on to the cloud storage using mobile phone, to be used for later analysis.
 System should allow users to save data in the cloud using a subscription-based model. The vision is
to scale it within a year to 1 million users.
 The vision is to scale it within a year to 1 million users.

FUNCTIONAL REQUIREMENTS

a) Register – User must be able to register to the application

 P a g e | 2-4

b) Buy Subscription – User must be able to buy the application subscription

c) Sign In - User must be able to Sign into the application
d) Forget password - User must be able to reset his/her password
e) Home Page – The application must have a homepage as a landing page
f) Search File - User must be able to search a file using name
g) Upload File – User must be able to upload photos on to the application
h) Rename File – User must be able to rename the uploaded files
i) Delete File – User must be able to delete uploaded files
j) Move File – User must be able to move file from one location to other
k) Share/Export File – User must be able to share/Export files
l) Download File – User must be able to download the files
m) Create Folder – User must be able to create folders within the application
n) Rename Folder – User must be able to rename the folders
o) Move Folder – User must be able to move folder from one location to other
p) Delete Folder – User must be able to delete folders
q) About - The system must have an about section to display information such as application
name, application version, Help, Build by etc.
r) Sign out – User must be able to sign out of the application

NON-FUNCTIONAL REQUIREMENTS

a) System Requirement:
Scalability and performance: This application is required to support a large volume of data storage.
The application should be light and fast.

b) Usability:
The screens should be self-explanatory and very user friendly.

c) Environments:
Highly secure, scalable, and reliable, user-friendly, self-explanatory

EPICS

1. ACCESS APPLICATION
 Register
 Sign In
 Forget password
 Sign out

2. BUY SUBSCRIPTION
 Debit/Credit Card
 Internet Banking
 P a g e | 2-5

3. BROWSE
 Home Page
 Sort by Type, Name, Size
 Search by keyword

4. FILE MANAGEMENT
 Upload File
 Rename File
 Delete File
 Move File
 Share/Export File
 Download File
 Create Folder
 Rename Folder
 Move Folder
 Delete Folder

5. APPLICATION INFORMATION
 About Us
 Contact US
 FAQ’s

USER STORIES

1. STORY: LOGIN

Description:

User State: Customer

As a user, I should be able to Login into the application, so that I can perform relevant
operation as required.

Entry Points & Pre-Conditions

 User has downloaded file storage application from the app store.
 User in on the Sign in screen.

Then I will be able to see the following content and behavior on the form:
Content Content Type UX Rule Error handling (
 P a g e | 2-6

If user submits without filling

out details)
Email ID Alpha-Numeric, Always Seen Mandatory Field
Textbox
Password Alpha-Numeric, Always Seen Mandatory Field
Textbox
Submit Button Always seen NA

Sign up Button Always seen NA

Acceptance Criteria:
 User must be able to enter the details into the Sign in form.
 Upon clicking on submit system must run frontend and backend validation check.
 In case of invalid information relevant error message must be displayed .
 Once user is successfully signed into the application, the user must be redirected to
homepage.

2. STORY: HOME PAGE

Description:

User State: Customer

As a user, I should be able to access the homepage, so that I can navigate to through file
storage application.

Entry Points & Pre-Conditions

 User has successfully signed in.

Then I will be able to see the following content and behavior on the form:
Content Content Type UX Rule Error handling (
If user submits without filling
out details)
Search Alpha-Numeric, Always Seen NA
Textbox
Menu Button Always Seen NA
Recent Button Always Seen NA
 P a g e | 2-7

Shared Button Always Seen NA

Starred Button Always Seen NA
Home Button Always Seen NA
Files Button Always Seen NA
Photos Button Always Seen NA
Account Button Always seen NA
Add Button Always seen NA

Acceptance Criteria:
 User must be able to search for an image using its name.
 Upon clicking on menu button, the application menu must be expended.
 Upon clicking on Recent button, the application must display most recently upload
photos tab.
 Upon clicking on shared button, the application must display shared images tab.
 Upon clicking on starred button, the application must display starred images tab.
 Upon clicking on home button, the application must redirect user to homepage.
 Upon clicking on Files button, the application must redirect user to folder list view
page.
 Upon clicking on photos button, the application must redirect user to photos list view
page.
 Upon clicking on Account button, the application must redirect user Account details
page.
 Upon clicking on Add button, the application must display a slider with Send Transfer,
Take Photo, upload photos, and create new folder option.

USE CASE:
 P a g e | 2-8

1. LOGIN

Use Case ID: FSA_UC_1

Use Case Name: Login
Created By: Saurabh Kumar
Date Created: 07-09-2022
This use case allows user to Sign In into the file storage application to access the relevant
Description: functions. To sign into the system, all users must enter their register email ID and password.
Once user is Signed in the system will display the relevant user homepage.
Primary Actor: Customer
Secondary Actor: None
Include Use
1. Retrieve customer details
Case:
1. User must be registered and have a valid account
Preconditions:
2. User must enter the registered email ID and password
Postconditions: 1. The system displays the valid homepage
1. System triggers retrieve customer details use case
2. The user enters the registered email ID and password
3. The user submits the email ID and password
Main Flow: 4. The system validates the email ID and password
5. The system verifies the email ID and password
6. The system displays the user's homepage
7. The use case ends
3a Missing email id and/or password
1. The system prompts for email ID and password
2. Use case resumes at main flow step 1

3b Invalid email id
1. The system display "Invalid email id"
Alternate Flows:
2. Use case resumes at main flow step 1

4a Incorrect password
1. The system display "Incorrect password"
2. Use case resumes at main flow step 1

3a No internet Connection
Exceptional Flow
1. The system display message "Please check your internet connection"

2. LOGIN
 P a g e | 2-9

Use Case ID: TEL_UC_2

Use Case Name: Upload Image
Created By: Saurabh Kumar
Date Created: 07-09-2022
This use case allows user to upload images on to the file storage mobile application from
Description:
mobile gallery.
Primary Actor: Customer
Secondary Actor: None
Include Use
1. Allow access to gallery
Case:
1. User must be signed into the application
Preconditions:
2. User must have clicked on Upload photos button
Postconditions: 1. The system displays the valid homepage
1. User clicked on upload photos button
2. The system must display the mobile phone gallery images to the user
3. The user selects the photos to be upload
4. The user clicks on submit button
Main Flow:
5. The system validates the uploaded images format
6. The system displays the uploading process progress bar for each photo
7. The system displays uploaded photo in the mobile application
7. The use case ends
1a Upload photos
1. User clicked on photos button
2. Use case resumes at main flow step 1
Alternate Flows:
5a Incorrect file format
1. The system display "Invalid file format"
2. Use case resumes at main flow step 1

6a Lost internet connection

Exceptional Flow
1. The system display message "Please check your internet connection and try again"

APPENDIX – MOCKUPS
 P a g e | 2-10

1. LOGIN

2. HOME (LANDING PAGE)

 P a g e | 2-11

3. ADD
P a g e | 2-12