Concept stage: Use case documentation
WebSphere Commerce includes a set of modifiable use case documents that describe the functionality provided with the Aurora, Madisons, Elite, and MayUJoy starter stores.
Navigate the tabs below to find modifiable documentation templates and reference applications that you can use to accelerate project progress and reduce costs for every phase of a WebSphere Commerce project.
| Concept stage: Static HTML starter stores | Design stage | Implementation stage | Testing stage | Launch stage | Maintenance stage |
 |
|||||
Introduction
The starter store use case documents describe the starter store functionality. Each use case corresponds to a task that a shopper can accomplish using a store. The use cases list main, alternate, and exception flows for each use case and also include flow diagrams for each section. The use case documentation was created using Microsoft Word and Visio.
Since enhancements can be applied to
the Madisons and Elite starter stores, and social commerce can be
applied to the Madisons starter store, additional use case documents
are provided to include enhancement and social commerce functionality.
Best practices
- Use the use cases to gain an understanding of the default store functionality, and to identify any potential gaps in functionality that you may need to customize.
- Section 1 contains tips on how to customize the use case document and how to update the document's table of contents when you add, edit, or remove use cases from the original set.
- Each use case document includes a blank use case template that you can copy and paste for consistency.
- In certain starter store use case documents,
some use cases were renumbered to make them consistent across the
starter store document set. If you are using a previous version of
the use cases, you may need to update the use case numbers.
- Adding new use cases: To not clash with the WebSphere Commerce documents, begin numbering any new use cases you add at 5001.
See