Table of Contents |
---|
User Story 1: Create/Edit Catalog
User creates the catalog which will be associated to the product store. User can also Edit the catalog with catalog Id and update the information.
Use Case:
Use Case Name | Create/Edit Catalog |
Actor | Catalog Manager |
Description | User creating the catalog (associated with the product store) and updating its information. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | None. |
Basic Path |
|
Post-condition | User is able to Create/Edit catalog. |
User Story 2: Create/Build Category Hierarchy
User creates new category/categories in the system. There can be multiple levels of category hierarchy in the system. User can associate/dissociate the next level (child) categories with the category. User can also update the name of the category, the changes will be reflected throughout ERP instantly.
Apart from it, User associates product with the category and user can also copy the products to another category.
Use Case:
Use Case Name | Create/Build Category Hierarchy |
Actor | Catalog Manager |
Description | A user creates a new category in the system and associates/dissociates other categories and products with it. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | None. |
Basic Path |
|
Alternative Path | After step 8, user can also go for adding child category, and then add the products into it. |
Post-condition | User is able to Create/Build category hierarchy. |
User Story 3: Find/Update Category
User finds the category by entering the category name or Id. User manages category(ies) with updating the category information. User can associate or dissociate sub(child) categories to the category (if it is not leaf category). If the category is the leaf category in the hierarchy then user should be associate products(standard or virtual) as its category member.
Use Case:
Use Case Name | Find/Update Category |
Actor | Catalog Manager |
Description | User finding the desired category and updating its information with various different category association and dissociation. |
XRef | Create/Build Category Hierarchy. |
Trigger | The catalog Manager accesses the catalog. |
Precondition | Parent or root category exist in the system. |
Basic Path |
|
Post-condition | User is able to find and update the category. |
User Story 4: Create Product
User creates new product in the system by entering various product details like Product ID(should be unique, also it is auto generated if no value is entered), Product Name(Mandatory), Price(user also selects currency), Manufacturer #, Product Category(should have auto-completer for selecting) and product features. User can also associate cross sell or up sell products with the product.
Use Case:
Use Case Name | Create Product |
Actor | Catalog Manager |
Description | A user creates a new product into the system which he want to sell. For that he adds the product details and features he also links the product with others. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | At-least one category exists which can be linked as primary category to the product. |
Basic Path |
|
Alternative Path 1 | After step 3, if user enters product id of a existing product in the system, then it displays a notification message to the user. |
Alternative Path 2 | In step 3, if user does not enter any information in mandatory field(s), then system displays validation message. |
Post-condition | User is able to create the product in the system. |
User Story 5: Find/Update/Manage Product
User searches product either through product name or Id. Search result contains product Id with some information about it. User visits product overview page for a particular product which contains, details of product such as product-Id, product name, inventory etc. User can edit these details and update it.
Use Case:
Use Case Name | Find/Update/Manage Product |
Actor | Catalog Manager |
Description | A user is finding the desired product in the system and updating its information. |
XRef | Create Product |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | Product exist in the system. |
Basic Path |
|
Alternative Path | In step 9, System displays an error message if internal name is left blank. |
Post-condition | User is able to find and update the product in the system. |
User Story 6: Duplicate Product
User creates a duplicate (copy) of existing product. System should be flexible enough to select the features of the product. It is not mandatory that system would select all the features from existing product, rather it would depend on user to select attributes for product to be cloned. Cloning of product will reduce the overheads of the user.
Use Case:
Use Case Name | Duplicate Product |
Actor | Catalog Manager |
Description | A user creating a duplicate of a particular product with selective features. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | At-least one product exists which can be cloned. |
Basic Path |
|
Alternative Path | In step 3, if user does not enter any information in mandatory field(s), then system displays validation message. |
Post-condition | User is able to create the duplicate product in the system. |
User Story 7: Product image management
User can upload the images for product which are available for adding. User can upload the image every time from his/her local system. User can also choose the size from already uploaded images which he/she want to display over store front. User chooses the format (.jpg/.gif) for the image to be displayed.
Use Case:
Use Case Name | Product image management |
Actor | Catalog Manager |
Description | A user uploading selected image of product which he want to display for that product. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | At-least one product exists in the system. |
Basic Path |
|
Post-condition | User is able to manage images in the system. |
User Story 8: Product inventory management
User visits details of product inventory, with product info. The product information includes its all facilities, ATP, QOH, suppliers and outgoing purchase orders. User can navigate to inventory item page for that product.
Use Case:
Use Case Name | Product inventory management |
Actor | Catalog Manager |
Description | A user viewing the inventory and its details for a particular product. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | At-least one product exists in the system. |
Basic Path |
|
Post-condition | User is able to manage inventory in the system. |
User Story 9: Create/Update/Remove cross-sell/up-sell products
On the Product Association page user can create cross sell/up sell products with respect to that product. User can also edit and remove those associated products.
Use Case:
Use Case Name | Create/Update/Remove cross-sell/up-sell products |
Actor | Catalog Manager |
Description | User associating other products which he want sell with that product. |
Trigger | The Catalog Manager accesses the catalog. |
Basic Path |
|
Post-condition | User is able to Create/Update/Remove cross-sell/up-sell products in the system. |
User Story 10: Create Promotion
User creates new promotion in the system. The user should enter the basic information while creating the promotion such as Name(Mandatory), Promo Text, Date Range(validity duration), Promo Show To Customer flag(default yes) and User Limit Per Order flag. Promo rules for customer can be created for many conditions. For example, promo rule for cart sub total can be applied on order's sub total for customer. The benefits of the promotion can be percentage discount, flat discount, a free gift product or free shipping for different shipping methods. When the promotion is created product wise, the user can decide on the eligibility criteria as order excluding or including particular product(s) and/or category(ies). The benefits of the product wise promotion can be percentage discount or a free gift product. Only one benefit can be associated per promotion at a time.
Use Case:
Use Case Name | Create Promotion |
Actor | Catalog Manager |
Description | A user has identified some items he wish to promote, so he will create a promotion with some terms and conditions. |
Trigger | The Catalog Manager accesses the Catalog. |
Precondition | None. |
Basic Path |
|
Alternative Path 1 | In step 4, if user does not enter promo name then system displays error message. |
Post-condition | User is able to create the promotion. |
User Story 11: Find/Update Promotion
User can find the desired promotion on Product Promotion page which are available with created date. User can go to the Edit promotion page from Promotions screen.
User can edit/update the promotion. User can update the name, promo text, extend the duration and change promo show to customer flag. When the promotion is to be used in future then user should be able to edit all the attributes/characteristics of the promotion which will include applied promo rules like criteria, qualifying cart range and benefit criteria value.
Use Case:
Use Case Name | Find Promotion |
Actor | Catalog Manager |
Description | A user is finding the desired promotion he wants to update, so he will update the information and conditions for that promotions. |
XRef | Create Promotion |
Trigger | The Catalog Manager accesses the Catalog. |
Precondition | Promotion exist in the system. |
Basic Path |
|
Post-condition | User is able to find and update the promotions in the system. |
User Story 12: Create Price Rule (Sale)
User creates new Price Rule(Sale) in the system. The user should enter the basic information while creating the sale such as Name(Mandatory), Activation Period(validity duration) and Sale Rule flag(default yes). User enters the conditions for rule i.e. product and category list on which rule will be applicable. User can add one or more conditions for the rule(sale). After that, User enters the actions to be performed on that conditions. The benefits or impact of the sale can be percentage discount or flat selling price. One or more benefits (actions) can be associated per sale at a time. If sale exists in system then only 'sale!' will be displayed on store front and product(s) will appear in that sale.
Use Case:
Use Case Name | Create Price Rule |
Actor | Catalog Manager |
Description | Catalog manager creates 'Sale' for some specific items. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | User want to create a Price Rule. |
Basic Path |
|
Alternative Path 1 | In step 3, if user does not enter the name then system will show an error message for the missing value. |
Post-condition | Price Rule is created in the system. |
User Story 13: Find/Update Price Rule (Sale)
User goes to price rule menu and finds all the price rules available in the system be it active or expired. User can edit/update the rule(sale) and also extend duration of sale. User Adds/Updates/Deletes the conditions for the Sale. User also Adds/Updates from overridden price to percentage discount and vice versa. Also the product and/or categories can be removed and added for the respective sale.
Use Case:
Use Case Name | Find/Update Price Rule |
Actor | Catalog Manager |
Description | The user identified desired sale and update the information and associated items in it. |
XRef | Create Price Rule. |
Trigger | The Catalog Manager accesses the catalog. |
Precondition | None. |
Basic Path |
|
Post-condition | User is able to Find/Update price rule. |
User Story 14: Manage Product Reviews
User searches reviews either through productId, status or content of the review. Search result will be displayed according to searched criteria. table contains productId, Status, Customer name, product rating, review comment. User can update review rating and comments. User can approve or reject the review.
Use Case:
Use Case Name | Manage Product Reviews |
Actor | Catalog Manager |
Description | User manages and publishes the Reviews by updating their details and statuses. |
Trigger | User manages reviews. |
Precondition | The Catalog Manager accesses the catalog. |
Basic path |
|
Post-condition | catalog manager is able to manage the reviews. |