There is a famous saying from the media industry that I don’t know who said it: Users can’t read text if they have pictures, and they can’t read pictures if they have videos. Although this reflects some impetuousness of modern people, it also shows from the side that in terms of communication efficiency, video is better than pictures, and pictures are better than words. But usually everyone complains that the predecessors did not leave the documents, and they did not write the documents. Using video to record documents is too costly to produce, and using words to record documents is not seen by anyone, so it is more economical to use diagrams to describe documents.
No one looks at the flow chart that has been drawn, mostly because people who read it can’t understand it. This is like passing the ball in a basketball game. Most of the responsibility for passing errors is caused by the passer’s irregular movements. The same is true for the document. People who read it cannot understand it. Mostly, the author of the document describes the problem unclearly. So we need a set of standardized definitions for flowcharts.
- Rounded rectangles indicate the beginning or end of the program
under what circumstances need to draw a flow chart
If there is only one step in the business process for approval, then there is no need to draw a flow chart. After all, the process is simple to look at the code. It doesn’t take much time. For approvals greater than one step, a flow chart must be drawn.
Precautions for drawing flowcharts
- Be sure to indicate the process of operating data on the line with arrows, such as “review pass”.
- Do not cross the lines.
- Don’t use one arrow for multiple lines.
- The flowchart must have a rounded rectangular box at the beginning and end, so that readers can see the whole data at first glance. This is also the rule of doing things, there is a beginning and an end.
I remember my junior high school math teacher talked about the drawing method of the coordinate system. He said that when drawing the coordinate system, you must write x, y and 0. If anyone only drew a cross, even No points will be awarded if the title is correct.
- The “beginning” of the flowchart should be drawn on the top, the “end” should be drawn on the bottom, and the normal data flow should be top-down, such as “approved”, abnormal The data flow can be bottom-up, such as “audit rejection”. Because people’s subconscious minds are all top-down, and they all hope to get a positive answer. So please follow the human subconscious mind to describe the needs.
- The flowchart can have multiple ends, but only one beginning.
- The flow chart is displayed on one screen as much as possible, or it can be printed on a piece of A4 paper. If there is too much content in one picture, it is recommended to split it into multiple flow charts.
Flowchart tool
- Visio, produced by Microsoft, only for windows.
- wps, can export jpg, png and other image formats, export svg, pos format requires member recharge.
- www.processon.com browser online editing, you can export image format and svg, pos format files, but the free mode can only create up to 9 flowcharts.
- Gliffy Diagrams Google browser plug-in, can only export image formats and self-developed gliffy files.
Note: svg and pos files are common format files for flowcharts
Drawing flowcharts What’s the use?
- Flowcharts are a powerful tool for communication. There is no need to waste too much tongue to explain things that can be explained by a picture on Dingding.
- The flow chart is a powerful tool for resignation and handover. With the flow chart, you can avoid the colleague who took over from the previous company from chasing down your home.
- The flowchart is also a powerful tool for demand changes. If the product manager wants to change the requirements, he only needs to see which rectangles are changed on the flowchart to know which pages need to be changed for this change; which lines on the flowchart are changed, and he knows the code logic of which buttons to change this time.
- The flowchart is the requirement. Because of the current needs, both you and God understand the details. After 2 months, only God can understand the details. For the functions I developed, newcomers in the future or people in other departments have doubts about this. They can only ask me if they don’t understand the functions developed by themselves, then tm will be embarrassed.
Written in the last
The university’s software engineering teacher said that as long as the requirements document is determined, everyone’s work needs to be written down. After work, I always think this is a joke of theory divorced from practice. .Until I studied the flow chart in depth, I found that the flow chart corresponds to the code. The diamond has several downward-pointing arrows, so the page has several corresponding buttons (or radio buttons).
written in the last two
If the product does not draw a flow chart, we will draw it technically. After colliding with the product manager, we must finalize a final version of the flow chart Used for development coding, because no one will read the lengthy text version of the requirements. Finally, I posted a flowchart drawn by Yogurt Papa before, which is stinking.
