The Islamia University of Bahawalpur

Department of Computer Science

SOFTWARE REQUIREMENTS SPECIFICATION

(SRS DOCUMENT)

for
Fruits-SELLING-WEBSITE
Version 1.0
By

Muhammad Hamza
F20BDOCS1E02019
Session Fall 2020-2024

Supervisor

Sir Fahad Ali

Bachelor of Science in Computer Science

 2
Application Evaluation History

Comments (by committee) Action Taken

*include the ones given at scope time both in
doc and presentation

Supervised by
SIR FAHAD ALI

Signature

1
 Contents
1 Chapter# 1.................................................................................................................................. 3

Introduction....................................................................................................................................3
1.1 Purpose.................................................................................................................................. 3

1.2 Scope......................................................................................................................................3

2 Chapter # 2................................................................................................................................. 3

Overall Description.....................................................................................................................3
2.1 Product Perspective...............................................................................................................3

2.2 Operating Environment.........................................................................................................4

2.3 Design and Implementation Constraints................................................................................4

3 Chapter # 3................................................................................................................................. 5
Requirements Identifying Techniques.........................................................................................5
3.1 Use Case Diagram................................................................................................................ 5

3.2 Use case description............................................................................................................. 6

4 Chapter # 4.............................................................................................................................. 10

4.1 Functional Requirements....................................................................................................10

4.2 Non Functional Requirements...........................................................................................12

4.2.1 Usability Requirements...................................................................................12

5 Chapter # 5 ............................................................................................................................ 13
References

2
 Chapter #1

1. Introduction

Welcome to Fresh Fruits Galaxy - Nature's Best Gifts Revealed!

As you step into the dynamic range of our natural product retail shop, you're not simply visiting a site;
you're leaving on a delightful excursion into the core of Earth's life giving force's liberality. At Plantation
Bounties, we put stock in praising the basic yet significant delights that the freshest and best natural
products give.
1.1Purpose

The purpose of this Software Requirements Specification (SRS) document is to establish a clear and
comprehensive set of requirements for the development and implementation of "Fresh Fruits Galaxy," an
online platform dedicated to the selling of an extensive variety of fresh fruits. This document aims to
facilitate communication among stakeholders, provide a basis for estimating costs and timelines, and serve
as a guide for developers and designers in the creation of the system.
1.2 Scope

"Fresh Fruits Galaxy" will provide customers with an online marketplace for purchasing a wide array of
fruits sourced from local farms and international suppliers. The platform will aim to make fruit shopping
convenient, efficient, and enjoyable. More than just a retail site, it will include features such as fruit
descriptions, nutritional information, and recipe suggestions, enhancing the shopping experience while
educating customers about the products.

3
 Chapter #2

2.Overall description

2.1 Product perspective

A comprehensive online platform that provides customers with access to a diverse selection of food
products will be the food selling website. It will act as an all in one resource for clients to buy a different
scope of food things, including new produce, storage room staples, specialty food varieties, and prepared
to-eat feasts. The site will take special care of the necessities of people and families looking for quality,
accommodation, and assortment in their food buys.

According to the client's point of view, the site will furnish a natural point of interaction with simple route,
permitting clients to peruse different food classes, view nitty gritty item depictions, and make secure web-
based installments. There will be a consistent client experience, with elements like pursuit usefulness,
customized proposals, and an easy to understand checkout process.
2.2 Operating environment

The operating environment for a food selling website can be summarized as follows:
: Compatible with Windows XP, Vista, 7, 8, 8.1, and 10.
: Developed using Php(Laravel) programming language.
: Requires WiFi connection for communication.
2.3 Design and implementation constraints
The following are the design and implementation constraints for The PetPals Market's website:
2.3.1 Programming Language: This setup uses front-end HTML, CSS, Bootstrap, and JavaScript to build the
user interface and interact with the database. Back-end PHP and Laravel are used to process data on the server
side, interact with databases, and build robust web applications.

2.3.2 Development tools: Wampserver provides a local server environment with Apache, MySQL, and PHP
for testing web applications, Visual Studio Code is an open-source code editor with features like syntax
highlighting and debugging tools.

2.3.3 Security and Privacy: Security and privacy of user data, financial transactions, and communication must
be prioritized during design and implementation. This includes adhering to regulations regarding the

4
protection of data, putting in place safe authentication and authorization mechanisms, and effectively
defending against cyber threats.

2.3.4 Payment Gateway Integration: The availability of payment processing partners, compliance with
financial regulations, and potential restrictions on international transactions may limit the integration of a
secure and dependable payment gateway to facilitate transactions.

2.3.5 Seller Verification: The stage should incorporate instruments to approve the validity and authenticity of ,
which might fruits be compelled by the accessibility of outsider confirmation administrations and information
protection contemplations.

2.3.6 User Experience and Accessibility: The need to accommodate users with varying abilities,
preferences, and technological capabilities may limit the design and implementation of an intuitive and
accessible user experience.

Chapter #3

3.Requirement identifying technique:

This section describes the requirements identifying technique(s) which further help to derive
functional requirements specification. The selection of the technique(s) will depend on the type of
project. For instance,

1. Use case is an effective technique for interactive end-user applications

2. Event- response tables is for real time system and

3.Story boarding for graphically intensive applications.

In addition to above, the projects involving data warehouses, batch processes,

hardware devices with embedded control software, and computationally intensive
applications required to follow other suitable techniques. Such techniques are
described further in Chapter 12, “A picture is worth1024 words.” For documenting
this section let consider identifying requirements through

5
3.1 Use case diagram
One of the primary features of the website is the ability to view products. This feature allows customers
to browse a wide range of products, including fruits like Apple Mango etc. Additionally , the website
provides a search function that enables customers to find specific products according to their preferences.
The website also offers the ability to add products to a cart and checkout. Customers can add products to
their cart and complete transactions securely using various payment methods, such as credit cards, HBL,
and others. This feature ensures that customers can complete transactions

3.1.1 Benefits of creating this use case diagram:

Creating a use case diagram for the E-commerce website provides benefits for the project team and
stakeholders. The use case diagram helps to define the scope of the system and identify the key functionalities
that it should provide. This makes it easier for the project team to prioritize tasks and allocate resources
effectively. By understanding the needs and requirements of customers and website administrators, the team
can develop a system that meets their expectations and provides a seamless user experience.

6
1.1Use case description

Table. 1 use case description User Registration

Use Case ID: PF-01
Use Case User Registration
Name:
Actors: User (Primary)
System (Secondary)

Description: This use case involves a user who wants to register on the fruits-selling
website to access the platform's features and services
Trigger: None
Preconditions: The user has accessed the fruits -selling website and intends to register as a
new user.
Postconditions: The user has successfully registered and can now log in to the website using
the provided credentials.
Flow of  The client taps on the "Register" or "Sign Up" button on the site's
Events:
landing page.
 The user is prompted to fill out information like their name, email
address, and password on a registration form that is displayed by the
system.
 The client fills in the necessary data and presents the enrollment
structure.
 The information entered is checked for errors and missing fields by the
system.
 The user is registered as a new member and given a unique user ID if
there are no validation issues.
 The framework sends an affirmation email to the client's given email
address to confirm the enrollment.
 The client follows the connection in the affirmation email to actuate the
record.
Exceptions: None.

7
1.2Use case description

Table. 2 use case description Searching for fruits

Use Case ID: PF-02
Use Case Fruits for Serarching
Name:
Actors: User (Primary)
System (Secondary)
Description: This use case involves a user searching for specific fruits available for sale
on the website.

Trigger: None
Preconditions: The user is logged in and has accessed the fruits -selling website to search for
fruits likes Apple, mango etc.
Postconditions: The user has successfully found and reviewed pet listings that match the
specified search criteria and can take further actions, such as contacting
sellers or making purchases
Flow of Events:  The user navigates to the search or browse section of the website.
 The user selects and inputs the desired search criteria.
 The user reviews the search results and selects a specific product
listing for more details.
 The system displays comprehensive information about the selected
fruits, including images, description, seller contact details, and
pricing.
 The user may choose to contact the seller for further inquiries or
proceed with purchasing the fruits.

1.3 Use case description

Table3. View Product

Use Case ID: PF-03
Use Case View Product on Website
Name:

8
Actors: Buyer

Description: The customer visits the website and navigates to the product page.
The website displays a list of products available for purchase.
The customer selects a specific product to view more details
Trigger: The customer selects a product category or searches for a specific
product on the website.
Preconditions: The customer has access to the internet and a web browser.

Postconditions: The customer has viewed the product details and may proceed with the
purchase or continue browsing.

Exceptional Flows: . If the website is experiencing technical issues, the product details may
not be displayed properly.

.
1.4 Use case description

Table4. Purchasing
Use Case ID: PF-04
Use Case Purchasing
Name:
Actors: Customer, Seller

Goal in The primary goal of the fruits selling website is to facilitate the sale and purchase
Context: of pets by providing a platform where sellers can list their products for sale.

Trigger: None
Preconditions: The fruits selling website is accessible and operational.
Sellers have fruits available for sale.
Customers have access to the website and means for online transactions.
Post None
conditions:
Special The website should have secure payment processing to ensure customer transactions
Requirements are safe and protected.
:
Frequency of
Occurrence: Customers browsing and purchasing: Daily or as per their requirements.

9
 1.4 Use case description

Table5. Add to the cart.

Use Case ID: PF-05
Use Case Add to the cart.
Name:
Actors: Buyer

Description: This use case involves the process of adding items to the shopping cart on a
website.

Trigger: None
Preconditions: The customer must be logged into their account on the website.

Post The item is now added to the customer's shopping cart, and they can
conditions: continue shopping or proceed to checkout.
Main Flow: 1. The customer selects the item they want to purchase on the product page.
2. The customer clicks on the "Add to Cart" button.
3. The website adds the selected item to the customer's shopping cart.
4. The website displays a confirmation message to the customer indicating that
the item has been successfully added to the cart.
Alternative If the customer tries to add an item to the cart without being logged in, the
Flow: website prompts them to log in or create an account before adding the item to
the cart.

Chapter #4
Functional Requirements: User Registration and Login

Description: The framework will give a client enrollment and login usefulness to permit clients to
make records and access the stage
Features:
. Registration: The system should allow users to register by providing their personal details like name,
address, contact information, and a valid email address.
. Login: Registered users should be able to log in using their credentials (username/email and password) to
access the website.

10
. Profile Management: Users ought to be able to manage their profiles and update personal information.
. Security: To safeguard user data, the system ought to incorporate security features like account
verification and password encryption.
These functional requirements provide the basis for implementing the user registration and login features
on the fruits selling website.

4.1 Functional Requirement X:

4.1.1 Description: The fruits selling website should provide a user registration and login functionality to
allow users to create and manage their accounts. This requirement aims to ensure that users can securely
access the website and perform various actions as registered members.

4.1.2 Inputs:
 User registration details: name, email address, password, contact information, delivery address.
 User login credentials: email address and password.

4.1.3 Processing:

4.1.3.1 User Registration:

 The user provides the required registration details.

 The system validates the email address for uniqueness and format.
 The system stores the user information in the database.
 Confirmation email may be sent to verify the user's email address.

4.1.3.2 User Login:

 The user enters their registered email address and password.

 The system validates the credentials against the stored user information.
 If the credentials are correct, the user is granted access to their account.

4.1.4 Outputs:

4.1.4.1 Success message: User registration is successful.

11
 4.1.4.2 Error messages: Invalid email address, email address already exists, incorrect login credentials.

Table 4.1 Show the functional requirement pet buying

Identifier F-T10
Title Fruits Buying
Requirement
. Adress must always have Street,City,State,Zipcode,and Country.
. Contact adress is defined as an address.
. Shipping Adress is defined as an address.
. The billing System shall produce pet purchase invoices.

Priority High

4.2 Non-Functional Requirements:

A fruit-selling website's Non-Functional Requirements (NFR) emphasize aspects of the system that define the
criteria for evaluating its operation rather than specific behaviors, or "how" the system works rather than
"what it does."
4.2.1 Performance Requirements:
 The website should load within 3 seconds when tested on a standard broadband connection.
 Search results for fruits should be displayed within 2 seconds.
 The system should support up to 10,000 simultaneous users without degradation in performance.
4.2.2 Usability Requirements:
 The website should be usable by people with no technical expertise.
 Navigation should be consistent and intuitive across all pages.
 The website should conform to WCAG 2.1 Level AA to ensure accessibility.
4.2.3 Security Requirements:
 The website must implement SSL encryption for all transactions.
 Users’ personal and payment data should be encrypted using at least AES-256 encryption.

12
  The system should be compliant with the latest OWASP security standards to protect against common
web vulnerabilities.
4.2.4 Reliability Requirements:
 The website should have an uptime of 99.9% outside of scheduled maintenance windows.
 Transactions should complete accurately with a 99.995% success rate.
 Daily backups have to be performed, and the system should support rapid restoration within 4 hours in
the event of a major failure.
4.2.5 Scalability Requirements:
 The system should be designed to scale up to accommodate a 20% increase in user load per year.
 The hosting infrastructure must provide the flexibility to scale resources up or down based on real-
time demand.
4.2.6 Compatibility Requirements:
 The website should be compatible with the latest versions of Chrome, Firefox, Safari, and Edge
browsers.
 The website should provide a responsive design that adapts seamlessly to mobile, tablet, and desktop
screens.
Chapter #5

References

A. www.wikipedia.org/
B. www.w3schools.com
C. www.google.com
D. www.laravel.com

13