In the project, we sometimes encounter such a scene: in the process of actually realizing the product on the customer's site, we find that some functions are not based on the product, so temporary design and development on the site will bring adverse effects to the project.

In order to reduce the occurrence of similar things in the future, this paper has compiled a series of lists as reference memos for product function demonstration.

First, check from the user's point of view.

-Why: Why does it have this function? Can you lead to other requirements?

-Who: Who are the users involved in the product/function? Take out the organization chart of the user's organization to see if it is missing.

What: What are the core demands of these users?

-When: when users use it, whether each user's operation is orderly, and whether these logics are restricted.

Encountered example: There are many functions designed for the customer's boss, and the customer's little soldier does not serve well. Or front-line operators have detailed functions, but they have not designed monitoring reports for upper-level leaders.

Second, check the data from the perspective of data.

Take out the data model of the product, and then check whether each data entity has considered the corresponding CRUD basic operation.

Common defects such as:

Missing query: A form has been added, but there is no query entry.

Omission: useless forms and data that cannot be deleted or deleted in batches.

Omission: Some data, especially dictionary configuration classes, cannot be maintained after online, so programmers have to add them in the background.

Insufficient update: especially in the update of some status fields, such as whether it is disabled or not, it must be enabled.

Third, check from the perspective of abnormality.

Take out the product's operation manual, and then suppose for each step of operation: how does the system exit/disconnect from the network during this step of operation, and can it continue after logging in again?

Common examples:

1. Design a simple process of saving, submitting and approving. When checking, it should be assumed that there is no place to resubmit after saving, log out of the system and log in again.

2. Add a new form according to the wizard. The last step of the form has a print operation. If the system exits before the last step of printing, can I switch to printing again? If you still need to browse the wizard again before printing, the display is inappropriate.