Software Requirements

Specification

for

Whatsapp

V.1.0.1

Prepared by

Group Name: Group Number 4

yash yogi 23/480 [email protected]
Yogesh Kumawat 23/482 [email protected]
Vansh sharma 23/474 [email protected]

Instructor: Vishal

Course: Software engineering

Lab Section: B-3

Teaching Assistant: Vishal

Date: 5/12/24
Software Requirements Specification for Whatsapp Page ii

Contents
CONTENTS ........................................................................................................................................................ II

REVISIONS ........................................................................................................................................................ II

1 INTRODUCTION ........................................................................................................................................ 1
1.1 DOCUMENT PURPOSE ..................................................................... ERROR! BOOKMARK NOT DEFINED.
1.2 PRODUCT SCOPE............................................................................ ERROR! BOOKMARK NOT DEFINED.
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW ........................... ERROR! BOOKMARK NOT DEFINED.
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ............................... ERROR! BOOKMARK NOT DEFINED.
1.5 DOCUMENT CONVENTIONS.............................................................. ERROR! BOOKMARK NOT DEFINED.
1.6 REFERENCES AND ACKNOWLEDGMENTS ......................................... ERROR! BOOKMARK NOT DEFINED.
2 OVERALL DESCRIPTION ........................................................................................................................ 2
2.1 PRODUCT OVERVIEW ...................................................................... ERROR! BOOKMARK NOT DEFINED.
2.2 PRODUCT FUNCTIONALITY .............................................................. ERROR! BOOKMARK NOT DEFINED.
2.3 DESIGN AND IMPLEMENTATION CONSTRAINTS ................................. ERROR! BOOKMARK NOT DEFINED.
2.4 ASSUMPTIONS AND DEPENDENCIES ................................................ ERROR! BOOKMARK NOT DEFINED.
3 SPECIFIC REQUIREMENTS.................................................................................................................... 4
3.1 EXTERNAL INTERFACE REQUIREMENTS ........................................... ERROR! BOOKMARK NOT DEFINED.
3.2 FUNCTIONAL REQUIREMENTS .......................................................... ERROR! BOOKMARK NOT DEFINED.
3.3 USE CASE MODEL................................................................................................................................ 4
4 OTHER NON-FUNCTIONAL REQUIREMENTS .................................................................................... 6
4.1 PERFORMANCE REQUIREMENTS...................................................... ERROR! BOOKMARK NOT DEFINED.
4.2 SAFETY AND SECURITY REQUIREMENTS.......................................... ERROR! BOOKMARK NOT DEFINED.
4.3 SOFTWARE QUALITY ATTRIBUTES ................................................... ERROR! BOOKMARK NOT DEFINED.
5 OTHER REQUIREMENTS ........................................................................................................................ 6

APPENDIX A – DATA DICTIONARY ................................................................................................................ 7

APPENDIX B - GROUP LOG ............................................................................................................................ 9

Revisions
Version Primary Author(s) Description of Version Date Completed
v.1.0 Yash yogi Information about the revision. This table does 4/12/2024
not need to be filled in whenever a document is
touched, only when the version is being
Software Requirements Specification for Whatsapp Page iii

Version Primary Author(s) Description of Version Date Completed

upgraded.
Software Requirements Specification for Whatsapp Page 1

1 Introduction

1.1 1. Introduction

1.1.1 1.1 Purpose

This SRS specifies the requirements for the WhatsApp application, a real-time messaging and
communication system that provides users with text, voice, video, and multimedia messaging
capabilities.

1.1.2 1.2 Scope

WhatsApp is a cross-platform application designed for Android, iOS, and desktop environments. It
enables secure and efficient communication, including features like group chats, status updates, and
end-to-end encryption.

1.1.3 1.3 Definitions, Acronyms, and Abbreviations

 API: Application Programming Interface

 E2EE: End-to-End Encryption

 VoIP: Voice over Internet Protocol

1.1.4 1.4 References

 IEEE Standard 830-1998 for Software Requirements Specifications

 WhatsApp official documentation

1.1.5 1.5 Overview

This document provides a comprehensive specification of the system's functional and non-functional
requirements.
Software Requirements Specification for Whatsapp Page 2

2 Overall Description

2.1 2. Overall Description

2.1.1 2.1 Product Perspective

WhatsApp operates as a client-server model, leveraging internet protocols for real-time

communication. It integrates with contact lists for seamless user experiences and relies on cloud-
based servers for data synchronization.

2.1.2 2.2 Product Functions

 Real-time text messaging

 Voice and video calls

 Multimedia sharing (images, videos, documents)

Software Requirements Specification for Whatsapp Page 3
 Group chat and broadcast messages

 End-to-end encryption for data security

2.1.3 2.3 User Characteristics

Users are expected to have basic smartphone literacy. Target demographics include individual users
and small-to-medium-sized businesses.

2.1.4 2.4 Constraints

 Internet connectivity is required for core functionality.

 Limited support for older device operating systems.

2.1.5 2.5 Assumptions and Dependencies

 Users have a valid phone number for registration.

 Dependency on third-party services like Google Play Services and Apple Push Notification
Service.
Software Requirements Specification for Whatsapp Page 4

3 Specific Requirements

3.1.1 3.1 Functional Requirements

 FR1: The system shall allow users to send and receive text messages in real-time.

 FR2: The system shall support one-to-one and group chats.

 FR3: The system shall allow multimedia sharing, including images, videos, and documents.

 FR4: The system shall provide end-to-end encryption for all communications.

3.1.2 3.2 Non-Functional Requirements

 NFR1: The application shall support at least 100 concurrent users in a group chat.

 NFR2: The application shall have a latency of less than 1 second for message delivery under
normal network conditions

3.2 Use Case Model

1. Key Components in the Diagram:

2. Actor:
o The user is depicted as the actor (a stick figure), who interacts with various
functionalities of the WhatsApp system.
3. System Boundary:
Software Requirements Specification for Whatsapp Page 5
o The rectangle labeled "WhatsApp" represents the boundary of the system. All
functionalities inside the rectangle are part of WhatsApp.
4. Use Cases:
o These are the ovals that represent different actions or functions available to the
user within the application. They include:
 Create user group: The user can create groups for collective
communication.
 Chat with a contact: The user can chat with individual contacts.
 Send Broadcast message: Allows the user to send messages to multiple
recipients without creating a group.
 Profile setting: The user can manage profile-related features.
 Manage Accounts: Options for managing account-specific settings.
5. Included Functionalities (<<include>>):
o Some use cases are further detailed or dependent on other actions:
 Within "Chat with a contact", the user can:
 Send text messages.
 Send smileys.
 Send images, which can also include videos.
 Share locations with contacts.
 Profile settings include:
 Editing the profile picture.
 Editing the display status.
 Manage Accounts include:
 Changing privacy settings.
 Changing the account number.
 Deleting the account.
6. Observations:
 Relationships: The use of <<include>> indicates that certain actions (like "Send Smilies")
are always a part of a higher-level action (like "Chat with a contact").
 Hierarchy: The diagram organizes features hierarchically to reflect how users interact with
the app’s functionality in a structured way.
 Scalability: This model can be extended to include additional features or actors, such as
administrators or bots.

3.2.1 Use Case #

…
Software Requirements Specification for Whatsapp Page 6

4 Other Non-functional Requirements

4.1 Other Non-Functional Requirements

4.1.1 4.1 Performance Requirements

 Messages must be delivered in less than 500ms under a stable network.

4.1.2 4.2 Security Requirements

 All data transmission shall be encrypted using AES-256.

4.1.3 4.3 Usability Requirements

 The application shall provide a tutorial for first-time users.

4.1.4 4.4 Reliability Requirements

 The system should have 99.9% uptime on cloud servers.

5 Other Requirements

 5. External Interface Requirements

 5.1 User Interfaces
 Intuitive graphical interface for mobile and desktop users
 Support for dark and light themes
 5.2 Hardware Interfaces
 Compatible with devices running Android 5.0+ and iOS 12.0+
 5.3 Software Interfaces
 Integration with mobile operating system APIs for notifications and permissions
 5.4 Communication Interfaces
 Uses HTTP, HTTPS, and WebSocket protocols for communication
Software Requirements Specification for Whatsapp Page 7

Appendix A – Data Dictionary

1. Dictionary of Terms
2. API (Application Programming Interface)
A set of protocols and tools that allow different software applications to communicate and
interact.
3. E2EE (End-to-End Encryption)
A communication system in which only the communicating users can read the messages,
ensuring security and privacy.
4. VoIP (Voice over Internet Protocol)
A technology that allows users to make voice calls over the internet instead of traditional
phone networks.
5. Latency
The time delay between a user sending a message and it being delivered to the recipient.
6. Cloud-Based Servers
Remote servers hosted on the internet that store data and provide services for
applications.
7. Cross-Platform
Software designed to work on multiple operating systems, such as Android, iOS, and
desktops.
8. Multimedia
Digital content that includes images, videos, audio files, and documents.
Software Requirements Specification for Whatsapp Page 8
9. Broadcast Messages
A feature that allows users to send messages to multiple recipients simultaneously without
creating a group.
10. Concurrent Users
The number of users actively using the system at the same time.
11. Graphical Interface
A user interface that includes visual elements like buttons, icons, and menus, making the
application more user-friendly.
12. AES-256 (Advanced Encryption Standard 256-bit)
A strong encryption standard used to secure data transmission and storage.
13. Uptime
The percentage of time a system is operational and accessible to users, typically
measured as a service-level agreement (SLA).
14. WebSocket Protocol
A communication protocol that provides full-duplex communication channels over a single
TCP connection.
15. HTTP (HyperText Transfer Protocol)
A protocol used for transmitting hypertext over the internet.
16. HTTPS (HyperText Transfer Protocol Secure)
A secure version of HTTP that encrypts data exchanged between a web browser and
server.
17. Tutorial
An interactive guide or walkthrough provided to assist new users in understanding how to
use an application.
18. Stable Network
A network with consistent and reliable internet connectivity without frequent interruptions.
19. Dark and Light Themes
User interface options where "dark theme" features darker colors and "light theme"
features brighter colors for display elements.
20. Glossary
A list of terms and their definitions provided to ensure clarity and consistency in
documentation.
21. Operating System APIs
Interfaces provided by an operating system to enable applications to perform specific
tasks such as sending notifications or accessing hardware components.
Software Requirements Specification for Whatsapp Page 9

Appendix B - Group Log

5.1 Appendix A: Group Meeting Minutes and

Activities

5.1.1 A.1 Meeting Logs

5.1.1.1 Meeting 1: Project Kickoff

Date: 24/11/24
Attendees: Yash yogi, Yogesh Kumawat, Vansh sharma.
Agenda:

 Discuss the scope and purpose of the SRS for WhatsApp.

 Assign initial roles and responsibilities.

Decisions Made:

 Agreed on IEEE format for the SRS document.

Software Requirements Specification for Whatsapp Page 10
 Identified primary features to focus on: messaging, voice/video calls, multimedia sharing, and
encryption.
Action Items:

 Research existing messaging platforms and their functionalities.

 Draft the introduction and overall description sections.

5.1.1.2 Meeting 2: Functional Requirements Discussion

Date: 26/11/24
Attendees: yash yogi, Yogesh Kumawat, Vansh Sharma.
Agenda:

 Define core functional requirements.

 Discuss prioritization of features.

Decisions Made:

 Core functionalities finalized: real-time messaging, group chats, and E2EE.

 Agreed to include group size limits and multimedia capabilities.

Action Items:

 Team member A to draft the functional requirements section.

 Team member B to research communication protocols for inclusion.

5.1.1.3 Meeting 3: Non-Functional Requirements and Interface Design

Date: 27/11/24
Attendees: Yogesh Kumawat, Vansh Sharma, Yash yogi.
Agenda:

 Define non-functional requirements.

 Discuss user interface requirements.

Decisions Made:

 Emphasis on performance, usability, and reliability.

 UI must support cross-platform compatibility with light/dark mode options.

Action Items:

 Team member C to draft the non-functional requirements section.

 Team member D to create mockup designs for user interfaces.

Software Requirements Specification for Whatsapp Page 11
5.1.1.4 Meeting 4: Final Review and Consolidation
Date: 3/12/24
Attendees: Yash yogi, Yogesh Kumawat, Vansh sharma.
Agenda:

 Review the completed sections of the SRS.

 Edit and finalize the document.

Decisions Made:

 Minor changes to the non-functional requirements.

 Finalized glossary and references.

Action Items:

 Team member A to proofread and format the document.

 All team members to review the final version for approval.

5.1.2 A.2 Group Activities Log

1. Research Phase:

o Team members conducted research on encryption protocols, UI/UX trends, and cloud
server performance.

o Documented findings and shared them during weekly meetings.

2. Drafting Phase:

o Functional and non-functional requirements were written collaboratively.

o Drafts were reviewed and iterated upon after team discussions.

3. Mockup Designs:

o Basic user interface mockups were created to visualize end-user interactions.

4. Finalization Phase:

o Consolidated individual contributions.

o Conducted multiple reviews to ensure compliance with IEEE standards.

5.1.3 A.3 Effort Assessment

Team Member Role Tasks Completed Hours Invested

Software Requirements Specification for Whatsapp Page 12
Team Member Role Tasks Completed Hours Invested
Yash yogi Research Lead Drafted functional requirements, glossary [20hrs]
Yogesh Kumawat Document Coordinator Edited and formatted the document [45hrs]
Vansh sharma UI/UX Specialist Designed interface mockups [48hrs]
Yogesh Kumawat Technical Researcher Analyzed encryption protocols [12hrs]