lOMoARcPSD|413 342 37

TalkTime – chat application

Software Requirements

Specification 12/3/2024

Rishi Dubey

Roll No.-21C6049

Prepared for:
Software Engineering
practices assignment

2024
 D
lOMoARcPSD|413 342 37

Table of Contents

1. INTRODUCTION............................................................................................................................................ 1
1.1
PURPOSE...............................................................................................................................................................................................................1
1.2 SCOPE
....................................................................................................................................................................................................................1 1.3
DEFINITIONS, ACRONYMS, AND ABBREVIATIONS .............................................................................................................................1
1.4 REFERENCES
.......................................................................................................................................................................................................1 1.5
OVERVIEW...........................................................................................................................................................................................................1
2. SPECIFIC REQUIREMENTS......................................................................................................................... 2
2.1 EXTERNAL INTERFACE
REQUIREMENTS.................................................................................................................................................2 2.1.1 User
Interfaces..................................................................................................................................... 2 2.1.2
Hardware Interfaces............................................................................................................................. 2 2.1.3
Software Interfaces............................................................................................................................... 2 2.1.4
Communications Interfaces................................................................................................................... 2
2.2 FUNCTIONAL
REQUIREMENTS.....................................................................................................................................................................2 2.2.1 User
Authentication and Authorization................................................................................................ 2 2.2.2
Real-time Messaging............................................................................................................................ 2
2.3 NON-FUNCTIONAL
REQUIREMENTS.........................................................................................................................................................4 2.3.1
Performance......................................................................................................................................... 4 2.3.2
Reliability............................................................................................................................................. 4 2.3.2
Availability........................................................................................................................................... 4 2.3.4
Security ................................................................................................................................................ 4 2.3.5
Maintainability ..................................................................................................................................... 4 2.3.6
Portability ............................................................................................................................................ 4
2.7 DESIGN CONSTRAINTS
...................................................................................................................................................................................4 2.9 OTHER
REQUIREMENTS .................................................................................................................................................................................4
4. ANALYSIS MODELS...................................................................................................................................... 4 4.1
DATA FLOW DIAGRAMS (DFD) .................................................................................................................... 5 5.
GITHUB LINK................................................................................................................................................ 5 A.
APPENDICES ................................................................................................................................................. 5
A.1 APPENDIX 1................................................................................................................................................. 5 A.2
 Appendix 2 ................................................................................................................................................. 5

lOMoARcPSD|413 342 37
Software Requirements Specification Page ii

1. Introduction
The introduction to the Software Requirement Specification (SRS) document should provide an
overview of the complete SRS document. While writing this document please remember that this
document should contain all of the information needed by a software engineer to adequately
design and implement the software product described by the requirements listed in this
document. (Note: the following subsection annotates are largely taken from the IEEE Guide to
SRS).

1.1 Purpose
The purpose of this project is to develop a real-time chat application that enables users to
communicate seamlessly. This Software Requirements Specification (SRS) document provides a
comprehensive overview of the chat application, outlining the requirements, functionalities, and
constraints that will guide the design and implementation phases. The document serves as a
detailed guide for software engineers to develop the chat application with the described
features and functionalities.

1.2 Scope
The scope of this project encompasses the development of a real-time chat application using
Socket.io for real-time communication. The application will use MongoDB to store and
retrieve chat data and will utilize the Object-Relational Mapping (ORM) capabilities of
Mongoose for database interactions. The frontend will be developed using React, styled
with Tailwind CSS, while the backend will be built using Express.js. The application will
also implement JSON Web Tokens (JWT) for secure authentication and authorization of
users.
The target users for this chat application include individuals and groups who wish to
communicate in real-time. Users will interact with the application through a
user-friendly and responsive UI, facilitating smooth communication and an engaging
user experience.
1.3 Definitions, Acronyms, and Abbreviations
• Socket.io: A JavaScript library for real-time web applications.
• MongoDB: A NoSQL database for storing and retrieving data.
• Mongoose: An Object-Data Modeling (ODM) library for MongoDB and Node.js. •
React: A JavaScript library for building user interfaces.
• Express.js: A web application framework for Node.js.
• JWT: JSON Web Token for secure authentication and authorization.
• Tailwind CSS: A utility-first CSS framework for rapid UI development.

1.4 References
• Socket.io Documentation
• MongoDB Documentation
• Mongoose Documentation

lOMoARcPSD|413 342 37
Software Requirements Specification Page 1

• React Documentation
• Express.js Documentation
• JWT Documentation
• Tailwind CSS Documentation
.

1.5 Overview
The chat application is designed to provide users with a platform for real-time communication.
It will feature a user-friendly and responsive interface developed using React and Tailwind
CSS, ensuring an engaging and intuitive user experience. The backend, built with Express.js
and utilizing Socket.io, will facilitate real-time communication between users, with
MongoDB and Mongoose handling data storage and retrieval. Secure authentication and
authorization will be implemented using JWT, ensuring the privacy and security of user
interactions.

2. Specific Requirements
2.1 External Interface Requirements
2.1.1 User Interfaces
The user interface will be developed using React and styled with Tailwind CSS to provide a
responsive and engaging experience for users. The UI will consist of:
• Login/Register Page: A page where users can log in to existing accounts or register for
new accounts.
• Chat Interface: A real-time messaging interface displaying user conversations and
enabling users to send and receive messages.
2.1.2 Hardware Interfaces
The chat application will not have any specific hardware requirements and will be accessible on
standard computing devices such as laptops, desktops, tablets, and mobile phones.
2.1.3 Software Interfaces
• Backend:
• Express.js: The backend framework for handling server-side operations. •
Socket.io: The library for real-time communication between the server and
clients.
• MongoDB: The database for storing and retrieving chat data.
• Mongoose: The ORM for MongoDB and Node.js for database interactions. •
JWT: JSON Web Tokens for secure authentication and authorization. • Frontend:
• React: The library for building the user interface.
• Tailwind CSS: The framework for styling the UI.

lOMoARcPSD|413 342 37
Software Requirements Specification Page 2

2.1.4 Communications Interfaces

• Real-time Communication:
• Socket.io: For establishing real-time communication channels between the server
and clients.
• Data Storage and Retrieval:
• MongoDB: For storing and retrieving chat data.

2.2 Functional Requirements

This section describes specific features of the software project. If desired, some requirements
may be specified in the use-case format and listed in the Use Cases Section.
2.2.1 User Authentication and Authorization
• FR1.1: Users should be able to register by providing a username, email, and password. •
FR1.2: Users should be able to log in using their email and password. • FR1.2: The
application should validate user credentials and generate a JWT for authenticated users.
• FR1.4: Authenticated users should be authorized to access and participate in chat
conversations.
2.2.2 User Authentication and Authorization
• FR2.1: Users should be able to send and receive real-time messages within the app. •
FR2.2: The application should display the online status of users in the chat rooms.

2.3 Non-Functional Requirements

2.3.1 Performance
• The application should support concurrent connections for real-time messaging. •
Messages should be delivered in real-time with minimal latency.

2.3.2 Reliability
• The application should handle errors and exceptions gracefully, ensuring uninterrupted
service.

2.3.2 Availability
• The application should be available 24/7 with minimal downtime.

2.3.4 Security
• User passwords should be securely hashed and stored.
• JWT should be used for secure authentication and authorization.
• Data transmission should be encrypted using HTTPS.

lOMoARcPSD|413 342 37
Software Requirements Specification Page 3

2.3.5 Maintainability
• The codebase should be well-organized and documented to facilitate maintenance and
future development.
2.3.6 Portability
• The application should be accessible and functional across various devices and web
browsers.

2.4 Design Constraints

• The application must be developed using React for the frontend and Express.js for the
backend.
• Socket.io must be used for real-time communication.
• MongoDB must be used for data storage, with Mongoose handling database interactions.

2.5 Other Requirements

 The application should provide a seamless user experience with an intuitive and responsive
UI.
 The application should comply with data protection regulations and best practices for user
privacy and security.

3. Analysis Models
List all analysis models used in developing specific requirements previously given in this SRS.
Each model should include an introduction and a narrative description. Furthermore, each
model should be traceable the SRS’s requirements.

3.1 Data Flow Diagrams (DFD)

The Data Flow Diagram (DFD) provides a visual representation of the flow of data within the
chat application, illustrating how data moves between the system components.

Level 0 DFD (Context Diagram)

• Entities:
• User: The individuals interacting with the chat application.
• System: The chat application system consisting of frontend, backend, and
database.
• Processes:
• Login/Registration: Process for user authentication and registration.
• Real-time Messaging: Process for sending and receiving real-time messages. •
Data Storage and Retrieval: Process for storing and retrieving chat data. • Data
Stores:
• MongoDB Database: The database storing user information and chat data. •
Data Flows:
• User Data: Flow of user information between the User and the System. Software Requirements

Specification Page 4
lOMoARcPSD|413 342 37

• Chat Messages: Flow of real-time messages between the User and the System. •
Stored Messages: Flow of messages between the System and the MongoDB
Database.
Level 1 DFD
• Login/Registration Process:
• Input: User credentials (username, email, password).
• Output: JWT token, user profile data.
• Real-time Messaging Process:
• Input: User messages, chat room details.
• Output: Sent and received messages, user online status.
• Data Storage and Retrieval Process:
• Input: User messages, chat room details.
• Output: Stored chat messages, user profile data.
 Software Requirements Specification Page 5 lOMoARcPSD|413 342 37

A. Appendices
A.1 Appendix 1: Initial Conceptual Documents
This appendix contains the initial conceptual documents for the chat application
project. • Project Overview:
• Description: The chat application aims to provide real-time communication
capabilities to users, allowing them to send and receive messages in real-time. •
Objectives:
• Enable user registration and authentication.
• Facilitate real-time messaging between users.
• Store and retrieve chat data using MongoDB.
• Scope:
• Development of frontend using React and Tailwind CSS.
• Development of backend using Express.js and Socket.io.
• Implementation of JWT for secure authentication and authorization.
• Integration with MongoDB using Mongoose for data storage and retrieval.
A visual representation illustrating the interaction between the frontend, backend,and database
components of the chat application.
• User Interface Mockups:
• Design mockups showcasing the layout and features of the chat application's user
interface, including the login/register page, chat interface, and user profile page. • Database
Schema:
• A schema design for the MongoDB database, detailing the structure of the
database and the relationships between the data entities.
Note: The information contained in Appendix 1 is considered as a part of the SRS’s overall
set of requirements.

A.2 Appendix 2: Meeting Minutes with the Customer(s)

This appendix contains the minutes of meetings held with the customer(s) during the
project planning and development phases.
• Project Kick-off Meeting:
• Discussion of project requirements, objectives, and scope.
• Agreement on the technologies and tools to be used for frontend and backend
development.
• Design and Development Meetings:
• Discussions on system design, architecture, and development progress. •
Review and validation of the implemented features and functionalities. • Review
Meetings:
• Feedback sessions with the customer(s) to review the progress and discuss any
issues or requirements.
• Final Project Review Meeting:
• Conclusion meeting with the customer(s) to review the final product, validate the
implemented features, and discuss any remaining issues or requirements.
•
Note: The information contained in Appendix 2 is considered as a part of the SRS’s overall
set of requirements.