POS Refinement Iteration II Development documentation

One, use case model

1, System use case diagram

2, open single case analysis

Use case Name: Sales Open order

Main players: Cashier

Main success Scenarios:

(1), the cashier starts a new sale

(2), the cashier enters the product item in turn, selects the quantity (default 1)

(3), the total amount of the system with the entry of the product constantly refreshed

(4), cashier input completed, confirm checkout

(5), the system creates the transaction information table, and automatically records the transaction time, waits for the customer to pay

Extended:

2a. The cashier enters the wrong product or the customer does not need a product

1. Competent or high-authority personnel landing System

2. The supervisor or the High Authority person deletes this item entry information

3. The supervisor or the high-authority person exits the system

4. System display back to sales screen

5. Cashier to enter the next item

2-5a. Cancellation of Transaction by customer

1. Competent or high-authority personnel landing System

2. The supervisor or the High authority person cancels the transaction, deletes the transaction information form

3. The supervisor or the high-privileged person exits the account

4. The system resumes its initial sales status and waits for a new transaction

2-5b. Customer request to cancel a product

1. Competent or high-authority personnel landing System

2. The supervisor or the High Authority person deletes this item entry information

3. The supervisor or the high-authority person exits the system

4. The system deletes the transaction information table and re-executes step 6

5a. Customer Request Pending Order

1. Cashier Select Pending Order options

2. System Save Transaction Information table

3. System Recovery to step 1

Two, Supplemental Specifications

Brief introduction

This supplemental protocol lists the system requirements that are not readily available in use cases. The supplemental protocols and use-case models document a complete set of requirements for the system.

This document is not a final draft and will be continuously optimized as the project advances.

Functional performance

1. User unit Query.

According to the business code of Inquiry Business processing basic information and processing progress.

2. Process Control.

Administrators can query the existing process definitions and deploy new processes.

3. Equipment Import management staff can execute a process to create a new process instance.

4. Equipment import Management and foreign trade company staff can take specific tasks to carry out the work.

Feasibility

The desktop user interface should be compatible with Windows 2000, XP, Win7.

Reliability

The system should be available 24 hours a day, 7 days a week.

The downtime should be less than 10%.

System restart time is less than 1 minutes.

Performance

1. The system will be able to provide access to the database within 10 seconds.

2. The system must be able to complete 80% of all transactions within 2 minutes.

can support

Extensible support for peripheral devices such as barcode scanners.

Security

The system must be able to prevent unauthorized users from performing non-authoritative operations.

Design constraints

The system must provide a Windows desktop-based interface.

The key font should be visible one meter away (for example, the total amount), avoiding long periods of time and visual fatigue for the cashier.

There are keyboard shortcuts that make it easier for cashiers to work more efficiently.

Interface design, should be simple and easy to understand, color should not be too much, to avoid the cashier long time and visual fatigue.

PS: input design See next Blog ~ Thank you ~

POS Refinement Iteration II Development documentation