Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Current »

1. Use case name (Required)

Record all POS transactions to Transaction report in Backend as it is for online order

2. Keywords (Required)

Transaction report, accounting

3. Actors + description (Required)

  • As an accountant, I would like to check all transactions in POS with different kinds of payment methods so I can easily track cash flow easily

4. Pre-conditions

Any states that the system must be in or condition that must be met before the use case is started.

5. Post-conditions

Any states that the system must be in or conditions that must be met after the use case is completed successfully. These will be met if the main flow or alternative is allowed. Some exceptions may result in failure to meet the Post-conditions.

6. Main flow (Required)

The most common path of interactions between the user & the system:

  1. User accesses Backend > Omnichannel Reports > Daily Transaction Report to open the report page. There will not be any report shown yet until the user click Show report.

  2. User select the one value in Date Filter and click Show report button.

  3. User can click into Transaction ID/ Order ID/ Order Type/ Staff/ Customer email/ Transaction amount/ POS Location to sort the value in acscending or descending order.

8. Fit & Gap analysis (Keep internal)

Compare this use case with the current Magestore solution to identify 3 types:

  • FIT 100%
  • Partially FIT + What is the GAP then?
  • GAP 100%
  • No labels