Feature Pack 4 or later

Smart phone and tablet starter stores use cases

During a customization project, you must perform architectural design even when you use a WebSphere Commerce starter store. To reduce the time required to document use cases for your store, a modifiable use case document is provided that clearly describes the functionality provided with a starter store.

Smart phone and tablet starter stores use cases apply to the following storefronts:
  • Feature Pack 5Feature Pack 4Madisons
  • Feature Pack 6 or laterAurora

To modify the smart phone and tablet starter stores use cases to reflect changes that you want to make to the store, download and extract the appropriate version of the file. For more information, see Downloading the IBM WebSphere Commerce Starter Store Companion Assets package.

The file contains use case documents for the following platforms:
Feature Pack 4 or laterMobile Web for smart phone devices
Feature Pack 4 or laterUse-cases that are accessed using a smart phone's Web browser, including location-based services.
Feature Pack 5Feature Pack 4Mobile Web for tablet devices
Feature Pack 5Feature Pack 4 Use-cases that are accessed using a tablet's Web browser, including location-based services.

Feature Pack 6 or laterThe Aurora starter store is the default storefront for tablet devices.

Feature Pack 4 or laterHybrid application for smart phone devices
Feature Pack 4 or laterUse-cases that are accessed using an application installed on smart phones, including location-based services and device-specific functions.

Feature Pack 5Feature Pack 4This document contains use cases for Android and iPhone.

Feature Pack 6 or laterThis document contains use cases for Android only.

Feature Pack 5Feature Pack 4Hybrid application for tablet devices (iPad)
Feature Pack 5Feature Pack 4Use-cases that are accessed using an application installed on tablets, including location-based services and device-specific functions.
Feature Pack 5Feature Pack 4Native application for smart phone devices (Android)
Feature Pack 5Feature Pack 4Use-cases that are accessed using an application installed on Android smart phones, including location-based services and device-specific functions using REST services.

Example of customizing use case documentation

The following example shows an update to the Madisons use case document to include use cases for the features added in the Tutorial: Adding support for a Management Center tool to the Madisons starter store tutorial.
The customization adds two use cases:
  • Use Case: Shopper views a product's recipes (313)
  • Use Case: Shopper browses to find a recipe (314)
It also adds an alternate flow to an existing use case:
  • Use Case: Shopper adds an item to the Shopping Cart (1101)Alternate Flow I: Shopper adds one or more items to shopping cart from Recipe Details page.