Capstone Project Retail Store
Capstone Project Retail Store
Overview:
Create an Online Retail Store that sells products from various sellers.
An Online Retail store sells products from various sellers to customers. Various sellers list their
products on this retail store with a name, photo, price and other details. The store filters and list
these products: category wise or seller wise. Customer can choose how they would like to view –
category wise or seller wise. Products may be sorted based on price.
Customers and add products to cart, update quan es when viewing the cart and purchase what’s in
cart to generate a order id(invoice id).
Admin can create categories, add sellers, add products under category and seller. Admin can also
view all customer details, their orders and order details.
Group Project: This is a group project. Choose your team of 3 or 4 members only.
Check points:
CHECK POINT 1(25-OCT-2024): Complete Front-end.
Product
Order
Seller
ProductCateogory
Features:
Customers should be able to Register and Login to see home page.
Home page lists products from various sellers. Include product image in display.
CUSTOMER PAGES:
Customer Profile Edit page.
ADMIN PAGES:
Admin can view/add/update/disable Sellers.
Admin can view daily/monthly seller wise and category wise sale summary.
Technologies:
React for Front-end.
REST API using Spring Boot, Hibernate, SpringMVC, Spring HATEOAS, Spring Security, for
Back-end.
MySQL for database.
Other Requirements:
Incorporate Logging and Excep on Handling.
Tables should also have Date Created, User Created, Date Modified, User Modified.
Image links should not be hard-coded. Those should come from database.
Tes ng:
Test your REST API using curl or postman.
Document Java code on top of Class and methods. Add inline documenta on where necessary.
Source Repository:
Maintain a source repository for your project in github.
One person in the team will create the repository and give permissions to others to collaborate.
Branches in repository:
Developer branch: where all team members submit code (stable code) by placing a pull
request to owner of repository. Owner to review source or assign a reviewer. If code review is
posi ve and there are no conflicts between different developers code, code may be merged to
developer branch. Upon tes ng developer branch code may be merged to master branch.
Member branch: Each Member, including repository owner will have a member branch to
work with. When the code is stable they me submit a merge request to Developer branch.
README.md file
This file should give an overview of project, list team members and contain the main screen shots of
the front-end, domain diagram, usecase diagram, database diagram for the project.