JCart Requirements Analysis

Share this post:

For building our JCart e-commerce application we will develop two web applications, one for ShoppingCart and another one for Administration. Let us explore the requirements of both ShoppingCart and Administration websites in detail.

ShoppingCart Site Requirements

Home Page: This page shows list of categories and few products in each category. From this screen customers can click on any Category name to see all the products in that particular category or can add a product to cart.

Category Page: This page displays all the products in the selected category with pagination. Each product will be displayed along with a Add To Cart button.

Product Page: This page displays detailed information of the product along with one or more images of the product and shows Add To Cart button.

Search Results Page: In the header section we will provide a search box where customers can search for products. The search results will be displayed with pagination. Each product will be displayed along with a Add To Cart button.

Login/Registration Pages: Customers should be able to login/register with our system so that they can view their profile and order history.

Cart: In header section there will be Cart Icon showing the no. of items currently added to cart. When Cart icon is clicked we need to show the cart page with all the Items details. Customers should be able to update product quantities or remove products and the cart totals should be updated automatically.

Billing & Delivery Page: This page will be displayed once the customer clicked Checkout button in Cart page. If the customer is already registered with our system he should login otherwise a registration form will be displayed. Customer should register by providing Email and Password. After successfully login, customer should provide Delivery Address, Payment details like CreditCard number, CVV, Expiry Date etc.

Order Confirmation: Once the customer provided all the valid details and clicked on Submit button an Order should be placed and should display the Order Confirmation page with details including the Products, Delivery Address etc. An order confirmation email should be sent to customer with estimated delivery time.

My Account Page: Customer should be able to login into the system and see his profile details, order history, outstanding order details.

Administration Site Requirements

Security: We should provide Roles and Permission based security for our Administration website.

Privilege Management: Ability to configure and manage all the privileges within the system. Each privilege represent the ability to perform an action.

For ex: MANAGE_CATEGORIES represents the ability to create new Categories, update existing categories.

Role Management: Ability to create various roles with one or more assigned privileges.

For ex:

** ROLE_SUPER_ADMIN** – Users with this role can do anything within the system.

** ROLE_ADMIN** – Users with this role can create other users (except other SUPER_ADMIN or ADMIN), and can do Category Management, Product Management etc.

** ROLE_CMS_ADMIN**: Users with this role can manage Categories, Products etc.

Category Management: A category represent a logical grouping of related products.

Category management includes:

  • Create new categories
  • Update existing categories
  • Disable/enable categories

Product Management: In our system product is a quilling toy.

Product management includes

  • Create new products
  • Update existing products
  • Delete products

**Order Management:**Authorised users can see the list of order, update status or cancel orders.

If an order is cancelled then refund should be triggered and a cancellation email should be sent to customer.

Customer Management: Admin users should be able to view the customer details like their addresses, email ids etc for contacting them.

  • List all the customers
  • Search customers by email or name
  • View customer profile
  • Customer order history

Site Settings: We need to have some site level configurations like Currency and Locale.

**Locale & Currency:**We should be able to use different locale and currencies for our e-commerce system. So the implementation should consider the I18N and dynamic currency change using live currency converter or using some conversion ratio.

By looking at the above mentioned features you might be thinking these are all very basic features of any e-commerce system and lot of features like Promotions/Offers Management, Fulfilment Systems, Inventory management etc are not being considered. YES, you are right. We are not considering many aspects of a typical e-commerce system because WE DON’T NEED THEM FOR OUR APPLICATION.

As I mentioned in the project requirement, we are enabling customers to place orders through online and the items will be delivered manually by the person who makes those quilling toys and the administrator will mark that order as fulfilled. If our application become famous and we are being flooded with orders then we can think of automating these manual tasks as well. As simple as that :-).

Share this post:

Related content

comments powered by Disqus