E-Commerce Website

For Shopping
SE PBL
SY-B.TECH
 2
Group details
NAME PRN ROLL NO
Gaurav Dusane 22211395 15

Aaryan Jadhav 22211206 22

Yash Jagadale 22210340 23

Nilay Nahar 22211078 32

 Table of contents

01 02 03
Introduction Requirements Activity diagram

04 05
Methodology used Sprint Schedule
Customer Problem Statement
01
Introduction
E-Commerce Website
For Shopping
 About Project
o An e-commerce website for shopping is an online platform that enables
businesses to sell products or services to customers over the internet. It serves
as a digital storefront where users can browse, select, and purchase items from
the comfort of their homes.
o Online platform for businesses to sell products/services.
o User-friendly interface with product listings and shopping cart.
o Secure checkout process for transactions.
o User accounts for personalized features and order tracking.
o Customer support and marketing tools for engagement.
02
Requirements
 Functional Statements:

1. User Registration and Authentication: Allow users to register for an account and log in
securely. Authenticate users' credentials during login to ensure secure access to account
features.
2. Product Management: Enable admin users to add, edit, and delete products from the
inventory. Each product should have essential information like name, description, price,
and stock quantity.
3. Shopping Cart and Checkout: Users should be able to add items to a shopping cart and
view the cart contents. Provide a checkout process with options for entering shipping
and billing information and completing the purchase.
4. Order Management: Users should receive confirmation emails after placing orders. Admins should
have access to manage orders, including status updates and cancellations.
Non-Functional Requirements:
1. Performance: The website should load quickly and respond promptly to user
interactions. It should be able to handle a large number of concurrent users
without experiencing significant performance degradation.
2. Reliability: The website should be highly available, with minimal downtime for
maintenance or unexpected failures. It should have backup and recovery
mechanisms in place to ensure data integrity and continuity of service.
3. Maintainability: The system should be well-documented and modularized to
facilitate future updates, enhancements, and bug fixes. It should use coding best
practices and design patterns to promote code reuse and maintainability.
4.Usability: The website should have a user-friendly interface that is intuitive and
easy to navigate.
User Requirements
Browsing and
Product Search
• Users should be able to browse
through product categories and
subcategories easily.
• The search functionality should
be intuitive and provide relevant
results based on user queries.
Product Information
and Reviews
• Product pages should
provide detailed
information including
images, descriptions,
specifications, and pricing.
• Users should be able to
view product reviews and
ratings to make informed
purchasing decisions
Order Management
and Tracking:
• Users should be able to track
the status of their orders,
including shipment tracking
information.
• They should have access to
order history and the ability
to view past purchases.
Use case
Diagram
ACTIVITY
DAIGRAM
04
Methodology Used
Spiral Agile.
Why Agile?
Ability To change Incremental Delivery

Agile allows frequent iterations and Agile promotes delivering working

feedback loops. This flexibility is software in small, manageable
valuable where requirements may evolve increments. Hence, we can prioritize and
as the system is developed. implement essential features first.

Early detection of issues Reduced Risk

Agile practices such as daily meetings By breaking down the project into smaller,
and frequent demonstrations enable early manageable tasks and delivering them
detection of issues or discrepancies. iteratively, Agile helps mitigate risks
associated with software development.
05
Sprint Schedule
Sprint Schedule (3 days per sprint)

Sprint 1 Sprint 2 Sprint 3

Define project scope Create basic UI, static product pages Make pages dynamic, add search
and requirements

Sprint 4 Sprint 5 Sprint 6

Build database, user Implement product management, Test thoroughly, optimize, deploy
authentication shopping cart
 UI Requirements:
1. The platform shall have a clean and intuitive design with a consistent
layout and navigation to make it easy for users to find what they need.
2.The platform shall have responsive design and be optimized for different
devices, such as desktops, tablets, and smartphones.

3.The platform shall have clear and prominent calls-to-action (CTAs) for
users to add products to their carts, proceed to checkout, and complete
their purchases.
Software Requirements Specifications
 SRS stands for Software Requirements Specification, which is a document that describes the features, functionalities,
and technical requirements of a software application. In the context of an e-commerce website, the SRS should cover
the following:
 1. Introduction: This section should provide an overview of the e-commerce website, its purpose, and the target
audience.
 2. Functional Requirements: This section should describe the features and functionalities of the e-commerce website,
such as product browsing, searching, ordering, payment, and shipping
 .3. Non-Functional Requirements: This section should cover the technical requirements of the e-commerce website,
such as performance, security, scalability, reliability, and usability.
 4. User Interfaces: This section should describe the user interface design of the e-commerce website, including
wireframes, mockups, and prototypes.
 5. System Architecture: This section should outline the technical architecture of the e-commerce website, including the
hardware and software components, network infrastructure, and database schema.
SRS
 6. Data Management: This section should describe the data storage and management requirements of the e-
commerce website, including the database schema, data migration, backup, and recovery.
 7. Integration and Interoperability: This section should describe how the e-commerce website integrates with other
systems, such as payment gateways, shipping carriers, and customer relationship management tools.
 8. Testing and Quality Assurance: This section should describe the testing and quality assurance processes that will
be used to ensure the quality and reliability of the e-commerce website.
 9. Deployment and Maintenance: This section should describe how the e-commerce website will be deployed and
maintained, including the deployment environment, release management, and maintenance activities.Overall, the
SRS should provide a comprehensive description of the e-commerce website, its features, functionalities, and
technical requirements, to guide the development team in building a high-quality and reliable system that meets the
needs of the target audience.
THANK YOU !
User story map
CLASS DAIGRAM
STATE DAIGRAM