Software Requirements

Specification

for

PIXEL PALETTE

Version 1.0approved

Prepared by

Arnav Raina
(21bcs019)

Swastik Sharma
(21bes092)

Utkersh Uppal
(21bcs098)

Mr. Anuj Mahajan

(Assistant Professor SoCSE) 13-03-2024
Contents
1. INTRODUCTION..
1.1 Document Purpose
1.2 Product Scope.. 3

1.3 Definitions, Acronyms And Abbrevations. 3

1.4 Refrences And Refrences. 3

1.5 Overview 3

2. OVERALL DESCRIPTION 4

2.1 Product Perspective.

2.2 Product Functionalities 4

2.3 User Characterstics.

2.4 General Constraints.. 5

2.5 Assumptions And Dependencies. 5

3.SPECIFIC REQUIREMENTS 6

3.1. External Interface Requirements 6

3.1.1 User Interfaces 6

3.1.2 Hardware Interfaces 6

3.1.3 Software Interfaces. 6

3.2 Functional Requirements. 6

3.2.1 Authentication
3.2.2 Image Upload
3.3 Use Case Model... .6

3.3.1 Use Case 1: User Authentication 6

3.3.2 Use Case 2: Community Image Showcase. 7

3.3.3 Use Case 3: Advanced Image Search. 7

3.3.4 Use Case 4: Image Processing functionalities.. 8

3.3.5 Use Case 5: Payment Integration

3.4 Performance Requirements.
3.5 Design constraints..
3.5 Other Requirements. 10

4. APPENDICES ..a.......
..12

2
1. INTRODUCTION
1.1 DOCUMENT PURPOSE
The purpose of this Software Requirements Specification (SRS) document is to
provide a detailed description of the requirements for the developmentof an Al
image SaaS platform.This platform willoffer advanced image processing
capabilities, secure payment infrastructure, advanced image search functionalities,
and support for various Al features.

1.2PRODUCT SCOPE
The software will be developed as a web application using modern web
technologies. It wil include features such as authentication, image processing
functionalities, payment integration, and user management.

1.3 DEFINITIONS,ACRONYMS ANDABBREVIATIONS

SaaS: Software as a Service
Al: Artificial Intelligence
U: User Interface
UX: User Experience
CRUD: Create, Read, Update, Delete

1.4 REFERENCES AND ACKNOWLEDGMENTS

TypeScriptDocumentation
MongoDB Documentation
Clerk Documentation
Cloudinary Documentation
Stripe Documentation
Shadcn Documentation

1.5 OVERVIEW
The Al Image SaaS platform is an innovative solution designed to meet the diverse image
processing needs of users ranging from hobbyists and professionals to businesses and
researchers. Leveraging cutting-edge technologies such as Nextjs, TypeScipt, MongoDB,
Clerk,Cloudinary, Stripe, Shadcn, and TailwindCSs, the platform offers a comprehensive
suite of features for image transformation,customization, and enhancement.
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
The Al image SaaS platform(pixel palette) will serve as a standalone web
application, offering various image processing functionalities and payment
integration. It will interact with external services such as Stripe for payment
processing and Cloudinary for image storage and processing.:
Home Page: Allows anyone to browse and view images without requiring login.

Upload Page: Enables users to upload images.

User and Sign-In Page: Provides login functionality for users
Signup Page: Allows new users to register.

2.2 PRODUCT FUNCTIONALITIES

The platform will include the followingfeatures:
Authentication and Authorization
Community Image Showcase
Advanced Image Search
Image Restoration
Image Recolouring
Image Generative Fill
Object Removal
Background Removal
Download Transformed Images
Transformed Image Details
Transformation Management
Credits System
Profile Page
Credits Purchase
Responsive UWUX

2.3 USER CHARACTERSTICS

The users of the system include:
Regular Users: Individuals who upload images for processingand utilize the
platforms features.

4
2.4 GENERAL CONSTRAINTS
The platform will be built using Next.js and TypeScript, utilizing MongoDB for data
storage, Clerk for authentication, Cloudinary for image processing and storage,
Stripe for payment integration, and Tailwind CSSfor styling.

2.5 ASSUMPTIONS A\ND DEPENDENCIES

Assumptions:
interact
Users have a basic understanding of how to navigate and
with web applications.
Users have access to a stable internet connection.

Dependencies:
authentication, data
Express services are relied upon for user
storage, and backend functionality.
Next.js framework is used for frontend development, requiring
adherence to its conventions and best practices.

5
3.Specific Requirements
3.1. External Interface Requirements
3.1.1 User Interfaces
Home Page: Allows anyone to view images without logging in.
Upload Page: Enables users to upload images.
Sign-In Page: Allows both users to log in.

Sign-Up Page: Enables new user registration.

Admin-page: Checks the user data stored in MongoDB

3.1.2 Hardware Interfaces

browsers and does not require any
The application runs on standard web
specific hardware interfaces.

3.1.3 Software Interfaces

for building the web application.
Next.js: Frontend and backend framework
storage of the user data
Expressand MongoDB: Database and

3.2 Functional Requirements

3.2.1Authentication
functionalities.
Users must sign in to access their respective
New users can register through the sign-up page.

3.2.2 Image Upload

Users can upload photos to edit through the upload functionality.

3.3 Use Case Model

3.3.1 Use Case 1: User Authentication
Actor: User

Description: Authenticate user credentials to access the

application functionalities.
Preconditions: User must have registered credentials.

6
 Steps:
1. User navigates to the sign-in page.
2. User enters username and password.

3. System verifies the credentials.

redirected to the
4. If authentication is suCcessful, user is
respective dashboard.
Exception Scenarios:
username or paSSWord:
If the user enters an incorrect invalid credentials.
message indicating
The system displays an error
authentication.
User is prompted to retry

Image Showcase
3.3.2 Use Case 2: Community
Actor: User
transformations made by other
Description: Users can explore
navigation
through ashowcase with easy
user must be signed in.
Preconditions: For viewing the details the

Steps:
shoWcase page.
User navigates to the community image
images using pagination.
User browses through the showcased
its details.
User clicks on an image to view
Exception Scenarios:
If the user is not signed in:
in before accessing
The system prompts the user to sign
the community image showcase

3.3.3 Use Case 3: Advanced Image Search

Actor: User

Description: Verify uploaded images for validity.

Preconditions: User must be logged in.

Steps:

7
 1. User navigates to the advanced image search page.
2. User enters keywords or selects objects to search for.
search criteria.
3. System retrieves relevant images based on the
4. User views the search results

Exception Scenarios:
If the search criteria yield no results:
indicating no matching images
o The system displays a message
were found.

functionalities
3.3.4 Use Case 4: Image Processing
Actor: User
offers various image processing functionalities including
Description: The platform removal
recoloring, generative fill, object removal, and background
restoration,
authenticated.
Preconditions: User must be

Steps:
platform.
User uploads an image to the
image processing functionality.
User selects the desired selected functionality.
according to the
System processes the image
processed image.
User reviews and approves the
image.
User can download the processed
Exception Scenarios:
unsupported:
If the uploaded image format is message and prompts the user to
uploada
The system displays an error
supported image format.
technical issues:
If the image processing fals due to
failure and suggests retrying later
o The system notifies the user of the

3.3.5 Use Case 5: Payment Integration

Actor: User
Description: Users can purchase credits for image transformations securely via Stripe.

Preconditions: User must be authenticated.

Steps:
User navigates to the credits purchase page.
User selects the desired credit package and clicks on the
purchase button.

8
 System redirects the user to the Stripe payment gateway.
User enters paymentdetails and completes the transaction.
System updates the user's credit balance.

ExceptionScenarios:
If the payment transaction fails:
the payment or try an
The system prompts the user to retry
alternative payment method.
with the Stripe payment gateway:
" If there's a communication error indicatingthe issue and advises the
displays a message
Thesystem
user to try again later.

3.4 Performance Requirements user

application should be responsive and provide a seamless seconds.
The 2
system should respond to user actions within
experience. The
processes should be efficient, with minimal latency.
Upload and download standard
should be completed within 10seconds for
Image processing
sized images.

3.5 Design constraints that

the Alimage SaaS platform encompass various factors
Design constraints for implementation approach. These constraints ensure
limit the design choices and regulatory, and
platform meets its objectives while considering technical,
the formulated design constraints for the project:
usability aspects. Here are some

The platform must be developed using

the
1, Technology Stack Compatibility:
MongoDB, Clerk, Cloudinary, Stripe,
specified technologies (Next.js, TypeScript,
integration, and optimal performance.
Shadcn, TailwindCSS) to ensure compatibility,

scalability to accommodate agrowing

2. Scalability: The architecture must support
demands. It should be capable of
user base and increasing image processing
handlingconcurrent user requestsefficiently.

industry-standard security
3, Security Compliance: The platform must adhere to
practices and comply with relevant regulations (e.g., GDPR) to protect user data,
ensure secure authentication, and handle payment transactions securely.

9
5. Data Privacy: User data, including images and personal information, must
be handled with strict confidentiality and protected against unauthorized
access, manipulation, or disclosure.

6. Payment Gateway Integration: The platform must integrate seamlessly with

the Stripe payment gateway to facilitate secure credit purchases for image
transformations.

APls (e.g., Cloudinary

7. Third-Party API Dependencies: Integration with external
reliable and robust, considering
for image storage and processing) should be
potential APl rate limits, downtime, or changes in APIfunctionality.

interface should be intuitive, responsive,

8. User Experience (UX): The platform's user engagement.
satisfaction and
and optimizedfor usability to enhance user

3.5 Other Requirements

based on SaaS platform are:
The hardware requirements for the Al Image

1. Server Infrastructure
High-performance servers capable of handling concurrent user requests
and image processing tasks efficiently.
CPU: Multi-core processors with high clock speeds to ensure fast
image processing.
RAM: Sufficient memory to handle multiple user sessions and image
processingoperations simultaneously.
Storage: SSDstorage for fast data access, with ample capacity to store
user-uploaded images and processed data.
Network: High-speed internet connection to ensure smooth data
transfer between clients and servers.

2.Database Server
Dedicated database server with sufficient CPU, RAM, and storage
resources to handle data storage and retrieval.
Database Management System (DBMS): MongoDB for storing user data,
image metadata, and system configurations.
10
4,Backup and Redundancy
Regular data backups to prevent data loss in case of server failures or disasters.
Redundant server setup with load balancing to distribute incoming traffic
andensure high availability.

5. Development and Testing Environment

Development servers for testing and debugging application code.
creating
Virtualization or containerization technology (e.g., Docker) for
isolated development environments.

6. Monitoring and Analytics

resource utilization,
Monitoring tools for tracking server performance,
and application health.
patterns, and system usage
Analytics tools for analyzing user behavior, traffic
experience.
to optimize performance and user

8. Hardware Security
hardware from
Physical security measures for protecting server
unauthorized access or tampering.
detection/prevention
Network security protocols (e.g., firewalls, intrusion
attacks.
systems) to safeguard against cyber threats and

platform can
By meeting these hardware requirements, the AL Image SaaS
users.
ensure reliable performance, scalability, and security for its

11
4. APPENDICES
5.1 Document history
Version 1.0: Initial release (YYYY-MM-DD)

5.2 Contact information

For any inquiries or assistance, please
contact 21bcs019@smvdu.ac.in
21bcs092@smvdu.ac.in
21bcs098@smvdu.ac.in