rev-shop

E-commerce Application

Center of Excellence 28-March-2023.

Table of Contents

Requirements

•Overview
•Core Functional Scope
•Standard Functional Scope
•Non-functional Scope
•Non-functional Scope
•Definition of Done

Expectations

•Security Standards
•Nice-to-haves

Project Requirements

Overview

The RevShopproject aims to develop a secure, user-friendly, and versatile e-commerce application for both buyers and sellers. The core functionalities for buyers include browsing products, adding products to cart, checkout, and payment processing. Sellers can add products, manage inventory, and fulfill orders. The project's completion will be demonstrated through a cloud-hosted working version, technical presentation, and associated diagrams.

Core Functional Scope

Buyer user account:

As a buyer, I should be able to: •View product details including image,price, description,rating,anduser review.
•Browse products by categoryor keywords.
•Add or remove products fromthe cartand provide quantity.
•Checkout and enter shipping and billing information.
•Get email notifications when anorder isplaced.
•View order history.
•Rate and review products.
•Submit a complaint against the seller.
•Return a defective product.
•Save product as favorite.
•Generate invoice for the order.
•Make paymentusing the paymentgateway.

Retailer user account:

As a retailer, I should be able to:

•Register as a seller with email, password, and business details.
•Receive an email regarding registration status.
•Manage inventory and product details.
•Add new products with price and description.
•See placed orders.
•Receive email notifications when a user places anorder.
•Providediscounts.
•A graphical dashboard to analyze the product sales.
•Get a notificationwhen user submits a review and respond to it.
•Manage inventory with low stock alerts for sellers.

Adminuser account:

As an admin, I should be able to:

•View all users and retailers present on the platform.
•Manage users and retailers, including blocking and unblocking them.
•View complaints submitted by the user.
•View all the registration requestssubmittedby the sellers.

Standard Functional Scope

1.Buyer and retailer accounts should be able to:

•Access settings to change personal or business details.
•Login as a buyer or sellerusing email and password.
•Sign up as a user with email, password, and personaldetails.
•Logout fromthe application.
•Reset the password and request for a forgotten password to the email.
•Delete or temporarily disable the account.

2.Admin account should be able to: •Login/ Logout.
•Reset the password and request for a forgotten password to the email. Non-functional Scope•Responsive to all the devices •Supported by common browsers(Chrome, Edge, Firefox, Safari) •80% unit testing on API business logic (Service layer)•Scrum/Agile Development Strategy with Burndown charts•RESTful API implementation•API logging and exception handling•Comments in the code base with respective detailsDefinition of Done•Presentation of technical details of the application.•Sharing the associates’ code repo for technical evaluation with:oERD Diagram.oArchitecture Diagram.oActivity Diagram.ExpectationsSecurity Standards•Password Hashing implementation.•Session management.Nice-to-Have's•Save billing and shipping information for faster checkout.•Notify users ofupcoming offers.•Sellers can pay to advertise their product.•Show different product suggestions to buyers.•Navigational mock for first-time users.•Provide discount for specific payment option.•customer service forum.•Integration with social media platforms to share products and reviews.