Synopsis

1.1 Title of the project: Online Chocolate Store

1.2 Objective of the project: To provide a wide range of high-quality chocolates and treats to
customers through a seamless, user-friendly online shopping experience. We aim to offer exceptional
customer service, and a diverse selection of flavours, ensuring that every chocolate lover can easily
indulge in their favourite sweets from the comfort of their home.

1.3 Problem analysis:

1. Market Competition: Focus on offering unique flavours and personalized services like custom
packaging or gift options to differentiate the brand.
2. Customer Trust and Satisfaction: Ensure detailed, accurate product descriptions, offer
customer reviews and ratings, provide guarantees on freshness.
3. Logistics and Shipping: Implement temperature-controlled shipping options or invest in
specialized packaging to maintain product quality during transit.
4. Inventory Management: Use a reliable inventory management system that helps track
demand, sales trends, and stock levels in real time.
5. Payment and Security: Ensure secure payment gateways and provide multiple payment
options to cater to a wide customer base.
6. Website Usability: Design a simple, easy-to-navigate website with clear calls to action.

1.4 Modules:
The system consists of two modules – The Admin Module and The End User Module.
Admin Module:
 The admin module of a Chocolate Store website is typically designed to provide website
administrators with tools to manage various aspects of the site efficiently.
 Allows admins to add, edit, and delete products, as well as manage product categories,
attributes, and inventory levels.
 Provides tools for managing user accounts, including creating new accounts, editing user
details, resetting passwords, and viewing user activity.
 Allows admins to update website content such as homepage banners and product descriptions
using a content management system.
 Enables admins to create and manage promotional campaigns, discount codes, and special
offers to attract customers and boost sales.
 Helps admins track and manage inventory levels, receive notifications for low stock items,
and synchronize inventory across multiple sales channels if applicable.
 Implements security measures to protect sensitive data and restrict access to certain features
or information based on user roles and permissions.

End User Module:

 Users can browse through various categories of Chocolate Store items such as different
varieties and flavours and many more.
 These modules typically include features such as product search, product categories, and
detailed product descriptions with images.
 Users can add items to their cart for purchase, and manage quantities or remove items as
needed.
 Users can create accounts to track orders and manage their personal information.
 Users can read and leave reviews and ratings for products, helping others make informed
decisions.
1.5 Future Scope:
Future enhancement to the system can be made as technology changes. This include development of
website in mobile application.
Advanced chatbots and automated customer service solutions can provide instant support to
customers, answering common queries about products, deliveries, returns, etc., which enhances the
user experience.

1.6 Hardware and Software Requirements:

 Laptop, Keyboard, Mouse
 HTML, MySQL, CSS, PHP, JavaScript
 XAMPP
 Text Editor (e.g. Visual Studio Code)

1.7 Benefits:
Shopping on a Chocolate Store website is super convenient! You can shop from home, save time, and
avoid crowds. With a wide range of products to choose from, you can easily find what you need and
compare prices. Customers enjoy the convenience of browsing and purchasing chocolates at any time,
making it a flexible shopping experience. This model also allows for 24/7 availability, meaning
customers can shop whenever it’s most convenient for them. Personalized experiences, like custom
chocolate boxes or unique flavours, can help build customer loyalty and stand out from competitors.
Overall, an online chocolate store provides flexibility, cost-effectiveness, and the potential for growth
through strategic marketing and personalized offerings.

1.8 Limitations:
1. Product Quality Control: Unlike in physical stores, customers can’t physically inspect the
chocolate before purchasing, which can lead to concerns about quality, especially with delicate
products like chocolates.
2. Shipping Challenges: Chocolates are temperature-sensitive and can melt or spoil during shipping,
especially in warmer climates or seasons, which requires additional care and packaging.
3. Limited Sensory Experience: Online shopping lacks the ability to smell or taste the chocolates
before purchasing, which can be a major drawback for food items that are often enjoyed for their
sensory qualities.
4. Storage and Shelf Life: Managing inventory for products with a limited shelf life can be tricky,
especially when balancing demand with perishable goods.
 System Requirement Specification
3.1 Introduction:
The software product is initiated by client’s needs. In beginning, these needs are in the minds of
various people of the client organization. The requirement analyst has to identify the requirements by
talking to these people and understanding their needs. The inputs have to be gathered from different
resources, these inputs may be inconsistent. The requirement phase translates the ideas in the minds of
the clients into a formal document. Software Requirements Specification (SRS) document is a
document that completely describes 'WHAT' the software must do without describing how the
software will do it.

3.2 Purpose:
 The purpose of this SRS is to specify the requirements of the web based software application,
which is an online Chocolate Store system.
 This Software Requirements Specification provides a complete description of all the functions
and specifications of modules.
 The basic purpose of the SRS is to bridge the gap between the developer and end user.
 Another important purpose of developing the SRS is to help clients to understand their own
needs.
 The final goal of the requirement is to produce a high quality and stable SRS.

3.3 Scope:
 The document is the one that describes the requirements along with interfaces for the system.
 It is meant for use by the developers and will be the basis for validating the final delivered
system. This SRS describes the requirements of the system.
 It is meant for use by the developer and will be the basis for validating the final delivered
system; any changes made to the requirement in the future will have to go through the formal
change approval process.
 This document contains complete description of the functioning of Chocolicious – online
shopping website.

3.4 Overview:
An Online Chocolate Store Software Requirements Specification (SRS) outlines the necessary
features, functionalities, and technical aspects needed to develop and maintain an e-commerce
platform dedicated to selling chocolates. The purpose of the SRS is to define the scope of the system,
which includes browsing products, managing a shopping cart, handling payments, and processing
orders. The system will feature a product catalogue displaying chocolates with detailed descriptions
and images, and allow users to add items to their cart and make secure payments through integrated
payment gateways. Additionally, customers will be able to track their orders, while administrators will
manage inventory and monitor order statuses via a backend interface. The SRS also includes non-
functional requirements such as security, performance, scalability, and availability, ensuring the
platform is secure, user-friendly, and capable of handling growing traffic and transactions. It also
emphasizes system architecture, including web and database components, and provides detailed user
interface designs and acceptance criteria to ensure the platform meets the stakeholders' expectations.
This document serves as a guide for developers, testers, and project managers throughout the
development lifecycle, ensuring a successful, functional, and user-centric online chocolate store.

3.5. Overall Description:

3.5.1 Product Perspective:
The chocolate website will serve as an online platform for users to browse, select, and purchase
chocolates as per their requirements.

3.5.2 Product Functions:

 User registration and login
 Browsing and searching for items
  Viewing detailed product descriptions and images
 Adding items to cart and making purchases
 Reviewing and rating products.

3.5.3 User Classes and Characteristics:

• Guest: Unregistered users browsing the website
• Admin: Admin are the ones who administrators the vendors, view the booking details.
• Customer: The customer will be the one who visits the website and buy’s product form the website.

3.5.4 General Constraints:

• The key restriction here will be to verify the validity of the purchaser, which is not always feasible.
Security threats may be involved. The item designs and product can run on any platform that includes
a web browser that support PHP, Java Script.
• The main constraint here would be checking the genuineness of the buyer, which is not always
possible.
• There can be security risks involved.
• The developed system should run under any platform Unix, Linux, Mac, Windows etc…

3.5.5 Assumptions:
• Users have access to stable internet connections to browse and make purchases on the website.
• Users have basic computer literacy skills to navigate the website effectively.
• The availability and accuracy of product information depend on the vendors/sellers updating their
product listings.
• Users will primarily use conventional web browsers and devices to access the website.
The website's performance and security rely on the proper functioning of third-party services such as
payment gateways and shipping providers.

3.6 Specific Requirements:

3.6.1 External Interface Requirements:
 User Interfaces:
Each part of the user interface intends to be as user friendly as possible. The fonts and buttons used
will be intended to be very fast and easy to load on web pages. The pages will be kept light in space
so that it won't take a long time for the page to load.
 Hardware Interfaces:
RAM: 12GB
Processor: Intel i5
 Software Interfaces:
Operating System: Windows 11
Development tool: PHP, JavaScript, CSS
Database: MySQL

3.7 Functional Requirements:

Module 1(Customer):
1. User Registration:
Users should be able to register with a unique username and password.
2. Product Browsing:
Users should be able to browse products by category, price range, and other filters.
3. Cart Management:
Users should be able to add items to their cart, update quantities, and remove items.
4. Product Management:
Admins should be able to add, edit, and delete products from the catalogue.

3.7.1 Non-functional Requirements:

1. Performance:
The website should load quickly and handle a large number of simultaneous users.
2. Security:
User passwords should be securely hashed and stored.
Payment information should be encrypted during transmission.
3. Usability:
The UI should be easy to navigate.

3.8 Design constraints:

 There are few restrictions that the device has to meet. They are:
 Both inputs should be reviewed for validation and messages should be issued for erroneous
results. Invalid data should be skipped and error messages should be given.
 The information given during registration should be maintained in the database.
 When submitting product to the scheme, the mandatory fields must be reviewed for the
validity as to whether the provider has entered the necessary data in these mandatory fields. If
this is not the case, the right error message should be shown or the data should be stored in
the archive for the later retrieval.

3.9 Security constraint:

Securing a Chocolate website is crucial to protect user data, financial transactions, and the overall
integrity of the platform. Here are some security constraints that should be considered for a Chocolate
website:
• Logging and Monitoring
• Data Backups
• Data Encryption
Logging and Monitoring:
Constraint: Implement comprehensive logging and monitoring mechanisms to detect and respond to
suspicious activities.
Rationale: Monitoring helps identify and respond to security incidents promptly, minimizing potential
damage and improving incident response capabilities.
Data Backups:
Constraint: Regularly back up critical data and ensure the availability of a robust disaster recovery
plan.
Rationale: Data backups and a disaster recovery plan help in mitigating the impact of data loss due to
security incidents or system failures.