Software Requirements Specification (SRS) for WhatsApp-like Website

1. Introduction

Purpose: This document outlines the functional and non-functional requirements for a WhatsApp-like
website that allows users to send and receive text messages, multimedia messages, make voice/video
calls, and interact with other users in real time.

Scope: The website allows users to create accounts, message other users, share media (text, images,
videos, documents), and participate in group chats. It also supports voice and video calling.

2. Overall Description

Product Perspective: The website is a web-based application mimicking WhatsApp's core features,
providing real-time messaging, media sharing, and communication tools.

User Classes and Characteristics:

End Users: People who create accounts, send messages, share multimedia, make voice and video calls,
and manage contacts.

Admin: Users who manage the platform's integrity, monitor suspicious activity, and handle user support.

Assumptions and Dependencies:

The website requires a stable internet connection.

It supports all modern web browsers (Chrome, Firefox, Safari, etc.).

Mobile number verification will be used for user authentication.

3. System Features

3.1 User Authentication

Description: Users need to log in and authenticate their identity before accessing the website.

Functional Requirements:

Users can sign up using their mobile number and receive an OTP (One Time Password) for verification.

Users can log in using their mobile number and OTP.

Users can log out of their account securely.

Forgotten passwords should be recoverable through OTP.

Non-Functional Requirements:

Ensure encryption of sensitive data such as phone numbers and authentication tokens.

3.2 Messaging
Description: Users should be able to send and receive text messages, media files, and voice notes in real
time.

Functional Requirements:

Users can send and receive real-time text messages to/from individual users and groups.

Users can send media, including images, videos, audio clips, and documents.

Messages should support features like sending emojis, stickers, and GIFs.

Messages should show timestamps and read receipt indicators (e.g., delivered, read).

Users can delete messages or media sent within a given timeframe.

Non-Functional Requirements:

Messages should be delivered in real-time with low latency.

The system should be able to handle a high number of concurrent users.

3.3 Voice and Video Calls

Description: Users should be able to make and receive voice and video calls with other users.

Functional Requirements:

Users can initiate one-on-one voice and video calls.

Users can accept or reject incoming voice/video calls.

Users can mute/unmute and switch between front and back camera during video calls.

Users should have the option to switch to a voice call during a video call.

Non-Functional Requirements:

Calls should be clear with minimal lag or disruptions.

Calls should be encrypted for security.

The system should automatically adjust call quality based on network conditions.

3.4 Group Chats

Description: Users should be able to create and participate in group chats with multiple users.

Functional Requirements:

Users can create a group, add/remove members, and assign admins.

Group admins can control who can send messages or change the group settings.

Users can send text messages, media, and documents in the group.
Users should be able to name the group, set a group icon, and update group details.

Non-Functional Requirements:

Real-time updates for new messages in group chats.

Efficient synchronization of group members' messages.

3.5 Notifications

Description: Users should receive notifications for new messages, calls, and events.

Functional Requirements:

Notifications for new messages should be received immediately.

Users should receive push notifications for incoming messages, even if the web app is not open.

Users can turn off or customize notification preferences (e.g., mute a chat).

Users can get notifications for missed calls.

Non-Functional Requirements:

Notifications should be sent in real-time with minimal delay.

Users should receive notifications even if they are not on the website.

3.6 Contact Management

Description: Users should be able to manage their contacts and chat with users who have shared their
contact information.

Functional Requirements:

Users can add or remove contacts from their address book.

Users can block/unblock contacts.

Users should be able to search for contacts by phone number or name.

The system should sync contacts automatically from the user's phone.

Non-Functional Requirements:

User's contact list should update in real-time.

3.7 Media Storage and Sharing

Description: Users can share and store media like images, videos, and documents.

Functional Requirements:

Users can share photos, videos, and documents in chats.

The website should compress images and videos for faster loading.

Non-Functional Requirements:

Media should be stored securely, with backups to prevent data loss.

Media should be delivered in a compressed format to optimize bandwidth.

3.8 Data Encryption and Privacy

Description: All communication and user data should be encrypted to ensure privacy and security.

Functional Requirements:

All messages and calls should be end-to-end encrypted.

User data (phone number, messages, media) should be stored securely and comply with data privacy
laws.

Non-Functional Requirements:

The system must ensure strong encryption standards.

The system should comply with relevant data privacy laws (e.g., GDPR).

3.9 User Profile and Settings

Description: Users should be able to manage their profiles and customize their settings.

Functional Requirements:

Users can update their profile picture and display name.

Users can change their status and set privacy settings.

Users can manage security settings (e.g., two-factor authentication).

Non-Functional Requirements:

Profile changes should be reflected in real-time.

4. External Interface Requirements

4.1 User Interface

The website should have a clean, modern, and intuitive design that mimics WhatsApp’s simplicity.

The website should be fully responsive and functional across desktop, tablet, and mobile browsers.

The interface should support keyboard shortcuts for quick navigation.

4.2 Hardware Interfaces

It will interface with users' webcams, microphones, and other hardware during voice and video calls.

4.3 Software Interfaces

The website should use WebRTC or similar technologies for voice and video calling.

It should be integrated with push notification services for real-time alerts.

5. System Attributes

5.1 Performance

The website should support high concurrency and fast message delivery.

Voice/video calls should have low latency with minimal interruptions.

5.2 Security

All user communications (text messages, calls, media) should be end-to-end encrypted.

Strong user authentication via OTP or two-factor authentication.

Secure media storage, preventing unauthorized access.

5.3 Scalability

The system should scale horizontally to handle millions of users.

Efficiently handle spikes in traffic, particularly during high usage times.

5.4 Availability

The system should ensure 99.9% uptime, with a disaster recovery plan in place.

5.5 Usability

The website should have an intuitive UI/UX for ease of use.

New users should be able to sign up and start chatting in just a few minutes.

5.6 Compliance

The platform must comply with data privacy regulations (e.g., GDPR, CCPA).

Regular security audits and privacy reviews should be conducted.

6. Other Non-Functional Requirements

6.1 Localization

The website should support multiple languages for global usage.

6.2 Backup and Recovery

The system must perform regular backups of user data and media.

A disaster recovery plan should be in place to handle server failures or data loss.