SYNOPSIS ON CSE320 (PROJECT)

ON

“Gmail.com”

Submitted by

GOURAV RAO NAGINENI

Registration No: 11806868

Section: K18TM

Roll No:A29

Submitted to

ROOPAM MAM

In partial fulfilment of Project for the award of the degree of

BACHELOR OF TECHNOLOGY (CSE)

School of Computer Science
LOVELY PROFESSIONAL UNIVERSITY
 CONTENTS

1. Introduction

1.1 Purpose

1.2 Scope

2. Functional Requirements

2.1 Functional Requirements

2.2 Requirements of Gmail.com website

2.3 Requirements of the system for the user

3. Non-Functional Requirements

4. Data Flow Diagram

5. Use Case Diagram

6. Test Cases
 1. INTRODUCTION

1.1 Purpose
This document describes the functional requirements and nonfunctional
requirements for Gmail.com website(www.gmail.com)

1.2 Scope
It is mandatory for users to create Gmail account for the usage of all the
google related apps or software. To create Gmail user need to open just
the link, no need to install any other heavy software on phones or laptops.

2. FUNCTIONAL REQUIREMENTS

2.1 Functional Requirements

Specific requirements are organized into 2 parts: First is requirement for
Gmail.com website and second is requirement of the user.

Functional Requirement 1
 Description:
Initialize the name, email, password and date of birth for creating
account.
 Input:
Name in characters and email, password, date of birth in alpha numerical
value.
 Processing:
Storing the value entered in the database.
 Output:
Confirmation message registered successfully.
Functional Requirement 2
 Description:
Enter the username and password for login.
 Input:
Username and password in alpha numerical value.
 Processing:
Storing the values and checking whether true or not.
 Output:
Confirmation message login successful or else login failed.

Functional Requirement 3
 Description:
User want to search a mail.
 Input:
Enter the name of mail you want to search.
 Processing:
Storing the values and checking whether present or not.
 Output:
Message displayed mail present or not.

Functional Requirement 4
 Description:
Profile update.
 Input:
Name in characters, email and password in alpha numerical value,
profile picture, mobile number, date of birth.
 Processing:
Storing the value entered in the database.
 Output:
Confirmation message profile updated successfully.
Functional Requirement 5
 Description:
Compose mail.
 Input:
Enter the mail id and subject.
 Processing:
Storing the entered info in database.
 Output:
Display mail sent or not.

Functional Requirement 6
 Description:
Calendar.
 Input:
Enter the important dates.
 Processing:
Storing the entered values in the database.
 Output:
Confirmation message displayed stored successfully.

Functional Requirement 7
 Description:
Change display settings.
 Input:
Setting the details the user wish to have.
 Processing:
Settings updated in the database.
 Output:

Functional Requirement 8
 Description:
Setting the tasks.
 Input:
Entering the time and date to perform a specific task.
 Processing:
 Storing the entered values in the database.
 Output:
Confirmation message displayed stored successfully.

Functional Requirement 9
 Description:
Forget password.
 Input:
Enter the mobile number and date of birth.
 Processing:
Storing the values and checking weather true or false.
 Output:
Confirmation message data true or false. If true enter new password.

Functional Requirement 10
 Description:
Reset password.
 Input:
Previous password and new password in alphanumeric value.
 Processing:
Checking whether the previous password is correct and changing new
password with previous one in database.
 Output:
Password reset successfully.

Functional Requirement 11
 Description:
Sent mails
 Input:
Select sent icon.
 Processing:
Checking in the database for sent mails.
 Output:
Displays previously sent messages.
Functional Requirement 12
 Description:
Inbox.
 Input:
Select inbox.
 Processing:
Checking in the database for all the mails.
 Output:
Displays all the mails.

Functional Requirement 12
 Description:
Social.
 Input:
Select social.
 Processing:
Checking in the database for all the social mails.
 Output:
Displays all the social mails.

Functional Requirement 13
 Description:
Starred.
 Input:
Select starred.
 Processing:
Checking in the database for all the starred mails.
 Output:
Displays all the starred mails.
Functional Requirement 14
 Description:
Drafts.
 Input:
Select draft box.
 Processing:
Checking in the database for all the drafted mails.
 Output:
Displays all the drafted mails.

Functional Requirement 15
 Description:
Logout.
 Input:
Click logout.
 Processing:
It will be logged out from the database temporarily.
 Output:
Confirmation message logout successful.

Functional Requirement 16
 Description:
Configure inbox
 Input:
Click configure inbox.
 Processing:
Changes are made in the database.
 Output:
Displays changed successfully.

Functional Requirement 17
 Description:
Sync.
 Input:
Click sync or relode.
  Processing:
Updating the database for all the new mails.
 Output:
Displays all the updated/new mails.

Functional Requirement 18
 Description:
Mark all as read.
 Input:
Click mark all as read.
 Processing:
Changing all the unread mails into read mails in the database.
 Output:
Confirmation message all messages are read.

Functional Requirement 19
 Description:
Download mail.
 Input:
Click download mail.
 Processing:
Checking in the database for all the mail and downloading it into the
device.
 Output:
Download successful.

Functional Requirement 20
 Description:
Report spam.
 Input:
Select report spam.
 Processing:
Updating it in the database.
 Output:
Displays updated successfully.
Functional Requirement 21
 Description:
Delete.
 Input:
Click on delete.
 Processing:
Deleting it from the database.
 Output:
Displays deleted successfully.

Functional Requirement 22
 Description:
Archive.
 Input:
Select archive.
 Processing:
Checking and adding it to archive list in the database.
 Output:
Displays added successfully.

Functional Requirement 23
 Description:
Create event.
 Input:
Click create event.
 Processing:
Updating the information in the database.
 Output:
Confirmation message updated successfully.

2.3 Requirements of the system for the user

Functional Requirement 1
 Description:
 Internet connectivity.
 Input:
Sending data to internet to check whether internet connection is there.
 Processing:
Establishing the connection with database through servers.
 Output:
Confirmation message successfully connected to internet and database
else no internet connection.

3.NON FUNCTIONAL REQUIREMENTS

 Performance
 Scalability
 Capacity
 Availability
 Reliability
 Recoverability
 Maintainability
 Serviceability
 Security
 Regulatory
 Manageability
 Environmental
 Data integrity
 Usability
 Interoperability
Use Case Diagram
 Test Cases:

Sr. Negative/ Positive

Functional Test Cases
No. Test Case

1 Verify if a user will be able to login with a valid username and valid Positive
password.

2 Verify if a user cannot login with a valid username and an invalid Negative
password.

3 Verify the login page for both, when the field is blank and Submit Negative
button is clicked.

4 Verify the ‘Forgot Password’ functionality. Positive

5 Verify the messages for invalid login. Positive

6 Verify the ‘Remember Me’ functionality. Positive

7 Verify if the data in password field is either visible as asterisk or Positive

bullet signs.

8 Verify if a user is able to login with a new password only after he/she Positive
has changed the password.

9 Verify if the login page allows to log in simultaneously with different Positive
credentials in a different browser.

10 Verify if the ‘Enter’ key of the keyboard is working correctly on the Positive
login page.
S.NO ACTION EXPECTED SYSTEM RESPONSE PASS/FAIL

11 Click send mail Enter recipient valid Gmail id pass

12 Click search mail Enter the valid name for searching pass

13 Click search mail Enter invalid name for searching fail

14 Click sent mail Sent mail page should be displayed pass

15 Click logout Login page should be displayed pass

16 Click inbox Inbox page should be displayed pass

17 Click compose mail Compose mail page should be displayed pass

END OF REPORT