SW System Components of e-Commerce Sites

1. Inventory Management System

   Stores info about products and services you are selling

• Name of Products/Services
• Description of Product/Services
• Price
• Quantity in Stock/Availability
• Quantity sold till Date

Implementation Idea Database + Servlet that pulls data and builds web-page based on products available or requested

>Provide links to product information dynamically constructed >Send warnings that quantities are reaching low levels for re-ordering >Provide ability to search using keywords store in database describing products >Categorize products for ease in browsing dynamically built product pages.

Database Tables: Products- id, category(s) ids, name, description, price, display price, quantity in stock, danger-stock-level, search-keywords, email-report-problems, modified by, modifcation date Categories- id, category id, sub-categories list, name, description, search-keywords, modified by, modification date Product to Categories - product id, category id. optional, can make searching more efficient than having list of categories in products table.

 

 

2. Profile Management System

Stores info about customers. Typically consist of

• Registration System

  Allows personalization of pages. Ease of future shopping. Can use for front end into tracking of past and current orders. May hold following:

  • Name
  • Login&Password
  • Contact Info (Address-billing&shipping, phone, fax, email)
  • Payment Info (credit card)
  • Orders List - this is a pointer to another data set containing info about orders customer has placed so far.

• Update Profile System

user can update profile as required

Implementation Idea Database +Servlet that pulls data and builds web-page based on products available or requested

Database Tables: Profiles: id, username, password, registration date, first name, last name, phone, fax, email, credit card #, credit card exp. date, credit card type, status Addresses: id, profile_id, type(shipping or mailing), line1, line2, city, state, zip, country

3. Ordering Management System

Front and backend that the customers use to place orders or buy products/services. Linked to Inventory Management System to determine if product/services are available. Recall that the Profile Managment System pointed to an Orders List. An Orders List would be a grouping of orders and could be maintained here. Each order may contain the following information.

• Order Identifier - often a unique number used for tracking
• Customer ID - a pointer to the customer profile making this order.
• Products ordered
• Price for each product
• quantities
• total amount billed
• date order was placed
• date order was shipped
• status of order

Implementation Idea Shopping Cart Model....Database+Servlet to maintain persistent dat.

Database Tables: orders: id, profile id, date ordered, date shipped, shipment method, status, payment recieved, total billed order item: id, order id, product id, quantity, order price for regular customers could develop 3. regular-shop: id, profile id, product id, quantity.

4. Shipping Management System

Stores more detailed information about the shipping and related status of each order. Each shipment may contain the following

• Customer ID
• Order ID
• Detailed Shipping Status - this can include ids for sub-contractor systems, etc.

5. Reporting System

This system uses all of the previous system's data to assemble reports as needed for business development. Some common items that are tracked (there are many more):

• Total Sales in a Given Period
• Sales Information per product or category
• Regional sales Information, or by other demographics
• Delivery Time tracking

   

 

Implementation Idea Database +Servlet that pulls data and builds web-page based on products available or requested