In the field of products and technology, there is UML skill knowledge, and UML for product personnel is more about use case diagram, which is what I call user flow chart.

In fact, the user flow diagram is a structured way of expressing the use case diagram at the beginning of the product rule. As a structured way, the use case is too abstract and lacks logical expression, and the article prefers to the functional user flow. It is not the actual use case. Therefore, I will supplement a text today to elaborate on the UML use case diagram and use case document.

The use case document is a document composed of multiple use cases. It is mainly used for technology development and testing. It is an important auxiliary document in PRD. It is used to explain the functional logic of a link, such as user registration, activity registration and so on. All functions require auxiliary use cases.

The writing time of use case documents is usually synchronized with PRD documents after prototype design.

There are two cases in the use case document.

They are use case diagrams and flow charts.

The use case diagram is a class diagram representation of UML, which describes the function of the product from the user point of view, and points out the user's operation authority in every function of the product.

Flowchart is the process of describing product functions through the way of wire frame graphics, mainly describing the execution sequence, branch and circulation logic of functions.

write

The commonly used software is Word, and the production software of use case diagrams and flowcharts is usually Visio. Of course, it is also produced by Axure RP software. For example, the third step flowchart below is made by Axure RP.

A complete use case document is composed of the following three points, of which the third point "use case" is the part describing the functional logic, and determines the number of use cases according to the number of functions.

The approximate components are as follows:

1, modify the records: Notes for each modification, together with PRD documents.

2. Role description: describe the roles involved in the system.

3, use case: the fourth step of the next step, in which the flow chart in the third step is directly inserted into the flowchart table item of the fourth step.