This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • PIM User Stories, Use Cases, and Test Cases

Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

Skip to end of metadata
Go to start of metadata
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

ActorCatalog Manager
DescriptionUser creating the catalog (associated with the product store) and updating its information.

Trigger

The Catalog Manager accesses the catalog.

Precondition

None.

Basic Path

  1. User selects 'Catalogs' menu item.

  2. Systemdisplays criteria for search and list of catalogs present in the system.
  3. User clicks on [New Prod Catalog] button.
  4. Systemdisplays a form to create the new catalog.
  5. Userenters the information and click on [Update] button.
  6. Systemsuccessfully creates a new catalog.
  7. Useragain selects 'Catalogs' menu item.

  8. User Clicks on any catalog Id.
  9. Systemdisplays edit product catalog page.
  10. User enters/updates the information and click on [Update] button.
  11. Systemsuccessfully updates the catalog.

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

ActorCatalog Manager
DescriptionA 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

  1. User selects 'Category' menu item.

  2. User clicks on [New Category] button.
  3. System displays create category page along with a form with text fields asking for category Id, category type, category name, description, primary parent category. None of thefieldis mandatory.
  4. Users enters the information and click on [Update] button.
  5. Systemsuccessfully createsnewcategory.
  6. User selects 'ROLL UP' tab.
  7. Systemdisplays the 'Category RollUp' page.
  8. User enters 'parent category' and click on [Add] button.
  9. Systemassociates the parent category with the current category.
  10. Userselects 'Products' tab.
  11. Systemdisplays 'Edit Category Products' page.
  12. User enters information under 'Add Product Category Member' section and click on [Add] button.
  13. Productgets successfully added undercategory.
Alternative PathAfter step 8,usercan also go for adding childcategory,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

ActorCatalog Manager
DescriptionUser 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

  1. User selects 'Categories' menu item.

  2. Systemdisplays a Categories page.
  3. User clicks on [Find] button.
  4. Systemdisplays default category list.
  5. User enters category Id or category name in the text field and clicks on [Find] button.
  6. Systemdisplays category list according to search criteria.
  7. User clicks on category Id.
  8. Systemdisplays a detailed view page ofcategory.
  9. User updates category information and clicks onUpdatebutton.
  10. Systemsuccessfully updates category information.

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

ActorCatalog Manager
DescriptionA user creates a new product into the system which hewantto sell. Forthathe 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 asprimarycategory to the product.

Basic Path

  1. User selects 'Products' menu item.

  2. User clicks on [New Product] button.
  3. The system displays a form with various product information fields. Internal name is mandatory field,  product Id is auto generated if not filled. There are other field primary category, introduction date, release date, inventory, rate, measures .

  4. Userenters the information and clicks on [Create] button.

  5. Systemsuccessfully creates the product.

Alternative Path 1

After step 3, ifuserenters product id ofa existingproduct in the system, then it displays a notification message to the user.

Alternative Path 2

In step 3, ifuserdoes 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

ActorCatalog Manager
DescriptionA user is finding the desired product in the system and updating its information.
XRef

Create Product

Trigger

The Catalog Manager accesses the catalog.

Precondition

Productexistin the system.

Basic Path

  1. User selects 'Products' menu item.

  2. System displays Find Product page.
  3. User clicks on [Find] button.
  4. Systemdisplays default product list.
  5. User enters product Id or internal name in the text field and clicks on [Find] button.
  6. Systemdisplays product list according to search criteria.
  7. Click on product Id.
  8. Systemdisplays edit product page.
  9. Update internal name, primary category, dates, inventory, rate, amount, measure and click on Update Product button.
  10. System updates the product successfully.

Alternative Path

In step 9, System displays an error message ifinternalname 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

ActorCatalog Manager
DescriptionA 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

  1. User selects 'Products' menu item.

  2. System displays Find Product page.

  3. User clicks on [Find] button.

  4. Systemdisplays default product list.

  5. User clicks on product-Id of product to be cloned.
  6. Systemdisplays edit product page with a section 'Duplicate Product'.
  7. User enters name, description of the product and select the attributes to becloned  andclick on [Duplicate] button.
  8. Duplicateproduct is created successfully.

Alternative Path

In step 3, ifuserdoes 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

ActorCatalog Manager
DescriptionA user uploading selected image ofproductwhich hewantto display for that product.

Trigger

The Catalog Manager accesses the catalog.

Precondition

At-least one product exists in the system.

Basic Path

  1. User selects 'Image Management' menu item.

  2. Userselects product-Id andclickon [Submit] button.

  3. Systemdisplays Gallery page which displays added images.

  4. User clicks on 'UPLOAD' tab.

  5. Systemdisplays a page to upload images.

  6. User browse for images in his local system and upload it on system by clicking on [Upload] button.
  7. Imageis uploaded successfully and will be displayed on the product page over store front.

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

ActorCatalog Manager
DescriptionA 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

  1. User selects 'Products' menu item.
  2. System displays Find Product page.
  3. User clicks on [Find] button.
  4. Systemdisplays default product list.
  5. User enters product Id or internal name in the text field and clicks on [Find] button.
  6. Systemdisplays product list according to search criteria.
  7. User clicks on any product Id.
  8. System displays 'Edit Product Page' for that particular product.
  9. User clicks on 'Inventory' section.
  10. Systemdisplays the fields for inventory information.
  11. User enters information and click on [Update Product] button.
  12. Inventory is updated successfully.

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

ActorCatalog Manager
DescriptionUser associating other products which hewantsell with that product.

Trigger

The Catalog Manager accesses the catalog.

Basic Path

  1. User selects 'Product' menu item.

  2. System displays Find Product page.

  3. User clicks on [Find] button.

  4. Systemdisplays default product list.

  5. User enters product Id or internal name in the text field and clicks on [Find] button.

  6. Systemdisplays product list according to search criteria.

  7. Click on any product Id.

  8. Systemdisplays edit product page.

  9. User clicks on 'Associations' tab.

  10. Systemdisplays edit product association page with association form.
  11. Userenters association type and other information andclickon [Create] button.
  12. Productgets successfully associated for that product.

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

ActorCatalog Manager
DescriptionA user has identified some items hewishto promote, so he will create a promotion with some terms and conditions.

Trigger

The Catalog Manager accesses the Catalog.

Precondition

None.

Basic Path

  1. User chooses the 'Promos' menu item.

  2. User clicks on [New Product Promo] button.

  3. Systemdisplays edit product promo page.

  4. User enter promo name(mandatory field), text limit per order, limit per customer, limit per promotion and click on [Update] button.
  5. The Promotion is successfully created with a unique promo id.
Alternative Path 1
In step 4, ifuserdoes not enter promo name thensystemdisplayserrormessage.

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

ActorCatalog Manager
DescriptionA 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

  1. User chooses the 'Promos' menu item. 

  2. System displays product promotions list with promoId, promo name, promo text and created date.
  3. User clicks on any promoId.
  4. Systemdisplays edit product promo page.
  5. User updates promo name, text,limitper code and other fields, and click on [Update] button.
  6. Promotion gets successfully updated.

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

ActorCatalog Manager
DescriptionCatalog manager creates 'Sale' for some specific items.

Trigger

The Catalog Manager accesses the catalog.

Precondition

Userwantto create a Price Rule.

Basic Path

  1. User selects 'Price Rule' menu item.
  2. System displays 'Add Price Rule' section with a name field and [Add] button.

  3. Userenters Name and clicks on[Add]button.

  4. Price rule is successfully created and user will be navigated to create Product Price Rule page.
  5. User add condition and actions to the price rule and click on [Add] button.
  6. Price Rule is successfully created with entered conditions and actions.

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

ActorCatalog Manager
DescriptionThe user identified desired sale and update the information and associated items in it.
XRefCreate Price Rule.

Trigger

The Catalog Manager accesses the catalog.

Precondition

None.

Basic Path

  1. User click on 'Price Rule' menu item.

  2. System displays a listwithall price rules.
  3. Click on [Edit] button.
  4. System displays edit product price rule page.
  5. User updates name, description, conditions, actions and click on [Update] button.
  6. Price rule gets successfully updated.

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 NameManage Product Reviews
ActorCatalog Manager
DescriptionUser manages and publishes the Reviews by updating their details and statuses.
TriggerUser manages reviews.
PreconditionThe Catalog Manager accesses the catalog.
Basic path
  1. User selects 'Reviews' menu item.
  2. System displays a Reviews page with search options and search results sections.

  3. User clicks on [Find] button.

  4. System displayed default reviews list.
  5. User selects 'Approved' status from status dropdown and clicks on [Find] button.
  6. System displays respective Reviews which has been approved. 
  7. User updates the ratings and comments for a review and clicks on [Update] button.
  8. Review gets successfully updated.
  9. User selects 'Pending' status from status dropdown and clicks on [Find] button.
  10. System displays respective Reviews which are pending.
  11. User updates ratings and comments for a review and clicks on [Update] button.
  12. Review gets successfully updated.
  13. Click on [Approve] button.
  14. The review gets approved successfully.
  15. Click on [Reject] button.
  16. The review is been rejected and status of that review becomes 'Deleted'.
  17. User selects 'Deleted' status from status drop-down and clicks on [Find] button.
  18. System displays respective Reviews which are deleted. 
  19. User clicks on product name link.
  20. The System displays the product overview page for the same product.
Post-conditioncatalog manager is able to manage the reviews.